Ah, thank you. By renaming AppName_JauntePE.ini to JauntePE_JauntePE.ini, it works good with RocketDock, but with ObjectDock it gives the same result. It creates reg according to the exe name I launch (OSK, Regedit), but with OD the reg files are not empty.
Now get ready for a quite long post...
Talking about OD using different ini setting, I think I experienced it. But, I'm not sure. As you know I'm using template, to redirect file system to specific directory which is "JPE-FileSystem". But before, I used: "JPE-File System" (with space between File and System). When I tested those apps, I was getting "JPE-File System" folder besides "JPE-FileSystem" in the application. Which means it had used different ini setting, but it happened only once on the test.
I put:
ObjectDock, JauntePE.dll, and ObjectDock_jauntePE.ini (now JauntePE_JauntePE.ini) are in Y:\SYSTEM FILES\PROGRAM FILES\ObjectDock(JPE)
OSK.exe in Z:\WINDOWS\system32
JauntePE.dll 0.1.0 in Y:\TOOLS\+SYSTEM\JauntePE 0.1.0
..
Up to JauntePE.dll 0.1.3 in Y:\TOOLS\+SYSTEM\JauntePE 0.1.3
The madchook.dlls are always in the same location with JauntePE.dlls.
I also put JauntePE.dll & madchook.dll in template directory in JauntePE.dll 0.1.0 in Y:\TOOLS\+SYSTEM\JauntePE 0.1.0\Template. I also put
rename_JauntePE.ini. So, when I want to make portable I only need to copy all file & 2 empty folders (from template folder) to the exe, rename
rename as the exe; and build the exe with wizard. I also copy empty folders, because if I'm not mistaken JauntePE won't create the folders by itself.
So my JauntePE.dll & madchook.dll are in:
1. Y:\TOOLS\+SYSTEM\JauntePE 0.1.0
2. Y:\TOOLS\+SYSTEM\JauntePE 0.1.0\template
3. Y:\TOOLS\+SYSTEM\JauntePE 0.1.1
4. Y:\TOOLS\+SYSTEM\JauntePE 0.1.2
5. Y:\TOOLS\+SYSTEM\JauntePE 0.1.3
6. Y:\SYSTEM FILES\PROGRAM FILES\ObjectDock(JPE)
I don't really understand what do you mean by building launcher, but I built JPEexe using JauntePE.exe wizard. After I rename the ini to JauntePE_JauntePE.ini, I tried to rename JauntePE.dll, it complains. I rename it back to ObjectDock_JauntePE.ini, it also complains. So, I think it is using the correct JauntePE. But I have one thought, that maybe another JPEized application could effecting another.
For example, I tried to JPEized one global application (Window Manager type) that connected to every window. I was successfully captured the registry & file system to its folder, but it also still writing to the real Windows registry.
Have you actually played around with the JPEized OD enough to get those portable appdata and my docs directories populated with stuff?
I believe the appdata is the place where OD save its settings. It creates files: AppImages,ini, CurrentTheme.ini, CurentTheme_Backup.ini, and Settings.ini
But it seems, JPE redirects only 2: CurrentTheme.ini and Settings.ini. And regarding My Documents\ObjectDock Library, I never touched it, when I deleted OD files in myDoc, it was redirected to application folder.
I got one problem with a dll tho, which doesn't show one icon, but maybe I can do something about it.
Sounds like it's not getting its info stored into any registry, system or portable. Could it be that the .reg it's using is set as read only?
I'm sure it has not set to read-only, as it create the registry by itself. If I have sysinternal in the real registry, it will not ask any EULA. But if I delete sysinternal from real registry, processExplorer would always ask EULA. So, it seems that processExplorer can read the real registry but can not write to the real registry. Maybe it would be better to give you a movie to show you. I think logging feature should be great to check things.
EDIT: I thought ObjectDock was working, so I edit my post accordingly.