installing to a hdd on a promise pci card without a floppy...

[Guest]

I re-created a slipstreamed cd, and took the following steps:

Created a $OEM$ folder in i386
Created a pnpdrvrs folder in $OEM$
Put the driver files (ultra.inf, ultra.sys, ultra.cat) in $OEM$\$1
Added these lines to an answer file:

[Unattended]
UnattendMode=FullUnattended
OemSkipEula=Yes
OemPnPDriversPath=\pnpdrvrs
OemPreinstall=Yes
TargetPath=\WINNT

Put the answer file in i386

This did not work, so I put the 3 driver files (ultra.*) in i386, unpacked
driver.cab, put the 3 driver files in driver.cab, and repackaged driver.cab.

Still, setup does not find the hard drives on the pci promise card and asks
for a floppy disk.

What am I missing?

 

[Gerry Hickman]

Hi,

It sounds like to forgot to sort out the TXTSETUP.OEM stuff?

I re-created a slipstreamed cd, and took the following steps:

Created a $OEM$ folder in i386
Created a pnpdrvrs folder in $OEM$
Put the driver files (ultra.inf, ultra.sys, ultra.cat) in $OEM$\$1
Added these lines to an answer file:

[Unattended]
UnattendMode=FullUnattended
OemSkipEula=Yes
OemPnPDriversPath=\pnpdrvrs
OemPreinstall=Yes
TargetPath=\WINNT

Put the answer file in i386

This did not work, so I put the 3 driver files (ultra.*) in i386, unpacked
driver.cab, put the 3 driver files in driver.cab, and repackaged driver.cab.

Still, setup does not find the hard drives on the pci promise card and asks
for a floppy disk.

What am I missing?

 

[Guest]

Gerry,

I did miss that. I found the details on it in the DPG and will be trying
that out soon.

Brandon

Hi,

It sounds like to forgot to sort out the TXTSETUP.OEM stuff?

I re-created a slipstreamed cd, and took the following steps:

Created a $OEM$ folder in i386
Created a pnpdrvrs folder in $OEM$
Put the driver files (ultra.inf, ultra.sys, ultra.cat) in $OEM$\$1
Added these lines to an answer file:

[Unattended]
UnattendMode=FullUnattended
OemSkipEula=Yes
OemPnPDriversPath=\pnpdrvrs
OemPreinstall=Yes
TargetPath=\WINNT

Put the answer file in i386

This did not work, so I put the 3 driver files (ultra.*) in i386, unpacked
driver.cab, put the 3 driver files in driver.cab, and repackaged driver.cab.

Still, setup does not find the hard drives on the pci promise card and asks
for a floppy disk.

What am I missing?

 

[Gerry Hickman]

Hi Brandon,

I did miss that. I found the details on it in the DPG

What is the DPG??

and will be trying
that out soon.

Use the Win2k ResKit if you have it. I've copied some text from it here:

(Be aware that some controllers such as Dell PERC2 won't work with this
method).





To install a mass storage device
In the distribution folder, create the Textmode subfolder in the \$OEM$
subfolder.
In the Textmode subfolder, copy the following files, which you obtain
from the device vendor (replace the word Driver with the appropriate
driver name):

Driver.sys
Driver.dll
Driver.inf
Driver.cat
Txtsetup.oem
Note You must also copy the driver files to the <PnPdrvrs> location that
you specified for the OemPnPDriversPath parameter in the answer file.
For example:

\$OEM$\$1\<PnPdrvrs>\<Storage>


Some drivers, such as SCSI miniport drivers, might not include a DLL file.

In the answer file, create a [MassStorageDrivers] section, and include
the driver entries that you want to include. For example, a possible
entry in the [MassStorageDrivers] section might be the following:
"Adaptec 2940U" = "OEM"


Information for this section can be obtained from the Txtsetup.oem file,
which is provided by the hardware manufacturer.

In the answer file, create an [OEMBootFiles] section, and include a list
of the files in the $OEM$\Textmode folder. For example, a possible entry
to the [OEMBootFiles] section might be the following:
[OEMBootFiles]
Driver.sys
Driver.dll
Driver.inf
Txtsetup.oem


Where Driver is the driver name.

In the Txtsetup.oem file, verify that a section named
[HardwareIds.Scsi.yyyyy] exists. If it does not, create it following
this format:
[HardwareIds.scsi. yyyy]
id = "xxxxx" , "yyyyy"


