1 of 1 people found this helpful
If keyboard & mouse aren't working at the time you get the prompt, there's no way you're going to know what file mini-setup is looking for. It would certainly help to know that. Probably all it takes to make kb & mouse work is add 2 entries to the CriticalDeviceDatabase. Go to a fully installed machine that is identical to your target, have a look at its CriticalDeviceDatabase, find the entries for kb & mouse and add them to the .reg file that you give to injectmsd.
I had very similar problems this time last year. I got prompted for the WinXP SP3 disk and kb & mouse weren't working. I believe the files it was after were the HAL files. The problem went away when I put sp3.cab in driver cache. This may be a long shot but one thing that changed since then is that the HAL files have recently been updated. If you look at a WinXP SP3 with all patches applied, you'll find a new set of HAL files dated 4 Aug 2009 in driver cache. I wonder if that somehow changes the equation.
I can't think how this would have anything to do with SATA. And it's probably nothing to do directly with the Montevina chipset either, but with the fact that source and target have different HALs.
Thanks for the reply Jan. I was hoping you would respond. All of my HII project has been helped a lot by your blogs, documents, etc. Anyways, I'm also thinking it's the HAL. I have the sp3.cab and the newer HAL files in the driver cache folder, but it's still not working. I'm going to try to slip the newer HAL files into the sp3.cab file and see if that works. Work is over today, but tomorrow I'm going to look into the CriticalDeviceDatabase you are talking about.
Okay, I still can't get the mouse/keyboard to work during mini-setup. Can someone point me in the right direction to getting this to work properly?
Just so you know, we use Dell 760s as well, and aren't having this problem. I'd check the copydrivers settings for why you're being prompted in general, but as to kb/mouse not working, I have no idea.
Maybe a KVM that's filtering out the system's auto-detection of them? We have that problem when switching our KVM away from the boot process in the middle - WinPE loses the keyboard/mouse and doesn't re-detect them...