Sorry for not getting to these sooner.
Quote:
Not really a bug, but as I posted in the trouble-shooting forum, JPE is no longer stealthy under Vista.
There was only one beta version Vista test by someone other than me. It was reported that JPE ran fine in the limited case I had him test. I can't say anymore as the information given is incomplete and I don't even have XP to test on anymore. I'd be willing to send you a logging version of the JPE runtime if you want to try and find out what's wrong.
Quote:
I get error message "JauntePE can only run under MS 2000 or newer", so I had to use the Compatability Wizard to run it under WinXP SP2 compatibility mode.
Should be fixed in the new version.
Quote:
cannot hook User Data folder ("c:\Documents and Settings\bla\bla") from other WinXp language than English
It would be helpful if the bug reporter could say what the JPE runtime ini used for the app has in its [computername\username] section as far as special folder path names. The ##L= lines should agree with the registry contents found at "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders". I'm willing to try and get this fixed but I need someone with a non-english version of 2K or XP to help test.
Quote:
If you go to Settings>Registry tab OR File System tab>Exceptions, there should be buttons at the red area
I think this was a 2K only problem, or an old Explorer shell version problem, or a problem related to the shell font in use. Anyway, I think I may have fixed it in the new version if you'd like to go see.
Quote:
Unable to hook at the root of C:\Documents and Settings\{username} I tried to put it in [FilesystemInclude] but still no success
In the JPE runtime ini you're using for the app, you should have a [computername\username] section, with a Created=1 line followed by a bunch of lines that start with numbers, e.g., "38L=C:\Program Files;38", "43S=C:\PROGRA~1\COMMON~1;43", and
"38S=C:\PROGRA~1;38". There should be a 40L and a 40S line in there. If not, then that's the problem, but it may be due to your particular system not supporting that special folder type. The way to tell this is to see if it shows up in the "JPE Settings->File System->Exceptions->Includes->Add->Special File Folder Paths" drop down list. If it does, and if using it adds a 1=40 line to the [FilesystemInclude] section, then it probably is a bug somewhere in the JPE runtime.