TheTechGuide Forum
General Category => Software => Topic started by: h20 on September 21, 2003, 08:25:28 AM
-
Help: I have a working boot cd (W2K Server with SP4 integrated) that reads a:\winnt.sif and does most of what I want with one exception - it seems to ignore OemFilesPath="..\$OEM$" or maybe I've missunderstood a step somewhere?
At install completion I'd like to have a c:\I386 folder with the sp4 slipstreamed kit in it...
My CD root contains "$OEM$" (at same level as "I386" ); my unattend winnt.sif contains
Unattended]
UnattendMode=FullUnattended
OemSkipEula=Yes
OemPreinstall=No
TargetPath=\WINNT
ExtendOemPartition=0
FileSystem=ConvertNTFS
Repartition=Yes
OemFilesPath="..\$OEM$" < ---- Is this right?
OEMPnPDriversPath=Install\Drv\Video;Install\Drv\Storage;Install\Drv\Net;Install\Drv\Audio
Thanks in advance for any enlightenment...
Pete
-
Use OEMPreinstall=Yes
-
[quote name=\'h20\' date=\'Sep 21 2003, 09:25 AM\']Help: I have a working boot cd (W2K Server with SP4 integrated) that reads a:\winnt.sif and does most of what I want with one exception - it seems to ignore OemFilesPath="..\$OEM$" or maybe I've missunderstood a step somewhere?
At install completion I'd like to have a c:\I386 folder with the sp4 slipstreamed kit in it...
My CD root contains "$OEM$" (at same level as "I386" ); my unattend winnt.sif contains
Unattended]
UnattendMode=FullUnattended
OemSkipEula=Yes
OemPreinstall=No
TargetPath=\WINNT
ExtendOemPartition=0
FileSystem=ConvertNTFS
Repartition=Yes
OemFilesPath="..\$OEM$" < ---- Is this right?
OEMPnPDriversPath=Install\Drv\Video;Install\Drv\Storage;Install\Drv\Net;Install\Drv\Audio
Thanks in advance for any enlightenment...
Pete[/quote]
I am not sure if I understand you correctly. Why do you need a C:\i386 folder?
Do you understand the right OEM file structure? I have done this many times and I don't have/need any OemFilesPath="..\$OEM$" in my winnt.sif
Here is a schematic
W2PFPP_EN\
--------------\$OEM$\
------------- \$$
------------------\system32
------------- \$1
------------------\DRIVERS
------------------\WINAPPS
------------------ \Program Files
--------------\Textmode
--------------\C
--------------\D
--------------\Cmdlines.txt
--------------\*.bat
Could you be more precise on what you are trying to do and what is not happening
-
I have been trying to my w2k boot CD to work with my IBM RAID controller for sometimes now but I still can't get it.
I get this message during textmode setup:
"file txtsetup.oem caused an unexpected error (18) at line 1044 in d:\nt\private\ntos\boot\setup\oemdisk.c."
After that it fails to find any hard disk and couldn't continue with setup
Here's my MassStorageDrivers and OEMBootFiles sections in winnt.sif
[MassStorageDrivers]
"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller"="Retail"
"IBM ServeRAID 4M/4Mx/4L/4Lx/5i Controller (Windows 2000)"="OEM"
[OEMBootFiles]
txtsetup.oem
nfrd960.sys
ibmnfrd.cat
nfrdci.dll
oemsetup.inf
Here's the section in oemsetup.inf that I modified
[SourceDisksNames]
1 = %INSTALL_MEDIA_DESCRIPTION%, \NFRD960.SYS,
everything else in the file remains unchanged
Here's my oemsetup.txt in $oem$\textmode folder
[Disks]
d1 = "IBM ServeRAID Device Driver Diskette", NFRD960.SYS,.
[Defaults]
scsi = NFRDWin2k32
computer = SOMEDEFAULT
[scsi]
NFRDWin2k32 = "IBM ServeRAID 4M/4Mx/4L/4Lx/5i Controller (Windows 2000)"
[computer]
ibmhal_mp = "IBM eServer xSeries 440 (Windows 2000 HAL)"
[Files.scsi.NFRDWin2k32]
driver = d1, nfrd960.sys, NFRD960
#driver = d1, nfrdci01.dll, NFRDCI01
driver = d1, nfrd960.sys, NFRD960
catalog = d1, ibmnfrd.cat
inf = d1, oemsetup.inf
[Config.NFRD960]
value = parameters\PnpInterface,5,REG_DWORD,1
value = parameters\Device,NumberOfRequests,REG_DWORD,128
[Config.IPSRAIDN]
value = parameters\PnpInterface,5,REG_DWORD,1
value = parameters\Device,NumberOfRequests,REG_DWORD,128
[Config.NFRDCI01]
[HardwareIDs.scsi.NFRDWin2k32]
id = "PCI\VEN_1014&DEV_01BD", "nfrd960"
Does anyone know what am I doing wrong? Any help you can offer would be appreciated.
-
[quote name=\'AC\' date=\'Sep 26 2003, 11:23 AM\']Does anyone know what am I doing wrong? Any help you can offer would be appreciated.[/quote]
Hi!
First I presume, that your driver disk contains a tag file? For example this file is named "IBM" and it's a simple textfile with the disk name in it (IBM). Always add this file to OEMBootFiles!
Why did you edit inf files? This is not neccessary normaly.
Try again with the original files and if it does not work, try another driver version.
Pit
P.S.: It's a much better way to include mass-storage drivers directly into the setup without using the unattend.txt!
-
[quote name=\'AC\' date=\'Sep 26 2003, 11:23 AM\']I have been trying to my w2k boot CD to work with my IBM RAID controller for sometimes now but I still can't get it.
I get this message during textmode setup:
"file txtsetup.oem caused an unexpected error (18) at line 1044 in d:\nt\private\ntos\boot\setup\oemdisk.c."
After that it fails to find any hard disk and couldn't continue with setup
Here's my MassStorageDrivers and OEMBootFiles sections in winnt.sif
[MassStorageDrivers]
"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller"="Retail"
"IBM ServeRAID 4M/4Mx/4L/4Lx/5i Controller (Windows 2000)"="OEM"
[OEMBootFiles]
txtsetup.oem
nfrd960.sys
ibmnfrd.cat
nfrdci.dll
oemsetup.inf
Here's the section in oemsetup.inf that I modified
[SourceDisksNames]
1 = %INSTALL_MEDIA_DESCRIPTION%, \NFRD960.SYS,
everything else in the file remains unchanged
Here's my oemsetup.txt in $oem$\textmode folder
[Disks]
d1 = "IBM ServeRAID Device Driver Diskette", NFRD960.SYS,.
[Defaults]
scsi = NFRDWin2k32
computer = SOMEDEFAULT
[scsi]
NFRDWin2k32 = "IBM ServeRAID 4M/4Mx/4L/4Lx/5i Controller (Windows 2000)"
[computer]
ibmhal_mp = "IBM eServer xSeries 440 (Windows 2000 HAL)"
[Files.scsi.NFRDWin2k32]
driver = d1, nfrd960.sys, NFRD960
#driver = d1, nfrdci01.dll, NFRDCI01
driver = d1, nfrd960.sys, NFRD960
catalog = d1, ibmnfrd.cat
inf = d1, oemsetup.inf
[Config.NFRD960]
value = parameters\PnpInterface,5,REG_DWORD,1
value = parameters\Device,NumberOfRequests,REG_DWORD,128
[Config.IPSRAIDN]
value = parameters\PnpInterface,5,REG_DWORD,1
value = parameters\Device,NumberOfRequests,REG_DWORD,128
[Config.NFRDCI01]
[HardwareIDs.scsi.NFRDWin2k32]
id = "PCI\VEN_1014&DEV_01BD", "nfrd960"
Does anyone know what am I doing wrong? Any help you can offer would be appreciated.[/quote]
Here's the section in oemsetup.inf that I modified
[SourceDisksNames]
from
1 = %INSTALL_MEDIA_DESCRIPTION%, \NFRD960.SYS,
to
1 = %InstallDisk%, \NFRD960.SYS,
Here's my oemsetup.txt in $oem$\textmode folder
from
d1 = "IBM ServeRAID Device Driver Diskette",
to
[Disks]
d1 = "Windows 2000 Driver Set v1.00",w2kdsk1,\
w2kdsk1 is the mame of cd W2k disk
modified if not. ti the mame
[Defaults]
scsi = NFRDWin2k32
computer = SOMEDEFAULT
[scsi]
NFRDWin2k32 = "IBM ServeRAID 4M/4Mx/4L/4Lx/5i Controller (Windows 2000)"
[computer]
ibmhal_mp = "IBM eServer xSeries 440 (Windows 2000 HAL)"
[Files.scsi.NFRDWin2k32]
driver = d1, nfrd960.sys, NFRD960
#driver = d1, nfrdci01.dll, NFRDCI01
driver = d1, nfrd960.sys, NFRD960
catalog = d1, ibmnfrd.cat
inf = d1, oemsetup.inf
[Config.NFRD960]
value = parameters\PnpInterface,5,REG_DWORD,1
value = parameters\Device,NumberOfRequests,REG_DWORD,128
[Config.IPSRAIDN]
value = parameters\PnpInterface,5,REG_DWORD,1
value = parameters\Device,NumberOfRequests,REG_DWORD,128
[Config.NFRDCI01]
[HardwareIDs.scsi.NFRDWin2k32]
id = "PCI\VEN_1014&DEV_01BD", "nfrd960"
-
This thread looks a little dated but I am having the same problem. I got past the "file txtsetup.oem caused an unexpected error (18) at line 1044 in d:\nt\private\ntos\boot\setup\oemdisk.c." error by changing
OEM to Retail for the mass storage driver.
Example:
[MassStorageDrivers]
"IBM ServeRAID 4M/4Mx/4L/4Lx/5i Controller (Windows 2000)"="Retail"
Don't know if this is right but it forces it to look at the txtsetup.sif instead of the oem. I got nowhere with the txtsetup.oem file. I'm using the new ServRaid7k. I'm now getting an error about the "nfrd960.sys under [SourceDisksNames] in inf is missing or currupt". I think I just need to get the path right in the nfrd960.inf, but not sure. Damn IBM. They could have made it so much easier.
p.s. You may want to also check out the unnatend.doc on the Win2K CD.
Steve D.