where xxxxx is the device identifier and yyyyy is the device service
name. For example, for the Symc810 driver, which has a device ID of
PCI\VEN_1000&DEV_0001, you create this section:

[HardwareIds.scsi.symc810]
id = "PCI\VEN_1000&DEV_0001" , "symc810"

 

[Brandon]

Gerry,

Is it just me, or does the web interface for this site keep going down? Fortunate that we can post via nntp.

Sorry about the non-standard abbreviation. By DPG I meant Deployment Guide.

I tried it now, and I'm getting 2 errors.

ERROR 1:
The file txtsetup.oem could not be found.
Press any key to continue.

ERROR 2: (I'm guessing the file here is the same as in error 1?)
The manufacturer provided file that setup is trying to use is corrupted or invalid.
Line 1 contains a syntax error.
Setup cannot continue. To quit setup, press F3.

DETAILS:

I have the following folders (using full paths):

CDroot:\I386\$OEM$\$$\Help (currently empty)
CDroot:\I386\$OEM$\$$\System32 (empty)
CDroot:\I386\$OEM$\$1\pnpdrvrs (contains the Promise UATA drivers and modem drivers)
CDroot:\I386\$OEM$\Textmode (contains the Promise UATA drivers)

Promise UATA drivers consist of these files:

txtsetup.oem
ultra
ultra.cat
ultra.inf
ultra.sys

Because of the above errors, I put the txtsetup.oem in the pnpdrvrs and I386 folders as well as the textmode folder, but the errors still occur.

I386 has both txtsetup.oem and txtsetup.sif now...

My answer file, (winnt.sif in I386), has the following applicable entries:

[Unattended]
OemPreinstall=Yes
OemPnPDriversPath=\Pnpdrvrs

[MassStorageDrivers]
"Win2000 Promise ULTRA100 TX2 (tm) Controller"="OEM"

[OEMBootFiles]
txtsetup.oem
ultra
ultra.cat
ultra.inf
ultra.sys

Any ideas where the problem is?

Hi Brandon,

I did miss that. I found the details on it in the DPG

What is the DPG??

and will be trying that out soon.

Use the Win2k ResKit if you have it. I've copied some text from it here:

(Be aware that some controllers such as Dell PERC2 won't work with this
method).





To install a mass storage device
In the distribution folder, create the Textmode subfolder in the \$OEM$
subfolder.
In the Textmode subfolder, copy the following files, which you obtain
from the device vendor (replace the word Driver with the appropriate
driver name):

Driver.sys
Driver.dll
Driver.inf
Driver.cat
Txtsetup.oem
Note You must also copy the driver files to the <PnPdrvrs> location that
you specified for the OemPnPDriversPath parameter in the answer file.
For example:

\$OEM$\$1\<PnPdrvrs>\<Storage>


Some drivers, such as SCSI miniport drivers, might not include a DLL file.

In the answer file, create a [MassStorageDrivers] section, and include
the driver entries that you want to include. For example, a possible
entry in the [MassStorageDrivers] section might be the following:
"Adaptec 2940U" = "OEM"


Information for this section can be obtained from the Txtsetup.oem file,
which is provided by the hardware manufacturer.

In the answer file, create an [OEMBootFiles] section, and include a list
of the files in the $OEM$\Textmode folder. For example, a possible entry
to the [OEMBootFiles] section might be the following:
[OEMBootFiles]
Driver.sys
Driver.dll
Driver.inf
Txtsetup.oem


Where Driver is the driver name.

In the Txtsetup.oem file, verify that a section named
[HardwareIds.Scsi.yyyyy] exists. If it does not, create it following
this format:
[HardwareIds.scsi. yyyy]
id = "xxxxx" , "yyyyy"


where xxxxx is the device identifier and yyyyy is the device service
name. For example, for the Symc810 driver, which has a device ID of
PCI\VEN_1000&DEV_0001, you create this section:

[HardwareIds.scsi.symc810]
id = "PCI\VEN_1000&DEV_0001" , "symc810"

 

[Gerry Hickman]

Hi Brandon,

If you are using a CD, you have to put the $oem$ in the root, not the
i386. See:

<http://www.willowhayes.co.uk/windows2000/>

Scroll down to view the correct para.

Gerry,

Is it just me, or does the web interface for this site keep going down?
Fortunate that we can post via nntp.

Sorry about the non-standard abbreviation. By DPG I meant Deployment
Guide.

I tried it now, and I'm getting 2 errors.

ERROR 1:
The file txtsetup.oem could not be found.
Press any key to continue.

ERROR 2: (I'm guessing the file here is the same as in error 1?)
The manufacturer provided file that setup is trying to use is corrupted
or invalid.
Line 1 contains a syntax error.
Setup cannot continue. To quit setup, press F3.

DETAILS:

I have the following folders (using full paths):

CDroot:\I386\$OEM$\$$\Help (currently empty)
CDroot:\I386\$OEM$\$$\System32 (empty)
CDroot:\I386\$OEM$\$1\pnpdrvrs (contains the Promise UATA drivers and
modem drivers)
CDroot:\I386\$OEM$\Textmode (contains the Promise UATA drivers)

Promise UATA drivers consist of these files:

txtsetup.oem
ultra
ultra.cat
ultra.inf
ultra.sys

Because of the above errors, I put the txtsetup.oem in the pnpdrvrs and
I386 folders as well as the textmode folder, but the errors still occur.

I386 has both txtsetup.oem and txtsetup.sif now...

My answer file, (winnt.sif in I386), has the following applicable entries:

[Unattended]
OemPreinstall=Yes
OemPnPDriversPath=\Pnpdrvrs

[MassStorageDrivers]
"Win2000 Promise ULTRA100 TX2 (tm) Controller"="OEM"

[OEMBootFiles]
txtsetup.oem
ultra
ultra.cat
ultra.inf
ultra.sys

Any ideas where the problem is?

Hi Brandon,

I did miss that. I found the details on it in the DPG

What is the DPG??

and will be trying that out soon.

Use the Win2k ResKit if you have it. I've copied some text from it here:

(Be aware that some controllers such as Dell PERC2 won't work with
this method).





To install a mass storage device
In the distribution folder, create the Textmode subfolder in the
\$OEM$ subfolder.
In the Textmode subfolder, copy the following files, which you obtain
from the device vendor (replace the word Driver with the appropriate
driver name):

Driver.sys
Driver.dll
Driver.inf
Driver.cat
Txtsetup.oem
Note You must also copy the driver files to the <PnPdrvrs> location
that you specified for the OemPnPDriversPath parameter in the answer
file. For example:

\$OEM$\$1\<PnPdrvrs>\<Storage>


Some drivers, such as SCSI miniport drivers, might not include a DLL
file.

In the answer file, create a [MassStorageDrivers] section, and include
the driver entries that you want to include. For example, a possible
entry in the [MassStorageDrivers] section might be the following:
"Adaptec 2940U" = "OEM"


Information for this section can be obtained from the Txtsetup.oem
file, which is provided by the hardware manufacturer.

In the answer file, create an [OEMBootFiles] section, and include a
list of the files in the $OEM$\Textmode folder. For example, a
possible entry to the [OEMBootFiles] section might be the following:
[OEMBootFiles]
Driver.sys
Driver.dll
Driver.inf
Txtsetup.oem


Where Driver is the driver name.

In the Txtsetup.oem file, verify that a section named
[HardwareIds.Scsi.yyyyy] exists. If it does not, create it following
this format:
[HardwareIds.scsi. yyyy]
id = "xxxxx" , "yyyyy"


where xxxxx is the device identifier and yyyyy is the device service
name. For example, for the Symc810 driver, which has a device ID of
PCI\VEN_1000&DEV_0001, you create this section:

[HardwareIds.scsi.symc810]
id = "PCI\VEN_1000&DEV_0001" , "symc810"

 

[Brandon]

Thany you! Now I've passed one major roadblock.

Funny, I had that page bookmarked, but did not notice the (now obvious)
note about where to place the $oem$ folder.

Now setup finds txtsetup.oem, however I get this error:

File txtsetup.oem caused an unexpected error (18) at line 1044 in
d:\nt\private\ntos\boot\setup\oemdisc.c

Press any key to continue.

The following Google search did not have anything useful to me:

http://www.google.com/search?q="Fil...ient=firefox-a&rls=org.mozilla:en-US:official

Any ideas?

Thank you,

Brandon

Hi Brandon,

If you are using a CD, you have to put the $oem$ in the root, not the
i386. See:

<http://www.willowhayes.co.uk/windows2000/>

Scroll down to view the correct para.

Gerry,

Is it just me, or does the web interface for this site keep going
down? Fortunate that we can post via nntp.

Sorry about the non-standard abbreviation. By DPG I meant Deployment
Guide.

I tried it now, and I'm getting 2 errors.

ERROR 1:
The file txtsetup.oem could not be found.
Press any key to continue.

ERROR 2: (I'm guessing the file here is the same as in error 1?)
The manufacturer provided file that setup is trying to use is
corrupted or invalid.
Line 1 contains a syntax error.
Setup cannot continue. To quit setup, press F3.

DETAILS:

I have the following folders (using full paths):

CDroot:\I386\$OEM$\$$\Help (currently empty)
CDroot:\I386\$OEM$\$$\System32 (empty)
CDroot:\I386\$OEM$\$1\pnpdrvrs (contains the Promise UATA drivers and
modem drivers)
CDroot:\I386\$OEM$\Textmode (contains the Promise UATA drivers)

Promise UATA drivers consist of these files:

txtsetup.oem
ultra
ultra.cat
ultra.inf
ultra.sys

Because of the above errors, I put the txtsetup.oem in the pnpdrvrs
and I386 folders as well as the textmode folder, but the errors still
occur.

I386 has both txtsetup.oem and txtsetup.sif now...

My answer file, (winnt.sif in I386), has the following applicable
entries:

[Unattended]
OemPreinstall=Yes
OemPnPDriversPath=\Pnpdrvrs

[MassStorageDrivers]
"Win2000 Promise ULTRA100 TX2 (tm) Controller"="OEM"

[OEMBootFiles]
txtsetup.oem
ultra
ultra.cat
ultra.inf
ultra.sys

Any ideas where the problem is?

Hi Brandon,

I did miss that. I found the details on it in the DPG




What is the DPG??

and will be trying that out soon.




Use the Win2k ResKit if you have it. I've copied some text from it here:

(Be aware that some controllers such as Dell PERC2 won't work with
this method).





To install a mass storage device
In the distribution folder, create the Textmode subfolder in the
\$OEM$ subfolder.
In the Textmode subfolder, copy the following files, which you obtain
from the device vendor (replace the word Driver with the appropriate
driver name):

Driver.sys
Driver.dll
Driver.inf
Driver.cat
Txtsetup.oem
Note You must also copy the driver files to the <PnPdrvrs> location
that you specified for the OemPnPDriversPath parameter in the answer
file. For example:

\$OEM$\$1\<PnPdrvrs>\<Storage>


Some drivers, such as SCSI miniport drivers, might not include a DLL
file.

In the answer file, create a [MassStorageDrivers] section, and
include the driver entries that you want to include. For example, a
possible entry in the [MassStorageDrivers] section might be the
following:
"Adaptec 2940U" = "OEM"


Information for this section can be obtained from the Txtsetup.oem
file, which is provided by the hardware manufacturer.

In the answer file, create an [OEMBootFiles] section, and include a
list of the files in the $OEM$\Textmode folder. For example, a
possible entry to the [OEMBootFiles] section might be the following:
[OEMBootFiles]
Driver.sys
Driver.dll
Driver.inf
Txtsetup.oem


Where Driver is the driver name.

In the Txtsetup.oem file, verify that a section named
[HardwareIds.Scsi.yyyyy] exists. If it does not, create it following
this format:
[HardwareIds.scsi. yyyy]
id = "xxxxx" , "yyyyy"


where xxxxx is the device identifier and yyyyy is the device service
name. For example, for the Symc810 driver, which has a device ID of
PCI\VEN_1000&DEV_0001, you create this section:

[HardwareIds.scsi.symc810]
id = "PCI\VEN_1000&DEV_0001" , "symc810"

 

[Patrick J. LoPresti]

Now setup finds txtsetup.oem, however I get this error:

File txtsetup.oem caused an unexpected error (18) at line 1044 in
d:\nt\private\ntos\boot\setup\oemdisc.c

Press any key to continue.

The following Google search did not have anything useful to me:

http://www.google.com/search?q="Fil...ient=firefox-a&rls=org.mozilla:en-US:official

Try searching Google Groups instead. Here are two old messages of
mine on the subject:

http://groups-beta.google.com/group/microsoft.public.win2000.setup_deployment/msg/96a057392f20da32

http://groups-beta.google.com/group/microsoft.public.windowsxp.setup_deployment/msg/708d9fccde35c221

In short, txtsetup.oem simply does not work with CD-based installs.
You either need to switch to a network install or you need to hack
your driver directly into the installation media (txtsetup.sif and
friends). See <http://www.google.com/search?q=txtsetup.sif>,
especially the stuff on MSFN.

- Pat
http://unattended.sourceforge.net/

 

[Brandon]

Thank you Patrick. I'll give that a try. Here is another link I found:

http://www.pcstats.com/articleview.cfm?articleid=1703&page=1

What do you think of that one? It talks about modifying txtsetup.sif.

 

[Gerry Hickman]

In short, txtsetup.oem simply does not work with CD-based installs.

Is that it? I ran into the problem building Dell servers but assumed it
was an issue with the Dell controller.

So are we saying TXTSETUP.OEM has never worked from CD?

 

[Gerry Hickman]

Thank you Patrick. I'll give that a try. Here is another link I found:

http://www.pcstats.com/articleview.cfm?articleid=1703&page=1

What do you think of that one? It talks about modifying txtsetup.sif.

Yup, that's what I had to do for my bootable server CD-ROMs.

Make sure you backup txtsetup.sif before you start, and make sure you
keep ALL modified and added text strings in a separate text file for
later reference.

 

[Patrick J. LoPresti]

So are we saying TXTSETUP.OEM has never worked from CD?

To my knowledge, many have tried but nobody has ever gotten it to
work. (Not for XP, anyway. I am less sure about win2k.)

- Pat
http://unattended.sourceforge.net/

 

[Brandon]

I just tried it and it didn't work. One thing I noticed: one of the
names seems to be much longer than anything else in it's section, e.g.:
ultra100nt5_tx2 (or something like that). I renamed all instances of
ultra100nt5_tx2 (or whatever) to ultra100. I will post if it works or
not later...

 

[Brandon]

OK, I tried it twice now, and it didn't work in either case. I'm
supposing I'll have to abandon the idea of an automated install to an
hdd on a PCI UATA controller card. Any further suggestions?

 

[Brandon]

I noticed that if I set OEMpreinstall=yes, I still get the line 1044 error even with the $oem$ folder in the CD root. If I set it to no, or remove the line entirely, I boot just fine. I've added the driver information to txtsetup.sif, but I still can't see the drive (see a couple other posts I have on that).

I wonder if the $oem$ folder structure will work without OEMpreinstall=yes?

 

[Patrick J. LoPresti]

I wonder if the $oem$ folder structure will work without
OEMpreinstall=yes?

Doubtful. OEMpreinstall=yes is what causes the $oem$ tree to get
copied to the hard drive.

- Pat
http://unattended.sourceforge.net/

 

[Gerry Hickman]

To my knowledge, many have tried but nobody has ever gotten it to
work. (Not for XP, anyway. I am less sure about win2k.)

Thanks for clarification. This is somewhat crazy!

 

[Gerry Hickman]

Hi Brandon,

Sorry but your text below is meaningless to me (and probably is to
others reading this).

You need to post the EXACT cut/paste of RELEVANT sections of both your
winnt.sif and txtsetup.sif files. Should be less than 30 lines of text
in total.

Can you also identify the exact controller you're trying to use and
where you got the driver from and which files you extracted to where.

We also need exact error text from any error that occurrs.

 

[Brandon]

Gerry,

No problem, I'll provide the details now.

The card is the Promise Ultra100 TX2:

http://www.promise.com/support/download/download2_eng.asp?productId=11&amp;category=driver&amp;os=0

I downloaded driver version 2.00.0.42.

txtsetup.oem contains details for multiple cards and mutiple OSes.&nbsp; I removed all the extra OSes and all the extra cards.&nbsp; This is what was left:
[Disks]
d1 = "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 = d1, Ultra.sys, Ultra
inf&nbsp;&nbsp;&nbsp; = d1, Ultra.inf
catalog = d1, Ultra.cat

[HardwareIds.scsi.Ultra100TX2_nt5]
id = "PCI\VEN_105A&amp;DEV_4D68","Ultra"
These are the resulting txtsetup.sif lines:
[SourceDisksFiles]
Ultra.sys = 1,,,,,,3_,4,1

[HardwareIdsDatabase]
PCI\VEN_105A&amp;DEV_4D68 = Ultra100TX2_nt5

[SCSI.load]
Ultra100TX2_nt5 = Ultra.sys, 4

[scsi]
Ultra100TX2_nt5 = "Win2000 Promise ULTRA100 TX2 (tm) Controller", Ultra
Finally, winnt.sif includes these lines:
[Unattended]
&nbsp;&nbsp;&nbsp; UnattendMode=FullUnattended
&nbsp;&nbsp;&nbsp; DriverSigningPolicy=Ignore
&nbsp;&nbsp;&nbsp; OemSkipEula=Yes
&nbsp;&nbsp;&nbsp; TargetPath=\WINNT
&nbsp;&nbsp;&nbsp; OemPnPDriversPath=\Pnpdrvrs
Note that I removed the oempreinstall=yes because it does not seem to work, but with or without it, the PCI Promise card drivers do not load for setup.

Thank you (and/or anyone else who participates in this thread) for your help

Brandon

Gerry Hickman wrote: Hi Brandon,

Sorry but your text below is meaningless to me (and probably is to others reading this).

You need to post the EXACT cut/paste of RELEVANT sections of both your winnt.sif and txtsetup.sif files. Should be less than 30 lines of text in total.

Can you also identify the exact controller you're trying to use and where you got the driver from and which files you extracted to where.

We also need exact error text from any error that occurrs.

Brandon wrote:

I just tried it and it didn't work.&nbsp; One thing I noticed: one of the names seems to be much longer than anything else in it's section, e.g.: ultra100nt5_tx2 (or something like that).&nbsp; I renamed all instances of ultra100nt5_tx2 (or whatever) to ultra100.&nbsp; I will post if it works or not later...

 

[Gerry Hickman]

Hi Brandon,

The TXTSETUP.SIF looks correct to me, provided you have checked '3_' in your
[DiskSourceNames] section is pointing to the right place. On my system all
the entries in [DiskSourceNames] are pointing to the same place

%srvcd%,\cdrom_is.5,,""

But my actual driver entry under [SourceDisksNames] uses '_x', as opposed to
'3_'

Are you sure you have posted the full winnt.sif file below, it's very short!
You need to keep oempreinstall=yes in the file or I don't think it will work
at all. You can comment out lines in WINNT.SIF and TXTSETUP.SIF using a
semi-colon while doing experiments.

To look into it further, I'd need the exact error you get with line number,
and at which point it occurs (e.g. just after loading cpqarray driver)

Gerry Hickman
SSRU SysAdmin

Gerry,

No problem, I'll provide the details now.

The card is the Promise Ultra100 TX2:

http://www.promise.com/support/download/download2_eng.asp?productId=11&category=driver&os=0

I downloaded driver version 2.00.0.42.

txtsetup.oem contains details for multiple cards and mutiple OSes. I

removed all the extra OSes and all the extra cards. This is what was left:

[Disks]
d1 = "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 = d1, Ultra.sys, Ultra
inf = d1, Ultra.inf
catalog = d1, Ultra.cat

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

These are the resulting txtsetup.sif lines:

[SourceDisksFiles]
Ultra.sys = 1,,,,,,3_,4,1

[HardwareIdsDatabase]
PCI\VEN_105A&DEV_4D68 = Ultra100TX2_nt5

[SCSI.load]
Ultra100TX2_nt5 = Ultra.sys, 4

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

Finally, winnt.sif includes these lines:

[Unattended]
UnattendMode=FullUnattended
DriverSigningPolicy=Ignore
OemSkipEula=Yes
TargetPath=\WINNT
OemPnPDriversPath=\Pnpdrvrs

Note that I removed the oempreinstall=yes because it does not seem to

work, but with or without it, the PCI Promise card drivers do not load for
setup.

Thank you (and/or anyone else who participates in this thread) for your help

Brandon

Gerry Hickman wrote:
Hi Brandon,

Sorry but your text below is meaningless to me (and probably is to others reading this).

You need to post the EXACT cut/paste of RELEVANT sections of both your

winnt.sif and txtsetup.sif files. Should be less than 30 lines of text in
total.

Can you also identify the exact controller you're trying to use and

where you got the driver from and which files you extracted to where.

We also need exact error text from any error that occurrs.

Brandon wrote:


I just tried it and it didn't work. One thing I noticed: one of the

names seems to be much longer than anything else in it's section, e.g.:
ultra100nt5_tx2 (or something like that). I renamed all instances of
ultra100nt5_tx2 (or whatever) to ultra100. I will post if it works or not
later...