portable-freak, thanks for the info and kind words.
nycjv321, thanks for the info on PE packers and the links. Looks like stuff to look at once I get all of this other stuff worked out.
nycjv321 wrote:can portaPotty pick up a app trying to registry dlls... and can it run a app portably and catch that apps that that app runs.
Yes, this new version should be able to, at least in theory. I've only tested it on Scorched3D so far, but it worked w/o problems (Scorched3D launches another copy of itself to run the actual game.)
nycjv321 wrote:so now does it pick up any type of settings or just registry and %appdata% what about %profile% and also all user's data since theres also application data folder in all users section... And also will portaPotty (the new one you are testing) pick up any form of settings or just registry / current user appdata / userprofile (e.g. Abiword) /settings in other locations (e.g. xpsyspad settings stored in C:\windows\xpsyspad.ini.
This new PP treats file system access in a manner similar to the way the registry access works. For instance, the first time you start Scorched3D, it creates a directory in %profile% called ".scorched3d". Before that can be done, PP strips off the %profile% front end part of that path, takes what's left over (the ".scorched3d" part), tacks that onto the end of the app's directory, and then lets the directory creation request go on through. So the app thinks it's creating %profile%\.scorched3d when in fact it creates .scorched3d in its own directory. Then the app creates a %profile%\.scorched3d\display.xml file. PP does the same thing again, effectively redirecting the file into the app directory's .scorched3d subdirectory. Ditto for anything else created or written to %profile%\.scorched3d. And when the app opens the %profile%\.scorched3d\display.xml file, PP changes that to a request to open up the real file that exists in the app directory's .scorched3d subdirectory.
This new PP does this sort of thing by default for all "known system directories" (admintools, appdata, bitbucket (recycle bin), cdburnarea (include this by default?), cookies, desktop, favorites, fonts, history, internet cache, mymusic, mypictures, myvideo, nethood, printhood, profile, profiles, programfiles, programs, recent, sendto, startmenu, startup, system, templates, windows, and any local (nonroaming) or common (alluser) or alt (nonlocalized) equivalents), although I've only tested this with Scorched3D and it only wrote to profile.
The catch to all of this is it won't work for all types of apps. For instance, you'll want a system cleaner app (deletes cookies, history, recycle bin files, etc.) to be able to delete files in those directories. So we need a way to specify on a per app basis exactly what directories and/or files it is allowed to muck with; something like an ini exclusion list, for instance.
nycjv321 wrote:or will it pick up any type of settings like local machine application data and anywhere else ?
Here's an example of what I think you're asking: You start a portablized text editor, open up a text file in "My Documents", modify it and then save it. By default that modified file would be written to a "My Documents" subdirectory in the app's directory, leaving the original untouched. But, if you open up a text file in "C:\SomeFolder", modify it and then save it, PP will not redirect that file to the app's directory because that directory is not a "known system directory". However, it would be a simple matter to have PP redirect file mods for that directory as well. All we need is some mechanism (an ini inclusion list?) to specify what additional directories we want redirected for that particular app.
nycjv321 wrote:and as for foxit im useing the newest build which supports portabilizing it and it wont work even with "build even if it might now work"? what im i doing wrong im using xp with no service packages
I just tried Foxit Reader (v1.3 build 1621) here (XP Home SP2) and it works fine with just the normal PP build option. Are you sure that all of the app's system registry entries are gone? How does the app fail? Is it creating any ini entries? Did you try deleting or renaming the ini and then running the app? Did you try the logging version I posted a link to earlier? That's about all I can think of because "it wont work" really doesn't tell me anything useful.