SeaMonkey bug in 1.1 (I think) - Mozilla

This is a discussion on SeaMonkey bug in 1.1 (I think) - Mozilla ; I just installed SeaMonkey 1.1 (browser only) exactly by the book, and I also uninstalled all extensions before doing so, adding them back one by one, quicklaunch off, closing and opening the browser between installs, and testing it out as ...

+ Reply to Thread
Page 1 of 2 1 2 LastLast
Results 1 to 20 of 24

Thread: SeaMonkey bug in 1.1 (I think)

  1. SeaMonkey bug in 1.1 (I think)

    I just installed SeaMonkey 1.1 (browser only) exactly by the book, and I
    also uninstalled all extensions before doing so, adding them back one by
    one, quicklaunch off, closing and opening the browser between installs, and
    testing it out as I went along, which was a good thing or else I wouldn't
    have been able to isolate the problem.

    Everything was fine until I got to the prefbar. It installed OK,
    self-updated OK, browser worked fine, but when I switched profiles a note
    popped up, as it also had done in the default profile, asking if I wanted to
    update its data base. I clicked yes, and the note closed but then a big
    blank 1" band appeared across the bottom of the screen. I closed the browser
    but after that it froze, and wouldn't open with any shortcut or
    seamonkey.exe.

    Reverted with GoBack to before the prefbar installation and installed it
    again. When I switched profiles, same thing happened again. This time I
    answered no to the data base update box ("cancel" as I recall), but the
    result was the same. Love SeaMonkey, but unfortunately this one's
    mission-critical so I'm back to 1.0.7 until it can be fixed.

    One additional item. When you delete an extension with the extension
    manager, it asks you to specify a place to create a back up folder (I
    believe, but I'm not sure, that you don't have to fill this in). I specified
    D:\ , but no files or folders were ever created there. Everything was
    automatically backed up to *.slt\chrome\uninstall\backup\ of the default
    profile. No harm that I can see, but the user-defined location doesn't work,
    at least it didn't for me.

    Extensions: adblock (old), dictionary search, flashblock, prefbar, themer,
    home button (on nav. toolbar), extension manager, extension uninstallerapi.

    Running Windows 98SE.




  2. Re: SeaMonkey bug in 1.1 (I think)

    On Friday 19 January 2007 19:17, Roger Fink wrote:
    >... but then a big
    > blank 1" band appeared across the bottom of the screen.


    Hi Roger,

    I experienced the same when I tried to just delete a .jar file. So maybe an
    extension-file is missing in your profile folder, but is still listed in
    chrome.rdf.

    I recommend to read
    http://kb.mozillazine.org/Uninstalli...lling_manually
    beginning from "Uninstalling in other versions"
    carefully.

    I just had to remove all entries regarding the "missing" (removed) extension
    in chrome.rdf and delete the XUL.mfasl file. Then seamonkey was looking
    poerfect again. But look in the URL above first.

    Oh, before changing/removing anything: backup/copy your profile folder, so you
    can revert in case something goes wrong.

    I cannot say anything about the freeze, but I also have an old Win98 box and
    that freezes all the time. I guess thats normal W98 behaviour and has nothing
    to do with Seamonkey...

    Daniel
    --
    Daniel Bauer photographer Basel Switzerland
    professional photography: http://www.daniel-bauer.com
    Madagascar special: http://www.sanic.ch

  3. Re: SeaMonkey bug in 1.1 (I think)

    Daniel Bauer wrote:
    > On Friday 19 January 2007 19:17, Roger Fink wrote:
    >> ... but then a big
    >> blank 1" band appeared across the bottom of the screen.

    >
    > Hi Roger,
    >
    > I experienced the same when I tried to just delete a .jar file. So
    > maybe an extension-file is missing in your profile folder, but is
    > still listed in chrome.rdf.
    >
    > I recommend to read
    > http://kb.mozillazine.org/Uninstalli...lling_manually
    > beginning from "Uninstalling in other versions"
    > carefully.
    >
    > I just had to remove all entries regarding the "missing" (removed)
    > extension in chrome.rdf and delete the XUL.mfasl file. Then seamonkey
    > was looking poerfect again. But look in the URL above first.
    >
    > Oh, before changing/removing anything: backup/copy your profile
    > folder, so you can revert in case something goes wrong.
    >
    > I cannot say anything about the freeze, but I also have an old Win98
    > box and that freezes all the time. I guess thats normal W98 behaviour
    > and has nothing to do with Seamonkey...
    >
    > Daniel


    Thanks for the reply and I will check it out. But even if the solution
    proposed in mozillazine work, the complexity of the solution, as you've
    describe it through your own experiences, merits a structural fix from the
    developers, IMO.

    BTW, I wouldn't be too dismissive of of the current operating system from
    4000 mi. away - it's a fairly recent box with 98 installed by choice. Apart
    from very infrequent mis-interaction with the printer, it rarely crashes,
    and when something does go wrong, it's eminently fixable.



  4. Re: SeaMonkey bug in 1.1 (I think)

    Roger Fink wrote:
    > I just installed SeaMonkey 1.1 (browser only) exactly by the book, and I
    > also uninstalled all extensions before doing so, adding them back one by
    > one, quicklaunch off, closing and opening the browser between installs, and
    > testing it out as I went along, which was a good thing or else I wouldn't
    > have been able to isolate the problem.
    >
    > Everything was fine until I got to the prefbar. It installed OK,
    > self-updated OK, browser worked fine, but when I switched profiles a note
    > popped up, as it also had done in the default profile, asking if I wanted to
    > update its data base. I clicked yes, and the note closed but then a big
    > blank 1" band appeared across the bottom of the screen. I closed the browser
    > but after that it froze, and wouldn't open with any shortcut or
    > seamonkey.exe.
    >
    > Reverted with GoBack to before the prefbar installation and installed it
    > again. When I switched profiles, same thing happened again. This time I
    > answered no to the data base update box ("cancel" as I recall), but the
    > result was the same. Love SeaMonkey, but unfortunately this one's
    > mission-critical so I'm back to 1.0.7 until it can be fixed.
    >
    > One additional item. When you delete an extension with the extension
    > manager, it asks you to specify a place to create a back up folder (I
    > believe, but I'm not sure, that you don't have to fill this in). I specified
    > D:\ , but no files or folders were ever created there. Everything was
    > automatically backed up to *.slt\chrome\uninstall\backup\ of the default
    > profile. No harm that I can see, but the user-defined location doesn't work,
    > at least it didn't for me.
    >
    > Extensions: adblock (old), dictionary search, flashblock, prefbar, themer,
    > home button (on nav. toolbar), extension manager, extension uninstallerapi.
    >
    > Running Windows 98SE.
    >


    Roger, I had a similar thing happen (band across bottom of browser
    screen) a few versions ago (may have even been Moz suite).

    With mine, there was a message in the bottom part of screen, that
    indicated one of the extensions I was using was incompatible with the
    updated browser. Do you get similar message?? If so, go looking for an
    updated version of problem extension....maybe give developers a couple
    of days!

    HTH

    Daniel

  5. Re: SeaMonkey bug in 1.1 (I think)

    Daniel wrote:
    > Roger Fink wrote:
    >> I just installed SeaMonkey 1.1 (browser only) exactly by the book,
    >> and I also uninstalled all extensions before doing so, adding them
    >> back one by one, quicklaunch off, closing and opening the browser
    >> between installs, and testing it out as I went along, which was a
    >> good thing or else I wouldn't have been able to isolate the problem.
    >>
    >> Everything was fine until I got to the prefbar. It installed OK,
    >> self-updated OK, browser worked fine, but when I switched profiles a
    >> note popped up, as it also had done in the default profile, asking
    >> if I wanted to update its data base. I clicked yes, and the note
    >> closed but then a big blank 1" band appeared across the bottom of
    >> the screen. I closed the browser but after that it froze, and
    >> wouldn't open with any shortcut or seamonkey.exe.
    >>
    >> Reverted with GoBack to before the prefbar installation and
    >> installed it again. When I switched profiles, same thing happened
    >> again. This time I answered no to the data base update box ("cancel"
    >> as I recall), but the result was the same. Love SeaMonkey, but
    >> unfortunately this one's mission-critical so I'm back to 1.0.7 until
    >> it can be fixed.
    >>
    >> One additional item. When you delete an extension with the extension
    >> manager, it asks you to specify a place to create a back up folder (I
    >> believe, but I'm not sure, that you don't have to fill this in). I
    >> specified D:\ , but no files or folders were ever created there.
    >> Everything was automatically backed up to
    >> *.slt\chrome\uninstall\backup\ of the default profile. No harm that
    >> I can see, but the user-defined location doesn't work, at least it
    >> didn't for me.
    >>
    >> Extensions: adblock (old), dictionary search, flashblock, prefbar,
    >> themer, home button (on nav. toolbar), extension manager, extension
    >> uninstallerapi.
    >>
    >> Running Windows 98SE.
    >>

    >
    > Roger, I had a similar thing happen (band across bottom of browser
    > screen) a few versions ago (may have even been Moz suite).
    >
    > With mine, there was a message in the bottom part of screen, that
    > indicated one of the extensions I was using was incompatible with the
    > updated browser. Do you get similar message?? If so, go looking for an
    > updated version of problem extension....maybe give developers a couple
    > of days!
    >
    > HTH
    >
    > Daniel


    The same thought had occurred to me - wait for a prefbar update. I just
    updated the version I had, which was one behind, thinking that maybe the
    problem was that it couldn't make the jump, and then repeated the whole
    process, but the result was the same. BTW, still no message on the bottom
    band.



  6. Re: SeaMonkey bug in 1.1 (I think)

    Daniel wrote:
    > Roger Fink wrote:
    >> I just installed SeaMonkey 1.1 (browser only) exactly by the book, and I
    >> also uninstalled all extensions before doing so, adding them back one by
    >> one, quicklaunch off, closing and opening the browser between
    >> installs, and
    >> testing it out as I went along, which was a good thing or else I wouldn't
    >> have been able to isolate the problem.
    >>
    >> Everything was fine until I got to the prefbar. It installed OK,
    >> self-updated OK, browser worked fine, but when I switched profiles a note
    >> popped up, as it also had done in the default profile, asking if I
    >> wanted to
    >> update its data base. I clicked yes, and the note closed but then a big
    >> blank 1" band appeared across the bottom of the screen. I closed the
    >> browser
    >> but after that it froze, and wouldn't open with any shortcut or
    >> seamonkey.exe.
    >>
    >> Reverted with GoBack to before the prefbar installation and installed it
    >> again. When I switched profiles, same thing happened again. This time I
    >> answered no to the data base update box ("cancel" as I recall), but the
    >> result was the same. Love SeaMonkey, but unfortunately this one's
    >> mission-critical so I'm back to 1.0.7 until it can be fixed.
    >>
    >> One additional item. When you delete an extension with the extension
    >> manager, it asks you to specify a place to create a back up folder (I
    >> believe, but I'm not sure, that you don't have to fill this in). I
    >> specified
    >> D:\ , but no files or folders were ever created there. Everything was
    >> automatically backed up to *.slt\chrome\uninstall\backup\ of the default
    >> profile. No harm that I can see, but the user-defined location doesn't
    >> work,
    >> at least it didn't for me.
    >>
    >> Extensions: adblock (old), dictionary search, flashblock, prefbar,
    >> themer,
    >> home button (on nav. toolbar), extension manager, extension
    >> uninstallerapi.
    >>
    >> Running Windows 98SE.
    >>

    >
    > Roger, I had a similar thing happen (band across bottom of browser
    > screen) a few versions ago (may have even been Moz suite).
    >
    > With mine, there was a message in the bottom part of screen, that
    > indicated one of the extensions I was using was incompatible with the
    > updated browser. Do you get similar message?? If so, go looking for an
    > updated version of problem extension....maybe give developers a couple
    > of days!
    >
    > HTH
    >
    > Daniel


    Had a similar problem. If I recall, deleting the XUL.mlf was one
    possibility I tried, which is not a bad practice from time to time.

    Otherwise it's a chrome.rdf problem. Don't remember exactly, or how I
    got rid of it. I think I deleted the entire chrome.rdf and reinstalled
    the extensions. Try using Mr. Tech Local Install to verify versions.
    It has a max version override available when installing extensions.

    Searching the earlier threads on this board, look through>

    Error message on invocation of Seamonkey - 11/13/2006
    Extension Error - 11/13/2006

    That kind of thing (a red message in a grey banner at the
    bottom of the browser window) is usually caused by a misbehaving
    extension. The "classical" solution is to disable your extensions one at
    a time: when the problem disappears, you've got the culprit. Sometimes
    the contents of the message can help you guess which extension is
    causing the problem. (Do you have an extension which alters the
    Preferences UI ?)

    Note: To help you manage your Seamonkey extensions, there exist a couple
    of extensions named "Extension Manager" and "Extension Uninstaller API".
    The former requires the latter. IIRC, they are both available from
    http://addons.mozilla.org/seamonkey/ . I have them installed, and I
    don't see that grey banner, but I'm using Sm 1.5 alpha.




  7. Re: SeaMonkey bug in 1.1 (I think)

    On 1/19/2007 7:36 PM Roger Fink created this reply
    > Daniel wrote:
    >
    >> Roger Fink wrote:
    >>
    >>> I just installed SeaMonkey 1.1 (browser only) exactly by the book,
    >>> and I also uninstalled all extensions before doing so, adding them
    >>> back one by one, quicklaunch off, closing and opening the browser
    >>> between installs, and testing it out as I went along, which was a
    >>> good thing or else I wouldn't have been able to isolate the problem.
    >>>
    >>> Everything was fine until I got to the prefbar. It installed OK,
    >>> self-updated OK, browser worked fine, but when I switched profiles a
    >>> note popped up, as it also had done in the default profile, asking
    >>> if I wanted to update its data base. I clicked yes, and the note
    >>> closed but then a big blank 1" band appeared across the bottom of
    >>> the screen. I closed the browser but after that it froze, and
    >>> wouldn't open with any shortcut or seamonkey.exe.
    >>>
    >>> Reverted with GoBack to before the prefbar installation and
    >>> installed it again. When I switched profiles, same thing happened
    >>> again. This time I answered no to the data base update box ("cancel"
    >>> as I recall), but the result was the same. Love SeaMonkey, but
    >>> unfortunately this one's mission-critical so I'm back to 1.0.7 until
    >>> it can be fixed.
    >>>
    >>> One additional item. When you delete an extension with the extension
    >>> manager, it asks you to specify a place to create a back up folder (I
    >>> believe, but I'm not sure, that you don't have to fill this in). I
    >>> specified D:\ , but no files or folders were ever created there.
    >>> Everything was automatically backed up to
    >>> *.slt\chrome\uninstall\backup\ of the default profile. No harm that
    >>> I can see, but the user-defined location doesn't work, at least it
    >>> didn't for me.
    >>>
    >>> Extensions: adblock (old), dictionary search, flashblock, prefbar,
    >>> themer, home button (on nav. toolbar), extension manager, extension
    >>> uninstallerapi.
    >>>
    >>> Running Windows 98SE.
    >>>
    >>>

    >> Roger, I had a similar thing happen (band across bottom of browser
    >> screen) a few versions ago (may have even been Moz suite).
    >>
    >> With mine, there was a message in the bottom part of screen, that
    >> indicated one of the extensions I was using was incompatible with the
    >> updated browser. Do you get similar message?? If so, go looking for an
    >> updated version of problem extension....maybe give developers a couple
    >> of days!
    >>
    >> HTH
    >>
    >> Daniel
    >>

    >
    > The same thought had occurred to me - wait for a prefbar update. I just
    > updated the version I had, which was one behind, thinking that maybe the
    > problem was that it couldn't make the jump, and then repeated the whole
    > process, but the result was the same. BTW, still no message on the bottom
    > band.
    >
    >
    >

    Hello Roger,

    Preference Bar works very well here on Win XP Pro.

    From your description I suspect it is an incompatibility between themes
    and another extension.
    Try removing all your extensions and see how it works, then try
    installing them again one at a time until you find the culprit. It is
    not SeaMonkey 1.1 that is at fault, it is one of the add on applications
    that is not compatible with another ad on application.

    Michael

    --
    Posting Guidelines for MTMM

    Posting To Mozilla.Test.Multimedia


    SeaMonkey the all in one browser, mail, and composer SeaMonkey

    The "All In One Internet Application Suite"

  8. Re: SeaMonkey bug in 1.1 (I think)

    Michael Gordon wrote:
    > On 1/19/2007 7:36 PM Roger Fink created this reply
    >> Daniel wrote:
    >>
    >>> Roger Fink wrote:
    >>>
    >>>> I just installed SeaMonkey 1.1 (browser only) exactly by the book,
    >>>> and I also uninstalled all extensions before doing so, adding them
    >>>> back one by one, quicklaunch off, closing and opening the browser
    >>>> between installs, and testing it out as I went along, which was a
    >>>> good thing or else I wouldn't have been able to isolate the
    >>>> problem.
    >>>>
    >>>> Everything was fine until I got to the prefbar. It installed OK,
    >>>> self-updated OK, browser worked fine, but when I switched profiles
    >>>> a note popped up, as it also had done in the default profile,
    >>>> asking
    >>>> if I wanted to update its data base. I clicked yes, and the note
    >>>> closed but then a big blank 1" band appeared across the bottom of
    >>>> the screen. I closed the browser but after that it froze, and
    >>>> wouldn't open with any shortcut or seamonkey.exe.
    >>>>
    >>>> Reverted with GoBack to before the prefbar installation and
    >>>> installed it again. When I switched profiles, same thing happened
    >>>> again. This time I answered no to the data base update box
    >>>> ("cancel" as I recall), but the result was the same. Love
    >>>> SeaMonkey, but unfortunately this one's mission-critical so I'm
    >>>> back to 1.0.7 until it can be fixed.
    >>>>
    >>>> One additional item. When you delete an extension with the
    >>>> extension manager, it asks you to specify a place to create a back
    >>>> up folder (I believe, but I'm not sure, that you don't have to
    >>>> fill this in). I specified D:\ , but no files or folders were ever
    >>>> created there. Everything was automatically backed up to
    >>>> *.slt\chrome\uninstall\backup\ of the default profile. No harm that
    >>>> I can see, but the user-defined location doesn't work, at least it
    >>>> didn't for me.
    >>>>
    >>>> Extensions: adblock (old), dictionary search, flashblock, prefbar,
    >>>> themer, home button (on nav. toolbar), extension manager, extension
    >>>> uninstallerapi.
    >>>>
    >>>> Running Windows 98SE.
    >>>>
    >>>>
    >>> Roger, I had a similar thing happen (band across bottom of browser
    >>> screen) a few versions ago (may have even been Moz suite).
    >>>
    >>> With mine, there was a message in the bottom part of screen, that
    >>> indicated one of the extensions I was using was incompatible with
    >>> the updated browser. Do you get similar message?? If so, go looking
    >>> for an updated version of problem extension....maybe give
    >>> developers a couple of days!
    >>>
    >>> HTH
    >>>
    >>> Daniel
    >>>

    >>
    >> The same thought had occurred to me - wait for a prefbar update. I
    >> just updated the version I had, which was one behind, thinking that
    >> maybe the problem was that it couldn't make the jump, and then
    >> repeated the whole process, but the result was the same. BTW, still
    >> no message on the bottom band.
    >>
    >>
    >>

    > Hello Roger,
    >
    > Preference Bar works very well here on Win XP Pro.
    >
    > From your description I suspect it is an incompatibility between
    > themes and another extension.
    > Try removing all your extensions and see how it works, then try
    > installing them again one at a time until you find the culprit. It is
    > not SeaMonkey 1.1 that is at fault, it is one of the add on
    > applications that is not compatible with another ad on application.
    >
    > Michael


    Michael, you may be right that it is not SeaMonkey 1.1, but that does not
    necessarily equate to not having a mystery on my hands. The first time I
    installed prefbar in 1.1 I used the default modern theme and all extensions
    had been removed and reinstalled one by one, and prefbar was the last in
    that sequence. When I installed it the second time (upgraded to latest
    prefbar version) all extensions had again been removed, I was again using
    the default modern theme, but this time prefbar was the first install in the
    sequence. A possible culprit could be a dated operating system that
    overworked developers (understandably) can't spend enough time on. Or,
    perhaps certain jar edits I do to customize the GUI had an effect, but I've
    been through many of these upgrades now (like for instance every one of
    them) and this has never presented a problem before.

    I assume that prefbar will in fact be updated as a result of this release -
    I hope so because it's so customizable and can display so much information
    that it's probably a more important tool for SeaMonkey than for FF. I'll try
    again then, or earlier if there is some procedure I did that could be
    improved, but it sounds to me as though what I did was pretty much what you
    are suggesting.










  9. Re: SeaMonkey bug in 1.1 (I think)

    On 1/19/2007 9:18 PM Roger Fink created this reply
    > Michael Gordon wrote:
    >
    >> On 1/19/2007 7:36 PM Roger Fink created this reply
    >>
    >>> Daniel wrote:
    >>>
    >>>
    >>>> Roger Fink wrote:
    >>>>
    >>>>
    >>>>> I just installed SeaMonkey 1.1 (browser only) exactly by the book,
    >>>>> and I also uninstalled all extensions before doing so, adding them
    >>>>> back one by one, quicklaunch off, closing and opening the browser
    >>>>> between installs, and testing it out as I went along, which was a
    >>>>> good thing or else I wouldn't have been able to isolate the
    >>>>> problem.
    >>>>>
    >>>>> Everything was fine until I got to the prefbar. It installed OK,
    >>>>> self-updated OK, browser worked fine, but when I switched profiles
    >>>>> a note popped up, as it also had done in the default profile,
    >>>>> asking
    >>>>> if I wanted to update its data base. I clicked yes, and the note
    >>>>> closed but then a big blank 1" band appeared across the bottom of
    >>>>> the screen. I closed the browser but after that it froze, and
    >>>>> wouldn't open with any shortcut or seamonkey.exe.
    >>>>>
    >>>>> Reverted with GoBack to before the prefbar installation and
    >>>>> installed it again. When I switched profiles, same thing happened
    >>>>> again. This time I answered no to the data base update box
    >>>>> ("cancel" as I recall), but the result was the same. Love
    >>>>> SeaMonkey, but unfortunately this one's mission-critical so I'm
    >>>>> back to 1.0.7 until it can be fixed.
    >>>>>
    >>>>> One additional item. When you delete an extension with the
    >>>>> extension manager, it asks you to specify a place to create a back
    >>>>> up folder (I believe, but I'm not sure, that you don't have to
    >>>>> fill this in). I specified D:\ , but no files or folders were ever
    >>>>> created there. Everything was automatically backed up to
    >>>>> *.slt\chrome\uninstall\backup\ of the default profile. No harm that
    >>>>> I can see, but the user-defined location doesn't work, at least it
    >>>>> didn't for me.
    >>>>>
    >>>>> Extensions: adblock (old), dictionary search, flashblock, prefbar,
    >>>>> themer, home button (on nav. toolbar), extension manager, extension
    >>>>> uninstallerapi.
    >>>>>
    >>>>> Running Windows 98SE.
    >>>>>
    >>>>>
    >>>>>
    >>>> Roger, I had a similar thing happen (band across bottom of browser
    >>>> screen) a few versions ago (may have even been Moz suite).
    >>>>
    >>>> With mine, there was a message in the bottom part of screen, that
    >>>> indicated one of the extensions I was using was incompatible with
    >>>> the updated browser. Do you get similar message?? If so, go looking
    >>>> for an updated version of problem extension....maybe give
    >>>> developers a couple of days!
    >>>>
    >>>> HTH
    >>>>
    >>>> Daniel
    >>>>
    >>>>
    >>> The same thought had occurred to me - wait for a prefbar update. I
    >>> just updated the version I had, which was one behind, thinking that
    >>> maybe the problem was that it couldn't make the jump, and then
    >>> repeated the whole process, but the result was the same. BTW, still
    >>> no message on the bottom band.
    >>>
    >>>
    >>>
    >>>

    >> Hello Roger,
    >>
    >> Preference Bar works very well here on Win XP Pro.
    >>
    >> From your description I suspect it is an incompatibility between
    >> themes and another extension.
    >> Try removing all your extensions and see how it works, then try
    >> installing them again one at a time until you find the culprit. It is
    >> not SeaMonkey 1.1 that is at fault, it is one of the add on
    >> applications that is not compatible with another ad on application.
    >>
    >> Michael
    >>

    >
    > Michael, you may be right that it is not SeaMonkey 1.1, but that does not
    > necessarily equate to not having a mystery on my hands. The first time I
    > installed prefbar in 1.1 I used the default modern theme and all extensions
    > had been removed and reinstalled one by one, and prefbar was the last in
    > that sequence. When I installed it the second time (upgraded to latest
    > prefbar version) all extensions had again been removed, I was again using
    > the default modern theme, but this time prefbar was the first install in the
    > sequence. A possible culprit could be a dated operating system that
    > overworked developers (understandably) can't spend enough time on. Or,
    > perhaps certain jar edits I do to customize the GUI had an effect, but I've
    > been through many of these upgrades now (like for instance every one of
    > them) and this has never presented a problem before.
    >
    > I assume that prefbar will in fact be updated as a result of this release -
    > I hope so because it's so customizable and can display so much information
    > that it's probably a more important tool for SeaMonkey than for FF. I'll try
    > again then, or earlier if there is some procedure I did that could be
    > improved, but it sounds to me as though what I did was pretty much what you
    > are suggesting.
    >
    >
    >
    >
    >
    >
    >
    >
    >
    >

    Roger,

    You may be right in that developers no longer take the time required to
    make their systems, plugins, and extensions compatible for older
    Microsoft operating systems.

    I recall that Mozilla products install critical files in different
    locations between Win 98 and Win XP, but if the extensions and themes
    are partly installed in the Mozilla/SeaMonkey program folder then
    deleting the program folder and all its contents will cause major
    problems such as you now have.

    In Win XP plugins are saved in the Mozilla/SeaMonkey program folder, and
    extensions are stored in the SeaMonkey Profile folder. It is for this
    reason that when I upgrade to a new version of SeaMonkey I do not allow
    the installer to remove the program folder and all remaining files and
    when I install an extension I install for a single user.

    After installing the new version all my plugins, extensions and themes
    are intact and working well.

    Michael

    --
    Posting Guidelines for MTMM

    Posting To Mozilla.Test.Multimedia


    SeaMonkey the all in one browser, mail, and composer SeaMonkey

    The "All In One Internet Application Suite"

  10. Re: SeaMonkey bug in 1.1 (I think)

    On Friday 19 January 2007 20:50, Roger Fink wrote:
    > Daniel Bauer wrote:
    > > On Friday 19 January 2007 19:17, Roger Fink wrote:
    > >> ... but then a big
    > >> blank 1" band appeared across the bottom of the screen.

    > >
    > > I recommend to read
    > > http://kb.mozillazine.org/Uninstalli...lling_manually
    > > beginning from "Uninstalling in other versions"
    > > carefully.
    > >
    > > I just had to remove all entries regarding the "missing" (removed)
    > > extension in chrome.rdf and delete the XUL.mfasl file. Then seamonkey
    > > was looking poerfect again. But look in the URL above first.
    > >
    > > Oh, before changing/removing anything: backup/copy your profile
    > > folder, so you can revert in case something goes wrong.

    >
    > Thanks for the reply and I will check it out. But even if the solution
    > proposed in mozillazine work,


    it works :-)

    > the complexity of the solution, as you've
    > describe it through your own experiences, merits a structural fix from the
    > developers, IMO.


    Yes it would be nice to have a easy way to de-install/repair the extensions
    stuff - even the "extension manager" sometimes fails with removing something.

    On the other hand, if you follow the instructions in the link above it should
    be solveable without problems. I copied the text from said page to a text
    file, and just went thru it step-by-step. Will not take longer than 5
    minutes.

    But if all that is too complicated, there's still the possibility to rename
    your profile folder (or move it to another directory to back it up), then
    start seamonkey (which will build a new profile folder) and then re-install
    your extensions/plugins and import the old bookmarks.

    good luck :-)

    Daniel
    --
    Daniel Bauer photographer Basel Switzerland
    professional photography: http://www.daniel-bauer.com
    Madagascar special: http://www.sanic.ch

  11. Re: SeaMonkey bug in 1.1 (I think)

    Michael Gordon wrote:
    > On 1/19/2007 9:18 PM Roger Fink created this reply
    >> Michael Gordon wrote:
    >>
    >>> On 1/19/2007 7:36 PM Roger Fink created this reply
    >>>
    >>>> Daniel wrote:
    >>>>
    >>>>
    >>>>> Roger Fink wrote:
    >>>>>
    >>>>>
    >>>>>> I just installed SeaMonkey 1.1 (browser only) exactly by the
    >>>>>> book,
    >>>>>> and I also uninstalled all extensions before doing so, adding
    >>>>>> them
    >>>>>> back one by one, quicklaunch off, closing and opening the browser
    >>>>>> between installs, and testing it out as I went along, which was a
    >>>>>> good thing or else I wouldn't have been able to isolate the
    >>>>>> problem.
    >>>>>>
    >>>>>> Everything was fine until I got to the prefbar. It installed OK,
    >>>>>> self-updated OK, browser worked fine, but when I switched
    >>>>>> profiles
    >>>>>> a note popped up, as it also had done in the default profile,
    >>>>>> asking
    >>>>>> if I wanted to update its data base. I clicked yes, and the note
    >>>>>> closed but then a big blank 1" band appeared across the bottom of
    >>>>>> the screen. I closed the browser but after that it froze, and
    >>>>>> wouldn't open with any shortcut or seamonkey.exe.
    >>>>>>
    >>>>>> Reverted with GoBack to before the prefbar installation and
    >>>>>> installed it again. When I switched profiles, same thing happened
    >>>>>> again. This time I answered no to the data base update box
    >>>>>> ("cancel" as I recall), but the result was the same. Love
    >>>>>> SeaMonkey, but unfortunately this one's mission-critical so I'm
    >>>>>> back to 1.0.7 until it can be fixed.
    >>>>>>
    >>>>>> One additional item. When you delete an extension with the
    >>>>>> extension manager, it asks you to specify a place to create a
    >>>>>> back
    >>>>>> up folder (I believe, but I'm not sure, that you don't have to
    >>>>>> fill this in). I specified D:\ , but no files or folders were
    >>>>>> ever created there. Everything was automatically backed up to
    >>>>>> *.slt\chrome\uninstall\backup\ of the default profile. No harm
    >>>>>> that
    >>>>>> I can see, but the user-defined location doesn't work, at least
    >>>>>> it didn't for me.
    >>>>>>
    >>>>>> Extensions: adblock (old), dictionary search, flashblock,
    >>>>>> prefbar, themer, home button (on nav. toolbar), extension
    >>>>>> manager, extension uninstallerapi.
    >>>>>>
    >>>>>> Running Windows 98SE.
    >>>>>>
    >>>>>>
    >>>>>>
    >>>>> Roger, I had a similar thing happen (band across bottom of browser
    >>>>> screen) a few versions ago (may have even been Moz suite).
    >>>>>
    >>>>> With mine, there was a message in the bottom part of screen, that
    >>>>> indicated one of the extensions I was using was incompatible with
    >>>>> the updated browser. Do you get similar message?? If so, go
    >>>>> looking
    >>>>> for an updated version of problem extension....maybe give
    >>>>> developers a couple of days!
    >>>>>
    >>>>> HTH
    >>>>>
    >>>>> Daniel
    >>>>>
    >>>>>
    >>>> The same thought had occurred to me - wait for a prefbar update. I
    >>>> just updated the version I had, which was one behind, thinking that
    >>>> maybe the problem was that it couldn't make the jump, and then
    >>>> repeated the whole process, but the result was the same. BTW, still
    >>>> no message on the bottom band.
    >>>>
    >>>>
    >>>>
    >>>>
    >>> Hello Roger,
    >>>
    >>> Preference Bar works very well here on Win XP Pro.
    >>>
    >>> From your description I suspect it is an incompatibility between
    >>> themes and another extension.
    >>> Try removing all your extensions and see how it works, then try
    >>> installing them again one at a time until you find the culprit. It
    >>> is
    >>> not SeaMonkey 1.1 that is at fault, it is one of the add on
    >>> applications that is not compatible with another ad on application.
    >>>
    >>> Michael
    >>>

    >>
    >> Michael, you may be right that it is not SeaMonkey 1.1, but that
    >> does not necessarily equate to not having a mystery on my hands. The
    >> first time I installed prefbar in 1.1 I used the default modern
    >> theme and all extensions had been removed and reinstalled one by
    >> one, and prefbar was the last in that sequence. When I installed it
    >> the second time (upgraded to latest prefbar version) all extensions
    >> had again been removed, I was again using the default modern theme,
    >> but this time prefbar was the first install in the sequence. A
    >> possible culprit could be a dated operating system that overworked
    >> developers (understandably) can't spend enough time on. Or, perhaps
    >> certain jar edits I do to customize the GUI had an effect, but I've
    >> been through many of these upgrades now (like for instance every one
    >> of them) and this has never presented a problem before.
    >>
    >> I assume that prefbar will in fact be updated as a result of this
    >> release - I hope so because it's so customizable and can display so
    >> much information that it's probably a more important tool for
    >> SeaMonkey than for FF. I'll try again then, or earlier if there is
    >> some procedure I did that could be improved, but it sounds to me as
    >> though what I did was pretty much what you are suggesting.
    >>
    >>
    >>
    >>
    >>
    >>
    >>
    >>
    >>
    >>

    > Roger,
    >
    > You may be right in that developers no longer take the time required
    > to
    > make their systems, plugins, and extensions compatible for older
    > Microsoft operating systems.
    >
    > I recall that Mozilla products install critical files in different
    > locations between Win 98 and Win XP, but if the extensions and themes
    > are partly installed in the Mozilla/SeaMonkey program folder then
    > deleting the program folder and all its contents will cause major
    > problems such as you now have.
    >
    > In Win XP plugins are saved in the Mozilla/SeaMonkey program folder,
    > and extensions are stored in the SeaMonkey Profile folder. It is for
    > this
    > reason that when I upgrade to a new version of SeaMonkey I do not
    > allow
    > the installer to remove the program folder and all remaining files and
    > when I install an extension I install for a single user.
    >
    > After installing the new version all my plugins, extensions and themes
    > are intact and working well.
    >
    > Michael


    OK, you have made a suggestion here and sometime over the weekend I will try
    it out.

    First attempt, in addition to the extension deletions/reinstalls, will be to
    not delete the install directory (I didn't used to delete it but somehow
    wound up having to do that for the last upgrade, at this point I can't tell
    you why)

    Second attempt, if all else fails, will be a "modified pristine install"
    adding back only bookmarks, userchrome, usercontent, prefs.js (I really do
    not want to lose my adblock settings) and user.js. I'll even do a screenshot
    of my passwords and enter them in later.

    If none of that works, I'll hang around in 1.0.7 waiting for a prefbar
    update.

    If that doesn't work, I could do a hell of a lot worse than sticking with
    what I have.





  12. Re: SeaMonkey bug in 1.1 (I think)

    On 1/20/2007 7:59 AM Roger Fink created this reply
    > Michael Gordon wrote:
    >
    >> On 1/19/2007 9:18 PM Roger Fink created this reply
    >>
    >>> Michael Gordon wrote:
    >>>
    >>>
    >>>> On 1/19/2007 7:36 PM Roger Fink created this reply
    >>>>
    >>>>
    >>>>> Daniel wrote:
    >>>>>
    >>>>>
    >>>>>
    >>>>>> Roger Fink wrote:
    >>>>>>
    >>>>>>
    >>>>>>
    >>>>>>> I just installed SeaMonkey 1.1 (browser only) exactly by the
    >>>>>>> book,
    >>>>>>> and I also uninstalled all extensions before doing so, adding
    >>>>>>> them
    >>>>>>> back one by one, quicklaunch off, closing and opening the browser
    >>>>>>> between installs, and testing it out as I went along, which was a
    >>>>>>> good thing or else I wouldn't have been able to isolate the
    >>>>>>> problem.
    >>>>>>>
    >>>>>>> Everything was fine until I got to the prefbar. It installed OK,
    >>>>>>> self-updated OK, browser worked fine, but when I switched
    >>>>>>> profiles
    >>>>>>> a note popped up, as it also had done in the default profile,
    >>>>>>> asking
    >>>>>>> if I wanted to update its data base. I clicked yes, and the note
    >>>>>>> closed but then a big blank 1" band appeared across the bottom of
    >>>>>>> the screen. I closed the browser but after that it froze, and
    >>>>>>> wouldn't open with any shortcut or seamonkey.exe.
    >>>>>>>
    >>>>>>> Reverted with GoBack to before the prefbar installation and
    >>>>>>> installed it again. When I switched profiles, same thing happened
    >>>>>>> again. This time I answered no to the data base update box
    >>>>>>> ("cancel" as I recall), but the result was the same. Love
    >>>>>>> SeaMonkey, but unfortunately this one's mission-critical so I'm
    >>>>>>> back to 1.0.7 until it can be fixed.
    >>>>>>>
    >>>>>>> One additional item. When you delete an extension with the
    >>>>>>> extension manager, it asks you to specify a place to create a
    >>>>>>> back
    >>>>>>> up folder (I believe, but I'm not sure, that you don't have to
    >>>>>>> fill this in). I specified D:\ , but no files or folders were
    >>>>>>> ever created there. Everything was automatically backed up to
    >>>>>>> *.slt\chrome\uninstall\backup\ of the default profile. No harm
    >>>>>>> that
    >>>>>>> I can see, but the user-defined location doesn't work, at least
    >>>>>>> it didn't for me.
    >>>>>>>
    >>>>>>> Extensions: adblock (old), dictionary search, flashblock,
    >>>>>>> prefbar, themer, home button (on nav. toolbar), extension
    >>>>>>> manager, extension uninstallerapi.
    >>>>>>>
    >>>>>>> Running Windows 98SE.
    >>>>>>>
    >>>>>>>
    >>>>>>>
    >>>>>>>
    >>>>>> Roger, I had a similar thing happen (band across bottom of browser
    >>>>>> screen) a few versions ago (may have even been Moz suite).
    >>>>>>
    >>>>>> With mine, there was a message in the bottom part of screen, that
    >>>>>> indicated one of the extensions I was using was incompatible with
    >>>>>> the updated browser. Do you get similar message?? If so, go
    >>>>>> looking
    >>>>>> for an updated version of problem extension....maybe give
    >>>>>> developers a couple of days!
    >>>>>>
    >>>>>> HTH
    >>>>>>
    >>>>>> Daniel
    >>>>>>
    >>>>>>
    >>>>>>
    >>>>> The same thought had occurred to me - wait for a prefbar update. I
    >>>>> just updated the version I had, which was one behind, thinking that
    >>>>> maybe the problem was that it couldn't make the jump, and then
    >>>>> repeated the whole process, but the result was the same. BTW, still
    >>>>> no message on the bottom band.
    >>>>>
    >>>>>
    >>>>>
    >>>>>
    >>>>>
    >>>> Hello Roger,
    >>>>
    >>>> Preference Bar works very well here on Win XP Pro.
    >>>>
    >>>> From your description I suspect it is an incompatibility between
    >>>> themes and another extension.
    >>>> Try removing all your extensions and see how it works, then try
    >>>> installing them again one at a time until you find the culprit. It
    >>>> is
    >>>> not SeaMonkey 1.1 that is at fault, it is one of the add on
    >>>> applications that is not compatible with another ad on application.
    >>>>
    >>>> Michael
    >>>>
    >>>>
    >>> Michael, you may be right that it is not SeaMonkey 1.1, but that
    >>> does not necessarily equate to not having a mystery on my hands. The
    >>> first time I installed prefbar in 1.1 I used the default modern
    >>> theme and all extensions had been removed and reinstalled one by
    >>> one, and prefbar was the last in that sequence. When I installed it
    >>> the second time (upgraded to latest prefbar version) all extensions
    >>> had again been removed, I was again using the default modern theme,
    >>> but this time prefbar was the first install in the sequence. A
    >>> possible culprit could be a dated operating system that overworked
    >>> developers (understandably) can't spend enough time on. Or, perhaps
    >>> certain jar edits I do to customize the GUI had an effect, but I've
    >>> been through many of these upgrades now (like for instance every one
    >>> of them) and this has never presented a problem before.
    >>>
    >>> I assume that prefbar will in fact be updated as a result of this
    >>> release - I hope so because it's so customizable and can display so
    >>> much information that it's probably a more important tool for
    >>> SeaMonkey than for FF. I'll try again then, or earlier if there is
    >>> some procedure I did that could be improved, but it sounds to me as
    >>> though what I did was pretty much what you are suggesting.
    >>>
    >>>
    >>>
    >>>
    >>>
    >>>
    >>>
    >>>
    >>>
    >>>
    >>>

    >> Roger,
    >>
    >> You may be right in that developers no longer take the time required
    >> to
    >> make their systems, plugins, and extensions compatible for older
    >> Microsoft operating systems.
    >>
    >> I recall that Mozilla products install critical files in different
    >> locations between Win 98 and Win XP, but if the extensions and themes
    >> are partly installed in the Mozilla/SeaMonkey program folder then
    >> deleting the program folder and all its contents will cause major
    >> problems such as you now have.
    >>
    >> In Win XP plugins are saved in the Mozilla/SeaMonkey program folder,
    >> and extensions are stored in the SeaMonkey Profile folder. It is for
    >> this
    >> reason that when I upgrade to a new version of SeaMonkey I do not
    >> allow
    >> the installer to remove the program folder and all remaining files and
    >> when I install an extension I install for a single user.
    >>
    >> After installing the new version all my plugins, extensions and themes
    >> are intact and working well.
    >>
    >> Michael
    >>

    >
    > OK, you have made a suggestion here and sometime over the weekend I will try
    > it out.
    >
    > First attempt, in addition to the extension deletions/reinstalls, will be to
    > not delete the install directory (I didn't used to delete it but somehow
    > wound up having to do that for the last upgrade, at this point I can't tell
    > you why)
    >
    > Second attempt, if all else fails, will be a "modified pristine install"
    > adding back only bookmarks, userchrome, usercontent, prefs.js (I really do
    > not want to lose my adblock settings) and user.js. I'll even do a screenshot
    > of my passwords and enter them in later.
    >
    > If none of that works, I'll hang around in 1.0.7 waiting for a prefbar
    > update.
    >
    > If that doesn't work, I could do a hell of a lot worse than sticking with
    > what I have.
    >
    >
    >
    >
    >

    If you have to go to a "modified pristine install" then go "whole hog"
    and make everything pristine at the beginning. Copy over your Bookmarks
    and test, then Userchrome and test, Usercontent (don't recognize this
    one) and test. When it comes to prefs.js leave that one alone and
    create a new user.js file, then add only those items you must have into
    user.js and test as you go.

    Whenever you modify manually the SeaMonkey configuration files be sure
    all of SM is closed including Quick Launch if you have it set to open.
    When you add an entry to user.js SM will read and write the new entries
    into the prefs.js file, and I think if you remove an entry from User.js
    SM will remove that entry from prefs.js as SM is launched. The whole
    purpose of the user.js file is for testing and debugging preference
    settings without destroying the prefs.js configuration file.

    Michael



    --
    Posting Guidelines for MTMM

    Posting To Mozilla.Test.Multimedia


    SeaMonkey the all in one browser, mail, and composer SeaMonkey

    The "All In One Internet Application Suite"

  13. Re: SeaMonkey bug in 1.1 (I think)

    Michael Gordon wrote:
    > On 1/20/2007 7:59 AM Roger Fink created this reply
    >> Michael Gordon wrote:
    >>
    >>> On 1/19/2007 9:18 PM Roger Fink created this reply
    >>>
    >>>> Michael Gordon wrote:
    >>>>
    >>>>
    >>>>> On 1/19/2007 7:36 PM Roger Fink created this reply
    >>>>>
    >>>>>
    >>>>>> Daniel wrote:
    >>>>>>
    >>>>>>
    >>>>>>
    >>>>>>> Roger Fink wrote:
    >>>>>>>
    >>>>>>>
    >>>>>>>
    >>>>>>>> I just installed SeaMonkey 1.1 (browser only) exactly by the
    >>>>>>>> book,
    >>>>>>>> and I also uninstalled all extensions before doing so, adding
    >>>>>>>> them
    >>>>>>>> back one by one, quicklaunch off, closing and opening the
    >>>>>>>> browser between installs, and testing it out as I went along,
    >>>>>>>> which was a good thing or else I wouldn't have been able to
    >>>>>>>> isolate the
    >>>>>>>> problem.
    >>>>>>>>
    >>>>>>>> Everything was fine until I got to the prefbar. It installed
    >>>>>>>> OK, self-updated OK, browser worked fine, but when I switched
    >>>>>>>> profiles
    >>>>>>>> a note popped up, as it also had done in the default profile,
    >>>>>>>> asking
    >>>>>>>> if I wanted to update its data base. I clicked yes, and the
    >>>>>>>> note closed but then a big blank 1" band appeared across the
    >>>>>>>> bottom of
    >>>>>>>> the screen. I closed the browser but after that it froze, and
    >>>>>>>> wouldn't open with any shortcut or seamonkey.exe.
    >>>>>>>>
    >>>>>>>> Reverted with GoBack to before the prefbar installation and
    >>>>>>>> installed it again. When I switched profiles, same thing
    >>>>>>>> happened again. This time I answered no to the data base
    >>>>>>>> update box ("cancel" as I recall), but the result was the
    >>>>>>>> same. Love
    >>>>>>>> SeaMonkey, but unfortunately this one's mission-critical so I'm
    >>>>>>>> back to 1.0.7 until it can be fixed.
    >>>>>>>>
    >>>>>>>> One additional item. When you delete an extension with the
    >>>>>>>> extension manager, it asks you to specify a place to create a
    >>>>>>>> back
    >>>>>>>> up folder (I believe, but I'm not sure, that you don't have to
    >>>>>>>> fill this in). I specified D:\ , but no files or folders were
    >>>>>>>> ever created there. Everything was automatically backed up to
    >>>>>>>> *.slt\chrome\uninstall\backup\ of the default profile. No harm
    >>>>>>>> that
    >>>>>>>> I can see, but the user-defined location doesn't work, at least
    >>>>>>>> it didn't for me.
    >>>>>>>>
    >>>>>>>> Extensions: adblock (old), dictionary search, flashblock,
    >>>>>>>> prefbar, themer, home button (on nav. toolbar), extension
    >>>>>>>> manager, extension uninstallerapi.
    >>>>>>>>
    >>>>>>>> Running Windows 98SE.
    >>>>>>>>
    >>>>>>>>
    >>>>>>>>
    >>>>>>>>
    >>>>>>> Roger, I had a similar thing happen (band across bottom of
    >>>>>>> browser screen) a few versions ago (may have even been Moz
    >>>>>>> suite).
    >>>>>>>
    >>>>>>> With mine, there was a message in the bottom part of screen,
    >>>>>>> that indicated one of the extensions I was using was
    >>>>>>> incompatible with
    >>>>>>> the updated browser. Do you get similar message?? If so, go
    >>>>>>> looking
    >>>>>>> for an updated version of problem extension....maybe give
    >>>>>>> developers a couple of days!
    >>>>>>>
    >>>>>>> HTH
    >>>>>>>
    >>>>>>> Daniel
    >>>>>>>
    >>>>>>>
    >>>>>>>
    >>>>>> The same thought had occurred to me - wait for a prefbar update.
    >>>>>> I
    >>>>>> just updated the version I had, which was one behind, thinking
    >>>>>> that maybe the problem was that it couldn't make the jump, and
    >>>>>> then
    >>>>>> repeated the whole process, but the result was the same. BTW,
    >>>>>> still
    >>>>>> no message on the bottom band.
    >>>>>>
    >>>>>>
    >>>>>>
    >>>>>>
    >>>>>>
    >>>>> Hello Roger,
    >>>>>
    >>>>> Preference Bar works very well here on Win XP Pro.
    >>>>>
    >>>>> From your description I suspect it is an incompatibility between
    >>>>> themes and another extension.
    >>>>> Try removing all your extensions and see how it works, then try
    >>>>> installing them again one at a time until you find the culprit.
    >>>>> It
    >>>>> is
    >>>>> not SeaMonkey 1.1 that is at fault, it is one of the add on
    >>>>> applications that is not compatible with another ad on
    >>>>> application.
    >>>>>
    >>>>> Michael
    >>>>>
    >>>>>
    >>>> Michael, you may be right that it is not SeaMonkey 1.1, but that
    >>>> does not necessarily equate to not having a mystery on my hands.
    >>>> The first time I installed prefbar in 1.1 I used the default modern
    >>>> theme and all extensions had been removed and reinstalled one by
    >>>> one, and prefbar was the last in that sequence. When I installed it
    >>>> the second time (upgraded to latest prefbar version) all extensions
    >>>> had again been removed, I was again using the default modern theme,
    >>>> but this time prefbar was the first install in the sequence. A
    >>>> possible culprit could be a dated operating system that overworked
    >>>> developers (understandably) can't spend enough time on. Or, perhaps
    >>>> certain jar edits I do to customize the GUI had an effect, but I've
    >>>> been through many of these upgrades now (like for instance every
    >>>> one
    >>>> of them) and this has never presented a problem before.
    >>>>
    >>>> I assume that prefbar will in fact be updated as a result of this
    >>>> release - I hope so because it's so customizable and can display so
    >>>> much information that it's probably a more important tool for
    >>>> SeaMonkey than for FF. I'll try again then, or earlier if there is
    >>>> some procedure I did that could be improved, but it sounds to me as
    >>>> though what I did was pretty much what you are suggesting.
    >>>>
    >>>>
    >>>>
    >>>>
    >>>>
    >>>>
    >>>>
    >>>>
    >>>>
    >>>>
    >>>>
    >>> Roger,
    >>>
    >>> You may be right in that developers no longer take the time required
    >>> to
    >>> make their systems, plugins, and extensions compatible for older
    >>> Microsoft operating systems.
    >>>
    >>> I recall that Mozilla products install critical files in different
    >>> locations between Win 98 and Win XP, but if the extensions and
    >>> themes
    >>> are partly installed in the Mozilla/SeaMonkey program folder then
    >>> deleting the program folder and all its contents will cause major
    >>> problems such as you now have.
    >>>
    >>> In Win XP plugins are saved in the Mozilla/SeaMonkey program folder,
    >>> and extensions are stored in the SeaMonkey Profile folder. It is
    >>> for
    >>> this
    >>> reason that when I upgrade to a new version of SeaMonkey I do not
    >>> allow
    >>> the installer to remove the program folder and all remaining files
    >>> and when I install an extension I install for a single user.
    >>>
    >>> After installing the new version all my plugins, extensions and
    >>> themes
    >>> are intact and working well.
    >>>
    >>> Michael
    >>>

    >>
    >> OK, you have made a suggestion here and sometime over the weekend I
    >> will try it out.
    >>
    >> First attempt, in addition to the extension deletions/reinstalls,
    >> will be to not delete the install directory (I didn't used to delete
    >> it but somehow wound up having to do that for the last upgrade, at
    >> this point I can't tell you why)
    >>
    >> Second attempt, if all else fails, will be a "modified pristine
    >> install" adding back only bookmarks, userchrome, usercontent,
    >> prefs.js (I really do not want to lose my adblock settings) and
    >> user.js. I'll even do a screenshot of my passwords and enter them in
    >> later.
    >>
    >> If none of that works, I'll hang around in 1.0.7 waiting for a
    >> prefbar update.
    >>
    >> If that doesn't work, I could do a hell of a lot worse than sticking
    >> with what I have.
    >>
    >>
    >>
    >>
    >>

    > If you have to go to a "modified pristine install" then go "whole hog"
    > and make everything pristine at the beginning. Copy over your
    > Bookmarks
    > and test, then Userchrome and test, Usercontent (don't recognize this
    > one) and test. When it comes to prefs.js leave that one alone and
    > create a new user.js file, then add only those items you must have
    > into user.js and test as you go.
    >
    > Whenever you modify manually the SeaMonkey configuration files be sure
    > all of SM is closed including Quick Launch if you have it set to open.
    > When you add an entry to user.js SM will read and write the new
    > entries
    > into the prefs.js file, and I think if you remove an entry from
    > User.js
    > SM will remove that entry from prefs.js as SM is launched. The whole
    > purpose of the user.js file is for testing and debugging preference
    > settings without destroying the prefs.js configuration file.
    >
    > Michael


    OK will do. When my installation party is over, I'll post back on this
    thread, if only to make it known who/what the culprit was (although if it's
    operator error there will be a great temptation to keep silent).



  14. Re: SeaMonkey bug in 1.1 (I think)

    Roger Fink wrote:

    >
    > OK will do. When my installation party is over, I'll post back on this
    > thread, if only to make it known who/what the culprit was (although if it's
    > operator error there will be a great temptation to keep silent).
    >
    >


    Two suggestions:

    1. Trim your posts to something less than 228 lines :-)
    2. File a bug if the reinstallation doesn't work:
    http://prefbar.mozdev.org/bugs.html
    If it is a bug this will give Manuel Reimer a chance to look at it &
    possibly fix it.

  15. Re: SeaMonkey bug in 1.1 (I think)

    NoOp wrote:
    > Roger Fink wrote:
    >
    >>
    >> OK will do. When my installation party is over, I'll post back on
    >> this thread, if only to make it known who/what the culprit was
    >> (although if it's operator error there will be a great temptation to
    >> keep silent).
    >>
    >>

    >
    > Two suggestions:
    >
    > 1. Trim your posts to something less than 228 lines :-)
    > 2. File a bug if the reinstallation doesn't work:
    > http://prefbar.mozdev.org/bugs.html
    > If it is a bug this will give Manuel Reimer a chance to look at it &
    > possibly fix it.


    Please explain to me, or provide a link, on how to do this, if it is
    something other than wholesale deleting of text.



  16. Re: SeaMonkey bug in 1.1 (I think)

    Two suggestions:
    >> 1. Trim your posts to something less than 228 lines :-)
    >> 2. File a bug if the reinstallation doesn't work:
    >> http://prefbar.mozdev.org/bugs.html
    >> If it is a bug this will give Manuel Reimer a chance to look at it &
    >> possibly fix it.
    >>

    >
    > Please explain to me, or provide a link, on how to do this, if it is
    > something other than wholesale deleting of text.
    >
    >
    >

    Hello Roger,

    When you reply to a long post you can highlight that part that does not
    pertain to your answer and select Edit/Cut to remove the extra text, or
    highlight the text and right click the mouse and select Cut.

    However in this case all the text pertains to trying to solve your
    problem and a late arrival may miss some important discussion.

    For the gentleman who suggested shortening your post because it is very
    long I suggest he use the "Space Bar" to scroll page by page.

    Michael

    --
    Posting Guidelines for MTMM

    Posting To Mozilla.Test.Multimedia


    SeaMonkey the all in one browser, mail, and composer SeaMonkey

    The "All In One Internet Application Suite"

  17. Re: SeaMonkey bug in 1.1 (I think)

    Michael Gordon wrote:
    > Two suggestions:
    >>> 1. Trim your posts to something less than 228 lines :-)
    >>> 2. File a bug if the reinstallation doesn't work:
    >>> http://prefbar.mozdev.org/bugs.html
    >>> If it is a bug this will give Manuel Reimer a chance to look at it &
    >>> possibly fix it.
    >>>

    >>
    >> Please explain to me, or provide a link, on how to do this, if it is
    >> something other than wholesale deleting of text.
    >>
    >>
    >>

    > Hello Roger,
    >
    > When you reply to a long post you can highlight that part that does
    > not pertain to your answer and select Edit/Cut to remove the extra
    > text, or highlight the text and right click the mouse and select Cut.
    >
    > However in this case all the text pertains to trying to solve your
    > problem and a late arrival may miss some important discussion.
    >
    > For the gentleman who suggested shortening your post because it is
    > very long I suggest he use the "Space Bar" to scroll page by page.
    >
    > Michael


    I thought that there might have been some automated way to do it. Now that I
    think of it, I'm using the Devil's Newsreader anyway, so extensions would be
    pointless.
    Last you'll hear from me until I'm finished with the exercises above.



  18. Re: SeaMonkey bug in 1.1 (I think)

    _Roger Fink_ spoke thusly on 20/01/2007 8:19 PM:
    > Michael Gordon wrote:
    >> However in this case all the text pertains to trying to solve your
    >> problem and a late arrival may miss some important discussion.
    >>
    >> For the gentleman who suggested shortening your post because it is
    >> very long I suggest he use the "Space Bar" to scroll page by page.

    >
    > I thought that there might have been some automated way to do it. Now that I
    > think of it, I'm using the Devil's Newsreader anyway, so extensions would be
    > pointless.
    > Last you'll hear from me until I'm finished with the exercises above.


    The Mozilla Forum Etiquette page says to trim.

    --
    Chris Ilias
    List-owner: support-firefox, support-thunderbird
    mozilla.test.multimedia moderator
    (Please do not email me tech support questions)

  19. Re: SeaMonkey bug in 1.1 (I think)

    Michael Gordon wrote:
    > Two suggestions:
    >>> 1. Trim your posts to something less than 228 lines :-)
    >>> 2. File a bug if the reinstallation doesn't work:
    >>> http://prefbar.mozdev.org/bugs.html
    >>> If it is a bug this will give Manuel Reimer a chance to look at it &
    >>> possibly fix it.
    >>>

    >>
    >> Please explain to me, or provide a link, on how to do this, if it is
    >> something other than wholesale deleting of text.
    >>
    >>
    >>

    > Hello Roger,
    >
    > When you reply to a long post you can highlight that part that does not
    > pertain to your answer and select Edit/Cut to remove the extra text, or
    > highlight the text and right click the mouse and select Cut.
    >
    > However in this case all the text pertains to trying to solve your
    > problem and a late arrival may miss some important discussion.
    >
    > For the gentleman who suggested shortening your post because it is very
    > long I suggest he use the "Space Bar" to scroll page by page.
    >
    > Michael
    >


    A late arrival can scroll back up in the thread to obtain additional
    information. It's easy enough to do this. Just tacking on to the end of
    each post seems to be a carryover from the old Netscape newgroup whereby
    everyone just added something at the end (sometimes only a single
    sentence or word) and the posts would grow to 300 lines or more. You
    then spend the time scrolling down each one only to find some dit
    tacking a "I agree" or similar at the end.

    The OP (and others) can do as they wish, but common courtesy would
    suggest that trimming posts to the relevant bits makes life easier for
    those that follow the posts in the thread :-)

    As an added point; it's always good to also include attributes in your
    reply so that other folks know who you are responding to. Example; in
    your post (left intact on purpose because Michael Gordon provided no
    attribute to who he was responding to) you responded do someone but
    there is no attribute to who you are reponding to (e.g., Roger Fink
    wrote: or NoOp wrote. You can fix this by:

    about:config
    pref mailnews.reply_header_authorwrote
    insert the original: %s wrote
    and that will get you back to the basic "author wrote" setting.

    For the OP/Roger:

    Select the irrelevent bits of what you are replying to and delete them;
    marked the dead space as [snip] if you'd like to indicate that you've
    cut text out of the post you are replying to. However, if you do include
    text from multiple authors in the post be sure to include the "author
    wrote" bit at the top. Example:

    NoOp wrote:
    > Roger Fink wrote:
    >
    >>


    That way folks know that lines with > are from the author listed first
    (in this case NoOp) and lines with >> are from the author listed second etc.










  20. Re: SeaMonkey bug in 1.1 (I think)

    Roger Fink wrote:
    > Michael Gordon wrote:


    >>
    >> For the gentleman who suggested shortening your post because it is
    >> very long I suggest he use the "Space Bar" to scroll page by page.
    >>
    >> Michael

    >
    > I thought that there might have been some automated way to do it. Now that I
    > think of it, I'm using the Devil's Newsreader anyway, so extensions would be
    > pointless.
    > Last you'll hear from me until I'm finished with the exercises above.
    >
    >


    Yep: X-Newsreader: Microsoft Outlook Express 6.00.2800.1409

    Use Seamonkey :-)


+ Reply to Thread
Page 1 of 2 1 2 LastLast