When I have RunLocally set to true, so that it copies my data to my PC and then copies it back afterwards (to ease load on my USB) the Launcher doesn't get past the splash-screen. Can somebody help! I am running PA.c 12.0 beta 2 if this helps, and my INI is as follows:
[ThunderbirdPortable]
ThunderbirdDirectory=App\thunderbird
ThunderbirdExecutable=thunderbird.exe
AdditionalParameters=
GPGPathDirectory=App\gpg
ProfileDirectory=Data\profile
PluginsDirectory=Data\plugins
RegistryDirectory=Data\registry
SettingsDirectory=Data\settings
GPGHomeDirectory=Data\gpg
DisableSplashScreen=false
AllowMultipleInstances=false
DisableIntelligentStart=false
SkipCompregFix=false
RunLocally=true
RunLocally is for running in live mode from a CD for demo purposes. All changes are lost at the end.
https://portableapps.com/support/thunderbird_portable#cd
Additionally, we don't test live mode much anymore as optical media is on the way out and there's not much interest in the feature.
Sometimes, the impossible can become possible, if you're awesome!
Other apps, like Chrome Portable, take RunLocally to mean "copy to local machine, then copy back when done". Why can't this be done with Thunderbird?
Chrome has that feature due to an old custom launcher written by another developer. It was from the time period when Chrome's cache could not be disabled and had to be a part of its profile, so it ran absurdly slow on USB drives, unlike Firefox which supported both disabling and relocating cache. It performs fine on any average retail drive these days. We will likely be phasing that feature out when the launcher is updated to properly handle Unicode paths and the like.
Sometimes, the impossible can become possible, if you're awesome!
Thanks for the comments on this, I assumed it was the same in all apps so that you could turn it on to extend the life of the drive - sad to see it being phased out.
The lifespan of most modern flash drives isn't as much of an issue as it was when we started doing this back in 2004. Modern flash drives have wear leveling algorithms so that even if you write a file over and over, it winds up writing it to a different area of the drive each time. That's why the warranties are much longer.
There are some companies that are cheating, though, and hoping the wear algorithms will mask them using really low quality RAM that can only handle thousands of cycles instead of 10s of thousands.
Sometimes, the impossible can become possible, if you're awesome!