[Unattended] TXTSETUP.OEM error with nt5x-install

[Nils Østbjerg]

Hi

I've upgraded to version 4.8rc5 a few weeks ago, and it is working like 
a charm, except when I need to select TEXTMODE drivers

After nt5x-install have rebooted the box and it comes up with the blue 
windows installer I get the following error:

  "File TXTSETUP.OEM caused an unexpected error (18) at line 1747 in 
  d:\xpsp\base\boot\setup\oemdisk.c."

Im a bit lost, cause it worked on my old 4.7 installation, and I 
basicaly copied the os dir to the new installation.

Anyone got any good ideas?

The (intel) textdriver is copied to c:\$\TEXTMODE\ but I got no idea 
weather or not that is the right place for it, as I dont got my old 
installation handy.



Nils
-- 
Nils Østbjerg
SAMF-IT, Faculty of Social Sciences, Aalborg University, Denmark

--
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
___
unattended-info mailing list
unattended-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unattended-info

Re: [Unattended] TXTSETUP.OEM, MassStorageDrivers, etc.

[Sebastian Mellmann]

Hello Maurice!

Here is a short description of what I did:

Description on the basis of a Dell Perc 320

1.) 

Load and extract the driver into the desired directory
You should have something like this:

aac.cat
aac.inf
aac.sys
aaccin.dll
aacevt.exe
aacmgt.inf
raiddisk1
txtsetup.oem

Interesting files are .cat, .inf, .sys, .dll, .exe and the txtsetup.oem

2.)

Copy the files .cat, .inf and .sys to $XP_SHARE\i386\$oem$\TEXTMODE

Copy the files .exe, .dll and maybe others to $XP_SHARE\i386\$oem$\$$\OemDir

Copy ALL files to $XP_SHARE\i386\$oem$\Drivers\SCSI
The subdirectory under $oem$ is arbitrary.

Compress ALL .sys files using 'makecab' and copy them to $XP_SHARE\i386

3.)

Modification of the 'txtsetup.sif' file located at $XP_SHARE\i386

Open the 'txtsetup.sif' with your favorite editor and search for the section 
called [SourceDisksFiles].
Add the following lines to this section: 

[SourceDisksFiles]
aac.sys  = 100,,3_,4,1,,,1,4

You've to do this for ALL .sys files.
Since there's only one .sys file for this driver, you only have one line here.

Search for the section called [HardwareIdsDatabase] and add the following:

[HardwareIdsDatabase]
PCI\VEN_9005&DEV_0285&SUBSYS_02871028 = "aac"

Again: There could be more lines like this!
You can find these line inside the 'txtsetup.oem' shipped with the driver.

Next search for [SCSI.load] and add the following line:

[SCSI.Load]
aac = aac.sys,4

Here you also have to add ALL .sys files!

At last search for the [SCSI] section and add the following:

[SCSI]
aac  = "Dell PERC 320/DC SCSI RAID Controller"

You're free to choose a description here!

4.)

Save the txtsetup.sif file and try to boot the windows setup.
You should be able to access your hdd without to press F6 at the beginning.



Something unclear?
Drop me an e-mail.


Sebastian M.

> >
> > If you need to know, what I did just pass me an e-mail.
> >   
> 
> yes of course, i would like to know what you did and how?
> many thanks if you have a little operating text
> ML


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
unattended-info mailing list
unattended-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unattended-info

[Unattended] TXTSETUP.OEM, MassStorageDrivers, etc.

[Sebastian Mellmann]

Hello everyone!

I think everybody who uses unattended for a long time now, knows the problem 
with 3rd party drivers and OEM drivers respectively for SATA/RAID etc..

I've always had a problem with integrating these drivers into unattended and 
also got this problem with unattended-gui (thanks to Mario Gzuk at this point 
for helping me a lot with the unattended-gui version).

