Don't worry about that. We need to see if we can even get it working first. Performance issues come after.On second thought, would it decrease the performance if being hooked more than once? I mean hooked by the ContextMenu & FileTypes, and its own redirection. Maybe it would be much efficient to define what process would use ContextMenu & FileTypes than hooked it to all process.
This is all very confusing and wasn't really what I was talking about. I was suggesting that you get a feel for how JPE can affect explorer by seeing if you could see the fake drives that the jpeCrypto plugin creates from within the explorer window. That's it. That one simple test. I don't even know what to say about all of that other stuff you tried. Of course it won't work. Something as complicated as what you want to do has to be approached in a logical manner to make sure you know exactly what's going on at each step. And it needs to be properly researched so that a proper jpe ini can be created for explorer.I think I understand the concept, but I encountered problem in the testing. So, here it is:
I put explorer in the JPE launcher. Run the explorer, import file type & context menu .reg. Tried the right click, but it didn't show the menu I registered using the .reg.
And I noticed something. Each time I choose play & media player started, every explorer I started would be in JPE mode with border & icon. I tried to open it via GeoShell menu (I'm not using Explorer as shell) and taskman. The taskman itself has no border, I even try to choose the explorer.exe in Windows folder (not just by typing explorer in the taskman).
If I didn't choose to play or Media Player didn't start, the explorer I opened via task man & GeoShell would be normal.
I was able to reproduce the problem few times: drag explorer.exe to 020 launcher. Launch the explorer via launcher->right click any .mp3->choose play. After Media Player started, close the Media Player & run explorer via taskman.
ARGGHHH!!!! Sorry. I just had to get that out.I did a test with regedit.exe, but using OD JPE-reg. I could not find the OD JPE-reg entries when I rename OD JPE-reg to regedit_JauntePE.reg. So, JPE doesn't import the JPE-reg & FileSystem then start the JPEized app?
regedit browses the registry. Which is different from most regular apps that just go after specific keys. As a registry browser, it needs to be given the entire key hierarchy in order to be tricked into thinking that the .reg is in fact the system registry. That's what the currently disabled code does.redllar wrote:there's a feature in the JPE runtime, that's currently turned off,
Also, what did you do to ensure that regedit was using a sensible jpe ini? The one provided won't do the trick since that's for running regedit against the system registry.
But if you still want to try this I can walk you through the manual steps necessary. It's not pretty though. That's why I wrote the code to do it for me.