Jens Manfredson wrote:
>
> But maybe something in the prefs file?
Could very well be. If you haven't already, check it for trash resulting
from a bad write on exit. If it looks ok, you might try creating a new
profile with default prefs and see if that eliminates the launch
failure. If it does, incrementally modifying the defaults to match the
broken prefs should identify the culprit. If it doesn't, you might check
if any other unjarred *.js files differ, or try reinstalling from the
.rar; also, sometimes just deleting the *.dat and *.reg files created on
first launch magically fixes things.
h~
