DriverPacks.net Forum - RIS input

Re: RIS input

null@example.com (OverFlow) — Sat, 14 Mar 2009 23:40:05 +0000

I agree... RogueSpear is a hero. We will miss him greatly.
I really love the Tab for driverpacks with all the selections on one page.
Code... did somebody say code... hmmm

Re: RIS input

null@example.com (danny) — Sat, 14 Mar 2009 15:55:37 +0000

I know he stopped it, but so faar it still works for integrating driverpacks from this site into ris images.
Using just DP_Base for that somehow makes the instalation halt before its even started (if you integrate text mode storage drivers only though)
So for me it was still a great tool

Re: RIS input

null@example.com (mr_smartepants) — Sat, 14 Mar 2009 14:30:30 +0000

RogueSpear has ceased development of AutoImage.
He's jumping the M$ ship and moving to Linux. I saw this coming a while ago and I hardly blame him.
It's possible he'll release the source code and some enterprising soul will pick up where he left off.

Re: RIS input

null@example.com (danny) — Sat, 14 Mar 2009 14:16:41 +0000

RougeSpear's autoimage works fine you just have to set it to RIS image mode.
You wont get problems about drivers and bootdisks if you just use PXE boot, tftpd will serve anything the instalation need directly from the RIS image.

Re: RIS input

null@example.com (OverFlow) — Wed, 25 Feb 2009 22:15:07 +0000

the error is windows not DriverPacks... the driver does not support your OS... seems like it is what it says it is...

Re: RIS input

null@example.com (Temmu) — Wed, 25 Feb 2009 20:45:55 +0000

hello,

any luck with RIS yet?

i did this: http://forum.driverpacks.net/viewtopic.php?id=1262

into which i placed 1 and only 1 lan driver folder. B1
there was nothing in the DriverPack_LAN_wnt5_x86-32.ini
to delete.
i 7z-ipped the file and called it DP_LAN_wnt5_x86-32_8122.7z
which netted me a "where did you get that" on the automatic update portion of running base.

i selected disk
and browsed to E:\RemoteInstall\Setup\English\Images\XP-SP3-Apps\i386\Mirror1\UserData\WINDOWS
which is a folder on the RIS machine's remoteinstall share.
i also tried the system32 folder below windows and the i386 folder above windows. (see path above.)

that got me a "not developed for this operating system" error.

here's the log file

2009-02-25 14:31:01 : DriverPacks BASE 8.12.4 initialized.
2009-02-25 14:31:01 : Host environment: WIN_2003 Service Pack 1 on X86 CPU.
2009-02-25 14:31:01 : Created temporary working directory.
2009-02-25 14:31:01 : Imported proxy settings from Internet Explorer.
2009-02-25 14:31:01 : Start scanning for DriverPacks for the wnt5_x86-32 platform.
2009-02-25 14:31:01 : Detected DriverPack LAN 8122!
2009-02-25 14:31:01 : Could not detect any 3rd party DriverPacks for wnt5_x86-32.
2009-02-25 14:31:01 : Finished scanning.
2009-02-25 14:31:01 : Detected settings file "E:\DriverPack\DPs_BASE.ini".
2009-02-25 14:31:01 : No OS could be detected.
2009-02-25 14:31:01 : Imported settings from settings file.
2009-02-25 14:31:01 : [Settings]\DPsMethod not specified: default (2) was set.
2009-02-25 14:31:01 : [Settings]\finisherMethod not specified: default (GUIRunOnce) was set.
2009-02-25 14:31:01 : [OptionalSettings]\KTD not specified: default (none) was set.
2009-02-25 14:31:01 : [OptionalSettings]\QSC not specified: default (yes) was set.
2009-02-25 14:31:01 : [OptionalSettingsOther]\ATI_cpl not specified: default (None) was set.
2009-02-25 14:31:01 : [OptionalSettingsOther]\Nvidia_cpl not specified: default (None) was set.
2009-02-25 14:31:01 : QuickStream Cache directory not found!
2009-02-25 14:31:01 : Initialized GUI.
2009-02-25 14:31:01 : Created a list of all available language files.
2009-02-25 14:31:01 : Set the last used language, English, as the GUI language.
2009-02-25 14:31:06 : Refreshed UpdateChecker with success.
2009-02-25 14:32:06 : Changed Windows installation files OR export (depending on the installation platform) location to E:\RemoteInstall\Setup\English\Images\XP-SP3-Apps\i386\Mirror1\UserData\WINDOWS\system32.
2009-02-25 14:32:06 : No OS could be detected.
2009-02-25 14:32:09 : Saved settings!
2009-02-25 14:32:09 : Closed GUI.
2009-02-25 14:32:09 : There are not yet any slipstream modules available for the selected platform!
2009-02-25 14:32:14 : Temporary working directory successfully deleted.
- = DriverPacks BASE ini settings used = -
[General]
; preferred language
prefLang = "English"
; yes/no, enable or disable the wizard-style buttons, if not specified: yes
wizardButtons = "yes"
; yes/no, enable or disable the GUI, if not specified: yes
GUI = "yes"

