In microsoft.public.win2000.registry Fred wrote:
> Yes, ordinary safe mode is the problem.
> Can you highlight and export the subkey registry files as
> suggested in KB article 258795 from a W2K machine? If so,
> could you e-mail them to me and I can try that for a fix?
Sure Fred but see
http://www.jsiinc.com/
Tip number 2423
where you could copy/paste it.
Basically the same as I posted up-thread, but includes also
"Safe Boot with Networking".
A great site BTW.
I am at a loss. My Safe Mode dutifully loads up basic mouse and
keyboard support. From ntbtlog.txt (about half way through):
...
Loaded driver \SystemRoot\System32\DRIVERS\i8042prt.sys
Loaded driver \SystemRoot\System32\DRIVERS\mouclass.sys
Loaded driver \SystemRoot\System32\DRIVERS\kbdclass.sys
...
And I would have expected you to get something like an Event Log
entry from Service Control Manager reporting a load failure or
some other event indicating an error.
Perhaps those key valuenames are bad but not visibly detected as such.
"(Default)" entries can be confusing sometimes. I would in fact try
merging the standard values were I in this situation. Please say if this
fixes the problem. And I think it is perhaps possible a
"BIOS Plug and Play OS = Yes" setting could be a problems (that is a
guess). Good luck.
>
> Thanks again for your help.
>
>>-----Original Message-----
>>In microsoft.public.win2000.registry Fred wrote:
>>
>>[ ]
>>>>>>> Knowledge base article 258795 states how to restore
>>[ ]
>>>>> boot normally with no problems with the keyboard or
>>>>> mouse. I only have a problem when trying to boot
> into
>>>>> safe mode, which is needed occasionally to delete
>>>>> files. Booting to safe mode results in no keyboard
> or
>>>>> mouse functionality. The registry subkeys
>>[ ]
>>>>What mouse/keyb do you have and what drivers? The
>>
>>[ ]
>>> The keyboard and mouse are both PS/2 hardware, and
> there
>>> are no drivers installed (they are not required with
>>> W2K). I'm not using any USB connections.
>>
>>Okay. I don't know. :-)
>>But I will see what I can up with here by rebooting with
> bootlogging
>>enabled into Safe Mode. Just to clarify, you mean
> ordinary Safe Mode
>>right? Not Command Prompt Only or Recovery Console. Try
> to get back
>>here Tuesday.
>>
>>.
>>
>