QUOTE (Ninho @ Sep 21 2008, 10:33 AM)
Care to share your experience by writing down a 'how-to' and posting to this forum ?
That would be very nice ! I for one haven't jumped in yet for the reason you stated above, confusing-looking instructions on the Japanese site, compounded with the fact that I have a non-English (and non-Japanese!) version of Windows. It sure would help me and, I bet, many others, to look-up better worded English instructions.
And if Win2000 (praise to him) became interested, you might eventually arrange to have your international instructions added to his site too. Just a dream...
I was a bit frightened by this at first too, but I've had a lot of success with it.
Here's my guide to how at least the system file substitution bit works (I think!)
The main system file substitution program is KDLLINST.EXE.
When you unzipped the program to its folder, it should have determined the paths to your system files in the system32 folder, and the backups in the DLLCache folder.
These paths should be displayed at the top of the program GUI.
It appears to display a Japanese character in place of the "\" character, but this does not seem to matter.
The "Wrapper" path is the path to the replacement modified files which will be used.
The "EzInstall" path will be the path to the executable which is to be patched to work in EzInstall mode.
This does not actually replace the system files in the system32 folder, but instead puts them in the folder with the program that you're trying to get to work under Windows 2000, using a more traditional "wrapper" system.
To use the program in "full" mode, where it will actually change your system files for the modified versions, you need to click on the box beside each file that you want to change.
The versions of the original and substitute will be displayed if "Version Disp" is checked.
"EZ KD Registry" must be checked, as that puts the necessary entry in the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\ExcludeFromKnownDlls
key. If the system files concerned are not listed there, the "EzInstall" method will not work, as the system will always use the files in the system32 folder, and ignore any others.
In fact I found that tampering with that key caused my system to refuse to start even using full mode, so always keep it checked!
When you've selected the files that you want to change, hitting the "Start Setup" button should bring up a screen telling you what substitutions the program is going to make, and prompting a reboot.
You can do as many or as few files at a time as you wish, but I found that some actually needed several attempts before they "stuck".
When the file has been substituted correctly, it will say "same version" beside it.
I found that three files, Shlwapi, Esent, and SHFOLDER were being apparently substituted with versions with lower version numbers, and in fact this caused Windows Auto Update to cry that I had lost an Internet Explorer cumulative security update, and wanted to install it again.
For that reason I have left those files as they were.
The first four files listed are the important ones for getting most XP programs to run I suspect.
If you want to undo this, just check "Uninstall Mode" and click next to the files you want to restore to their original versions. That has worked fine for me several times while I've been experimenting.
To use "EzInstall" mode, do the same thing but browse ("Refer") for the folder where the program you want to patch is so the path is in the "EzInstall" field.
Select the files you need as before, but this time hit the "Ez Install" button.
I managed to get Quicktime 7.5 and WMP10 to work using this.
In fact I found that using them didn't actually give me any real advantages over the versions I already had, so I went back to them, but the fact that the newer versions could be made to work at all amazed me.
Win2000 is a genius!
I hope this is useful.
If so I'll write something similar about the "other bit" the FCWIN2K.EXE program.
