Hello all!

Last time I successfully tried Warpzilla (which was a long time ago) I was
very pleased with it. The loadtime was exceptionally long, but once up, it
rendered pages fast as heck.

However, technology never lets users have fun too long.

The second time I launched Warpzilla, it crashed while loading a page. After
that crash, I couldn't start Warpzilla. It would start loading the
application, but crashed quite soon. (I think this was M17, or something.. I
remember there was some dll-fix released for it).

Since then I have completely reinstalled my system, and I thought I'd try
Warpzilla again. I downloaded mozilla-i386-pcos2-vacpp-2001-01-05.zip and I
got this in popuplog.os2 when I tried to launch it:

01-24-2001  20:40:43  SYS2070  PID 0120  TID 0001  Slot 0078
D:\WARPZILLA\BIN\MOZILLA.EXE
SMIME
193


So a few days later another archive showed up and I tried
mozilla-i386-pcos2-vacpp-2001-02-01.zip, and I got this:

------------------------------------------------------------

02-02-2001  20:15:06  SYS2070  PID 03dc  TID 0001  Slot 0080
D:\WARPZILLA\BIN\MOZILLA.EXE
JSLOADER
193
------------------------------------------------------------

02-02-2001  20:15:07  SYS2070  PID 03dc  TID 0001  Slot 0080
D:\WARPZILLA\BIN\MOZILLA.EXE
GKPLUGIN
193
------------------------------------------------------------



So, I thought I'd try with an http-address specified on the commandline, just
in case. Then I get the following:
------------------------------------------------------------

02-02-2001  20:22:38  SYS2070  PID 03e4  TID 0001  Slot 0088
D:\WARPZILLA\BIN\MOZILLA.EXE
CHARDET
193

------------------------------------------------------------


This behavior is very similar to the problem which I had with the M17 build
(or whatever it was). Is it a know problem? Do I need to do something before
I launch Mozilla.exe?

I am using SDD 7.04 and I'm at FP15 using Warp4.


I can provide more details if this is a new one.


 /j




Reply via email to