First of all I've read the ML article from Patrick 
(http://www.mail-archive.com/unattended-info@lists.sourceforge.net/msg00107.html)
  but that wasn't of any help at all since windows setup always complained 
about missing files or missing entrys in either txtsetup.oem or txtsetup.sif.
I've asked myself several times what I'm doing wrong and how microsoft is 
dealing with this problem, when releasing a new service pack.
How do they integrate massstoragedrivers?

Atfer 'googling' a lot, I've found these article 
(http://www.msfn.org/board/index.php?showtopic=13173) and it worked great for 
me. 
So far I've integrated only a SCSI driver for adaptec controllers, but I'm sure 
this also works for other hardware like intel or nvidia adapters.

If you need to know, what I did just pass me an e-mail.

So far,
Sebastian M.

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
unattended-info mailing list
unattended-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unattended-info

[Unattended] txtsetup.oem

[guillaume]

hi,
i have a small problem when unattended installation start it doesn't 
find txtsetup.oem in TEXTMODE

is it important or not ?
if i put the correct sata driver in $oem$/$1/sata_driver i can forget 
txtsetup.oem ?

because txtsetup.oem is not the same for all computer...
and i must install with unattended a lot of different computer...
thx, bye
Guillaume


---
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
___
unattended-info mailing list
unattended-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unattended-info

Re: [Unattended] TXTSETUP.OEM

[Ryan Nowakowski]

Ron,

There was a thread on the list shortly after my posting about
automatically generating the txtsetup.oem.  I don't know what came of
it.

- Ryan

On Thu, Mar 11, 2004 at 10:46:31AM -0500, Ron Gentile wrote:
> Pat,
> 
> I seem to be having the same problem Ryan is having. I found your reply but I'm 
> still having problems. Let me tell you a little more I have 3 types of servers I 
> want to install Windows on ( HP, Dell, and IBM) each have different mass storage 
> controllers. I can't seam to get the unattend.txt file and the txtsetup.oem to 
> complete the install correctly. I'm including the two files in this email for you to 
> look at. Please see if you can point me in the right direction
> 
> Thanks for your time,
> 
> Ron Gentile
> 
> -------
>   a.. From: Ryan Nowakowski 
>   b.. Subject: [Unattended] TXTSETUP.OEM 
>   c.. Date: Tue, 03 Feb 2004 15:37:19 -0800 
> 
> 
> Hey Folks,
> 
> I'm using unattended to install servers from 3 vendors: IBM, Compaq/HP,
> and Dell.  What is the easiest way to make sure I have all the drivers I
> need for each vendor?  I'd like to be able to install Win2k on any
> server from each of the three vendors.
> 
> What's the best way to generate the combined TXTSETUP.OEM file?
> My current solution goes something like this:
> 
> 1) Try to install the server -  The install breaks due to missing SCSI drivers so...
> 2) Copy all drivers off of the vendor CD into the $OEM directory
> 3) Play around with the txtsetup.oem file
> 4) Try to install the server -  The install breaks due to missing SCSI drivers so...
> 5) goto step 3 until it works
> 
> Does anyone have some sage-like advice regarding my questions above?
> 
> Thanks in advance,
> 
> Ryan
>  
> 
> ---
> Unattend.txt file...
> 
> [Data]
> AutoPartition=1
> UnattendedInstall="Yes"
> 
> [Unattended]
> UnattendMode=FullUnattended
> OemSkipEula=Yes
> FileSystem=ConvertNTFS
> ;** Grow partition sixe by XXGB 
> ExtendOemPartition=4096
> ;***
> OemPreinstall=YES
> TargetPath=\winnt
> DriverSigningPolicy=Ignore
> NtUpgrade=no
> OverwriteOemFilesOnUpgrade=no
> OemFilesPath=f:\I386\$oem$
> 
> 
> [GuiUnattended]
> AdminPassword="password"
> EncryptedAdminPassword=NO
> OEMSkipRegional=1
> TimeZone=35
> OemSkipWelcome=1
> AutoLogon=yes
> AutoLogonCount=1
> 
> [UserData]
> FullName="."
> OrgName="RON"
> ;** Host Name for server being installed 
> ComputerName=test1
> ;
> ProductID=--X-
> 
> [LicenseFilePrintData]
> AutoMode=PerServer
> AutoUsers=5
> 
> [Identification]
> JoinWorkgroup=WORKGROUP
> 
> [Display]
> BitPerPixel=8
> XResolution=800
> YResolution=600
> VRefresh=60
> InstallDriver=1
> AutoConfirm=1
> 
> [GuiRunOnce]
> "c:\pscripts.bat"
> 
> [Networking]
> ;InstallDefaultComponents=Yes
> 
> [MassStorageDrivers]
> 
>  "Dell PERC 2, 2/Si, 3/Si, 3/Di RAID Controllers"=OEM
>  "Smart Array 5i, 532, 5312 Controllers"=OEM
>  "Compaq Smart Array Controllers"=OEM
> 
> [OemBootFiles]
> perc2mgt.inf 
> perc2.inf
> perc2.cat
> perc2.sys
> CPQARRY2.SYS
> CPQCISSM.SYS
> Symmpi.sys
> LsiCsb6.sys
> TXTSETUP.OEM
> 
> 
> ;***NetWork 
> Adapter
> 
> [NetAdapters]
> Adapter1=params.Adapter1
> Adapter2=params.Adapter2
> 
> [params.Adapter1]
> INFID=*
> 
> [NetClients]
> MS_MSClient=params.MS_MSClient
> 
> [NetServices]
> MS_SERVER=params.MS_SERVER
> 
> [NetProtocols]
> MS_TCPIP=params.MS_TCPIP
> 
> [params.MS_TCPIP]
> DNS=No
> UseDomainNameDevolution=No
> EnableLMHo

Re: [Unattended] TXTSETUP.OEM

[mark harburn]

this would be great for us, we have loads of diffrent types of hardware
comming through our place, how about a "pre-parser" to chuck all the
txtsetup.oem files into a single clean one with only the stuff they need,
i.e. dump them in a folder with subdirectories and pull out the relavent
info and mash it into a single clean file bit like the boot disks.
- Original Message - 
From: "Ryan Nowakowski" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, February 04, 2004 10:37 PM
Subject: Re: [Unattended] TXTSETUP.OEM




---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
___
unattended-info mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/unattended-info

Re: [Unattended] TXTSETUP.OEM

