The workaround suggested by crownixx was to make an optimized configuration for JauntePE hooking only the needed APIs
No..no. Dont get my post wrong. If your read carefully, what i write is to make optimized runtime ini configuration
and not APIs only. From what i understand, optimize runtime ini can be made by controlling the registry usage, file system usage, module usage, child process usage and APIs usage.
To be honest, optimizing runtime ini using APIs usage is far too advance for me and i'm not dare yet to touch those settings.
Ok, for Open File" or "Save File" dialog problem workaround, to be precise you should optimize the Registry usage.
* If your app is not using registry usage but only use file system usage, then turn off your registry redirection
* If your app use registry, the way you should work is RegistryExclude all
, then RegistryInclude the application registry key usage
I try to search which registry keys that cause this failure and the keys are
I try to go more detail which CLSID that are cause the failure but i only manage to exclude 50 plus keys then i gave up.
2. The UPX thing looks strange, I *guess* that this is a bug and UPX by randomly changing the executables has some chance of making them not trigger the issue...but is not really a solution
Yes you are right. I learn new english term for this: To make JauntePE work in Vista you have to cross your fingers
JauntePE the portable maker: <<JauntePE Google Site