Michael Kaply wrote:
> OK, I understand now.
>
> I was forgetting about the silly WSOD file i/o stuff.
>
WSOD is not so silly... try to set xpti.dat and xptitemp.dat as readOnly and you will
se that Mozilla dies on a ordinary Warp Workstation too :-)
>
> I think the best solution is to check for the return codes from opening the files
> and allowing them to still work, rather than putting them in MOZILLA_HOME.
>
> The first option is easier to get past the Mozilla community.
>
> I am surprised you don't run into the same problem with the *.rdf file in
> bin/chrome.
>
So far I had a starting problem, and can imagine a few run problem too....
>
> They must be opened correctly (They are created if they don't exist as well)
>
created them, ok
>
Now I just have the proxy problem... Mozilla is useless with the responsetime I have
with proxy enabled. At my personal workstation is go out through the firewall without
proxy and with no proxy authentication, and that's fast. With proxy and the firewall
set to proxy authentication it's veeeeery slow. Caches data is fast, though.
BWA
