You are here

PortableApps.com Installer 3.4.1 > 3.4.2 upgrade launcher not replaced

3 posts / 0 new
Last post
Gord Caswell
Gord Caswell's picture
Offline
Last seen: 1 week 3 days ago
DeveloperModerator
Joined: 2008-07-24 18:46
PortableApps.com Installer 3.4.1 > 3.4.2 upgrade launcher not replaced

I've just noted the following error - after upgrading PAI from 3.4.1 to 3.4.2, the installer's launcher displays 3.4.1 rather than 3.4.2 for some reason. This is not the case when installing 3.4.2 directly.

Does anyone else see this behaviour?

See here for what I mean: http://imgur.com/a/S0WzB - The tooltip disappeared under my pointer, PAI displays in the menu as 3.4.2, which lines up with what appinfo.ini shows.

[EDIT] I thought maybe that the version number was hard-coded somewhere, although I felt it was unlikely, and as expected couldn't find the value of "3.4.1" when doing a NP++ "Find in Files" search in the PAI directory.

Maybe the launcher needs to be regenerated for 3.4.1 > 3.4.2?

[EDIT2]

After replacing the launcher exe temporarily with a "clean" 3.4.2 launcher, the incorrect value goes away, and comes back when the original launcher is put back in place. It appears the original launcher exe isn't deleted on upgrade. I'm reclassifying this as a bug report accordingly.

John T. Haller
John T. Haller's picture
Offline
Last seen: 2 hours 25 min ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
Was Running

Likely, you had the wizard running when you ran the upgrade which would cause the file not to be replaced. PortableApps.comInstaller.exe in 3.4.1 has an MD5 of 07fa82a39bb4d7933ad10a1cf91b5867. Check it against the old one you have and it will match. The launcher included with 3.4.2 definitely says 3.4.2.

Sometimes, the impossible can become possible, if you're awesome!

Gord Caswell
Gord Caswell's picture
Offline
Last seen: 1 week 3 days ago
DeveloperModerator
Joined: 2008-07-24 18:46
Possible

I don't think I was, however it is certainly possible. Nevertheless, I have been unable to duplicate the problem when doing a straight update on a new copy of 3.4.1. I'll remove the bug tag, and keep an eye out in case it happens again.

Log in or register to post comments