The easy way of creating a custom install cd with 3rd party drivers is to use the utility NLite (Requires .NET to use)
One can manually slipstream the driver on the installation cd, so Windows NT will automatically recognize the controller without having to press F6 and use a floppy disk:
- Create a directory $OEM$ under the i368 directory:
<Drive>\i386\$OEM$
- Create a directory Textmode under the $OEM$ directory:
<Drive>\i386\$OEM$\Textmode
- Copy only the needed drivers for the specific operating system to the Textmode directory.
All the files should be placed in the Textmode directory, there should not
be created any sub directories below the Textmode directory.
Txtsetup.oem (Required)
Driver.sys
Driver.inf
Driver.cat
- Edit the file <Drive>\i386\$OEM$\Textmode\TXTSETUP.OEM and find the [disks] section. Ex.:
Update the path (\win2000\ultra160) so it points to current directory (<Drive>\i386\$OEM$\Textmode) instead of referencing floppy drives or sub directories.[disks]
d1 = "Windows 2000 Driver Set v1.00", \w2kdsk1, \win2000\ultra160\
If installing on a FAT / FAT32 partition then replace the path with period "."
If installing on a NTFS partition then replace the path with slash "\"[disks]
d1 = "Windows 2000 Driver Set v1.00", \w2kdsk1, .
All references to other Operating Systems inside the TXTSETUP.OEM should be removed. Example of an Original and Modified image of the TXTSETUP.OEM for a Promise Fasttrak to install on NTFS in WinXP. Credits spc.org.nc[disks]
d1 = "Windows 2000 Driver Set v1.00", \w2kdsk1, \
- Edit the file <Drive>\i386\Unattend.txt, and create a [MassStorageDrivers] section:
Ex. :[MassStorageDrivers]
"string that identifies the controller in the [scsi] section of TXTSETUP.OEM" = "OEM".
[MassStorageDrivers]
"Adaptec Ultra160 Family PCI SCSI Controller (29160, 39160, etc.)" = "OEM"
- If intending to use the onboard IDE controller during installation, Edit the file <Drive>\i386\Unattend.txt,
and add this line to the [MassStorageDrivers] section:
If the line is not added a BSOD will appear during install with INACCESSIBLE_BOOT_DEVICE. This error comes because the controller which the device(HDD/CD-ROM/DVD) is attached to is not recognized. Therefore requiring one to give it a driver for the controller.Ex. :"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"
[MassStorageDrivers]
"Adaptec Ultra160 Family PCI SCSI Controller (29160, 39160, etc.)" = "OEM"
"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"
- Edit the file <Drive>\i386\Unattend.txt, and create a [OEMBootFiles] section.
List the driver filenames copied to the Textmode folder:
[OEMBootFiles]
Driver.sys
Driver.inf
Driver.cat
Txtsetup.oem
- Edit the file <Drive>\i386\Unattend.txt, and set the following option in the [Unattended] section:
[Unattended]
OemPreinstall=Yes
OemSkipEula=Yes
- Launch the installation with the created unattend file:
Note if doing the install from DOS then load SMARTDRV before launching the install, or else the initial file copying in textmode will be extremely slow.WINNT /U:<Drive>\i386\Unattend.txt /S:<Drive>\i386
Related Unattended Windows Guide
More Info MS KB288344
More Info MS KB155197
More Info MS KB166028
More Info MS KB254078
More Info MS KB255771
More Info MS KB314479
More Info MS KB816299
Credits jsifaq.com
I need to Include 3rd party controller drivers using unattended install but I do not know the hardware I may end up getting. I have no problem building a library on the boot cd \i386\$OEM$.
I do not want to change the the txtsetup and the unattended file every time I go to a machine. I would like to just build the libary for the systems I have and be able to use the single cd build to install on all hardware that I have the SCSI drives for.
Hope someone can help.
I haven't tried this myself but an idea could be to combine the TXTSETUP.OEM's of the different SCSI drivers into a single one, so it contains the hardwareids of all the SCSI devices.
A similar thing can be seen in the tip where one adds an extra scsi driver to the Recovery Console.
Well, when are you going to try it? When you do let me know :-).
Thanks
i've tried doing this w/ FAsttrak MB lite 133 controller, but winxp cannot find the device at all!
i've tried so many times, wasted so many cds, if anyone could catch what i'm doing wrong, i'd appreciate it very much!
here's my txtsetup.oem file located in cd:\i386\$OEM$\textmode
and here's part of my UNATTEND.txt file that i've modified, located in cd:\i386\
and last, here's part of my winnt.sif file
well.. i didn't modify any of parts in this file.. but here's part
can anyone see what i'm doing wrong?? .. i really can't tell why it's not recognizing..
lmk tia!!
I guess you have tried to use F6 and a floppy disk, just to make sure that WinXP is able to detect your Fasttrak133 Controller in a normal install.
Remember that one have to start an unattended installation, unless overwritting the winnt.sif with the contents of unattend.txt.
I see you have chosen MBFastTrak133 (RAID-1 Mirroring), are you sure you are not using SBFastTrak133 (RAID-0 Stripping) ?
Also if you have a HDD attached to your Standard IDE Controller, then you can place the WinXP Install Files (With your unattend file) and do the install from there while testing. You could also consider getting hold of a CD-RW.
the setup as posted on the board didnt work for me
\i386\$oem$\$1\$win_nt$.~ls\
i suggest trying to use this line somewhere in the setup
im gonna try this tomorow (its late now)