[Ryan Nowakowski]

On Wed, Feb 04, 2004 at 02:23:19PM -0500, Patrick J. LoPresti wrote:
> Excellent reference; thank you!  This shows that 12 means
> "$oem$\$$\system32\drivers".
> 
> And now the entire mechanism makes sense.  With this information in
> hand, it should be possible to write the definitive document (and
> automation tool!) for dealing with txtsetup.oem drivers.  Maybe I will
> take a crack at it this weekend...
> 
>  - Pat

This would be a HUGE help for our group since we deal with so many
different SCSI drivers.  I'll be the first to volunteer to test it.

- Ryan


signature.asc
Description: Digital signature

Re: [Unattended] TXTSETUP.OEM

[Patrick J. LoPresti]

Dag Nummedal <[EMAIL PROTECTED]> writes:

> Jordan Share writes:
>
> > Yes, I have read that KB article.  It says, "The correct OEMDIR
> > destination can be found by searching the INF file used to install
> > the device or driver."

Ah.  Well, that is embarrassing.

Would you believe I treated OEMDIR as a constant and it actually
appeared to work?  Which makes no sense; something very strange must
have been going on.

> > .  I have empirically determined that (for one of these files,
> > anyway) "12" corresponds to "$oem$\$$\system32".  (It may also
> > "just work" to have that file in there, due to it being on the
> > path, or some such thing).

The latter, I would guess, since:

> You can find the information you're looking for here:
> 
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/install/hh/install/create-inf_3aav.asp

Excellent reference; thank you!  This shows that 12 means
"$oem$\$$\system32\drivers".

And now the entire mechanism makes sense.  With this information in
hand, it should be possible to write the definitive document (and
automation tool!) for dealing with txtsetup.oem drivers.  Maybe I will
take a crack at it this weekend...

 - Pat


---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
___
unattended-info mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/unattended-info

Re: [Unattended] TXTSETUP.OEM

[Jordan Share]

Dag Nummedal wrote:
Jordan Share writes:
I'd like to find out if anyone has a pointer to the breakdown of what 
each numeric code means.


The destination is defined by the [DestinationDirs] section in the inf file.
You can find the information you're looking for here:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/install/hh/install/create-inf_3aav.asp

Fantastic.  That is exactly what I was looking for.

Jordan

---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
___
unattended-info mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/unattended-info

Re: [Unattended] TXTSETUP.OEM

[Dag Nummedal]

Jordan Share writes:
> Patrick J. LoPresti wrote:
> > He asked a question about dealing with .dll files; I have tried the
> > method documented in KB275334 and it seems to work:
> > 
> >   http://support.microsoft.com/?id=275334
> > 
> > It should be possible to automate these steps, but not at install time
> > because the share is read-only.  Maybe if I get bored one day I will
> > take a crack at it...  Meanwhile, your best bet is trial and error, as
> > you surmised.
> 
> Yes, I have read that KB article.  It says, "The correct OEMDIR 
> destination can be found by searching the INF file used to install the 
> device or driver."
> 
> But, when you search the INF file, it only has numeric codes for the 
> destinations.  I have empirically determined that (for one of these 
> files, anyway) "12" corresponds to "$oem$\$$\system32".  (It may also 
> "just work" to have that file in there, due to it being on the path, or 
> some such thing).
> 
> I'd like to find out if anyone has a pointer to the breakdown of what 
> each numeric code means.

The destination is defined by the [DestinationDirs] section in the inf file.
You can find the information you're looking for here:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/install/hh/install/create-inf_3aav.asp

-- 
Dag Nummedal ([EMAIL PROTECTED])


---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
___
unattended-info mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/unattended-info

Re: [Unattended] TXTSETUP.OEM

[Jordan Share]

Patrick J. LoPresti wrote:
He asked a question about dealing with .dll files; I have tried the
method documented in KB275334 and it seems to work:
  http://support.microsoft.com/?id=275334

It should be possible to automate these steps, but not at install time
because the share is read-only.  Maybe if I get bored one day I will
take a crack at it...  Meanwhile, your best bet is trial and error, as
you surmised.
Yes, I have read that KB article.  It says, "The correct OEMDIR 
destination can be found by searching the INF file used to install the 
device or driver."

But, when you search the INF file, it only has numeric codes for the 
destinations.  I have empirically determined that (for one of these 
files, anyway) "12" corresponds to "$oem$\$$\system32".  (It may also 
"just work" to have that file in there, due to it being on the path, or 
some such thing).

I'd like to find out if anyone has a pointer to the breakdown of what 
each numeric code means.

Jordan

---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
___
unattended-info mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/unattended-info

Re: [Unattended] TXTSETUP.OEM

[Patrick J. LoPresti]

Ryan Nowakowski <[EMAIL PROTECTED]> writes:

> I'm using unattended to install servers from 3 vendors: IBM,
> Compaq/HP, and Dell.  What is the easiest way to make sure I have
> all the drivers I need for each vendor?  I'd like to be able to
> install Win2k on any server from each of the three vendors.
> 
> What's the best way to generate the combined TXTSETUP.OEM file?

Jordan Share gave a pretty good description of this in:

  http://www.mail-archive.com/[EMAIL PROTECTED]/msg00992.html

He asked a question about dealing with .dll files; I have tried the
method documented in KB275334 and it seems to work:

  http://support.microsoft.com/?id=275334

It should be possible to automate these steps, but not at install time
because the share is read-only.  Maybe if I get bored one day I will
take a crack at it...  Meanwhile, your best bet is trial and error, as
you surmised.

You might want to get each driver (with its txtsetup.oem) working by
itself first, then merge them together.

 - Pat


---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
___
unattended-info mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/unattended-info

[Unattended] TXTSETUP.OEM

[Ryan Nowakowski]

Hey Folks,

I'm using unattended to install servers from 3 vendors: IBM, Compaq/HP,
and Dell.  What is the easiest way to make sure I have all the drivers I
need for each vendor?  I'd like to be able to install Win2k on any
server from each of the three vendors.

What's the best way to generate the combined TXTSETUP.OEM file?
My current solution goes something like this:

1) Try to install the server -  The install breaks due to missing SCSI drivers so...
2) Copy all drivers off of the vendor CD into the $OEM directory
3) Play around with the txtsetup.oem file
4) Try to install the server -  The install breaks due to missing SCSI drivers so...
5) goto step 3 until it works

Does anyone have some sage-like advice regarding my questions above?

Thanks in advance,

Ryan


signature.asc
Description: Digital signature

Re: [Unattended] TXTSETUP.OEM and multiple SCSI drivers

[Jordan Share]

Jordan Share wrote:
Wolf wrote:
IMHO you are trying the wrong drivers here.

I've just checked their website and downloaded the (FastTrack 
100-)Drivers and there ist an txtsetup.oem that lists the drivers.

Maybe it helps. Sorry if this is way off. I'm not sure I should have 
written it myself... ;-)


Well, it's possible, but I downloaded these drivers from Intel's 
website, so I expect they'd be correct.  I haven't actually tried 
installing with the floppy version though.

I tried installing from CD with the floppy.  Doesn't find any hard disks.

Woops.  Yep, there are indeed some Promise drivers on Intel's page.

I'll give it a go with the other disks, and try to get the unattended 
thinger to work /after/ getting the normal floppy to work.

*sigh*

Thanks, Wolf. :)

Jordan



---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
___
unattended-info mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/unattended-info

Re: [Unattended] TXTSETUP.OEM and multiple SCSI drivers

[Jordan Share]

Wolf wrote:

Hi,

maybe I got this all wrong, so please bear with me!!
I just read the above mail in the daily digest. I once had a 
FastTrack-Controller.

just as a thought: I have had a Promise FastTrack 100-Controller and it 
would not work with the standard Windows-Drivers. When installing 
manually, you had to press "F6" during the boot process and add the 
drivers disk in order to have access to the disks. I don't remember 
Promise being bought by someone (like Adaptec), so I assume the drivers 
are still from fasttrack and are still called "FASTTRAK.xyz".
IMHO you are trying the wrong drivers here.

I've just checked their website and downloaded the (FastTrack 
100-)Drivers and there ist an txtsetup.oem that lists the drivers.

Maybe it helps. Sorry if this is way off. I'm not sure I should have 
written it myself... ;-)
Well, it's possible, but I downloaded these drivers from Intel's 
website, so I expect they'd be correct.  I haven't actually tried 
installing with the floppy version though.

Jordan

---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
___
unattended-info mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/unattended-info

Re: [Unattended] TXTSETUP.OEM and multiple SCSI drivers

[Wolf]

Von: Jordan Share <[EMAIL PROTECTED]>
Datum: 22. Januar 2004 01:18:45 MEZ
An: Jordan Share <[EMAIL PROTECTED]>
Cc: "Patrick J. LoPresti" <[EMAIL PROTECTED]>,  [EMAIL PROTECTED]
Betreff: Re: [Unattended] TXTSETUP.OEM and multiple SCSI drivers


Jordan Share wrote:
Patrick J. LoPresti wrote:
Jordan Share <[EMAIL PROTECTED]> writes:


I am now trying to get another machine to work.  It has a Promise
RAID chipset built into the motherboard (an Intel S875WP-1E).  I am
able to get the inital file copy to work.  But, when it tries to go
into native win32 mode I get the "INACCESSIBLE_BOOT_DISK" error.

Anyone have pointers on this?



I have never tried this, although I believe it should work in theory.
But I do not know of anybody else who has tried it.

First, lets make sure Unattended is doing its job.  I assume
install.pl correctly offers you the two OEM drivers?

It does offer them both.

Could you send along the [MassStorageDrivers] and [OEMBootFiles]
sections of the generated unattend.txt?

Ok here they are:
[MassStorageDrivers]
"Adaptec Embedded Serial ATA HostRAID Driver For Windows 2000/XP/2003" = OEM

; See comments for [MassStorageDrivers]
[OEMBootFiles]
txtsetup.oem
aarich.cat
aarich.sys
adhraid.inf
readme.txt
3waregsm.cat
adhraid.cat
oemsetup.inf
disk1
3wdrv100.sys
hraidsk1
3wfltdrv.sys
adaptec.inf

Or, as an alternative, you could eliminate the d2 declaration from
[Disks] entirely and use d1 instead of d2 in
[Files.scsi.ADAPTEC_SATARAID_W2K].  This is arguably a better plan,
since what you are really doing is creating a single "disk" with
multiple drivers on it...
I will give this a shot too.

No good.

Jordan


Hi,

maybe I got this all wrong, so please bear with me!!
I just read the above mail in the daily digest. I once had a FastTrack-Controller.

just as a thought: I have had a Promise FastTrack 100-Controller and it would not work with the standard Windows-Drivers. When installing manually, you had to press "F6" during the boot process and add the drivers disk in order to have access to the disks. I don't remember Promise being bought by someone (like Adaptec), so I assume the drivers are still from fasttrack and are still called "FASTTRAK.xyz".
IMHO you are trying the wrong drivers here.

I've just checked their website and downloaded the (FastTrack 100-)Drivers and there ist an txtsetup.oem that lists the drivers.

Maybe it helps. Sorry if this is way off. I'm not sure I should have written it myself... ;-)

cheers

wolf

Re: [Unattended] TXTSETUP.OEM and multiple SCSI drivers

[Jordan Share]

Jordan Share wrote:
Patrick J. LoPresti wrote:

Jordan Share <[EMAIL PROTECTED]> writes:


I am now trying to get another machine to work.  It has a Promise
RAID chipset built into the motherboard (an Intel S875WP-1E).  I am
able to get the inital file copy to work.  But, when it tries to go
into native win32 mode I get the "INACCESSIBLE_BOOT_DISK" error.
Anyone have pointers on this?


I have never tried this, although I believe it should work in theory.
But I do not know of anybody else who has tried it.
First, lets make sure Unattended is doing its job.  I assume
install.pl correctly offers you the two OEM drivers?
It does offer them both.

Could you send along the [MassStorageDrivers] and [OEMBootFiles]
sections of the generated unattend.txt?
Ok here they are:
[MassStorageDrivers]
"Adaptec Embedded Serial ATA HostRAID Driver For Windows 
2000/XP/2003" = OEM

; See comments for [MassStorageDrivers]
[OEMBootFiles]
txtsetup.oem
aarich.cat
aarich.sys
adhraid.inf
readme.txt
3waregsm.cat
adhraid.cat
oemsetup.inf
disk1
3wdrv100.sys
hraidsk1
3wfltdrv.sys
adaptec.inf
Or, as an alternative, you could eliminate the d2 declaration from
[Disks] entirely and use d1 instead of d2 in
[Files.scsi.ADAPTEC_SATARAID_W2K].  This is arguably a better plan,
since what you are really doing is creating a single "disk" with
multiple drivers on it...


I will give this a shot too.
No good.

Jordan




---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
___
unattended-info mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/unattended-info

Re: [Unattended] TXTSETUP.OEM and multiple SCSI drivers

[Jordan Share]

Patrick J. LoPresti wrote:

Jordan Share <[EMAIL PROTECTED]> writes:


I am now trying to get another machine to work.  It has a Promise
RAID chipset built into the motherboard (an Intel S875WP-1E).  I am
able to get the inital file copy to work.  But, when it tries to go
into native win32 mode I get the "INACCESSIBLE_BOOT_DISK" error.
Anyone have pointers on this?


I have never tried this, although I believe it should work in theory.
But I do not know of anybody else who has tried it.
First, lets make sure Unattended is doing its job.  I assume
install.pl correctly offers you the two OEM drivers?
Could you send along the [MassStorageDrivers] and [OEMBootFiles]
sections of the generated unattend.txt?
I manually added a [MassStorageDrivers] and [OEMBootFiles] section to 
the unattend.txt that is in my site directory.

I hadn't realized that install.pl would scan them and create those 
sections.  Let me try removing them and get back to you.

[Disks]
d1 = "3ware Escalade 7000/8000 Series ATA RAID Controller for Windows
2000/XP/2003", \disk1, ""
d2   = "Adaptec Embedded Serial ATA HostRAID Driver Ver 2.00 for
Windows 2000/XP/2003", \disk1, ""


