I just allowed FFP 1.5.09 to update to 1.5.10
I am waiting a while before I go to FFP2.x
I notice something strange. It "seems" that FFP.exe (the launcher?) is launching ff.exe and then exiting?!
FFP.exe appears in the task manager and then disappears.
The files that appear in user APPDATA appear and then go way.
I thought that the launcher (ffp.exe) continued to run till firefox was closed, the way it does in TBP and CWP(I just tested it, the launcher TBP.exe stays open untill TB.exe is closed and than does the clean up in user APPDATA, same with CWP)
Did the update to 1.5.10 break something, or am I missing something?
Has it been like this for a while and perhaps I'm just confused as a result of watching the APPDATA dir after getting the newest CWP launcher from John.
I'm a little concerned here.
Please reply,
Thanks,
Tim
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
The launcher detects whether you have a local install of FF.
If you don't, it keeps running till Firefox closes and cleans the files afterwards.
But If you do have a local install, then the launcher stops running after he launched FFP because there is no need to clean up anything because the files he would clean up are the same ones your local FF uses.
So it has nothing to do with the update.
Hope this helps to resolve all doubt.
"What about Love?" - "Overrated. Biochemically no different than eating large quantities of chocolate." - Al Pacino in The Devils Advocate
"Hope this helps to resolve all doubt."
I'm not sure.
I guess it depends on what you mean by a "local install".
I am running PFF from my hard drive.
I do not have "regular" FF "installed" on my hard drive in anyway. PFF only. That's it.
I'll need to test it at work tomorrow [same setup]. I was "pretty sure" that the FFP files in APPDATA were "cleaned up" after I closed FF, but now I'm not sure. As I said, perhaps I'm confused by the behavior of the other PAs I use [TBP and CWP] which "hang around" till the app is closed and then do the cleanup and shut down.
Anymore feed back in the mean time would be appreciated.
Tim
Tim
Geek w/o portfolio
Things have got to get better, they can't get worse, or can they?
the files in APPDATA are left by your "regular installed" FF (normal version of FF installed just like any other program).
If PFF detects a local install, the Launcher stops running after starting PFF.
If there is no local install, I has to wait to clean up the files in APPDATA.
"What about Love?" - "Overrated. Biochemically no different than eating large quantities of chocolate." - Al Pacino in The Devils Advocate
There is no "regular installed" FF (normal version of FF installed just like any other program)"
But FFP is closing right away.
I am using FFP right now.
Taskmanger says "firefox.exe" is running.
"firefoxportable.exe" closed a few moments after it started.
The user APPDATA was populated for a few moments then emptied.
I'm confused and concerned.
Is FFP therefore allowing data/settings to be left behind that should be removed? This is not a privacy issue, it's my machine. I just want to know if something is broken.
I interpret your last post as agreeing with me in that you think FFP.exe should continue to be running until I close the app [ff] that it launched.
Tim
Things have got to get better, they can't get worse, or can they?
Ok,
It's Monday morning and I'm at work.
I'm using FFP 1.5.09.
I'm running it from the harddrive.
I do not have "normal" FF installed at all.
I am posting from FFP.
Firefoxportable.exe is currntly running in the TaskManger
I have the normal dir/files in temp:
\nsm133.tmp
FindProcDLL.dll,
newadvsplash.dll
System.dll
splash.jpg [I have confirmed this is the FFP splash jpg.
So what is going on at home?
I allowed FF to update to 1.5.10 and now [at home] the Launcher [ffp.exe] quits almost immediately and the temp files and dir disappear almost immediately.
Did the update break the Launcher?
Is FF now behaving like "normal" Firefox?
What should I do to fix this?
Tim
[followup: 11:55]===============
Okay, the work machine just updated to 1.5.10, I thought I stopped it but couldn't.
The samething is now happening at work. FFP.exe quites right away and the APPDATA files as well.
It appears the update does break FFP.
What now!
Things have got to get better, they can't get worse, or can they?
Any particular reason you're still using 1.5? I ask because only the launcher bundled with 2.0 is being updated and further supported. The one you're using isn't Vista compatible (that was added with 2.0.0.0 in November 2006), for instance. Mozilla is dropping all support for the 1.5 branch in less than 2 months for regular installs as well.
That said, be sure you don't have a FirefoxPortable.ini file in your FirefoxPortable directory. And, as long as you don't have Firefox or Thunderbird installed locally, delete the %APPDATA%/mozilla directory to ensure that isn't causing the issue. (if FFP detects certain files, it assumes FF is installed and won't stick around to cleanup stuff since it's already there)
Other than that, the only thing I can think of is if 1.5.0.10 starts and restarts itself which would trick the launcher into thinking it's closed.
Sometimes, the impossible can become possible, if you're awesome!
John,
Sorry it took me so long to reply, rough trip home from work.
"FirefoxPortable.ini" was not a factor in play.
I took your advise and deleted:
"C:\Documents and Settings\Tim\Application Data\Mozilla\Firefox"
it contained the file "pluginreg.dat"
After this I started FFP things seemed to be working as before:
FFP.exe is in the taskmanger and stays till I exit FF.
The folder "nsdC.tmp" is created in
C:\Documents and Settings\Tim\Local Settings\Temp
and remains there till closing of FF.
The folder:
C:\Documents and Settings\Tim\Application\Data\Mozilla\Firefox
is created on launch but is Empty, and goes away on closing of FF.
I "remote logged in" to my work machine, same situation there.
Since this happened on two machines during the update I'm "guessing" that Mozilla might have changed something in the update which prevented FFP from deleting that directory and it's content [pluginreg.dat] when restarting to install the update.
Could this have effected the people with the 2.0.x updates as well?
In answer to your questions, I will be updating/grading to FFP2.0.0.X before the April deadline.
The reasons I have not done so yet?
1. Compfort, I like the 1.5 series quite a lot, more than FF2 [But I will do it before I have to].
2. When FF2 came out a couple of my important extentions had not been updated yet, by now they might be, I have to check.
3. I have no doubt that by mid April we will be at FF 2.0.0.3. As you can see in the case of this update, things don't always go well with inplace updates.
I usually prefer to wait for a new release of PAs and install a fresh FFP and then copy in my current profile rather than an inplace update [except for my U3 drive as the interum is too long].
I think the people who "bug" you for a new release probably feel similer
[They trust you more than Mozilla!]
If you think about it, we are [with your assistance] "hacking" FF. I'm sure the Mozilla people are not taking into account the situation of the portable apps people when they plan their updates.
As far as Vista is concerned, I don't plan on buying a machine with it till the release of at least Service Pack 1, maybe 2.
My work will not be upgrading anytime in the next year and a half.
My current concern is needing to know if there is any "damage control" I need to do, now that the situation is fixed?
With the Launcher closing early was FF behaving like "normal/installed" FF and making changes I should be aware of?
As always thanks for all your help. In the future I will keep an eye on the "\Tim\Application Data\Mozilla\" folder.
Much love and respect,
Tim
Things have got to get better, they can't get worse, or can they?
Actually, it's a very simple answer. On update, Firefox relaunched itself but after a while which cause the launcher to think it closed. When it relaunched, it left a file behind (pluginreg.dat). This file makes the launcher think FF is already installed, so it doesn't bother to stick around to clean up.
FF is a clean running app and only needs the launcher to stick around to delete the pluginreg.dat. (This has been discussed probably 2 dozen times previously)
This can happen when you let FF update. It's not a huge deal but something to keep in mind. There's no workaround aside from doing an in-place upgrade. There are no upgrades to the 1.5 series or launcher, though. Everyone should be moving to 2.0 asap.
Sometimes, the impossible can become possible, if you're awesome!
BTW, Tim... check out the current release:
https://portableapps.com/apps/internet/firefox_portable#legacy
I posted a 1.5.0.10 just for you. You can install it over your current version (it won't lose any of your data) and you'll have the most recent launcher, etc.
Sometimes, the impossible can become possible, if you're awesome!
Thank you John,
I saw that yesterday when I was downloading 2.0.0.2
I downloaded it to have a backup but I think I am going to take your advice [you did use the expression "asap"] and begin the migration to the 2.x series.
Sometime today I will probably extract FFP2.0.0.2 and copy over my profile and see what breaks. I have not worked with FFP2 since you first release it. I have to remember which 2.0.0.0 extensions I hacked to make them work with 1.5.0.8 and which 1.5 extentions I hacked to make them work with with 2.0.0.1
btw, I Hate the Mozilla version numbering scheme
Thanks as always,
Tim
Things have got to get better, they can't get worse, or can they?