Oops. The other constant between my 3 machines would be my use of
"graymodern" as a new theme. If I quit a particular Mozilla in this
theme and then restart it with a different Mozilla build without that
theme, the app freezes.
Conversely, if I shift that particular Mozilla back to one of the
default themes before quitting, quit, and then open a different build
of Mozilla, everything's fine.
Anybody know why this happens? Kind of a pain in the butt to install
new themes when I download new browser builds. Can you treat themes
like mail or some sort of independent preference to avoid this problem?
Steve
In article <[EMAIL PROTECTED]>, Steve
<[EMAIL PROTECTED]> wrote:
> I frequently play around with new builds of Mozilla on Linux, MacOS,
> and Win9x systems. I would delete or rename the old Mozilla folder,
> unpack a newer build in its place, and let the new build access the
> same user info as the old one.
>
> This worked for the last few weeks (months?), but suddenly, it doesn't
> work anymore (on all 3 systems). Either the application hangs on the
> Mozilla intro screen or nothing happens. If I remove the new build
> (actually, I get similar problems if I install an older build) and
> replace it with the original one, then things work fine. The only way
> to get the new build to work is to let it create a new Application
> Registry which is a bit inconvenient.
>
> Either something has fundamentally changed with Mozilla recently, or
> there's some sort of user error on my end (since I have now posted this
> publicly, it will surely be user error :P ). Anybody else having these
> problems?
>
> Steve