I am not sure it is a good idea to use the same tag file (\disk1) for
both of these "disks".  You might try changing the second one to
\disk2.
Although since neither of those files really exist (do they?), I am
not sure this will help.
Yes, that file exists (it's the one from the 3ware disk, actually) and 
just has some human-readable info about the disk.

I have also tried it with two entries, using \disk1 and \hraidsk1 (which 
came on the Adaptec disk).  No dice.

[Files.scsi.3ware]
driver  = d1, 3wDrv100.sys, 3wDrv100
driver  = d1, 3wFltDrv.sys, 3wFltDrv
inf = d1, oemsetup.inf
catalog = d1, 3waregsm.cat


[snip]


[Files.scsi.ADAPTEC_SATARAID_W2K]
driver  = d2,aarich.sys, aarich
inf = d2,adaptec.inf
inf = d2,adhraid.inf
catalog = d2,aarich.cat


Or, as an alternative, you could eliminate the d2 declaration from
[Disks] entirely and use d1 instead of d2 in
[Files.scsi.ADAPTEC_SATARAID_W2K].  This is arguably a better plan,
since what you are really doing is creating a single "disk" with
multiple drivers on it...
I will give this a shot too.

Jordan



---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
___
unattended-info mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/unattended-info

Re: [Unattended] TXTSETUP.OEM and multiple SCSI drivers

[Patrick J. LoPresti]

Jordan Share <[EMAIL PROTECTED]> writes:

> I am now trying to get another machine to work.  It has a Promise
> RAID chipset built into the motherboard (an Intel S875WP-1E).  I am
> able to get the inital file copy to work.  But, when it tries to go
> into native win32 mode I get the "INACCESSIBLE_BOOT_DISK" error.
> 
> Anyone have pointers on this?

I have never tried this, although I believe it should work in theory.
But I do not know of anybody else who has tried it.

First, lets make sure Unattended is doing its job.  I assume
install.pl correctly offers you the two OEM drivers?

Could you send along the [MassStorageDrivers] and [OEMBootFiles]
sections of the generated unattend.txt?

> [Disks]
> d1 = "3ware Escalade 7000/8000 Series ATA RAID Controller for Windows
> 2000/XP/2003", \disk1, ""
> d2   = "Adaptec Embedded Serial ATA HostRAID Driver Ver 2.00 for
> Windows 2000/XP/2003", \disk1, ""

I am not sure it is a good idea to use the same tag file (\disk1) for
both of these "disks".  You might try changing the second one to
\disk2.

Although since neither of those files really exist (do they?), I am
not sure this will help.

> [Files.scsi.3ware]
> driver  = d1, 3wDrv100.sys, 3wDrv100
> driver  = d1, 3wFltDrv.sys, 3wFltDrv
> inf = d1, oemsetup.inf
> catalog = d1, 3waregsm.cat

[snip]

> [Files.scsi.ADAPTEC_SATARAID_W2K]
> driver  = d2,aarich.sys, aarich
> inf = d2,adaptec.inf
> inf = d2,adhraid.inf
> catalog = d2,aarich.cat

Or, as an alternative, you could eliminate the d2 declaration from
[Disks] entirely and use d1 instead of d2 in
[Files.scsi.ADAPTEC_SATARAID_W2K].  This is arguably a better plan,
since what you are really doing is creating a single "disk" with
multiple drivers on it...

 - Pat


---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
___
unattended-info mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/unattended-info

[Unattended] TXTSETUP.OEM and multiple SCSI drivers

[Jordan Share]

We have a wide variety of machines at my work, and I'd like to be able 
to install them all with the unattended system.

I was able to get the 3ware RAID drivers to work.  That is, I can do an 
unattended install onto machines which have a 3ware RAID card as their 
only harddisk.

I am now trying to get another machine to work.  It has a Promise RAID 
chipset built into the motherboard (an Intel S875WP-1E).  I am able to 
get the inital file copy to work.  But, when it tries to go into native 
win32 mode I get the "INACCESSIBLE_BOOT_DISK" error.

Anyone have pointers on this?

Thanks,
Jordan
What follows are the contents of my txtsetup.oem file (some lines may wrap):
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
[Disks]
d1 = "3ware Escalade 7000/8000 Series ATA RAID Controller for Windows 
2000/XP/2003", \disk1, ""
d2   = "Adaptec Embedded Serial ATA HostRAID Driver Ver 2.00 for Windows 
2000/XP/2003", \disk1, ""

[Defaults]
scsi = ADAPTEC_SATARAID_W2K
[scsi]
3ware = "3ware Escalade 7000/8000 Series ATA RAID Controller"
ADAPTEC_SATARAID_W2K = "Adaptec Embedded Serial ATA HostRAID Driver For 
Windows 2000/XP/2003"

[Files.scsi.3ware]
driver  = d1, 3wDrv100.sys, 3wDrv100
driver  = d1, 3wFltDrv.sys, 3wFltDrv
inf = d1, oemsetup.inf
catalog = d1, 3waregsm.cat
[Config.3wDrv100]
value = "", Group, REG_SZ, "SCSI Miniport"
value = "", Start, REG_DWORD, 0
value = "", Tag,   REG_DWORD, 1
value = "", Type,  REG_DWORD, 1
[Config.3wFltDrv]
value = "", Start, REG_DWORD, 0
value = "", Tag,   REG_DWORD, 1
value = "", Type,  REG_DWORD, 1
[Files.scsi.ADAPTEC_SATARAID_W2K]
driver  = d2,aarich.sys, aarich
inf = d2,adaptec.inf
inf = d2,adhraid.inf
catalog = d2,aarich.cat
[Config.aarich]
value = "", Group, REG_SZ,"SCSI Miniport"
value = "", Start, REG_DWORD, 0
value = "", Tag,   REG_DWORD, 1
value = "", Type,  REG_DWORD, 1
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-



---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
___
unattended-info mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/unattended-info

[Unattended] TXTSETUP.OEM, MassStorageDrivers, etc.

[Patrick J. LoPresti]

Let me tell you a story.

Today I found myself tasked with installing Windows XP on a shiny new
piece of hardware: A Dell Precision 450 with an Ultra320 SCSI card and
a fast SCSI drive.

The only problem is that this SCSI card is new, so XP lacks built-in
support for it.  And Windows has trouble installing itself on a hard
drive which it cannot see.

Microsoft has a mechanism for dealing with this, of course.  It is
called "TXTSETUP.OEM".  You can learn more than you want to know at
,
but the theory is simple.  Your SCSI hardware vendor (in my case,
Dell) gives you a "driver disk" with a txtsetup.oem file at the top.
Shortly after you start an installation, Windows Setup says "Press F6
if you need to install a third party SCSI or RAID driver".  Then you
press F6, insert your driver disk, and everything works fine.

...If you are installing from CD-ROM, that is.  If instead you are
installing from DOS as part of (say) a network install, things are a
tad trickier.

Installing Windows from DOS goes roughly as follows.  You run the DOS
program winnt.exe.  It creates something on your C: drive very much
like a Windows installation CD and then reboots.  Then everything
proceeds much as if you had booted from the Windows CD, right down to
the "Press F6 if you need to install..." prompt.

As a quick and dirty hack, I launched a network installation, waited
for winnt.exe to populate the C: drive, waited for the "Press F6..."
prompt after the reboot, pressed F6, and fed in the Dell driver disk.
Oops, no good.  Setup complained about being unable to find various
.sys, .inf and .cat files.

Well, no matter.  Who wants to sit around every time you install
Windows, anyway?  And "Unattended" is practically my middle name.
Surely I can automate it.

Heck, Microsoft makes it plain as day in a KB article:

http://support.microsoft.com/?kbid=288344

Note step 5 in particular, which suggests that different installation
methods require slightly different txtsetup.oem files.

Let me share with you the relevant lines from the original
txtsetup.oem on the driver disk.  (For clarity, I am omitting the
non-relevant lines of the file, which is to say most of them.)

[Disks]
d3 = "LSI Logic Ultra320 1020/1030 Driver", \symmpi.tag, \WinXP

[scsi]
SYMMPI_XP32 = "LSI Logic Ultra320 1020/1030 Driver (XP 32-bit)",symmpi

[Files.scsi.SYMMPI_XP32]
driver = d3,symmpi.sys,SYMMPI
inf= d3,symmpi.inf
catalog = d3,mpixp32.cat

Here is what this means.

First, the [Disks] section declares a disk named "d3", with a
human-readable description of "LSI Logic Ultra320 1020/1030 Driver", a
tag file of "\symmpi.tag", and a directory of "\WinXP".  That is, this
disk can be recognized by the existence of the file \symmpi.tag, and
the driver files it includes all reside within the \WinXP directory.

Second, the [scsi] section declares a driver ID of "SYMMPI_XP32",
which is the identifier the rest of the file uses to name the driver.
It has a description of "LSI Logic Ultra320 1020/1030 Driver (XP
32-bit)".  It also has magic registry key of "symmpi", but that is not
relevant here.

