Post by: Javier on July 20, 2003, 02:25:28 AM
I'm trying to add the driver of the NIC in my PC to the product CD I got with Drive Image 7.0 in order to have it finding the network when booting the PowerQuest Recovery Environment.
I followed PQ guidance of doing an image of the CD using WinISO last version, add the WinXP NIC drivers files to INF and DRIVERS folders, saving it and re-making the CD.
But when I try to boot from the CD, I get the message: "TXTSETUP.OEM caused an unexpected error (18) at line 1742 in d:\xpsp1\base\boot\setup\oemdisk.c." "press any key to continue" and then, "press any key to restart the computer" and the booting is stopped and the computer restarted.
Of course, the product CD without making any modification works fine.
Any idea of help?
Thanks. Javier
Post by: TAMARELLE on September 09, 2003, 06:39:47 PM
Did you ever find a resolution to your problem? I have the exact same problem now trying to install my raid I get the EXACT message and message code 18.
Anybody?
Tam, a fair haired newbie
Post by: pantic on October 24, 2003, 04:08:39 PM
Saludos.
Post by: Ken on October 31, 2003, 02:04:12 PM
/laugh.gif\' class=\'bbc_emoticon\' alt=\':lol:\' /> I also have the exact same problem
Post by: Guest on November 04, 2003, 10:56:09 PM
/sad.gif\' class=\'bbc_emoticon\' alt=\':(\' />
Post by: duma031 on November 12, 2003, 01:40:50 PM
Post by: Guest on November 12, 2003, 01:47:50 PM
Post by: Guest on December 04, 2003, 03:14:09 AM
testing it out myself
Post by: Guest on December 04, 2003, 03:31:02 AM
becareful.. in txtsetup.oem ..
[Files.scsi.FastTrak133_xp2]
driver = d1, Fasttrak.sys, Fasttrak
inf = d1, Fasttrak.inf
the d(x) after = sign HAS to match d(x) under [Disks] section
default for Fastrak mb133 lite is d1 under disk section and d4 under files.scsi section.. this is where i spent 5 hours figuring out what da heck went wrong.
as for the section 18 error, i've got it when i put those [Massive Drive] section under winnt.sif instead of UNATTEND.txt
Post by: Guest on December 04, 2003, 04:14:37 AM
Post by: Guest_steve on December 09, 2003, 02:30:14 PM
Post by: Guest_steve on December 10, 2003, 04:05:20 PM
http://www.promise.com/support/download/do...ownload_eng.asp (http://\"http://www.promise.com/support/download/download_eng.asp\")
Post by: guest_luq on December 14, 2003, 02:18:56 PM
could you tell me how did you make it work steve?.. i still cant figur out
/dry.gif\' class=\'bbc_emoticon\' alt=\'<_<\' /> /sad.gif\' class=\'bbc_emoticon\' alt=\':(\' />
Post by: [email protected] on December 21, 2003, 09:24:47 PM
That is where I found the solution in French.
Post by: [email protected] on December 21, 2003, 09:32:56 PM
This error is caused by the file WINPEOEM.SIF in \I386\SYSTEM32 on the Drive Image 7 CD.
With a txt-editor put a ; sign in front of each line where it is not. (I gues it is the same as deleting the line)
Safe the modified WINPEOEM.SIF
Burn with a proper bootimage and you're done!!
/cool.gif\' class=\'bbc_emoticon\' alt=\'B)\' />
Post by: [email protected] on December 23, 2003, 07:14:58 PM
TXTSETUP.OEM caused an unexpected error (18) at line 1742 in d:\xpsp1\base\boot\setup\oemdisk.c
In dir \I386\SYSTEM32 of the VPRO200P CD there is a file called: WINPEOEM.SIF
You can open this file with NOTEPAD.EXE.
The name "EMULEX_LIGHTPULSE_9000_FIBRE_AD" in the line:
OemDriverDirs=OEM_IBM_ServeRAID_4LX, EMULEX_LIGHTPULSE_9000_FIBRE_AD, LSI_Logic_PCI_SCSI, VMWare_SCSI, Dell_PERC_RAID
is too long. Change this in a name with a max length of 31 characters.
Lets say
OemDriverDirs=OEM_IBM_ServeRAID_4LX, EMULEX_NEW_NAME, LSI_Logic_PCI_SCSI, VMWare_SCSI, Dell_PERC_RAID
You also have to rename a directory where "EMULEX_LIGHTPULSE_9000_FIBRE_AD" was pointing to.
So change \I386\SYSTEM32\DRIVERS\ADDITIONAL_OEM\EMULEX_LIGHTPULSE_9000_FIBRE_AD in
\I386\SYSTEM32\DRIVERS\ADDITIONAL_OEM\EMULEX_NEW_NAME
Burn the cd with a proper bootimage, ISO level 2, long Joilet names and it should work.
I do not know why this error does not happen with the original cd.
I also added additional RAID drivers on the cd so I do not have to push F6 during booting for my pc.
Make a new directory with a name of your choice in \I386\SYSTEM32\DRIVERS\ADDITIONAL_OEM.
Copy the following files in that directory:
\WINXP\*.* or \WIN2K_XP\*.* on the driver-floppy
TXTSETUP.OEM in the root directory of the floppy.
Edit TXTSETUP.OEM in such a way that there are no references to other operating systems like Win98.
E.g. I added a Gigabyte RAID driver. The original TXTSETUP.OEM of the driver floppy was:
#
# TXTSETUP.OEM for IT8212 ATA RAID Controller
#
[Disks]
d1 = "ITE IT8212 ATA RAID Driver Diskette", \ITERAID, \
d2 = "ITE IT8212 ATA RAID Driver Diskette", \ITERAID, \WINNT
d3 = "ITE IT8212 ATA RAID Driver Diskette", \ITERAID, \WIN2K_XP
[Defaults]
scsi = ITERAID_2000
[scsi]
ITERAID_NT = "ITE IT8212 ATA RAID Controller (Windows NT)", ITERAID
ITERAID_2000 = "ITE IT8212 ATA RAID Controller (Windows 2000/XP)", ITERAID
[Files.scsi.ITERAID_NT]
driver = d2, iteraid.sys, ITERAID
inf = d2, iteraid.inf
[Files.scsi.ITERAID_2000]
driver = d3, iteraid.sys, ITERAID
inf = d3, iteraid.inf
[HardwareIds.scsi.ITERAID_NT]
id = "PCI\VEN_1283&DEV_8212","ITERAID"
[HardwareIds.scsi.ITERAID_2000]
id = "PCI\VEN_1283&DEV_8212","ITERAID"
[Config.ITERAID_NT]
value = "", Tag, REG_DWORD, 1
value = "Parameters\PnpInterface", 5, REG_DWORD, 1
[Config.ITERAID_2000]
value = "", Tag, REG_DWORD, 1
value = "Parameters\PnpInterface", 5, REG_DWORD, 1
I changed that to:
#
# TXTSETUP.OEM for IT8212 ATA RAID Controller
#
[Disks]
d1 = "ITE IT8212 ATA RAID Driver Diskette", \ITERAID, \
[Defaults]
scsi = ITERAID_2000
[scsi]
ITERAID_2000 = "ITE IT8212 ATA RAID Controller (Windows 2000/XP)", ITERAID
[Files.scsi.ITERAID_2000]
driver = d1, iteraid.sys, ITERAID
inf = d1, iteraid.inf
[HardwareIds.scsi.ITERAID_2000]
id = "PCI\VEN_1283&DEV_8212","ITERAID"
[Config.ITERAID_2000]
value = "", Tag, REG_DWORD, 1
value = "Parameters\PnpInterface", 5, REG_DWORD, 1
I did the same for my MSI motherbord with RAID
/blink.gif\' class=\'bbc_emoticon\' alt=\':blink:\' />
Post by: Guest on January 07, 2004, 11:05:49 PM
/sad.gif\' class=\'bbc_emoticon\' alt=\':(\' /> It turns out I was trying to install the wrong driver off the disk that came with it - doh! So made sure I had the correct driver (reading the manual /biggrin.gif\' class=\'bbc_emoticon\' alt=\':D\' /> ) then gave it another shot and it worked sweet. Good luck to you's
Post by: Guest on January 10, 2004, 02:22:40 PM
Post by: Guest on January 10, 2004, 05:45:28 PM
Problem was because directory name for Emulex LP 9000 was truncated for some reason.
Post by: kikks on January 11, 2004, 09:11:32 AM
I have been trying to install that damn raid driver for days. BRAVO
Post by: Guest on March 25, 2004, 09:50:13 PM
/mad.gif\' class=\'bbc_emoticon\' alt=\':angry:\' /> Help!!!When I turn on my comp. it says(a problem has been detected & windows has shut down). HP sent me the recovery disk and it does not work. I have talked to them seven times with no luck at all. I have windows xp.
Post by: KillerElite on April 08, 2004, 09:16:02 PM
Thx
Post by: seansplayin on April 20, 2004, 08:15:16 AM
Post by: Guest_Max on August 16, 2004, 07:32:12 AM
I have the problem too : txtsetup.oem caused an unexpected error (18) at line 1742 in d:\xpsp1\base\boot\setup\oemdisk.c
I am not so much into computers, is there an easyer way to solve the problem ?
(a fix or something)
Cheers Max
Post by: Guest_Darren on August 17, 2004, 05:52:12 AM
/sad.gif\' class=\'bbc_emoticon\' alt=\':(\' /> It turns out I was trying to install the wrong driver off the disk that came with it - doh! So made sure I had the correct driver (reading the manual /biggrin.gif\' class=\'bbc_emoticon\' alt=\':D\' /> ) then gave it another shot and it worked sweet. Good luck to you's[/quote]Pile of Pants, what a nightmare this turned out to be.
/ohmy.gif\' class=\'bbc_emoticon\' alt=\':o\' />
Post by: Guest_Kris on September 24, 2004, 11:18:17 PM
File \win2k_xp\interaid.sys caused an unexpected error ( 18 ) at line 2113 in D:\xpsprtm\base\boot\setup\oemdisk.c.
IS there a certain driver version to install xp ( I used disk didnt work ) even downloaded most recent from gigabyte's site ... no luck....
Post by: rayce00 on December 10, 2004, 02:37:53 PM
/mad.gif\' class=\'bbc_emoticon\' alt=\':angry:\' />
Post by: Taras on December 16, 2004, 02:37:57 PM
When I've read it, and when I compare the error number (18) with the
line number in txtsetup.oem, I found there a long string (longer then 31 byte),
so I edit my winnt.sif, vendor's txtsetup.oem, recreate an CD...
Maybe it'll be work... :-(
Post by: rayce00 on December 16, 2004, 04:54:31 PM
Let me know if your fix works. Is the XP burner enough for reburning? And what edits did you make?
Post by: rayce00 on December 16, 2004, 06:02:43 PM
/unsure.gif\' class=\'bbc_emoticon\' alt=\':unsure:\' />
Post by: IT on Demand on February 03, 2006, 02:26:47 AM