Best, open the folder "/WINDOWS/System32/" next to the file we renamed in step 5 on the Desktop. Now, it won't give you an error when we delete the file in the next step.ĩ) Since WINXP tracks registered DLLs and even replaces them when deleted we need some quick timing here. It will be marked red now.Ĩ) Repeat with the second entry from the find dialogue. Right-click on that entry in the bottom panel and choose "Close Handle". In the top panel of the process window it will show you the parent process (i.e. On running under "winlogon.exe" service and one running under "svchost.exe" service.ħ) Click the first one from the find dialog. Use find option again with the string "kbd101.dll". You should see a second "kbd*.dll" running.Ĥ) Make a backup copy of your running "kbd101.dll" in "/WINDOWS/System32/"ĥ) Copy the "/WINDOWS/System32/kbd106.dll" file to the desktop and rename it to your "kbd101.dll"Ħ) Now back to Process Explorer. You might already have the "kbd106.dll" running, however if you reading here it doesn't do squat for you. Otherwise, try to find it with Process Explorer using the find option and string "kbd". For the rest of this hack, I'll just refer to it as such. I had a slip stream US XP install in my case and in probably most other cases it should be "kbd101.dll". If you have Japanese IME installed, there is a pretty good chance it is already under "/WINDOWS/System32/"Ģ) Download & install Process Explorer from M$:ģ) Figure out which "kbd*.dll" is running on your system. using the registry etc -> let me know! However, it works like a charm.ġ) Make sure you have a copy of the "kbd106.dll" file. Mind, this is a pretty crude hack (what else a unix guy is to do on Windows) and I am sure there are much more elegant methods, i.e.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |