On 26/09/2016 2:58 AM, Jonathan N. Little wrote:
Chris Ilias wrote:
On 2016-09-25 2:25 AM, Ray_Net wrote:
Hello !

I have now a new Windows 10 Pro 64 bits PC.
This is what I will do to install SeaMonkey on this new pc;

I will first upgrade to SeaMonkey 2.40 on my old Windows 7 pro 32 bits
PC with all needed extensions, plugins, etc ...
Then I will install SeaMonkey 2.40 on my new Windows 10 Pro 64 bits PC.
and now ....
If I remplace the directory
C:\Users\RAY\AppData\Roaming\Mozilla\SeaMonkey\
of the new pc with the directory
C:\Users\RZ\AppData\Roaming\Mozilla\SeaMonkey of the old pc.

Will I have the same environment and datas ?

I suspect problems ... see hereafter.

What happens with the installed plugins, extensions...etc ...
What happens with the "Helper Applications" when a lot of applications
not installed yet ?

Should I do differently to have the same options/.parameters, all the
mails and newsgroups, all the bookmarks ?

I don't think you'll have problems. The prefs.js file contains relative
file paths, so you shouldn't have to worry about editing it.

To support what Chris said, I have had no problem moving profile from
Windows to Linux

from:
C:\Users\Jonathan\AppData\Roaming\Mozilla\SeaMonkey\Profiles\

to:
/home/jonathan/.mozilla/seamonkey/

Just works, and you cannot get more different than moving to a different
OS and filesystem.

Jonathan, I'd ask "Why bother??". I share a profile between my Win7 SM install and my Linux install.

Profile on a Win7 drive and just point the Linux SM to the Win7 drive location.

Too easy .... been doing it with SeaMonkey Suite and MandrivaLinux 2007 ... no problems!!

--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 SeaMonkey/2.40 Build identifier: 20160120202951
or
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 SeaMonkey/2.38 Build identifier: 20150903203501
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to