[Unattended] TXTSETUP.OEM error with nt5x-install
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.
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_9005DEV_0285SUBSYS_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.
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
Re: [Unattended] TXTSETUP.OEM
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
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
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 [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
[Unattended] TXTSETUP.OEM
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
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
Re: [Unattended] TXTSETUP.OEM and multiple SCSI drivers
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 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 [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
Re: [Unattended] TXTSETUP.OEM and multiple SCSI drivers
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
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
