This, unlike my other recent posts which were about optimizing things, is actually a critical issue.
While testing out a burned CD on my PC I noticed when I went to select which harddrive to install on that my keyboard was not responding. I search the forums here and only found a few posts talking about this, but with no resolve (or at least I didn't find any as the issue was raised in another thread about another topic and I didn't want to read all 100+ replies to see if someone slipped it in). But doing a search on HFSLIP and USB keyboard brought no solutions.
So in my attempt at trouble shooting I did the following so far and discovered the following.
I stripped things down to just slipstreaming SP4, UR2, and UURollup v10d.
I included the following files in the HFEXPERT\STORAGE folder for my sata drives
I included the following file in the HFEXPERT\WIN\SYSTEM32 folder:
I included to .REG files in the HFSVCPACK folder for KB830407 and KB919521 which have the following:
I included in the REPLACE\I386 folder the modified SETUPREG.HIV that is supposed to help with the 127GB+ drive issue from http://www.msfn.org/...on-win2k-setup/
While the system was installing I was toggling the numlock key to see at what point it stops responding. I also press F6 to see if it was receiving any input. The keyboard functioned fine, including the F6 key and pressing <ENTER> to continue. The point where it froze was 1 second after it says "Setup is starting Windows 2000", right before the partition selection screen comes up. When it happens the numlock key turns off.
So what is causing the setup to turn off my keyboard? Is this an issue with the USB keyboard which just happens to die before the partition selection, or is something with the 127BG+ issue fix is causing the USB keyboard to stop working?
Any advise, suggestions, or hopefully solutions would be appreciated.
Thanks in advance.