Creating an Unattended Windows XP CD - Page 8

Mark_Venture · 09-08-2003, 06:00 PM

Quote:

Originally posted by tamarelle
*****waaaaaaa******

I need a drink

This is HARD

But admit it, its FUN!!!

I love stuff like this... but too bad I too into it to go to sleep... I feel like I'm back in college... give me a problem and I keep at it until its finished, no sleep until its done... Too bad my job is getting in the way

tamarelle · 09-08-2003, 06:11 PM

absolutelly!

I am enjoying this immensely!

I am having huge troubles just getting the raid drivers on the disk even when I press f6 they dont want to load at the installation screen!!

been at this all day

Tam

iMogal · 09-09-2003, 12:31 AM

Quote:

Originally posted by iMogal
So far so good for me, but I get the 'Who will use this computer' window popping up... I enter my user name, and the install continues without interaction... (I'm starting to like this!)

How do you enter the usernames that will use the computer?

BUMP!

tamarelle · 09-09-2003, 07:30 AM

I am having troubles getting the cd to USE my raid drivers.

I tried deleting any mention of raid drivers and just doing it manually but it still refuses to load RAID drivers on my unattended installation cd

so I decided I may as well try to tackle this problem from a stand point of INCLUDING the raid drivers in my installation CD. (DVD in this case this thing is big).

I NEED SOMEONE WHO HAS

A P4C800 DELUXE
USES PROMISE RAID
AND YOU ARE INSTALLING RAID SUCCESSFULLY FROM YOUR NEW UNATTENDED WINDOWS XP CD. (NO PRESSING F6)

CAN YOU POST YOUR TXTSETUP.OEM file?
CAN YOU POST YOUR WINNT.SIF file??

Any help we be so appreciated.

I keep getting the messages that indicate the syntax is wrong in my txtsetup.oem. I don't think that is the problem per se because an expert guided me in creating my txtsetup.oem file.

Thanks

Tamara

And

BKA · 09-09-2003, 08:34 AM

Quote:

Originally posted by tamarelle
I am having troubles getting the cd to USE my raid drivers.

I tried deleting any mention of raid drivers and just doing it manually but it still refuses to load RAID drivers on my unattended installation cd

so I decided I may as well try to tackle this problem from a stand point of INCLUDING the raid drivers in my installation CD. (DVD in this case this thing is big).

I NEED SOMEONE WHO HAS

A P4C800 DELUXE
USES PROMISE RAID
AND YOU ARE INSTALLING RAID SUCCESSFULLY FROM YOUR NEW UNATTENDED WINDOWS XP CD. (NO PRESSING F6)

CAN YOU POST YOUR TXTSETUP.OEM file?
CAN YOU POST YOUR WINNT.SIF file??

Any help we be so appreciated.

I keep getting the messages that indicate the syntax is wrong in my txtsetup.oem. I don't think that is the problem per se because an expert guided me in creating my txtsetup.oem file.

Thanks

Tamara

And

I have yet to get my RAID driver on the promise controller loaded. I get the same error 18. According to this site, error (18) is related to the directory that is ouline in the first line of the txtsetup.oem file.

I tried almost everything I could but no luck. I didn't have the "IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL" line under [MassStorageDrivers] section. So let me know if it works for you.

If I was a person who has headaches, I'm sure this would have problem would have given me one.

tamarelle · 09-09-2003, 09:06 AM

Hi bka4u2c

I am about to try another configuration.

I was thinking that its the syntax or perhaps the numbering system on the [Files.scsi.FastTrak_TX2K_xp] section or a syntax error in that section.

I will check that site out. Perhaps there is a header that is needed in the txtsetup.oem file?

I will test the masstoragedriver thing in a minute after this test.

Keep me updated too

Tam

Quote:

Originally posted by bka4u2c
I have yet to get my RAID driver on the promise controller loaded. I get the same error 18. According to this site, error (18) is related to the directory that is ouline in the first line of the txtsetup.oem file.

I tried almost everything I could but no luck. I didn't have the "IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL" line under [MassStorageDrivers] section. So let me know if it works for you.

If I was a person who has headaches, I'm sure this would have problem would have given me one.

tamarelle · 09-09-2003, 11:55 AM

I changed the configuration of the txtsetup.oem file and now its at least trying to load the files but I stil get that message at the point when you normally load the RAID drivers, BUT it allows me to continue........ but when its ready to give me a choice where to install I get an error screen with the following message:

"The manufacturer provided file this setup is trying to use is corrupted or invalid. Line 3 contains a syntax error".

I am assuming this refers to the txtsetup.oem file.

Here is my reconfigured txtsetup.oem file:

................................................................................
[Disks]
d1 = WinXP Promise FastTrak 376/378 (tm) Controller", fasttx2k,.

[Default]
scsi = FastTrak_TX2K_xp

[scsi]
FastTrak_TX2K_xp = "WinXP Promise FastTrak 376/378 (tm) Controller", fasttx2k

[Files.scsi.FastTrak_TX2K_xp]
driver = d1, fasttx2k.sys, fasttx2k,.
inf = d1, fasttx2k.INF,.
catalog= d1, Fasttx2k.cat,.

[HardwareIds.scsi.FastTrak_TX2K_xp]
id="PCI\VEN_105A&DEV_3376", "fasttx2k",.
id="PCI\VEN_105A&DEV_3373", "fasttx2k",.

[Config.fasttx2k]
value = "", Tag, REG_DWORD, 1
...............................................................................

as you can see I have eliminated the "\" at the end and replaced it with ".,"

as one of the sources that I read says that the "\" directs the program to look into a floppy drive.

The person who created the webpage said that he uses the "\" at the end of the line because it works for him but we must bear in mind he is using windows 2000, and that he doing a NETWORK install NOT an install from a CD.

Still its all a shot in the dark for me and I will just keep plugging away and maybe in a year or so I'll get it

AS always, any help would be appreciated greatly

Cheers

Tam

tamarelle · 09-09-2003, 11:56 AM

oh ...

I assumed line 3 would be "[Defaults]" so I changed it to "[Default]" but it made no difference I still get the same error message.

Tam

BKA · 09-09-2003, 02:17 PM

Quote:

Originally posted by tamarelle
oh ...

I assumed line 3 would be "[Defaults]" so I changed it to "[Default]" but it made no difference I still get the same error message. "The manufacturer provided file this setup is trying to use is corrupted or invalid. Line 3 contains a syntax error".

Tam

It looks like you might be onto something there. I wish I had time to help you out with trial and error but work has picked up lately. You've past the point where I left off, so eventually you'll figure it out.

tamarelle · 09-09-2003, 04:15 PM

I found this on the net

....................................................................................
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.

...............................................................................................

so it looks like a file named txtsetup.sif in the i386 folder needs to have some changes made to it also to get the scsi/raid files to load for un unnattended install.

I am checking it out, and I did find that there is indeed a txtsetup.sif file in place in the i386 folder so this may be the key to our problems!

Tam

FB · 09-10-2003, 01:12 AM

Not that it relates to your driver issues, i am almost done with my install stuff. all i have to do is get the drivers setup and ready and then burn i think.

How do i test? just run it

wildmage · 09-10-2003, 04:24 AM

Testing using Connectix Virtual PC saves all the hassles ...

tamarelle · 09-10-2003, 12:01 PM

Mark were you ever able to get it to boot using your PROMISE RAID drivers on the CD? Or are you still having to press f6?

Right now I am putting the ONBOARD RAID on the back burner and I created a cd with no reference to my promise controllerat all but I still get a message it can't load fastt2k.sys

Quote:

Originally posted by Mark_Venture
But admit it, its FUN!!!

I love stuff like this... but too bad I too into it to go to sleep... I feel like I'm back in college... give me a problem and I keep at it until its finished, no sleep until its done... Too bad my job is getting in the way

tamarelle · 09-12-2003, 03:11 PM

Sadly, I cannot get my Windows CD to preinstall RAID. In fact, to be able to install the RAID at ALL I have to turn OEMPREINSTALL to NO.

This of course pretty much stops everything but the winnt.sif from doing its job.

Tam

FB · 09-12-2003, 03:17 PM

i should really finish mine

gotta finish my case first

09-08-2003, 06:11 PM	#107
tamarelle talented amateur Join Date: Feb 2001 Location: Paris, France and Florida Posts: 3,265	absolutelly! I am enjoying this immensely! I am having huge troubles just getting the raid drivers on the disk even when I press f6 they dont want to load at the installation screen!! been at this all day Tam
(Offline)

09-09-2003, 07:30 AM	#109
tamarelle talented amateur Join Date: Feb 2001 Location: Paris, France and Florida Posts: 3,265	I NEED YOUR STUFF MAN I am having troubles getting the cd to USE my raid drivers. I tried deleting any mention of raid drivers and just doing it manually but it still refuses to load RAID drivers on my unattended installation cd so I decided I may as well try to tackle this problem from a stand point of INCLUDING the raid drivers in my installation CD. (DVD in this case this thing is big). I NEED SOMEONE WHO HAS A P4C800 DELUXE USES PROMISE RAID AND YOU ARE INSTALLING RAID SUCCESSFULLY FROM YOUR NEW UNATTENDED WINDOWS XP CD. (NO PRESSING F6) CAN YOU POST YOUR TXTSETUP.OEM file? CAN YOU POST YOUR WINNT.SIF file?? Any help we be so appreciated. I keep getting the messages that indicate the syntax is wrong in my txtsetup.oem. I don't think that is the problem per se because an expert guided me in creating my txtsetup.oem file. Thanks Tamara And
(Offline)

09-09-2003, 11:55 AM	#112
tamarelle talented amateur Join Date: Feb 2001 Location: Paris, France and Florida Posts: 3,265	I changed the configuration of the txtsetup.oem file and now its at least trying to load the files but I stil get that message at the point when you normally load the RAID drivers, BUT it allows me to continue........ but when its ready to give me a choice where to install I get an error screen with the following message: "The manufacturer provided file this setup is trying to use is corrupted or invalid. Line 3 contains a syntax error". I am assuming this refers to the txtsetup.oem file. Here is my reconfigured txtsetup.oem file: ................................................................................ [Disks] d1 = WinXP Promise FastTrak 376/378 (tm) Controller", fasttx2k,. [Default] scsi = FastTrak_TX2K_xp [scsi] FastTrak_TX2K_xp = "WinXP Promise FastTrak 376/378 (tm) Controller", fasttx2k [Files.scsi.FastTrak_TX2K_xp] driver = d1, fasttx2k.sys, fasttx2k,. inf = d1, fasttx2k.INF,. catalog= d1, Fasttx2k.cat,. [HardwareIds.scsi.FastTrak_TX2K_xp] id="PCI\VEN_105A&DEV_3376", "fasttx2k",. id="PCI\VEN_105A&DEV_3373", "fasttx2k",. [Config.fasttx2k] value = "", Tag, REG_DWORD, 1 ............................................................................... as you can see I have eliminated the "\" at the end and replaced it with ".," as one of the sources that I read says that the "\" directs the program to look into a floppy drive. The person who created the webpage said that he uses the "\" at the end of the line because it works for him but we must bear in mind he is using windows 2000, and that he doing a NETWORK install NOT an install from a CD. Still its all a shot in the dark for me and I will just keep plugging away and maybe in a year or so I'll get it AS always, any help would be appreciated greatly Cheers Tam
(Offline)

09-09-2003, 11:56 AM	#113
tamarelle talented amateur Join Date: Feb 2001 Location: Paris, France and Florida Posts: 3,265	oh ... I assumed line 3 would be "[Defaults]" so I changed it to "[Default]" but it made no difference I still get the same error message. Tam
(Offline)

09-09-2003, 04:15 PM	#115
tamarelle talented amateur Join Date: Feb 2001 Location: Paris, France and Florida Posts: 3,265	I found this on the net .................................................................................... 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. ............................................................................................... so it looks like a file named txtsetup.sif in the i386 folder needs to have some changes made to it also to get the scsi/raid files to load for un unnattended install. I am checking it out, and I did find that there is indeed a txtsetup.sif file in place in the i386 folder so this may be the key to our problems! Tam
(Offline)

09-10-2003, 01:12 AM	#116
FB Re-Retiring Join Date: Sep 2002 Location: MN, USA Posts: 24,834	Not that it relates to your driver issues, i am almost done with my install stuff. all i have to do is get the drivers setup and ready and then burn i think. How do i test? just run it __________________ Bye Bye ABXZone.....Rest In Peace.
(Offline)

09-10-2003, 04:24 AM	#117
wildmage Registered User Join Date: Apr 2001 Location: Canberra, ACT, Australia Posts: 135	Testing using Connectix Virtual PC saves all the hassles ...
(Offline)

09-12-2003, 03:11 PM	#119
tamarelle talented amateur Join Date: Feb 2001 Location: Paris, France and Florida Posts: 3,265	Sadly, I cannot get my Windows CD to preinstall RAID. In fact, to be able to install the RAID at ALL I have to turn OEMPREINSTALL to NO. This of course pretty much stops everything but the winnt.sif from doing its job. Tam
(Offline)

09-12-2003, 03:17 PM	#120
FB Re-Retiring Join Date: Sep 2002 Location: MN, USA Posts: 24,834	i should really finish mine gotta finish my case first __________________ Bye Bye ABXZone.....Rest In Peace.
(Offline)

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode