Topic: Unattended (network) install - using method 2

I currently use a customised boot image, which eventually runs winnt.exe from a network share. The OEMPnpDriversPath in unattened.txt has almost reached the maximum character limit (http://support.microsoft.com/kb/312535), that is starting to hamper the addition of new drivers to the install.

I have been reading up on driverpacks.net of using the slipstreamer to produce method 1 or 2. However I have a few questions which despite being covered in some posts seem to have no definite answer.

1) Using driver packs base and incorporating all driver packs available and then using method 2 - I don't see "MassStorage Drivers" or "OEMBootfiles" being added to winnt.sif. I can only see:

[GUIRunOnce]
    command9="%SystemDrive%\DPsFnshr.exe"

DriverPack MassStorgae text mode was selected. Have I done something wrong or is there something I am not understanding correctly?


2) Using method 2 - "presetup.cmd" refers to Finding CD/DVD driveletter. How does one get around using cd/dvd drive's then not using a cd install?

Many thanks in advance.

Last edited by Jamba (2007-06-12 00:25:25)

Re: Unattended (network) install - using method 2

hi
method 2 edits dosnet.inf and places the mass storage systemfiles used by TXTmode in i386 folder.
(that's why you do not see them in Winnt.sif)

The OEM folder has the 7zipped copies of the driverpacks you selected (including mass storage) and other files "setup" will use once TXTmode finished (in the BINaries folder).
What happens then is, 7zip/copy the driverpacks and executables to install them to hard disk, and then run the executables.

Your second question was answered by Bâshrat the Sneaky himself in another discussion.
I did not find that back yet, and when I do, I will post the link.
(I want to collect some info, and use it for a FAQ and maybe a tutorial )

The answer was 42?
Kind regards, Jaak.

Re: Unattended (network) install - using method 2

For question 2) the only thing you have to do is to copy the OEM directory from <yourosdir> to <yourosdir>/I386/$OEM$/$1. Windows setup is copying it on your hard disk with all installation file, so there's no problem. Works well for me.