Unsolved
This post is more than 5 years old
12 Posts
0
82529
October 19th, 2004 07:00
The file usbehci.sys is missing or corrupt (Slipstream SP2)
P/N: 1R594
I followed the instructions given to slipstream SP2 with my original XP CD (without SP1). I had the problem where it said i can not integrate these files because the updates are already installed. Therefore as recommended i deleted the SVSPACK folder in the i386 folder. In total i deleted the following files:
SVCPack (within the i386 folder)
SVC**.dl_
SVSpack.ini
i cant remember the middle file's name. I burnt this onto CD and tested it. 2 minutes into loading it says "The file usbehci.sys is missing or corrupt", press any key to continue. Pressing any key just forces the process to restart.
SVCPack (within the i386 folder)
SVC**.dl_
SVSpack.ini
i cant remember the middle file's name. I burnt this onto CD and tested it. 2 minutes into loading it says "The file usbehci.sys is missing or corrupt", press any key to continue. Pressing any key just forces the process to restart.
How could i slipstream this disk without the errors? i tested this on a Virtual PC.
No Events found!



1Bowtie
723 Posts
0
October 19th, 2004 13:00
Hi Lto
You don't delete the whole folder, just one file SVCPACK.inf then it will integrate fine.
LtoThaY
12 Posts
0
October 19th, 2004 16:00
LtoThaY
12 Posts
0
October 19th, 2004 20:00
jamieP
4 Posts
0
October 20th, 2004 11:00
Hi all!!!! I had this problem too. Ive slipstreamed my disk perfectly and upon installing with my new shiny disk i receive the same error "The file usbehci.sys is missing or corrupt".
Anyone got any idea on how to resolve this?
Thank you
JRosenfeld
2 Intern
•
4.4K Posts
0
October 20th, 2004 13:00
First thing to check is whether usbehci.sy_ is in the I386 folder of the slipstreamed CD. It should be 11,188 bytes, dated 3 August 2004. If it is not, then that is the problem; possibly something went wrong with the slipstream.
If it is there, try expand it to a temp folder (assuming that you have a working XP system) to usbehci.sys (start, run, type
expand x:\I386\usbehci.sy_ C:\temp\usbehci.sys [space between expand and X and between _ and C; X is your CD drive letter, C:\temp is the suggested destination folder: change to suit]
The expanded file should be 26,624 bytes, version 5.1.2600.2180. If it expands correctly, it should not be corrupted, I think. When I do that from my slipstreamed CD the expanded file has the same properties as the version installed on my system (c:\Windows\System32\drivers) when I installed SP2 over XP SP1.
usbehci.sys is the EHCI eUSB Miniport Driver, used by USB2 enhanced host controller.
If the file is there and it apparently expanded correctly, then I don't know what could be causing the problem. If it will let you, you could try continuing with the install, then sort out the USB problem later, perhaps by using the file from your original XP disk. (your USB ports may not work without the file: use SP2 mouse and keyboard).
jamieP
4 Posts
0
October 20th, 2004 14:00
-Friendlyname-
2 Intern
•
858 Posts
0
October 20th, 2004 23:00
Lto and Jamie,
I'm sorry to be the bearer of bad news, but you have the infamous IR594 CD. It had not been amenable to a slipstream of SP1, and no remedy had ever been discovered.
See the test done by Dell-Karell.
http://forums.us.dell.com/supportforums/board/message?board.id=sw_winxp&message.id=43165
This failure may be the case with SP2 or any other slipstream on it. Having said that, I hope someone will be able to solve the problem. I have the same CD. :smileysad:
Regards,
Jane:
Message Edited by -Friendlyname- on 10-20-2004 08:22 PM
pc_rose
2 Posts
0
December 3rd, 2004 08:00
Hi,
For all of you with this problem I had a similar problem. Having slipstreamed my re-installation disc to SP2 I used it to install the Recovery Console. When I attempted to load the Recovery Console I was greeted with this same message. On a thorough review of the cmdcons directory I discovered that the version of ntkrnlmp.exe was version 5.1.2600.31 and should have been version 5.1.2600.2180.
You can find the current version on any upgraded SP2 XP in directory Drivers. To resolve my problem it was a case of removing the old ntkrnlmp.exe file and replacing it with the new one. I ran up Recovery Console successfully. No corrupt usbehci.sys!
For the slipstreamed disc I suspect the same problem. So before burning the disc replace the ntkrnlmp.exe with the new one and I suspect you will be okay. I intend to re-burn my slipstream disc this weekend.
For those who have the Windows Resource Kit Tools you can work around the svcpack.ini file problem by using the compress command:-
compress /r svcpack.ini
This will create a file svcpack.in_ which avoids the error during the the slipstream process. This file is not updated or anything so I think it is a matter of having the file there for the call to expand to work during the slipstreaming process.
If anybody gets to the point that they try a re-installation I would be interested to here.
LtoThaY
12 Posts
0
December 3rd, 2004 10:00
pc_rose
2 Posts
0
December 4th, 2004 11:00
I was about to start my slipstream again but before starting checked the folder on my first slipstreamed attempt for the state of the ntkrnlmp file and as expected it was the old version, however there ar 2 other nt exe files which are also at the incorrect version ntkrnlpa and ntkrpamp 5.1.2600.31 instead of 5.1.2600.2180. Before I redo my slipstream disc I am going to check the files on the disk that have not been upgraded to see if they should have been and I will post a message on the forum as to my findings.
Regards
Peter