[Settings]
; disc/bartpe/multibootDisc
instPlatform = "disc"
; trailing backslash is allowed, but not necessary
location = "E:\RemoteInstall\Setup\English\Images\XP-SP3-Apps\i386\Mirror1\UserData\WINDOWS\system32"
2009-02-25 14:32:14 : Create a DPs_Base.log backup @ E:\DriverPack\LogFiles\DPs_BASE_09-02-25_14-32.log
2009-02-25 14:32:14 : Program terminated.

Re: RIS input

null@example.com (OverFlow) — Fri, 14 Dec 2007 21:36:49 +0000

RougeSpear is an awesome individual and im sure if his app didn't work he'll be glad to help as well.
He was on the main testing team here before we went open source and still drops in on us.

Re: RIS input

null@example.com (savage1) — Fri, 14 Dec 2007 21:22:17 +0000

I apologize for the other post, i thought i may need to clarify what i was wanting to know. I have installed windows deployment services on one of my 2003 servers and i am going to start breaking that. hehehe

anyway I believe i have tried rogue spears solution as well with no luck, anyway this is a great forumn and you guys are great for helping out.

Re: RIS input

null@example.com (twig123) — Fri, 14 Dec 2007 16:08:43 +0000

I'm testing some LAN installs via PXE Network share instead of RIS... maybe this will help me in my endeavors... I will take a look

Re: RIS input

null@example.com (OverFlow) — Fri, 14 Dec 2007 08:48:52 +0000

RogueSpear's autoimage will do this for you. watch in awe.
No need to reinvent the wheel.

Link to autoimage

Duplicate post deleted

Re: RIS input

null@example.com (TigerC10) — Thu, 13 Dec 2007 22:08:10 +0000

RIS installs are not officially supported by DriverPacks. However, one issue that MANY people have with RIS installations is that they don't setup the network share to be exactly like a CD.

http://forum.driverpacks.net/viewtopic. … 405#p15405

Another thing that you might consider is that in many RIS situations you have to slipstream drivers for CPU and Network cards on your bootdisk (since you have to have a boot disk to even initiate the RIS to begin with).

People have done it, but the I386 folder locations have thrown them for a loop so be careful. As I understand it, you have to basically treat the RIS image location just like a CD. That is, you have to put the OEM folder that gets added as part of the slipstream process next to the i386 directory in the RIS.

You should be able to do a forum search for RIS and find some more helpful topics.

EDIT:
I did a quick search and found out you had already asked about RIS...

You should avoid creating new threads for the same thing.

RIS input

null@example.com (savage1) — Thu, 13 Dec 2007 21:18:49 +0000

Greetings All,

I have been trying to implent RIS for about 3 weeks now and when I first found out about this awesome site on msfn i was like sweet.

I basically want to know can I slipstream a RIS image with the driver packs that are offered on this site with my images. It would be a god send to be able to do this as when i first started out this was a sound idea. Now the only way I have been able to get drivers to install is with the microsoft preferred way of adding OEM drivers, which sucks digging through all the install files to find the inf's or anything that looks close to be able to install.

As i mentioned earlier i had envisioned that i would be able to slipstream a cd using this tool along with ryanvm and then compile a dvd that i would then copy to my RIS server as an image. I would then associate the appropriate .sif file with the image and sit back and watch it in awe.

Now if I am totally off the preservation on this idea would any one be willing to point me in the right direction of a less time consuming way of getting OEM drivers that will work for ALL pc's or at least the ones in my arsenal with RIS.