"usbehci.sys could not be found"
"usbehci.sys could not be found"
I am getting an error "The file usbehci.sys could not be found" when I try to install from a CD. I used RVM_Integrator_1.4.3 and RVMUpdatePack2.1.11. I am sure I am doing something wrong but I have not been able to figure it out. I have read over the instructions.
- runningfool87
- Posts: 324
- Joined: Wed Apr 18, 2007 2:43 pm
Install this: http://www.nullriver.com/index/products/winmd5sum
And make sure the MD5 sum of the update pack file is this: 2A1534598304646757CFE6D8C6F0F221
Even if the file exists and there are no read errors on the CD, XP setup may also say that corrupt files are missing.
And make sure the MD5 sum of the update pack file is this: 2A1534598304646757CFE6D8C6F0F221
Even if the file exists and there are no read errors on the CD, XP setup may also say that corrupt files are missing.
If I had to wager a guess, I'd go with a bad CD
Get up to $200 off on hosting from the same people who host this website!
http://www.ryanvm.net/forum/viewtopic.php?t=2357
http://www.ryanvm.net/forum/viewtopic.php?t=2357
-
- Posts: 506
- Joined: Sun Feb 26, 2006 4:13 am
along the lines of the "bad cd" answer.. i found that if i am not carefull making my disc i sometimes forget to check nero's settings before actually burning.. it recently changed (or i just noticed, whichever!) nero now defaults to track-at-once instead of disc-at-once.. which of course for me, gives the same damn error that you report, missing files that ARE there 
anyhoo.. just something else to check.. (make sure that you have it set to disc-at-once if you use nero! )
TechnoHunter

anyhoo.. just something else to check.. (make sure that you have it set to disc-at-once if you use nero! )
TechnoHunter
That is a recurring problem. It is because it is not all caps. Change it to all caps USBEHCI.SY_ and the problem will go away. Same goes for the WIN51IP.SP2 file on the cd root.
For whatever reason some sp2 slipstreams do this. I have a script that changes those for me after slipstream. Worth mentioning the same thing happens in home vesions too.
I use grub4dos as my loader, and use mkisofs to create my image. Then I burn with whatever app that burns images. Strangely enough I have found that I have to use Lupas to change all files needed during text mode install to uppercase or they will not be found. Within windows the problem does not exist. Go figure.
MrWoo
For whatever reason some sp2 slipstreams do this. I have a script that changes those for me after slipstream. Worth mentioning the same thing happens in home vesions too.
I use grub4dos as my loader, and use mkisofs to create my image. Then I burn with whatever app that burns images. Strangely enough I have found that I have to use Lupas to change all files needed during text mode install to uppercase or they will not be found. Within windows the problem does not exist. Go figure.
MrWoo