tabbyFile gave me the same thing, but only the first time i ran it, afterwards, i ran it another 2-3 times with no errors, was odd, but yeah,
Please see my suggestion to portable-freak regarding what steps to take that will hopefully eliminate the flakiness - uninstall, re-install via PP, run via PP.
also, just a note, im running my programs through Pstart, it makes it ALOT easyer to test alot of programs at once, but it may skew my results,
I just want to make sure that you're saying you're PP-launching apps by using PStart? Not just running the apps themselves via PStart? Or are you PP-running PStart? That'd probably be okay although I did find a small bug today in the CreateProcess redirection. But maybe PStart's using the ShellExecute api call instead. Hmm, I'll have to download PStart and try it out. I was planning on letting devs make use of the PP dll for their launchers, but maybe that's not even necessary. Thanks for the heads-up.
with the 8/27 build, i ran into very few errors, it was Slow (:P), but, i only had one program freeze: "Depends" when i tryed to open a file, it seemed to be at random, because this also happened with the 8/29 build when i was trying VLC, but later, after i had closed everything re-launched Pstart through portaPotty and tried VLC again, it opened files just fine,
Yeah, there's apparently a lot of reg hits when a number of system dlls are first loaded into memory and used by the "first app of the day," especially when using the open dialog box. If that app happens to be a PP-run app, then it can take quite a long time. But I haven't really even addressed performance yet, so I'm not too concerned (yet.)
Most of the programs i used, when i went to open files, viewed the Actual file system on the computer, but Foxit Reader, got redirected to the portaPotty created directories.
That's probably because those programs had never tried to modify those files. Opening and browsing won't do anything to create redirected directories or files. Otherwise you could end up with an entire hard disk's worth of stuff in the redirected directories.
I also ran IE 6.0.2 through Pstart as a test, the 8/27 build ran it fine, slow, but fine, the 8/29 build showed my history folder as:
instead of the normal history table, but seemed to run fine otherwise,
I would never have thought that any version of IE would ever run successfully via PP. But it's really not a fair test, as I'm sure you didn't uninstall IE and then reinstall it via PP, prior to running it with PP. So it was basically using the registry for the most part and probably only modified a few entries. I'm not sure what you're talking about with regards to the history folder so I can't really comment.
really though, Everything else i ran worked fine, but thats like 20 programs and i doubt you want to read through them all, :P
That's good to know. Thanks for trying out so many. But I imagine quite a few of these were already installed on your system?
as a side note, the new version is a LOT faster with certain operations, like open files and such, but it still took a minute to load up and close programs, though, since im running them through Pstart, that might have something to do with it, ^-^
That's not PStart. That's the PP dll loading up all of the PP registry ini's keys into memory, and saving them when the app closes. If you've been PP-running 20+ apps from the same directory, you probably have a fair number of keys in that file. You might want to try and use app-specific PP registry inis to keep each app's redirected reg as small as possible. That should help somewhat.
Also, i ran Free Download Manager with both the 8/27 and 8/29 build and it worked pretty good from what i could tell, though it still uses the options of the installed version,
(you can use uniextract to get it out of the installer)
Yes, it will use the options of the installed version until the app attempts to rewrite them to the registry, which normally happens when you modify one or more of the options. But running the app this way is not running it portably, as you're relying on the pre-existing registry entries for the most part. Some apps this is okay on if you don't care about cleaning up your registry. For other apps though it will cause them all sorts of problems when run via PP.