Windows 2000 unnatended with drivers on CD

[tabularasa]

[Componants]accessopt = off
;paint = off
cdplayer = off
charmap=off
cluster = off
freecell = off
fp_extensions = off
indexsrv_system = off
minesweeper = off
;media_clips = off
;media_utopia = off
pinball = off
solitaire = off
chat = off
dialer = off
rec = off

Where can i get a full list of these componants you can intall?  I've gotten my install CD pretty tweaked, with Raid drivers, silent software installs, and drivers.  I would like to hand pick each windows componant to install with the winnt.sif file..

Anyone know where this list is?

[tabularasa]

Why did my post not show up?  

I asked where i could get a list of winnt.sif [Components] that could be used.

[Vandaahl]

after 4 days i found a nice sollution without messing with any inf files
i run the installation with command ; winnt /s:\i386 /u:unattended.txt

btw unattend.txt is renamed by the textmode part to winnt.sif

the i386 dir is in the root of a hard disk
in that dir;
$oem$


in the $oem$ dir;
$$
$1
C
Textmode

in the C dir HOTFIXES dir and PNPdrivers (dir)

files:
txtsetup.oem  (the same as in the textmode dir)
cmdlines.txt
oem.bmp

in the textmode dir drivers for my promise ultra100tx2 controller
i edited txtsetup.oem like this;


cmdlines.txt
-----------------------------------

[Commands]
".\regedit /s .\function.reg"
".\HotFixes\deton\setup.exe"
".\HotFixes\soundMAX\setup.exe"
-----------------------------------------------------------


------------------------------------------------------------------------------------------------
[Disks]

d3 = "Promise Ultra Series Driver Diskette", \ultra,""

[Defaults]

scsi = Ultra100TX2_nt5

[scsi]

Ultra100TX2_nt5 = "Win2000 Promise ULTRA100 TX2 (tm) Controller", Ultra



[Files.scsi.Ultra100TX2_nt5]
driver = d3, Ultra.sys, Ultra
inf    = d3, Ultra.inf
catalog = d3, Ultra.cat

[HardwareIds.scsi.Ultra100TX2_nt5]
id = "PCI\VEN_105A&DEV_4D68","Ultra"



[Config.Ultra]

value = "", Tag, REG_DWORD, 1
---------------------------------------------------------------------------------------------

the trick is the "" at the end of the first line
its the only thing i edited (i also took out the XP NT4 win2k3 stuff)


unattend.txt
-------------------------------------------------------------------------------------


[MassStorageDrivers]
    "Win2000 Promise ULTRA100 TX2 (tm) Controller"= "OEM"
    "IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"

[OEMBootFiles]
    Ultra
    ultra.sy_
    ultra.sys
    ultra.cat
    ultra.inf
    Txtsetup.oem

-----------------------------------------------------------------------------------------------

hmmm
 kindof a messy post ,sorry bout that

this worked for me
on a corporate win2k with sp4 slipstreamed in it

[vandaahl]

after 4 days i found a nice sollution without messing with any inf files
i run the installation with command ; winnt /s:\i386 /u:unattended.txt

btw unattend.txt is renamed by the textmode part to winnt.sif

the i386 dir is in the root of a hard disk
in that dir;
$oem$


in the $oem$ dir;
$$
$1
C
Textmode

in the C dir HOTFIXES dir and PNPdrivers (dir)

files:
txtsetup.oem  (the same as in the textmode dir)
cmdlines.txt
oem.bmp

in the textmode dir drivers for my promise ultra100tx2 controller
i edited txtsetup.oem like this;


cmdlines.txt
-----------------------------------

[Commands]
".\regedit /s .\function.reg"
".\HotFixes\deton\setup.exe"
".\HotFixes\soundMAX\setup.exe"
-----------------------------------------------------------


------------------------------------------------------------------------------------------------
[Disks]

d3 = "Promise Ultra Series Driver Diskette", \ultra,""

[Defaults]

scsi = Ultra100TX2_nt5

[scsi]

Ultra100TX2_nt5 = "Win2000 Promise ULTRA100 TX2 (tm) Controller", Ultra



[Files.scsi.Ultra100TX2_nt5]
driver = d3, Ultra.sys, Ultra
inf    = d3, Ultra.inf
catalog = d3, Ultra.cat

[HardwareIds.scsi.Ultra100TX2_nt5]
id = "PCI\VEN_105A&DEV_4D68","Ultra"



[Config.Ultra]

value = "", Tag, REG_DWORD, 1
---------------------------------------------------------------------------------------------

the trick is the "" at the end of the first line
its the only thing i edited (i also took out the XP NT4 win2k3 stuff)


unattend.txt
-------------------------------------------------------------------------------------


[MassStorageDrivers]
    "Win2000 Promise ULTRA100 TX2 (tm) Controller"= "OEM"
    "IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"

[OEMBootFiles]
    Ultra
    ultra.sy_
    ultra.sys
    ultra.cat
    ultra.inf
    Txtsetup.oem

-----------------------------------------------------------------------------------------------

hmmm
 kindof a messy post ,sorry bout that

this worked for me
on a corporate win2k with sp4 slipstreamed in it

[technicalplanet]

Dan is the man! I read about 5000 other posts and sites with no good results. Dan has it here for real! I LOVE YOU! the only thing to change is under:

[SCSI.Load]  ;add
<driver>  = driver.sys,4

[quote name=\'Dan\' post=\'10870\' date=\'Jul 22 2003, 01:36 PM\']Whilst a little late (like 7 months). I think I have found a solution to the problem of getting Win2K to detect OEM Mass Storage Devices on setup.

You need to edit the default txtsetup.sif file in the \i386 dir before you write it to the CD. I think that this will only work for PnP drivers tho'

Modify as follows:

under:

[SourceDisksFiles] ;add
driver.sys   = 1,,,,,,_x,4,1

where driver.sys is the name of your OEM driver

under:

[SCSI] ;add
<driver>  = "Description pulled from TXTSETUP.OEM supplied by oem"

where <driver> is the name of your drivers (without the .sys)

under:

[SCSI.Load]  ;add
<driver>  = driver.sys

replace <driver> and driver.sys as above

under:

[HardwareIdsDatabase]  ;add
"PCI\VEN_........" = <driver>

this line (the bit beginning with "PCI\VEN") is also supplied by the txtsetup.oem from your oem

Lastly - copy your driver.sys file to the \i386 dir

See how you get on - this has worked for me on 2 different drivers so....

The only reason I say it needs to be a PNP driver is that you also need to add the drivers under the $OEM$\$1\ dir structure, so that it is automatically detected in GUI portion of setup (I think) - otherwise, you will get through text mode, but no further.

Regards,

Dan[/quote]