Don Spam's Reckless Son wrote:


Looking at https://www.seamonkey-project.org/releases/#old_unofficial I'd say things are not as bad as they look.  The releases after 2.39 were: 2.40, 2.46, 2.48, 2.49.x and 2.53.x. Lemuel Johnson points out that the current release notes suggest installing 2.49.5 first and then upgrading, none of the levels between 2.39 and 2.49.5 made any such recommendation.

I concur that doing 2.49.5 as an intermediary is something that you want to do.

Can we assume she did not have a master password set?

As a general thing, before upgrading, make sure you get a backup of your user profile. In Windows, the fastest way of doing that is copying the contents of %APPDATA%\Seamonkey to another location.

2.39 was only available as a 32-bit version, 2.49.5 was the very first level which also came as a 64-bit version (talking Windows here).  In order to move from a 32-bit to a 64-bit version you will need to uninstall the old one and then install the new one.  This does not hurt the profile.  (I'm assuming a 64-bit Windows 8).


If moving from 32 to 64, you definitely want to uninstall the 32 bit version first. 32 and 64 install to different directories (\Program Files (x86) and \Program Files, respectively), and it is possible to have both versions installed simultaneously, which you don't want. An uninstall will give you the option of keeping your existing profile, which you do want.

One other caution -- as with Firefox, Seamonkey profiles are now no longer backward compatible. Firefox started doing that at around version 55. I forget where Seamonkey started doing that -- perhaps with 2.53. Thus, if a profile has been touched by a newer version of Seamonkey, you can't downgrade to an older version without risk of data loss. Thus, it's always good to get a backup of your profile before upgrading (even 2.53.5 to 2.53.6), just in case.

Smith




_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to