Hi there,
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
TXTSETUP.OEM unexpected error (18)
Started by
Guest_Javier_*
, Jul 20 2003 01:25 AM
30 replies to this topic
MultiQuote
#2
TAMARELLE
-
- Members
-
- 1 posts
Newbie
Posted 09 September 2003 - 05:39 PM
Javier
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
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
#3
Guest_pantic_*
Guest_pantic_*
-
- Guests
Posted 24 October 2003 - 03:08 PM
javier, la razon es que al tener la carpeta/i386/winsxs archivos y subdirectorios con nombres demasiados largos, a la hora de modificar la iso se te acortan los archivos y surge el probrema. Desgraciadamente no he encontrado la solucion. A ver si entre los dos....
Saludos.
Saludos.
#4
Guest_Ken_*
Guest_Ken_*
-
- Guests
Posted 31 October 2003 - 01:04 PM
Can you answer that in english? 
I also have the exact same problem
I also have the exact same problem
#5
Guest_Guest_*
Guest_Guest_*
-
- Guests
Posted 04 November 2003 - 09:56 PM
Bugger add me to the list I have the same problem..
#6
Guest_duma031_*
Guest_duma031_*
-
- Guests
Posted 12 November 2003 - 12:40 PM
It sounds like you have some corrupted disk, got to the vendor's site and you should be able to redownload the files and make your own disk. that should fix the problem.
#7
Guest_Guest_*
Guest_Guest_*
-
- Guests
Posted 12 November 2003 - 12:47 PM
You should be able to extract these files out of the CD that came with those mobos too, look under /DRIVERS/SATA. Dont copy pdfs, they'll just take up space.
#8
Guest_Guest_*
Guest_Guest_*
-
- Guests
#9
Guest_Guest_*
Guest_Guest_*
-
- Guests
Posted 04 December 2003 - 02:31 AM
i've figured it out..
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
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
#10
Guest_Guest_*
Guest_Guest_*
-
- Guests
Posted 04 December 2003 - 03:14 AM
nope.. still it won't recognize.. give up for the night
#11
Guest_Guest_steve_*
Guest_Guest_steve_*
-
- Guests
Posted 09 December 2003 - 01:30 PM
exactly same prob here pulling my hair out please help
#12
Guest_Guest_steve_*
Guest_Guest_steve_*
-
- Guests
Posted 10 December 2003 - 03:05 PM
sorted you have to goto promise web site and download drivers for your hard drive (just look for the driver you want ie tx2pro) unzip and save to floppy then try again this should work as it worked for me. The site was hard to find so this is the address
http://www.promise.c...ownload_eng.asp
http://www.promise.c...ownload_eng.asp
#13
Guest_guest_luq_*
Guest_guest_luq_*
-
- Guests
Posted 14 December 2003 - 01:18 PM
Hi,
could you tell me how did you make it work steve?.. i still cant figur out
could you tell me how did you make it work steve?.. i still cant figur out
#14
Guest_flyHENK@hotmail.com_*
Guest_flyHENK@hotmail.com_*
-
- Guests
Posted 21 December 2003 - 08:24 PM
#15
Guest_flyHENK@hotmail.com_*
Guest_flyHENK@hotmail.com_*
-
- Guests
Posted 21 December 2003 - 08:32 PM
Translated:
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!!
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!!
#16
Guest_flyHENK@hotmail.com_*
Guest_flyHENK@hotmail.com_*
-
- Guests
Posted 23 December 2003 - 06:14 PM
Solution for error:
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
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
#17
Guest_Guest_*
Guest_Guest_*
-
- Guests
Posted 07 January 2004 - 10:05 PM
Hey - I was reading this forum as I had the exact same problem 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 
) then gave it another shot and it worked sweet. Good luck to you's
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 ) then gave it another shot and it worked sweet. Good luck to you's
#18
Guest_Guest_*
Guest_Guest_*
-
- Guests
Posted 10 January 2004 - 01:22 PM
I have my drivers for my Promise Ultra 100 TX2 on a diskette. When booting from the ViProtector 2.01 Desktop CD, it appears to ignore the fact I am hitting F6...any ideas why? I havent tried to modify the CD yet.
#19
Guest_Guest_*
Guest_Guest_*
-
- Guests
Posted 10 January 2004 - 04:45 PM
Problem was because directory name for Emulex LP 9000 was truncated for some reason.I have my drivers for my Promise Ultra 100 TX2 on a diskette. When booting from the ViProtector 2.01 Desktop CD, it appears to ignore the fact I am hitting F6...any ideas why? I havent tried to modify the CD yet.
#20
Guest_kikks_*
Guest_kikks_*
-
- Guests
Posted 11 January 2004 - 08:11 AM
flyHENKEmail Removed, Thank you so much for that fix, it was pure genius.
I have been trying to install that damn raid driver for days. BRAVO
I have been trying to install that damn raid driver for days. BRAVO
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