Finally, the [Files.scsi.SYMMPI_XP32] section defines the files which
comprise the SYMMPI_XP32 driver.  This section says that the driver
proper is on disk d3 in the file symmpi.sys, the inf file is on d3 in
symmpi.inf, and the catalog file is on d3 in mpixp32.cat.  (The extra
SYMMPI at the end of the "driver" line is another registry-related
key.  It is also not relevant here.)

Right.  So, following the KB article's instructions, I edited the d3
line of txtsetup.oem like so:

d3 = "LSI Logic Ultra320 1020/1030 Driver", \symmpi.tag, .

That is, I replaced \WinXP with a dot.

Then I copied all of the driver files, plus txtsetup.oem itself, to
Z:\winxpoem\I386\$oem$\TEXTMODE.  I edited z:\site\unattend.txt to add
these lines:

[MassStorageDrivers]
"LSI Logic Ultra320 1020/1030 Driver (XP 32-bit)" = "OEM"

[OEMBootFiles]
TXTSETUP.OEM
SYMMPI.TAG
MPIXP32.CAT
SYMMPI.INF
SYMMPI.SYS

The [MassStorageDrivers] section says that I want to add a mass
storage driver during text mode setup.  It says to look for the key
"LSI Logic Ultra320 1020/1030 Driver (XP 32-bit)" in the [scsi]
section of txtsetup.oem and to load that driver.

The [OEMBootFiles] section tells winnt.exe to copy TXTSETUP.OEM,
SYMMPI.TAG, MPIXP32.CAT, SYMMPI.INF, and SYMMPI.SYS from
$OEM$\TEXTMODE to the C: drive before rebooting.

This is what the KB article said to do, so I did it.  And it worked
great.

Just kidding!  Actually, it failed miserably.  Well, winnt.exe ran OK.
But shortly after rebooting, Setup bombed like so:

File \$WIN_NT$.~BT\$OEM$\.\SYMMPI.SYS could not be loaded.
The error code is 18

Setup cannot continue.  Press any key to exit.

