Seamonkey 1.1.7 in Question

As to why it showed the wrong version, I would never know without seeing how you handle your programs. It should never happen because a profile was created with a different version. Actually, it does not matter if you start with one version or another, as long as you don't use that profile with that version. But, in my case, I name profiles for the version which it was created for, and I don't see what you report. My installed SM1.1.7 has a SM1.1.4 profile, and the unzipped one has a "netscape" profile. Both indicate that it is the same version, as I mentioned before.
By the way, if the profile is not corrupted, you don't have to worry about having removed a program. Even a corrupted profile can be utilized, by creating a new profile, and copy/pasting the key file, not the prefs.js, which is, most likely corrupted.

 

Greetings,

Trying to end this ongoing post, I contribute the following.

FWIW, these are only MY observations:
I do not have SM 1.0.5, so I will use SM 1.1.6 in examples.

The information displayed in Help > about Seamonkey is constructed from data in various *.dtd files in
the PROGRAM directory of the Program that is actually running at the time.

eg.
If you are actually running SM 1.1.6, then it will display information from the .dtd files in the directory that you have SM 1.1.6 installed in.
In my case: e:\Program Files\Monk_1.1.6\
( or the directory that unzipped files are in).

Profile has NOTHING to do with this display......

When you start any version of SM, one of the first things done is compare the rv: number stored in the prefs.js file

user_pref( "browser.startup.homepage_override.mstone ", "rv:1.8.1.9 ");

with the rv: number of the running version. If they do not agree, you are re-directed to the "override: url" specified in the:
(in MY case....)
e:\Program Files\Monk_1.1.6\chrome\US.jar\locale\US\navigator-region\region.properties

Depending on the running version, if the rv: number does not equal the running version,AND the running version IS NOT the latest version, you are re-directed to the "warning" page as indicated by Ray's link.

http://www.raysmyth.net/sm-6.jpg

If the running version is the latest version, you are directed to the "congratulations" page.

recap:
rv: for SM 1.1.6 = 1.8.1.9
rv: for SM 1.1.7 = 1.8.1.11

If you USE a profile for SM 1.1.6, it writes rv:1.8.1.9 to the prefs.js file.
If you then USE the same profile for SM 1.1.7, it will re-direct you to the "congratulations" page.

If you USE a profile for SM 1.1.7 it writes rv:1.8.1.11 to prefs.js file.
If you then use the same profile with SM 1.1.6, it will re-direct you to the "warning" page......

This is one of the many reasons why you should NOT share profiles.....

I know that this looks convoluted, but this is how I think it works.
Please dis-regard typos...

Hope this is of some help.

regards:captjldavis

 

Thank you so much Capt. Davis -- You cleared up my wondering and your explanation tells me a lot.

Now I can't track every step your providing and don't totally understand all of it but, having done a little programming in Turbo Pascal back in the days of DOS I can follow what your saying.

You also cleared up something I been wonder WHY about ever since I dropped Netscape 7.0.2 and started using Seamonkey as well as having installed Mozilla.

I been using Seamonkey as my default browser but, still have Netscape and the Mozilla browsers installed and therefore I occasionally will load them up AND against Ramona's advice I been using the same profile with all three browsers.

AND all this time I thought it was working great but, each time I loaded a different browser from the one last loaded, it would default to the browser's web site and I thought that strange and wondered WHY!!

Especially so since I could click the home button and it would go to the default home page I had established.

With your explanation I now understand that each different browser changes the pref.js file and that is the WHY the next different browser or version number doesn't read what it expects when it loads and therefore goes to the browsers web site page.

So, Thanks for explaining that.

I think we can now end this Thread and my THANKS to ALL who helped with this.

Ray

 

Thank you Capt., I will keep your explanation handy. I, often, said in other fora that sharing the same profile between other programs confuses the prefs.js. Not very sophisticated, but true.
But what you said in your reply is being contradicted

.
Isn't the prefs.js file in the profile? Eventually, everything goes to pot, sharing one profile. That's why Ramona urged that different programs use their own profiles. It takes a bit more time, but if desired, each program can display equally well with its profile. Home page is the least of my concerns, because I can use one tab, or more than one, or have a favorite page in the Prefbar or Personal Toolbar, or all of the above. The program which I use now has four tabs, four Prefbar link, fourteen folders and 19 individual bookmarks in the Personal Bookmarks folder.
Anyway, the fact that the fact that Netscape and Mozilla were, also, used, and the fact not mentioned, even occasionally, contributed to my confusion

 

Westside,

I stand by what I said......

"Profile has NOTHING to do with this display...... "

Of course "....... the prefs.js file in the profile? " but I am pretty sure that the "The information displayed in Help > about Seamonkey" is constructed from data in various *.dtd and some *.dll files ( including Necko.dll )perhaps others also......

regards:captjlddavis

 

Just wanted to point out that Netscape and Mozilla use of the same profile had nothing to do with what happened in this thread because neither had been loaded or used since SM 1.1.7 was first installed back on November 31, 2007 and that is why they were never mentioned.

Thanks, --- Ray

 

I was replying to the above statement (my emphasis on the occasionally.
Of course, if you have not done that since

, I have no idea why you had the problem. Anyway, it is time to stop the thread.