Re: Bad upgrade from 1.1.18 to 2.03
Daniel wrote: cmcadams wrote: Martin F. wrote: cmcadams schrieb: Nope. I _uninstalled_ SM1 once; profile was (and is) still present in the default location. SM2 was then installed, and this thread was the result. I see a little too much difference of opinion on ways and means, hereabouts, for total comfort. I'm thinking it wouldn't hurt a bit for the developers to establish some official, specific guidelines for manual profile transplants on the SM pages ... There is, but that doesn't help if you don't read them: http://kb.mozillazine.org/Profile_migration_-_SeaMonkey I read that. Nothing there worked in my case. This link is also mentioned in the Release Notes under the known issues: http://www.seamonkey-project.org/releases/seamonkey2.0.3/#issues The fact that your profile is not at the standard location results in not being imported automatically I guess. So just perform the necessary steps to migrate and you're done. regards The profile was in the default location. It's the program files that were and are in a nonstandard location, on another partition. Yes, I adjusted the command line to point to the actual location. cmcadams, could you please humour me and 1- Re-install your old SM in its old, non-standard, location and let it find your on SM profile. 2. Next, Un-install your SM 2 (the one that isn't working) and stick its profile somewhere else, preferably compress it or something. 3. Now re-install SM 2 completely and let it find (import) your SM 1 profile. 4. If all the above has gone well, un-install SM 1. Report back. Daniel Sorry. I blew most of a weekend on this, at the start, and there are too many emails/bookmarks under the bridge for me to risk going back and losing either. My setup (such as it is) remains stable, and I'll stick with it. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Bad upgrade from 1.1.18 to 2.03
cmcadams wrote: Daniel wrote: cmcadams wrote: Martin F. wrote: cmcadams schrieb: Nope. I _uninstalled_ SM1 once; profile was (and is) still present in the default location. SM2 was then installed, and this thread was the result. I see a little too much difference of opinion on ways and means, hereabouts, for total comfort. I'm thinking it wouldn't hurt a bit for the developers to establish some official, specific guidelines for manual profile transplants on the SM pages ... There is, but that doesn't help if you don't read them: http://kb.mozillazine.org/Profile_migration_-_SeaMonkey I read that. Nothing there worked in my case. This link is also mentioned in the Release Notes under the known issues: http://www.seamonkey-project.org/releases/seamonkey2.0.3/#issues The fact that your profile is not at the standard location results in not being imported automatically I guess. So just perform the necessary steps to migrate and you're done. regards The profile was in the default location. It's the program files that were and are in a nonstandard location, on another partition. Yes, I adjusted the command line to point to the actual location. cmcadams, could you please humour me and 1- Re-install your old SM in its old, non-standard, location and let it find your on SM profile. 2. Next, Un-install your SM 2 (the one that isn't working) and stick its profile somewhere else, preferably compress it or something. 3. Now re-install SM 2 completely and let it find (import) your SM 1 profile. 4. If all the above has gone well, un-install SM 1. Report back. Daniel Sorry. I blew most of a weekend on this, at the start, and there are too many emails/bookmarks under the bridge for me to risk going back and losing either. My setup (such as it is) remains stable, and I'll stick with it. O.K. Daniel ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Bad upgrade from 1.1.18 to 2.03
cmcadams schrieb: Nope. I _uninstalled_ SM1 once; profile was (and is) still present in the default location. SM2 was then installed, and this thread was the result. I see a little too much difference of opinion on ways and means, hereabouts, for total comfort. I'm thinking it wouldn't hurt a bit for the developers to establish some official, specific guidelines for manual profile transplants on the SM pages ... There is, but that doesn't help if you don't read them: http://kb.mozillazine.org/Profile_migration_-_SeaMonkey This link is also mentioned in the Release Notes under the known issues: http://www.seamonkey-project.org/releases/seamonkey2.0.3/#issues The fact that your profile is not at the standard location results in not being imported automatically I guess. So just perform the necessary steps to migrate and you're done. regards Martin ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Bad upgrade from 1.1.18 to 2.03
Martin F. wrote: cmcadams schrieb: Nope. I _uninstalled_ SM1 once; profile was (and is) still present in the default location. SM2 was then installed, and this thread was the result. I see a little too much difference of opinion on ways and means, hereabouts, for total comfort. I'm thinking it wouldn't hurt a bit for the developers to establish some official, specific guidelines for manual profile transplants on the SM pages ... There is, but that doesn't help if you don't read them: http://kb.mozillazine.org/Profile_migration_-_SeaMonkey I read that. Nothing there worked in my case. This link is also mentioned in the Release Notes under the known issues: http://www.seamonkey-project.org/releases/seamonkey2.0.3/#issues The fact that your profile is not at the standard location results in not being imported automatically I guess. So just perform the necessary steps to migrate and you're done. regards The profile was in the default location. It's the program files that were and are in a nonstandard location, on another partition. Yes, I adjusted the command line to point to the actual location. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Bad upgrade from 1.1.18 to 2.03
Ray_Net wrote: cmcadams wrote: Daniel wrote: cmcadams wrote: Daniel wrote: cmcadams wrote: Robert Kaiser wrote: cmcadams wrote: Here's a link to the bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=547523 That's exactly a Migrations fails if it's dawn and the weather is nice report, I don't expect any developer to be able to reproduce and investigate the problem based on what's in there. The goal of a bug report is to get it fixed. Due to that, please include the information you have that a developer can need to fix it. We know hundreds of cases where migration works, so even the summary is wrong. Robert Kaiser Nothing in the report is wrong. I supplied the circumstances and result. I'm sorry I can't supply you with register dumps. Given that I can't encompass all possible situations in my lone setup, I think you've just said a fix won't be happening, except by accident. So be it. I'm not the due-diligence sheriff. Craig Craig, looking at your bugzilla report, you specifally state at Step one that you un-install SM 1.1.18 before you install SM 2. What happens if you install SM 2 whilst you still have SM 1.1.18 installed?? Daniel No, because the best opinion I could find before installing 2.03 was not to. Where did you find out that the best opinion was not to?? Through Google links, basically. 'Consensus' may have been putting it too strongly. Say rather a mix of received/conventional wisdom and scary stories. That's correct, the best method for migration between SM1 and SM2 is to first remove SM1 then install SM2. In any case the migration process is influenced by the presence or not of an installed SM1. So the test is not to be done. I think there might be one or two people hereabouts that would suggest the bit of advise you have given here, Ray, is wrong. Daniel ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Bad upgrade from 1.1.18 to 2.03
cmcadams wrote: Paul B. Gallagher wrote: cmcadams wrote: Mark Hansen wrote: On 2/20/2010 6:29 PM, cmcadams wrote: A question for the developers: In the installation there's a target field, displaying the default target, with a Browse button beside it. WHY is that button there if you already KNOW installing to an alternative destination will likely fail? Craig Who said installing to an alternate location will likely fail? I did. See generally: https://bugzilla.mozilla.org/buglist.cgi?quicksearch=seamonkey+migration Specifically, I recall having to go through the same rigamarole transferring from Mozilla to Seamonkey. Not a new problem. Your experience is completely different from mine. I installed SeaMonkey over Mozilla on the first try. No muss, no fuss, just complete success. Now, of course, my computer configuration is pretty plain vanilla, so that may have something to do with it. I have no idea whether some of your setup may be challenging SM in ways that I do not. Paul, Congratulations on your good fortune. I've had the same sorts of problems every time there's been a major upgrade, specifically from Mozilla to SM1, and now from SM1 to SM2. Somehow I've always made it work. Fortunately minor-version updates aren't a problem. I might not have anything more to worry about until the SM3 migrator bombs on me (joke). My SM installation is also pretty vanilla: Just the browser/email, nothing fancy. Craig Does this mean, Craig, that you deleted Mozilla version 1.x.x before you installed SM version 1.x.x and SM 1 had troubles finding your profile and then, some time latter, you deleted SM Version 1.x.x before you installed SM version 2.x.x and SM 2 had troubles finding your profile?? I wonder why?? Daniel ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Bad upgrade from 1.1.18 to 2.03
Daniel wrote: Ray_Net wrote: cmcadams wrote: Daniel wrote: cmcadams wrote: Daniel wrote: cmcadams wrote: Robert Kaiser wrote: cmcadams wrote: Here's a link to the bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=547523 That's exactly a Migrations fails if it's dawn and the weather is nice report, I don't expect any developer to be able to reproduce and investigate the problem based on what's in there. The goal of a bug report is to get it fixed. Due to that, please include the information you have that a developer can need to fix it. We know hundreds of cases where migration works, so even the summary is wrong. Robert Kaiser Nothing in the report is wrong. I supplied the circumstances and result. I'm sorry I can't supply you with register dumps. Given that I can't encompass all possible situations in my lone setup, I think you've just said a fix won't be happening, except by accident. So be it. I'm not the due-diligence sheriff. Craig Craig, looking at your bugzilla report, you specifally state at Step one that you un-install SM 1.1.18 before you install SM 2. What happens if you install SM 2 whilst you still have SM 1.1.18 installed?? Daniel No, because the best opinion I could find before installing 2.03 was not to. Where did you find out that the best opinion was not to?? Through Google links, basically. 'Consensus' may have been putting it too strongly. Say rather a mix of received/conventional wisdom and scary stories. That's correct, the best method for migration between SM1 and SM2 is to first remove SM1 then install SM2. In any case the migration process is influenced by the presence or not of an installed SM1. So the test is not to be done. I think there might be one or two people hereabouts that would suggest the bit of advise you have given here, Ray, is wrong. Daniel You think that the presence of an installed SM1 is needed to install SM2 correctly ? I think the opposite. The only presence needed is the SM1 profile. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Bad upgrade from 1.1.18 to 2.03
Daniel wrote: cmcadams wrote: Paul B. Gallagher wrote: cmcadams wrote: Mark Hansen wrote: On 2/20/2010 6:29 PM, cmcadams wrote: A question for the developers: In the installation there's a target field, displaying the default target, with a Browse button beside it. WHY is that button there if you already KNOW installing to an alternative destination will likely fail? Craig Who said installing to an alternate location will likely fail? I did. See generally: https://bugzilla.mozilla.org/buglist.cgi?quicksearch=seamonkey+migration Specifically, I recall having to go through the same rigamarole transferring from Mozilla to Seamonkey. Not a new problem. Your experience is completely different from mine. I installed SeaMonkey over Mozilla on the first try. No muss, no fuss, just complete success. Now, of course, my computer configuration is pretty plain vanilla, so that may have something to do with it. I have no idea whether some of your setup may be challenging SM in ways that I do not. Paul, Congratulations on your good fortune. I've had the same sorts of problems every time there's been a major upgrade, specifically from Mozilla to SM1, and now from SM1 to SM2. Somehow I've always made it work. Fortunately minor-version updates aren't a problem. I might not have anything more to worry about until the SM3 migrator bombs on me (joke). My SM installation is also pretty vanilla: Just the browser/email, nothing fancy. Craig Does this mean, Craig, that you deleted Mozilla version 1.x.x before you installed SM version 1.x.x and SM 1 had troubles finding your profile and then, some time latter, you deleted SM Version 1.x.x before you installed SM version 2.x.x and SM 2 had troubles finding your profile?? Nope. I _uninstalled_ SM1 once; profile was (and is) still present in the default location. SM2 was then installed, and this thread was the result. I see a little too much difference of opinion on ways and means, hereabouts, for total comfort. I'm thinking it wouldn't hurt a bit for the developers to establish some official, specific guidelines for manual profile transplants on the SM pages ... Craig ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Bad upgrade from 1.1.18 to 2.03
cmcadams wrote: Daniel wrote: cmcadams wrote: Robert Kaiser wrote: cmcadams wrote: Here's a link to the bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=547523 That's exactly a Migrations fails if it's dawn and the weather is nice report, I don't expect any developer to be able to reproduce and investigate the problem based on what's in there. The goal of a bug report is to get it fixed. Due to that, please include the information you have that a developer can need to fix it. We know hundreds of cases where migration works, so even the summary is wrong. Robert Kaiser Nothing in the report is wrong. I supplied the circumstances and result. I'm sorry I can't supply you with register dumps. Given that I can't encompass all possible situations in my lone setup, I think you've just said a fix won't be happening, except by accident. So be it. I'm not the due-diligence sheriff. Craig Craig, looking at your bugzilla report, you specifally state at Step one that you un-install SM 1.1.18 before you install SM 2. What happens if you install SM 2 whilst you still have SM 1.1.18 installed?? Daniel No, because the best opinion I could find before installing 2.03 was not to. Where did you find out that the best opinion was not to?? It's something to try. I also see what Robert was saying...and it may pay me to experiment, trying out different install targets, and whatever else I can vary along the way. What I find may even be of use to the developers. :) My major problem is that my C: partition is pared down so much (for the sake of fast partition backups, as I mentioned far, far above somewhere) My C:\ is for system files, my D:\ is for my applications (including SeaMonkey) and my E:\ is for my SeaMonkey Profile, my Documents and my Games. As a bit more complexity, I also have Linux (my main operating system) on this computer, and its (Linux) SeaMonkey also uses the profile on the Windows E:\ it's problematic installing Seamonkey to the default location. And there's an extended partition sitting on top of C:, complicating things a tad more. Don't install SM in the default location if you want (I don't think I've every had Netscape/Mozilla/SeaMonkey in their default locations), it should make zero difference! Might be a few days. Fun time is done for this weekend. Craig Daniel ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Bad upgrade from 1.1.18 to 2.03
cmcadams wrote: Mark Hansen wrote: On 2/20/2010 6:29 PM, cmcadams wrote: A question for the developers: In the installation there's a target field, displaying the default target, with a Browse button beside it. WHY is that button there if you already KNOW installing to an alternative destination will likely fail? Craig Who said installing to an alternate location will likely fail? I did. See generally: https://bugzilla.mozilla.org/buglist.cgi?quicksearch=seamonkey+migration Specifically, I recall having to go through the same rigamarole transferring from Mozilla to Seamonkey. Not a new problem. Your experience is completely different from mine. I installed SeaMonkey over Mozilla on the first try. No muss, no fuss, just complete success. Now, of course, my computer configuration is pretty plain vanilla, so that may have something to do with it. I have no idea whether some of your setup may be challenging SM in ways that I do not. -- War doesn't determine who's right, just who's left. -- Paul B. Gallagher ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Bad upgrade from 1.1.18 to 2.03
Paul B. Gallagher wrote: cmcadams wrote: Mark Hansen wrote: On 2/20/2010 6:29 PM, cmcadams wrote: A question for the developers: In the installation there's a target field, displaying the default target, with a Browse button beside it. WHY is that button there if you already KNOW installing to an alternative destination will likely fail? Craig Who said installing to an alternate location will likely fail? I did. See generally: https://bugzilla.mozilla.org/buglist.cgi?quicksearch=seamonkey+migration Specifically, I recall having to go through the same rigamarole transferring from Mozilla to Seamonkey. Not a new problem. Your experience is completely different from mine. I installed SeaMonkey over Mozilla on the first try. No muss, no fuss, just complete success. Now, of course, my computer configuration is pretty plain vanilla, so that may have something to do with it. I have no idea whether some of your setup may be challenging SM in ways that I do not. Paul, Congratulations on your good fortune. I've had the same sorts of problems every time there's been a major upgrade, specifically from Mozilla to SM1, and now from SM1 to SM2. Somehow I've always made it work. Fortunately minor-version updates aren't a problem. I might not have anything more to worry about until the SM3 migrator bombs on me (joke). My SM installation is also pretty vanilla: Just the browser/email, nothing fancy. Craig ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Bad upgrade from 1.1.18 to 2.03
cmcadams wrote: Daniel wrote: cmcadams wrote: Daniel wrote: cmcadams wrote: Robert Kaiser wrote: cmcadams wrote: Here's a link to the bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=547523 That's exactly a Migrations fails if it's dawn and the weather is nice report, I don't expect any developer to be able to reproduce and investigate the problem based on what's in there. The goal of a bug report is to get it fixed. Due to that, please include the information you have that a developer can need to fix it. We know hundreds of cases where migration works, so even the summary is wrong. Robert Kaiser Nothing in the report is wrong. I supplied the circumstances and result. I'm sorry I can't supply you with register dumps. Given that I can't encompass all possible situations in my lone setup, I think you've just said a fix won't be happening, except by accident. So be it. I'm not the due-diligence sheriff. Craig Craig, looking at your bugzilla report, you specifally state at Step one that you un-install SM 1.1.18 before you install SM 2. What happens if you install SM 2 whilst you still have SM 1.1.18 installed?? Daniel No, because the best opinion I could find before installing 2.03 was not to. Where did you find out that the best opinion was not to?? Through Google links, basically. 'Consensus' may have been putting it too strongly. Say rather a mix of received/conventional wisdom and scary stories. That's correct, the best method for migration between SM1 and SM2 is to first remove SM1 then install SM2. In any case the migration process is influenced by the presence or not of an installed SM1. So the test is not to be done. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Bad upgrade from 1.1.18 to 2.03
cmcadams schrieb: A question for the developers: In the installation there's a target field, displaying the default target, with a Browse button beside it. WHY is that button there if you already KNOW installing to an alternative destination will likely fail? It isn't likely to fail - UNLESS you install OVER an old SeaMonkey version. Robert Kaiser ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Bad upgrade from 1.1.18 to 2.03
On 2/20/2010 6:29 PM, cmcadams wrote: A question for the developers: In the installation there's a target field, displaying the default target, with a Browse button beside it. WHY is that button there if you already KNOW installing to an alternative destination will likely fail? Craig Who said installing to an alternate location will likely fail? Why would they put a steering wheel in your car if steering the car into a tree could be fatal? ;-\ ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Bad upgrade from 1.1.18 to 2.03
Robert Kaiser wrote: cmcadams schrieb: A question for the developers: In the installation there's a target field, displaying the default target, with a Browse button beside it. WHY is that button there if you already KNOW installing to an alternative destination will likely fail? It isn't likely to fail - UNLESS you install OVER an old SeaMonkey version. Robert Kaiser Which it wasn't. And this is an ancient problem, as I discovered when filing a bugzilla report. Migration doesn't work in certain circumstances, period. Craig ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Bad upgrade from 1.1.18 to 2.03
Mark Hansen wrote: On 2/20/2010 6:29 PM, cmcadams wrote: A question for the developers: In the installation there's a target field, displaying the default target, with a Browse button beside it. WHY is that button there if you already KNOW installing to an alternative destination will likely fail? Craig Who said installing to an alternate location will likely fail? I did. See generally: https://bugzilla.mozilla.org/buglist.cgi?quicksearch=seamonkey+migration Specifically, I recall having to go through the same rigamarole transferring from Mozilla to Seamonkey. Not a new problem. Why would they put a steering wheel in your car if steering the car into a tree could be fatal? ;-\ Ask Toyota. Ask a meaningful question, get a meaningful answer. Craig ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Bad upgrade from 1.1.18 to 2.03
cmcadams schrieb: Robert Kaiser wrote: cmcadams schrieb: A question for the developers: In the installation there's a target field, displaying the default target, with a Browse button beside it. WHY is that button there if you already KNOW installing to an alternative destination will likely fail? It isn't likely to fail - UNLESS you install OVER an old SeaMonkey version. Robert Kaiser Which it wasn't. And this is an ancient problem, as I discovered when filing a bugzilla report. Migration doesn't work in certain circumstances, period. We know that it sometimes fails, we also know that those cases probably have no connection to the installation location, though. And we got good data on one spaceific case of failure which we could narrow down to a crash and fix in 2.0.3 - if we get consistent data on where the failure happens, we can try and get it fixed. Migrations fails if it's dawn and the weather is nice unfortuantely can't easily be narrowed down to a specific problem in our software. Unfortunately, many bug reports read somewhat like that. Robert Kaiser ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Bad upgrade from 1.1.18 to 2.03
cmcadams wrote: Here's a link to the bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=547523 That's exactly a Migrations fails if it's dawn and the weather is nice report, I don't expect any developer to be able to reproduce and investigate the problem based on what's in there. The goal of a bug report is to get it fixed. Due to that, please include the information you have that a developer can need to fix it. We know hundreds of cases where migration works, so even the summary is wrong. Robert Kaiser ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Bad upgrade from 1.1.18 to 2.03
On 2/21/2010 9:50 AM, cmcadams wrote: Mark Hansen wrote: On 2/20/2010 6:29 PM, cmcadams wrote: A question for the developers: In the installation there's a target field, displaying the default target, with a Browse button beside it. WHY is that button there if you already KNOW installing to an alternative destination will likely fail? Craig Who said installing to an alternate location will likely fail? I did. See generally: https://bugzilla.mozilla.org/buglist.cgi?quicksearch=seamonkey+migration Specifically, I recall having to go through the same rigamarole transferring from Mozilla to Seamonkey. Not a new problem. Why would they put a steering wheel in your car if steering the car into a tree could be fatal? ;-\ Ask Toyota. Ask a meaningful question, get a meaningful answer. Craig Sigh ... I tried. Good luck. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Bad upgrade from 1.1.18 to 2.03
cmcadams wrote: Robert Kaiser wrote: cmcadams wrote: Here's a link to the bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=547523 That's exactly a Migrations fails if it's dawn and the weather is nice report, I don't expect any developer to be able to reproduce and investigate the problem based on what's in there. The goal of a bug report is to get it fixed. Due to that, please include the information you have that a developer can need to fix it. We know hundreds of cases where migration works, so even the summary is wrong. Robert Kaiser Nothing in the report is wrong. I supplied the circumstances and result. I'm sorry I can't supply you with register dumps. Given that I can't encompass all possible situations in my lone setup, I think you've just said a fix won't be happening, except by accident. So be it. I'm not the due-diligence sheriff. Craig Craig, looking at your bugzilla report, you specifally state at Step one that you un-install SM 1.1.18 before you install SM 2. What happens if you install SM 2 whilst you still have SM 1.1.18 installed?? Daniel ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Bad upgrade from 1.1.18 to 2.03
Daniel wrote: cmcadams wrote: Robert Kaiser wrote: cmcadams wrote: Here's a link to the bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=547523 That's exactly a Migrations fails if it's dawn and the weather is nice report, I don't expect any developer to be able to reproduce and investigate the problem based on what's in there. The goal of a bug report is to get it fixed. Due to that, please include the information you have that a developer can need to fix it. We know hundreds of cases where migration works, so even the summary is wrong. Robert Kaiser Nothing in the report is wrong. I supplied the circumstances and result. I'm sorry I can't supply you with register dumps. Given that I can't encompass all possible situations in my lone setup, I think you've just said a fix won't be happening, except by accident. So be it. I'm not the due-diligence sheriff. Craig Craig, looking at your bugzilla report, you specifally state at Step one that you un-install SM 1.1.18 before you install SM 2. What happens if you install SM 2 whilst you still have SM 1.1.18 installed?? Daniel No, because the best opinion I could find before installing 2.03 was not to. It's something to try. I also see what Robert was saying...and it may pay me to experiment, trying out different install targets, and whatever else I can vary along the way. What I find may even be of use to the developers. :) My major problem is that my C: partition is pared down so much (for the sake of fast partition backups, as I mentioned far, far above somewhere) it's problematic installing Seamonkey to the default location. And there's an extended partition sitting on top of C:, complicating things a tad more. Might be a few days. Fun time is done for this weekend. Craig ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Bad upgrade from 1.1.18 to 2.03
Robert Kaiser wrote: cmcadams schrieb: Leonidas Jones wrote: u...@domain.invalid wrote: cmcadams wrote: Last evening I finally uninstalled 1.1.18, and installed 2.03. My Profiles Bookmarks Email and newsgroup accounts Addresses Saved emails didn't make the trip. 2.0.3's wizard said it had imported everything, but no evidence of that. Asking 2.03 to import the missing items after installation was fruitless since I don't use Eudora, Outlook, etc. The browser itself was functional. 1.1.18 is now back in use. The OS is XP SP3. Yes, I have a nonstandard SM installation. Program files are installed to: E:\Mozilla\SMonkey to keep my boot partition smaller, which makes boot partition image backups easier. 2.0.3 was installed to the same location. 1.1.18's config files have always been in the standard place: C:\Documents and Settings\[myname]\Application Data Has anyone dealt with this before, or can point me to a page where someone has? I had issues like that clear back when they came-out with SeaMonkey 2- the best way is not to upgrade until they get all the bugs worked-out, I think there's a settings under preferences, advanced for Seamonkey not to search for a upgrade. Stay tuned to this channel for news of when a good version comes out. Jack I'm afraid you're wrong there. The problem the OP posted was one of a problem profile migration. That is not a flaw in the program itself, but in the migration process. That is not going to improve. Anyone who is waiting for an improved migration tool is going to have a long wait. In fact, the profile migration will probably go away entirely, though that will be a while. The real answer is to migrate the data manually. It may be a pain but once its done its done, and you willbe positioned to move on. Yes, we all hope that there will be many improvements to the suite, but an improved migration tool, probably not. Lee Okay, that worked. Thank you very much. For those who might Google this in the future, I copied the CONTENTS of 1.1.18's *.slt folder (not the folder itself, but from within the folder) to the clipboard, made a backup copy of 2.03's as-installed *.default folder (just in case) and then deleted the contents of that folder. I then Pasted the copied contents of 1.1.18's *.slt into 2.03's new *.default folder. That folder, containing 2.03's config files, is in the new 2.03-created Seamonkey folder visible from: C:\Documents and Settings\[myname]\Application Data\Mozilla Et voila. This is the best recipe to have a lot of garbled and useless data even in your future, and that's why migration selectively copies only the really needed data and what can safely be migrated without disturbing your existence. Robert Kaiser As it happens nothing appears to be garbled, and I'm down to tweaking the small settings. What would you have had me do, after the wizard failed and nothing else worked except what I described? Craig ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Bad upgrade from 1.1.18 to 2.03
cmcadams wrote: Robert Kaiser wrote: cmcadams schrieb: Leonidas Jones wrote: u...@domain.invalid wrote: cmcadams wrote: /snip/ Okay, that worked. Thank you very much. For those who might Google this in the future, I copied the CONTENTS of 1.1.18's *.slt folder (not the folder itself, but from within the folder) to the clipboard, made a backup copy of 2.03's as-installed *.default folder (just in case) and then deleted the contents of that folder. I then Pasted the copied contents of 1.1.18's *.slt into 2.03's new *.default folder. That folder, containing 2.03's config files, is in the new 2.03-created Seamonkey folder visible from: C:\Documents and Settings\[myname]\Application Data\Mozilla Et voila. This is the best recipe to have a lot of garbled and useless data even in your future, and that's why migration selectively copies only the really needed data and what can safely be migrated without disturbing your existence. Robert Kaiser As it happens nothing appears to be garbled, and I'm down to tweaking the small settings. What would you have had me do, after the wizard failed and nothing else worked except what I described? Craig Transfer only the selected data you really needed, such as your email files, bookmarks, cookies, etc. SeaMonkey 2.0 ans sm 1.1 are very, very different programs. By copying over the entire profile, you are moving all kinds of data that does not apply to SM 2, and can cause problems. So far you seem to be lucky, but something may yet happen. For your sake, I hope not. The best case is there a lot of stuff in the profile that is just taking up space. The worst case it that it might cause corruption in the future. I was lucky in that all the profiles I transferred came through with no issues. Had I had a problem, I would have created a new, clean profile in SM 2, opened Mail/News, and recreated my mail accounts in the order I had them in SM 1.1.18. T would then close SeaMonkey, and move across the appropriate subfolders from the old profile to the new. After openinf SM and verifying that the data is there, I would have closed SM and moved bookmarks, passwords and cookies. For my use, that is all I need. Any extensions or themes need to be reinstalled anyway. Lee ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Bad upgrade from 1.1.18 to 2.03
Leonidas Jones wrote: cmcadams wrote: Robert Kaiser wrote: cmcadams schrieb: Leonidas Jones wrote: u...@domain.invalid wrote: cmcadams wrote: /snip/ Okay, that worked. Thank you very much. For those who might Google this in the future, I copied the CONTENTS of 1.1.18's *.slt folder (not the folder itself, but from within the folder) to the clipboard, made a backup copy of 2.03's as-installed *.default folder (just in case) and then deleted the contents of that folder. I then Pasted the copied contents of 1.1.18's *.slt into 2.03's new *.default folder. That folder, containing 2.03's config files, is in the new 2.03-created Seamonkey folder visible from: C:\Documents and Settings\[myname]\Application Data\Mozilla Et voila. This is the best recipe to have a lot of garbled and useless data even in your future, and that's why migration selectively copies only the really needed data and what can safely be migrated without disturbing your existence. Robert Kaiser As it happens nothing appears to be garbled, and I'm down to tweaking the small settings. What would you have had me do, after the wizard failed and nothing else worked except what I described? Craig Transfer only the selected data you really needed, such as your email files, bookmarks, cookies, etc. SeaMonkey 2.0 ans sm 1.1 are very, very different programs. By copying over the entire profile, you are moving all kinds of data that does not apply to SM 2, and can cause problems. So far you seem to be lucky, but something may yet happen. For your sake, I hope not. The best case is there a lot of stuff in the profile that is just taking up space. The worst case it that it might cause corruption in the future. I was lucky in that all the profiles I transferred came through with no issues. Had I had a problem, I would have created a new, clean profile in SM 2, opened Mail/News, and recreated my mail accounts in the order I had them in SM 1.1.18. T would then close SeaMonkey, and move across the appropriate subfolders from the old profile to the new. After openinf SM and verifying that the data is there, I would have closed SM and moved bookmarks, passwords and cookies. For my use, that is all I need. Any extensions or themes need to be reinstalled anyway. Tried as you suggested after a little more creative directory backing up. The upshot is, it didn't work, and I don't propose wasting more time on it. What I've got works: All accounts, emails, passwords, permissions, et al are all in good working order and display and edit correctly in their respective manager screens. Perhaps my setup is a very simple one. If anyone has, say, a list of specific files to beware of, or measures to take, I'll take another look at it. In the meantime I'll let sleeping dogs lie until they stop breathing. In which case there's still 1.1.18. A question for the developers: In the installation there's a target field, displaying the default target, with a Browse button beside it. WHY is that button there if you already KNOW installing to an alternative destination will likely fail? Craig ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Bad upgrade from 1.1.18 to 2.03
u...@domain.invalid wrote: cmcadams wrote: Last evening I finally uninstalled 1.1.18, and installed 2.03. My Profiles Bookmarks Email and newsgroup accounts Addresses Saved emails didn't make the trip. 2.0.3's wizard said it had imported everything, but no evidence of that. Asking 2.03 to import the missing items after installation was fruitless since I don't use Eudora, Outlook, etc. The browser itself was functional. 1.1.18 is now back in use. The OS is XP SP3. Yes, I have a nonstandard SM installation. Program files are installed to: E:\Mozilla\SMonkey to keep my boot partition smaller, which makes boot partition image backups easier. 2.0.3 was installed to the same location. 1.1.18's config files have always been in the standard place: C:\Documents and Settings\[myname]\Application Data Has anyone dealt with this before, or can point me to a page where someone has? I had issues like that clear back when they came-out with SeaMonkey 2- the best way is not to upgrade until they get all the bugs worked-out, I think there's a settings under preferences, advanced for Seamonkey not to search for a upgrade. Stay tuned to this channel for news of when a good version comes out. Jack I'm afraid you're wrong there. The problem the OP posted was one of a problem profile migration. That is not a flaw in the program itself, but in the migration process. That is not going to improve. Anyone who is waiting for an improved migration tool is going to have a long wait. In fact, the profile migration will probably go away entirely, though that will be a while. The real answer is to migrate the data manually. It may be a pain but once its done its done, and you willbe positioned to move on. Yes, we all hope that there will be many improvements to the suite, but an improved migration tool, probably not. Lee ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Bad upgrade from 1.1.18 to 2.03
Leonidas Jones wrote: u...@domain.invalid wrote: cmcadams wrote: Last evening I finally uninstalled 1.1.18, and installed 2.03. My Profiles Bookmarks Email and newsgroup accounts Addresses Saved emails didn't make the trip. 2.0.3's wizard said it had imported everything, but no evidence of that. Asking 2.03 to import the missing items after installation was fruitless since I don't use Eudora, Outlook, etc. The browser itself was functional. 1.1.18 is now back in use. The OS is XP SP3. Yes, I have a nonstandard SM installation. Program files are installed to: E:\Mozilla\SMonkey to keep my boot partition smaller, which makes boot partition image backups easier. 2.0.3 was installed to the same location. 1.1.18's config files have always been in the standard place: C:\Documents and Settings\[myname]\Application Data Has anyone dealt with this before, or can point me to a page where someone has? I had issues like that clear back when they came-out with SeaMonkey 2- the best way is not to upgrade until they get all the bugs worked-out, I think there's a settings under preferences, advanced for Seamonkey not to search for a upgrade. Stay tuned to this channel for news of when a good version comes out. Jack I'm afraid you're wrong there. The problem the OP posted was one of a problem profile migration. That is not a flaw in the program itself, but in the migration process. That is not going to improve. Anyone who is waiting for an improved migration tool is going to have a long wait. In fact, the profile migration will probably go away entirely, though that will be a while. The real answer is to migrate the data manually. It may be a pain but once its done its done, and you willbe positioned to move on. Yes, we all hope that there will be many improvements to the suite, but an improved migration tool, probably not. Lee After many failed profile migration attempts, I discovered the key is to change the program group that SM is installed in. Instead of accepting the default Seamonkey, I changed it to Seamonkey2. Migration proceeded normally, and all my profile settings, email, passwords, etc. were carried over. Plug-ins and extensions were lost and had to be manually re-installed. HTH Lance ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Bad upgrade from 1.1.18 to 2.03
cmcadams wrote: Leonidas Jones wrote: u...@domain.invalid wrote: cmcadams wrote: Last evening I finally uninstalled 1.1.18, and installed 2.03. My Profiles Bookmarks Email and newsgroup accounts Addresses Saved emails didn't make the trip. 2.0.3's wizard said it had imported everything, but no evidence of that. Asking 2.03 to import the missing items after installation was fruitless since I don't use Eudora, Outlook, etc. The browser itself was functional. 1.1.18 is now back in use. The OS is XP SP3. Yes, I have a nonstandard SM installation. Program files are installed to: E:\Mozilla\SMonkey to keep my boot partition smaller, which makes boot partition image backups easier. 2.0.3 was installed to the same location. 1.1.18's config files have always been in the standard place: C:\Documents and Settings\[myname]\Application Data Has anyone dealt with this before, or can point me to a page where someone has? I had issues like that clear back when they came-out with SeaMonkey 2- the best way is not to upgrade until they get all the bugs worked-out, I think there's a settings under preferences, advanced for Seamonkey not to search for a upgrade. Stay tuned to this channel for news of when a good version comes out. Jack I'm afraid you're wrong there. The problem the OP posted was one of a problem profile migration. That is not a flaw in the program itself, but in the migration process. That is not going to improve. Anyone who is waiting for an improved migration tool is going to have a long wait. In fact, the profile migration will probably go away entirely, though that will be a while. The real answer is to migrate the data manually. It may be a pain but once its done its done, and you willbe positioned to move on. Yes, we all hope that there will be many improvements to the suite, but an improved migration tool, probably not. Lee Okay, that worked. Thank you very much. For those who might Google this in the future, I copied the CONTENTS of 1.1.18's *.slt folder (not the folder itself, but from within the folder) to the clipboard, made a backup copy of 2.03's as-installed *.default folder (just in case) and then deleted the contents of that folder. I then Pasted the copied contents of 1.1.18's *.slt into 2.03's new *.default folder. That folder, containing 2.03's config files, is in the new 2.03-created Seamonkey folder visible from: C:\Documents and Settings\[myname]\Application Data\Mozilla Et voila. Can someone now explain to me what the heck the red underlines under certain words are about, when you're typing a message in 2.03? Craig Its your spellchecker, flagging a misspelling. Lee ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Bad upgrade from 1.1.18 to 2.03
Leonidas Jones wrote: cmcadams wrote: Leonidas Jones wrote: u...@domain.invalid wrote: cmcadams wrote: Last evening I finally uninstalled 1.1.18, and installed 2.03. My Profiles Bookmarks Email and newsgroup accounts Addresses Saved emails didn't make the trip. 2.0.3's wizard said it had imported everything, but no evidence of that. Asking 2.03 to import the missing items after installation was fruitless since I don't use Eudora, Outlook, etc. The browser itself was functional. 1.1.18 is now back in use. The OS is XP SP3. Yes, I have a nonstandard SM installation. Program files are installed to: E:\Mozilla\SMonkey to keep my boot partition smaller, which makes boot partition image backups easier. 2.0.3 was installed to the same location. 1.1.18's config files have always been in the standard place: C:\Documents and Settings\[myname]\Application Data Has anyone dealt with this before, or can point me to a page where someone has? I had issues like that clear back when they came-out with SeaMonkey 2- the best way is not to upgrade until they get all the bugs worked-out, I think there's a settings under preferences, advanced for Seamonkey not to search for a upgrade. Stay tuned to this channel for news of when a good version comes out. Jack I'm afraid you're wrong there. The problem the OP posted was one of a problem profile migration. That is not a flaw in the program itself, but in the migration process. That is not going to improve. Anyone who is waiting for an improved migration tool is going to have a long wait. In fact, the profile migration will probably go away entirely, though that will be a while. The real answer is to migrate the data manually. It may be a pain but once its done its done, and you willbe positioned to move on. Yes, we all hope that there will be many improvements to the suite, but an improved migration tool, probably not. Lee Okay, that worked. Thank you very much. For those who might Google this in the future, I copied the CONTENTS of 1.1.18's *.slt folder (not the folder itself, but from within the folder) to the clipboard, made a backup copy of 2.03's as-installed *.default folder (just in case) and then deleted the contents of that folder. I then Pasted the copied contents of 1.1.18's *.slt into 2.03's new *.default folder. That folder, containing 2.03's config files, is in the new 2.03-created Seamonkey folder visible from: C:\Documents and Settings\[myname]\Application Data\Mozilla Et voila. Can someone now explain to me what the heck the red underlines under certain words are about, when you're typing a message in 2.03? Craig Its your spellchecker, flagging a misspelling. Ah. Not misspellings, just not in the dictionary. I had it turned off in 1.1.18. Craig ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Bad upgrade from 1.1.18 to 2.03
cmcadams wrote: Leonidas Jones wrote: u...@domain.invalid wrote: cmcadams wrote: Last evening I finally uninstalled 1.1.18, and installed 2.03. My Profiles Bookmarks Email and newsgroup accounts Addresses Saved emails didn't make the trip. 2.0.3's wizard said it had imported everything, but no evidence of that. Asking 2.03 to import the missing items after installation was fruitless since I don't use Eudora, Outlook, etc. The browser itself was functional. 1.1.18 is now back in use. The OS is XP SP3. Yes, I have a nonstandard SM installation. Program files are installed to: E:\Mozilla\SMonkey to keep my boot partition smaller, which makes boot partition image backups easier. 2.0.3 was installed to the same location. 1.1.18's config files have always been in the standard place: C:\Documents and Settings\[myname]\Application Data Has anyone dealt with this before, or can point me to a page where someone has? I had issues like that clear back when they came-out with SeaMonkey 2- the best way is not to upgrade until they get all the bugs worked-out, I think there's a settings under preferences, advanced for Seamonkey not to search for a upgrade. Stay tuned to this channel for news of when a good version comes out. Jack I'm afraid you're wrong there. The problem the OP posted was one of a problem profile migration. That is not a flaw in the program itself, but in the migration process. That is not going to improve. Anyone who is waiting for an improved migration tool is going to have a long wait. In fact, the profile migration will probably go away entirely, though that will be a while. The real answer is to migrate the data manually. It may be a pain but once its done its done, and you willbe positioned to move on. Yes, we all hope that there will be many improvements to the suite, but an improved migration tool, probably not. Lee Okay, that worked. Thank you very much. For those who might Google this in the future, I copied the CONTENTS of 1.1.18's *.slt folder (not the folder itself, but from within the folder) to the clipboard, made a backup copy of 2.03's as-installed *.default folder (just in case) and then deleted the contents of that folder. I then Pasted the copied contents of 1.1.18's *.slt into 2.03's new *.default folder. That folder, containing 2.03's config files, is in the new 2.03-created Seamonkey folder visible from: C:\Documents and Settings\[myname]\Application Data\Mozilla Et voila. Can someone now explain to me what the heck the red underlines under certain words are about, when you're typing a message in 2.03? Craig That's the spellchecker indicating the words are misspelled,or its not familiar with the words, in which case you have it to learn the word. -- Phillip M. Jones, C.E.T.If it's Fixed, Don't Break it http://www.phillipmjones.net http://www.vpea.org mailto:pjon...@kimbanet.com ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Bad upgrade from 1.1.18 to 2.03
cmcadams wrote: Leonidas Jones wrote: cmcadams wrote: Leonidas Jones wrote: u...@domain.invalid wrote: cmcadams wrote: Last evening I finally uninstalled 1.1.18, and installed 2.03. My Profiles Bookmarks Email and newsgroup accounts Addresses Saved emails didn't make the trip. 2.0.3's wizard said it had imported everything, but no evidence of that. Asking 2.03 to import the missing items after installation was fruitless since I don't use Eudora, Outlook, etc. The browser itself was functional. 1.1.18 is now back in use. The OS is XP SP3. Yes, I have a nonstandard SM installation. Program files are installed to: E:\Mozilla\SMonkey to keep my boot partition smaller, which makes boot partition image backups easier. 2.0.3 was installed to the same location. 1.1.18's config files have always been in the standard place: C:\Documents and Settings\[myname]\Application Data Has anyone dealt with this before, or can point me to a page where someone has? I had issues like that clear back when they came-out with SeaMonkey 2- the best way is not to upgrade until they get all the bugs worked-out, I think there's a settings under preferences, advanced for Seamonkey not to search for a upgrade. Stay tuned to this channel for news of when a good version comes out. Jack I'm afraid you're wrong there. The problem the OP posted was one of a problem profile migration. That is not a flaw in the program itself, but in the migration process. That is not going to improve. Anyone who is waiting for an improved migration tool is going to have a long wait. In fact, the profile migration will probably go away entirely, though that will be a while. The real answer is to migrate the data manually. It may be a pain but once its done its done, and you willbe positioned to move on. Yes, we all hope that there will be many improvements to the suite, but an improved migration tool, probably not. Lee Okay, that worked. Thank you very much. For those who might Google this in the future, I copied the CONTENTS of 1.1.18's *.slt folder (not the folder itself, but from within the folder) to the clipboard, made a backup copy of 2.03's as-installed *.default folder (just in case) and then deleted the contents of that folder. I then Pasted the copied contents of 1.1.18's *.slt into 2.03's new *.default folder. That folder, containing 2.03's config files, is in the new 2.03-created Seamonkey folder visible from: C:\Documents and Settings\[myname]\Application Data\Mozilla Et voila. Can someone now explain to me what the heck the red underlines under certain words are about, when you're typing a message in 2.03? Craig Its your spellchecker, flagging a misspelling. Ah. Not misspellings, just not in the dictionary. I had it turned off in 1.1.18. Craig You can always right click and add them to the dictionary. Lee ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Bad upgrade from 1.1.18 to 2.03
cmcadams wrote: Yes, I have a nonstandard SM installation. Program files are installed to: E:\Mozilla\SMonkey to keep my boot partition smaller, which makes boot partition image backups easier. 2.0.3 was installed to the same location. You should not install SM2 into the same directory used for SM1. Graham. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Bad upgrade from 1.1.18 to 2.03
Leonidas Jones wrote: cmcadams wrote: Leonidas Jones wrote: cmcadams wrote: Leonidas Jones wrote: u...@domain.invalid wrote: cmcadams wrote: Last evening I finally uninstalled 1.1.18, and installed 2.03. My Profiles Bookmarks Email and newsgroup accounts Addresses Saved emails didn't make the trip. 2.0.3's wizard said it had imported everything, but no evidence of that. Asking 2.03 to import the missing items after installation was fruitless since I don't use Eudora, Outlook, etc. The browser itself was functional. 1.1.18 is now back in use. The OS is XP SP3. Yes, I have a nonstandard SM installation. Program files are installed to: E:\Mozilla\SMonkey to keep my boot partition smaller, which makes boot partition image backups easier. 2.0.3 was installed to the same location. 1.1.18's config files have always been in the standard place: C:\Documents and Settings\[myname]\Application Data Has anyone dealt with this before, or can point me to a page where someone has? I had issues like that clear back when they came-out with SeaMonkey 2- the best way is not to upgrade until they get all the bugs worked-out, I think there's a settings under preferences, advanced for Seamonkey not to search for a upgrade. Stay tuned to this channel for news of when a good version comes out. Jack I'm afraid you're wrong there. The problem the OP posted was one of a problem profile migration. That is not a flaw in the program itself, but in the migration process. That is not going to improve. Anyone who is waiting for an improved migration tool is going to have a long wait. In fact, the profile migration will probably go away entirely, though that will be a while. The real answer is to migrate the data manually. It may be a pain but once its done its done, and you willbe positioned to move on. Yes, we all hope that there will be many improvements to the suite, but an improved migration tool, probably not. Lee Okay, that worked. Thank you very much. For those who might Google this in the future, I copied the CONTENTS of 1.1.18's *.slt folder (not the folder itself, but from within the folder) to the clipboard, made a backup copy of 2.03's as-installed *.default folder (just in case) and then deleted the contents of that folder. I then Pasted the copied contents of 1.1.18's *.slt into 2.03's new *.default folder. That folder, containing 2.03's config files, is in the new 2.03-created Seamonkey folder visible from: C:\Documents and Settings\[myname]\Application Data\Mozilla Et voila. Can someone now explain to me what the heck the red underlines under certain words are about, when you're typing a message in 2.03? Craig Its your spellchecker, flagging a misspelling. Ah. Not misspellings, just not in the dictionary. I had it turned off in 1.1.18. Craig You can always right click and add them to the dictionary. Lee I had it turned off, before. Forgot it was there and didn't recognize it when it showed up again. Craig ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Bad upgrade from 1.1.18 to 2.03
Last evening I finally uninstalled 1.1.18, and installed 2.03. My Profiles Bookmarks Email and newsgroup accounts Addresses Saved emails didn't make the trip. 2.0.3's wizard said it had imported everything, but no evidence of that. Asking 2.03 to import the missing items after installation was fruitless since I don't use Eudora, Outlook, etc. The browser itself was functional. 1.1.18 is now back in use. The OS is XP SP3. Yes, I have a nonstandard SM installation. Program files are installed to: E:\Mozilla\SMonkey to keep my boot partition smaller, which makes boot partition image backups easier. 2.0.3 was installed to the same location. 1.1.18's config files have always been in the standard place: C:\Documents and Settings\[myname]\Application Data Has anyone dealt with this before, or can point me to a page where someone has? ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Bad upgrade from 1.1.18 to 2.03
cmcadams wrote: Last evening I finally uninstalled 1.1.18, and installed 2.03. My Profiles Bookmarks Email and newsgroup accounts Addresses Saved emails didn't make the trip. 2.0.3's wizard said it had imported everything, but no evidence of that. Asking 2.03 to import the missing items after installation was fruitless since I don't use Eudora, Outlook, etc. The browser itself was functional. 1.1.18 is now back in use. The OS is XP SP3. Yes, I have a nonstandard SM installation. Program files are installed to: E:\Mozilla\SMonkey to keep my boot partition smaller, which makes boot partition image backups easier. 2.0.3 was installed to the same location. 1.1.18's config files have always been in the standard place: C:\Documents and Settings\[myname]\Application Data Has anyone dealt with this before, or can point me to a page where someone has? I had issues like that clear back when they came-out with SeaMonkey 2- the best way is not to upgrade until they get all the bugs worked-out, I think there's a settings under preferences, advanced for Seamonkey not to search for a upgrade. Stay tuned to this channel for news of when a good version comes out. Jack ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Bad upgrade from 1.1.18 to 2.03
u...@domain.invalid wrote: cmcadams wrote: Last evening I finally uninstalled 1.1.18, and installed 2.03. My Profiles Bookmarks Email and newsgroup accounts Addresses Saved emails didn't make the trip. 2.0.3's wizard said it had imported everything, but no evidence of that. Asking 2.03 to import the missing items after installation was fruitless since I don't use Eudora, Outlook, etc. The browser itself was functional. 1.1.18 is now back in use. The OS is XP SP3. Yes, I have a nonstandard SM installation. Program files are installed to: E:\Mozilla\SMonkey to keep my boot partition smaller, which makes boot partition image backups easier. 2.0.3 was installed to the same location. 1.1.18's config files have always been in the standard place: C:\Documents and Settings\[myname]\Application Data Has anyone dealt with this before, or can point me to a page where someone has? I had issues like that clear back when they came-out with SeaMonkey 2- the best way is not to upgrade until they get all the bugs worked-out, I think there's a settings under preferences, advanced for Seamonkey not to search for a upgrade. Stay tuned to this channel for news of when a good version comes out. Jack Was afraid of that. Thanks. Craig ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
