The error could come from the application (file manager), or Windows, or from JPE.
First of all, thanks for your reply.
In regard with your statement above, I have thought about that too. I don't know how to correctly identify which process actually own the error windows\messages. But here are some snapshots of the Error messages, and imho, those pictures do give some important clues.
From JauntePE-ized Explorer (Two Error messages):
From JauntePE-ized FreeCommanderPortable (Same Two Error messages):
I have the same problem with other JauntePE-ized file manager that I have tried, eg. DoubleCommander, tabbyfile, etc...; So I'm pretty sure that this problem isn't an isolated case with just one or two file managers.
Below are some pictures showing that this problem ONLY appears on command line interpreter (cmd.exe, AFAIK), but not with other Windows applications.
Here under [ChildExclude], I have excluded two processes, Notepad.exe and cmd.exe. Notepad opened normally without being redirected (there are no JPE icons on the title bar), but cmd.exe did not.
Here under [ChildExclude], I have excluded everything (1=*). This should instruct JPE not to redirect any child process but apparently it did.
OTOH, if I disable redirecting child processes by setting RedirMisc to 0 (RedirMisc=0), cmd.exe bypass JPE as expected.
In theory, the last two cases above should give identical results. If I exclude every child process under [ChildExclude] ([ChildExclude] 1=*) and have no process under [ChildInclude]; then this should be identical to setting RedirMisc to 0. But my results above said otherwise.
Even though I can make cmd.exe to bypass JPE by setting RedirMisc to 0, this also disable child process redirection altogether and therefore is not what I wanted.
Below are some simple instructions to reproduce my problem:
1. Get the generic JPE launcher (it is much quicker and easier this way) and follow the instructions in this post. (joby_toss is a genius) http://www.portablefreeware.com/forums/viewtopic.php?f=13&t=6743&sid=a8a98337049c5d0e7e5f527fe308ed57
2. Use any portable file manager (FreeCommanderPortable, tabbyfile, etc...). Since they are already portable, this should rule out the possibility that they aren't set up correctly under JPE.
3. Create a cmd file. Just type some simple instructions and save it. (eg. just type pause and save it, this should open a command prompt)
4. Run the launcher and then run the cmd file you have just saved earlier. That's it.
I don't think my other settings in the ini file matters much, because we are running a portable file manager here. Since those portable file manager, in theory, should work right out of the box, without any need of JPE (they read their settings in their own ini files and recreate them if needed). Therefore I am not going to post my detailed config settings here.
PS. If you looked at the pictures I have posted above, you'll noticed that I have been running the file manager under Sandboxie (because I normally run everything under Sandboxie, lol). But I can assure you that this problem also appears if I run the launcher without Sandboxie.
This problem may only appears on my computer (because I'm an idiot
). So, in any case, you've already do me a great favor, if you can take some time and see if you can reproduce my problem on your computer. THIS IS A VERY MINOR ISSUE, and that's why I didn't post my questions for months (well, that and also because my English is very poor). I don't want to bother the developer, if Redllar doesn't has time, because I'm also waiting for version 0.6 to be ready. Version 0.5x is nice, but a fully working open source 0.6 is much better.