You see, winnt.exe places several things on your hard drive, including
a directory nam

RE: [Unattended] TXTSETUP.OEM, MassStorageDrivers, etc.

[Scott Card]

Great story.  I enjoyed it thoroughly :).

Cheers,
Scott

(Still fearful of the 2.6 upgrade)

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Patrick J. LoPresti
Sent: Monday, June 30, 2003 10:47 PM
To: [EMAIL PROTECTED]
Subject: [Unattended] TXTSETUP.OEM, MassStorageDrivers, etc.


Let me tell you a story.

Today I found myself tasked with installing Windows XP on a shiny new
piece of hardware: A Dell Precision 450 with an Ultra320 SCSI card and a
fast SCSI drive.

The only problem is that this SCSI card is new, so XP lacks built-in
support for it.  And Windows has trouble installing itself on a hard
drive which it cannot see.

Microsoft has a mechanism for dealing with this, of course.  It is
called "TXTSETUP.OEM".  You can learn more than you want to know at
<http://msdn.microsoft.com/library/en-us/install/hh/install/txtsetup_1wm
q.asp>,
but the theory is simple.  Your SCSI hardware vendor (in my case,
Dell) gives you a "driver disk" with a txtsetup.oem file at the top.
Shortly after you start an installation, Windows Setup says "Press F6 if
you need to install a third party SCSI or RAID driver".  Then you press
F6, insert your driver disk, and everything works fine.

...If you are installing from CD-ROM, that is.  If instead you are
installing from DOS as part of (say) a network install, things are a tad
trickier.

Installing Windows from DOS goes roughly as follows.  You run the DOS
program winnt.exe.  It creates something on your C: drive very much like
a Windows installation CD and then reboots.  Then everything proceeds
much as if you had booted from the Windows CD, right down to the "Press
F6 if you need to install..." prompt.

As a quick and dirty hack, I launched a network installation, waited for
winnt.exe to populate the C: drive, waited for the "Press F6..." prompt
after the reboot, pressed F6, and fed in the Dell driver disk. Oops, no
good.  Setup complained about being unable to find various .sys, .inf
and .cat files.

Well, no matter.  Who wants to sit around every time you install
Windows, anyway?  And "Unattended" is practically my middle name. Surely
I can automate it.

Heck, Microsoft makes it plain as day in a KB article:

http://support.microsoft.com/?kbid=288344

Note step 5 in particular, which suggests that different installation
methods require slightly different txtsetup.oem files.

Let me share with you the relevant lines from the original txtsetup.oem
on the driver disk.  (For clarity, I am omitting the non-relevant lines
of the file, which is to say most of them.)

[Disks]
d3 = "LSI Logic Ultra320 1020/1030 Driver", \symmpi.tag, \WinXP

[scsi]
SYMMPI_XP32 = "LSI Logic Ultra320 1020/1030 Driver (XP
32-bit)",symmpi

[Files.scsi.SYMMPI_XP32]
driver = d3,symmpi.sys,SYMMPI
inf= d3,symmpi.inf
catalog = d3,mpixp32.cat

Here is what this means.

First, the [Disks] section declares a disk named "d3", with a
human-readable description of "LSI Logic Ultra320 1020/1030 Driver", a
tag file of "\symmpi.tag", and a directory of "\WinXP".  That is, this
disk can be recognized by the existence of the file \symmpi.tag, and the
driver files it includes all reside within the \WinXP directory.

Second, the [scsi] section declares a driver ID of "SYMMPI_XP32", which
is the identifier the rest of the file uses to name the driver. It has a
description of "LSI Logic Ultra320 1020/1030 Driver (XP 32-bit)".  It
also has magic registry key of "symmpi", but that is not relevant here.

Finally, the [Files.scsi.SYMMPI_XP32] section defines the files which
comprise the SYMMPI_XP32 driver.  This section says that the driver
proper is on disk d3 in the file symmpi.sys, the inf file is on d3 in
symmpi.inf, and the catalog file is on d3 in mpixp32.cat.  (The extra
SYMMPI at the end of the "driver" line is another registry-related key.
It is also not relevant here.)

Right.  So, following the KB article's instructions, I edited the d3
line of txtsetup.oem like so:

d3 = "LSI Logic Ultra320 1020/1030 Driver", \symmpi.tag, .

That is, I replaced \WinXP with a dot.

Then I copied all of the driver files, plus txtsetup.oem itself, to
Z:\winxpoem\I386\$oem$\TEXTMODE.  I edited z:\site\unattend.txt to add
these lines:

[MassStorageDrivers]
"LSI Logic Ultra320 1020/1030 Driver (XP 32-bit)" = "OEM"

[OEMBootFiles]
TXTSETUP.OEM
SYMMPI.TAG
MPIXP32.CAT
SYMMPI.INF
SYMMPI.SYS

The [MassStorageDrivers] section says that I want to add a mass storage
driver during text mode setup.  It says to look for the key "LSI Logic
Ultra320 1020/1030 Driver (XP 32-bit)" in the [scsi] section of
txtsetup.oem and to load that driver.

The [OEMBootFiles] section tells winnt.exe to copy TXTSETUP.