Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Edit txtsetup.sif?

2 views
Skip to first unread message

Anony Mous

unread,
Sep 8, 2002, 3:00:54 PM9/8/02
to
I've seen a couple references online to editing the txtsetup.sif file
located in the /i386 folder on the WinXP cd. Specifically, I'd like
to add support for my Promise FastTrak Lite RAID controller under the
[SCSI] section. I've tried adding the requisite line, and put the
drivers in the i386/$oem$/textmode folder, but no joy.

Does anyone have any experience editing the txtsetup.sif file on the
WinXP cd? Please note I am not referring to the txtsetup.oem file
that comes with third party drivers, as this is a separate issue.

Thanks,


-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 80,000 Newsgroups - 16 Different Servers! =-----

shockwaveriderz-MVP

unread,
Sep 8, 2002, 8:10:47 PM9/8/02
to
anonymous:
this may work with xp:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q288344

you might also check the promise.com website for info....
"Anony Mous" <bugg...@buggeroff.com> wrote in message news:3j7nnusb1688b0jtq...@4ax.com...

Anony Mous

unread,
Sep 8, 2002, 8:46:50 PM9/8/02
to
yep, I should've mentioned that I've read every KB article that even
remotely pertains to this topic, as well as every GoogleGroups listing
that I found, including the thread from last December 15 in this very
group where you answered Iznogood's identical question. He never
reported his final results.

I've attempted the inclusion of the drivers in the $oem$/textmode/
folder, and edited the winnt.sif precisely as directed, and this
simply has never worked for me. It's entirely likely that I've made
some syntax error somewhere, but I've yet to hear from anyone who can
say "Yes, I've done exactly that, here's how I did it."

I found a reference in one of the old Win2k groups regarding adding
the RAID driver to the [SCSI]section of the txtsetup.sif, but the
location of the driver placement was unclear in that post.

If you, shockwaveriderz, have actually done this, please let me know
how. If you're interested I'll post my winnt.sif and txtsetup.oem
files and directory structure. Maybe I've made a glaring error
that'll be obvious to you.

Thanks

On Sun, 8 Sep 2002 20:10:47 -0400, "shockwaveriderz-MVP"
<shockwa...@hotmail.com> wrote:

>http://support.microsoft.com/default.aspx?scid=kb;en-us;Q288344

George S. Ellis

unread,
Sep 9, 2002, 8:09:28 AM9/9/02
to
OK, sounds like you have experience here, so I will not explain anything as I do not have the free cycles.  This is a paste job of a solution adding a driver to W2K for a similar issue.  Sorry about the formatting.  The MS support guys helped with (and composed) this.  This was the beginnings of a Q that may not have seen the light of day yet.
 
========================================

Copy the i386 folder and its contents from the 2000 Cd-rom to the root of a folder (ex. named "FLAT")

Now we are going to "trick" windows into thinking the 3rd party drivers are "in-the-box" by modifying the following files:

Winnt.sif

Hivesys.inf

Txtsetup.sif

File structure on the folder should look like this:

c:\flat\i386\$oem$\$1\drivers\scsi

You will need the following 3rd party drivers:

txtsetup.oem

3rdparty.cat

3rdparty.inf

3rdparty.sys

----------------------- FILE ADDITIONS TO FLAT -----------------------------

\i386\3rdparty.sys

\$oem$\$1\drivers\scsi\<entire contents of scsi driver package:txtsetup.oem,3rdparty.cat, 3rdparty.inf, 3rdparty.sys>

(SO, THE DRIVER (.SYS) FILE SHOULD BE LOCATED IN BOTH THE I386 AND THE $OEM$\$1\DRIVERS\SCSI DIRECTORIES)

------------------------ WINNT.SIF CHANGES-----------------------------------

Verify the following:

[Unattended]

OemPreinstall = Yes

OemPnPDriversPath = "DRIVERS\SCSI"

NT Upgrade = No

Win9xUpgrade = No

DriverSigningPolicy = Ignore

[MassStorageDrivers]

; Rem out all (cdrom should be detected during install process)

[OEMBootFiles]

; Rem out all

[UserData]

ProductID = xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

[GuiUnattended]

OEMSkipRegional=1

OemSkipWelcome=1

------------------------ HIVESYS.INF CHANGES-----------------------------

search HIVESYS.INF for reference to "aic78xx" and copy and paste the aic78xx lines directly below it to revise with our driver name instead, such as:

Copy these:

HKLM,"SYSTEM\CurrentControlSet\Services\aic78xx","ErrorControl",0x00010003,1

HKLM,"SYSTEM\CurrentControlSet\Services\aic78xx","Group",0x00000002,"SCSI miniport"

HKLM,"SYSTEM\CurrentControlSet\Services\aic78xx","Start",0x00010003,4

HKLM,"SYSTEM\CurrentControlSet\Services\aic78xx","Tag",0x00010003,30

HKLM,"SYSTEM\CurrentControlSet\Services\aic78xx","Type",0x00010003,1

HKLM,"SYSTEM\CurrentControlSet\Services\aic78xx\Parameters",,0x00000012

HKLM,"SYSTEM\CurrentControlSet\Services\aic78xx\Parameters\PnpInterface","5",0x00010003,1

and paste and revise as necessary (where "3rdparty" is the correctdrivername):

HKLM,"SYSTEM\CurrentControlSet\Services\3rdparty","ErrorControl",0x00010003,1

HKLM,"SYSTEM\CurrentControlSet\Services\3rdparty","Group",0x00000002,"SCSI miniport"

HKLM,"SYSTEM\CurrentControlSet\Services\3rdparty","Start",0x00010003,4

HKLM,"SYSTEM\CurrentControlSet\Services\3rdparty","Tag",0x00010003,30

HKLM,"SYSTEM\CurrentControlSet\Services\3rdparty","Type",0x00010003,1

HKLM,"SYSTEM\CurrentControlSet\Services\3rdparty\Parameters",,0x00000012

(**See Below**)

HKLM,"SYSTEM\CurrentControlSet\Services\aic78xx\Parameters\PnpInterface","5",0x00010003,1

**ALERT:

HKLM,"SYSTEM\CurrentControlSet\Services\3rdparty\Parameters\PnpInterface","5",0x00010003,1

PLEASE confirm that the value at the end of this line "0x00010003,1" is the same as the REG_DWORD value at the bottom of your 3rdparty.inf file  Search again for aic78xx and you will hit in a different section where you will see:

Copy these lines:

HKLM,"SYSTEM\CurrentControlSet\Services\EventLog\System\aic78xx","EventMessageFile",0x00020002,"%SystemRoot%\System32\IoLogMsg.dll"

HKLM,"SYSTEM\CurrentControlSet\Services\EventLog\System\aic78xx","TypesSupported",0x00010003,7

And paste and revise:

HKLM,"SYSTEM\CurrentControlSet\Services\EventLog\System\3rdparty","EventMessageFile",0x00020002,"%SystemRoot%\System32\IoLogMsg.dll"

**ALERT:

0x00020002 - confirm this number from the value listed in the 3rdparty.inf file under: REG_EXPAND_SZ value

HKLM,"SYSTEM\CurrentControlSet\Services\EventLog\System\3rdparty","TypesSupported",0x00010003,7

**ALERT:

0x00010003 - confirm this number from the value listed in the 3rdparty.inf file under: REG_DWORD value

--------------- TXTSETUP. SIF MODIFICATIONS (ADDITIONS)----------------------

;The specific values for this driver were taken from the driver's

OEMSETUP.INF

(or 3rdparty.inf) file

[SourceDisksFiles]

search for aic78xx.sys and paste the driver name with the same value:

3rdparty.sys = 1,,,,,,3_,4,1 (this value was copied from the aix78xx.sys entry)

[HardwareIdsDatabase]

example:

PCI\VEN_1044&DEV_A501 = "drivername" -

PLEASE NOTE: the PCI\VEN value will vary depending on the driver.

This value can be found from the 3rdparty.sys file, under the manufacturer section with a DeviceDesc% value in the string.

[SCSI.Load]

drivername = drivername.sys,4

[SCSI]

drivername = "Driver Description - SCSI Adapters for Windows 2000 and greater x86"

Burn these files as outlined and you should have a cdrom unattended install that includes 3rd party scsi drivers.

 
========================================
"Anony Mous" <bugg...@buggeroff.com> wrote in message news:3j7nnusb1688b0jtq...@4ax.com...

Anony Mous

unread,
Sep 9, 2002, 5:00:42 PM9/9/02
to
George,

Thanks so much for your help. I can't wait to get started on this.

I appreciate your assistance.

shockwaveriderz-MVP

unread,
Sep 10, 2002, 9:48:17 PM9/10/02
to
Where you been George? B)......you know all of this stuff........where do you think I learned some of what I know? from
YOU!....thanks
"Anony Mous" <bugg...@buggeroff.com> wrote in message news:bu2qnussqi6nsab8g...@4ax.com...

George S. Ellis

unread,
Sep 11, 2002, 8:58:30 AM9/11/02
to
Just really busy. I have W2K and WXP releases that I have been working on,
service pack testing, etc., so not much time for anything else. Thanks for
asking ;-)

"shockwaveriderz-MVP" <shockwa...@hotmail.com> wrote in message
news:uqhsOUTWCHA.1496@tkmsftngp11...

hubereevez

unread,
Sep 16, 2002, 6:47:53 PM9/16/02
to
great,
but....there is absolutly no way to add a mass storage driver from a
booting cd with the winnt.sif and txtsetup.oem solution? Is this the
only solution modifying the txtsetup.sif? so the $oem$ folder isn't
"see" by windows with the cd boot, is it?
thks.....
hubhub

George S. Ellis

unread,
Sep 17, 2002, 7:15:02 AM9/17/02
to
The only reason you would add the device to WINNT.SIF is if you did not want
to support other devices. This method listed allows your installation to
detect the device and move on without prompting. That allows for support of
multiple systems instead of a single device type.

You may want to read up on the $OEM$ configuration in the Deployment Guide.
I am not sure what you mean by being seen. If OEMPreInstall is set in
winnt.sif and the directory is a root directory on the CD, it is seen and
any $$ or $1 items are copied to the local hard drive.

"hubereevez" <huber...@ifrance.com> wrote in message
news:e4cd2c80.02091...@posting.google.com...

hubereevez

unread,
Sep 25, 2002, 2:35:55 PM9/25/02
to
i tried to add a mass storage driver with the winnt.sif and
txtsetup.oem. Adding $oem/scsci and $1/ and $oem/textmode but the
setup dosn't recognize these folder and the text setup abort with an
error (18) from txtsetup.oem in line 1742 oembootdik.c
?????
.....
so i ask me if the way modifying the txtsetup.sif is the only
solution to "adding" a mass storage driver (raid) during boot up....
tks
0 new messages