[Unattended] TXTSETUP.OEM error with nt5x-install

2009-02-03 Thread 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

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

2007-08-10 Thread 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 fi

[Unattended] TXTSETUP.OEM, MassStorageDrivers, etc.

2007-08-09 Thread 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

[Unattended] txtsetup.oem

2006-05-30 Thread 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

Re: [Unattended] TXTSETUP.OEM

2004-03-11 Thread Ryan Nowakowski
> > 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 > > ---

Re: [Unattended] TXTSETUP.OEM

2004-02-05 Thread mark harburn
t 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 Subjec

Re: [Unattended] TXTSETUP.OEM

2004-02-04 Thread 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 (an

Re: [Unattended] TXTSETUP.OEM

2004-02-04 Thread 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 OEM

Re: [Unattended] TXTSETUP.OEM

2004-02-04 Thread 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/lib

Re: [Unattended] TXTSETUP.OEM

2004-02-04 Thread 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 ins

Re: [Unattended] TXTSETUP.OEM

2004-02-03 Thread 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

Re: [Unattended] TXTSETUP.OEM

2004-02-03 Thread 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 vend

[Unattended] TXTSETUP.OEM

2004-02-03 Thread 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

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

2004-01-22 Thread 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...

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

2004-01-22 Thread 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 man

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

2004-01-22 Thread 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: Patri

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

2004-01-21 Thread 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 n

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

2004-01-21 Thread 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 g

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

2004-01-21 Thread 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_

[Unattended] TXTSETUP.OEM and multiple SCSI drivers

2004-01-20 Thread 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 t

[Unattended] TXTSETUP.OEM, MassStorageDrivers, etc.

2003-07-06 Thread 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 in

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

2003-07-05 Thread 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