Christian Sterzik,
27-Feb-98 23:04:00, Christian Sterzik wrote to Andy Roberts
          Subject: Re: Netscape/2 troubles
 AR>> I'm using ns2_128_US.zip level 4S now and it seems ok.  I agree
 AR>> with you about the version level 6 that was released just prior
 AR>> to 14-Feb-98 did have problems.
 CS> Hmmm... How often will I have to et a new Navigator 2.02 ?-)
 CS> Isn't it ironic....
I usually let most upgrades go by without me.  It was the Java
related issues that caused me to try the level 6 build.  It was
only after the bugs were exposed I decided to move back to an
earlier version.  I'll probably stay with this unless something
major that I need comes along in the future.  I see no need to
upgrade just because development continues.
 AR>> I read the latest level 7 version was supposed to have
 AR>> fixed some of the problems.
 CS> I'll try...
NETS202.EXE  10-Feb-98 15:47  4998803
NetScape - Version 2.02 level 7 build
http://service.boulder.ibm.com/asd-bin/doc/en_us/ns202/f-feat.htm
 AR>> That sounds more like a video card/driver problem.
 CS> I use an Elsa Winner Trio V, with an S3 (somehow enhanced)
 CS> Chipset. Elsa supports OS/2 since a long time, and they still
 CS> make drivers for their cards under OS/2... I got a new one
 CS> two months ago, the one that shipped with the card is about
 CS> 1.5 years old now (like the card...)
 CS> I thought that original drivers wouldn't cause problems like
 CS> that... Or could it be, that I haven't got enough RAM ? 2 MB
 CS> D-Ram , running in 800x600 in 65 thousand colours and 82 Mhz.
I heard some very good things about the Elsa video card.  I don't
have any experience with it myself.  As for the effect of RAM, with
the Matrox Millennium it allows the use of more colors at the higher
resolutions.  I choose 4MB RAM, which was the maximum at the time I
purchased, and use 800x600x16.7M.  My old Diamond only has 1MB RAM
and was barely usable at VGA and useless at very high resolutions.
 AR>> I had similar problems with many apps when I used a Diamond
 AR>> video card and Warp4. But since I bought a Matrox Millennium
 AR>> with 4MB RAM I have never had that problem again.
 CS> Hmmm... I won't like to buy new hardware right now...
Maybe (guessing) reduce the colors until you can afford more RAM.
 CS>>> I tried lots of stuff... Really... But some crashes are not
 CS>>> explainable logically. Sometimes at booting up he gives a Trap
 CS>>> with SingleQ$, another time a 000d, another time a 000e
 AR>> I think that is a video problem.
 CS> Ah. Do you know if there could be a software solution ?
I'm not up on the latest Elsa drivers.  But like you said Elsa does
support OS/2 so it might be best to ask them.
Reviewing old OS2 echo msgs I found:
17-Oct-97 12:00:12, Denis Tonn wrote to Garth Ramsay
          Subject: Trap E problem
 DT> I recognize this problem. It looks like one I have already
 DT> identified from a dump analysis. The fix will be included in
 DT> FP33 (and FP5), but here is an "unofficial" patch that will
 DT> also work. I have tried to keep the lines short so that they
 DT> will not be modified by other echo message processors. Just
 DT> cut to a file and run the following rexx program. Let me know
 DT> if the patch fixes your problem. It was written for FP31 and
 DT> FP 3 level, but I have verified it works (and is needed) at
 DT> FP32 and FP 4 level.
I did not include the REXX prgm Denis Tonn posted in the OS2 echo.
02-Feb-98 08:41:00, Denis Tonn wrote to Doug Vogt
          Subject: Singleq$ driver
 DT> Singleq$ is the "internal" name of PMDD.SYS (all device
 DT> drivers have an internal and external name - frequently the
 DT> same). This name dates back to OS/2 1.1 days.. It is the base
 DT> PM "driver". It determines which "app" has the focus for
 DT> mouse, keyboard, and queue.
01-Feb-98 12:17:00, Will Honea wrote to Doug Vogt
          Subject: Singleq$ driver
 DV>> trap 000d saying "Exception in device driver Singleq$."
 WH> Every time I've seen this, it was related to a video driver
 WH> mismatch of some kind.  Try either installing for plain old
 WH> VGA or at boot hit ALT-F1 then F3 to force vanilla VGA, then
 WH> re-install your video drivers.  This may also produce a crash
 WH> the first time it boots but should be after that.  If it still
 WH> fails, use ALT-F2 during boot, see what it was working on when
 WH> it bombed and get back.
18-Feb-98 19:16:00, MIKE FRITZ wrote to IAN MOOTE
 MF> SINGLEQ$
 MF> I've found that is has something to do with video.  I've had
 MF> times where the SVGA drivers got corrupted, and I would get a
 MF> SINGLEQ$ error on boot up. So I would ALT-F1 at boot time, and
 MF> re-load my VGA drivers.  Then, re-install the SVGA.
Let's hope just re-installing your video drivers solves the problem.
 AR>> I just went there and looked around for a long time and went back
 AR>> and forth and never had the slightest problem of any kind.
 CS> With java = on, i could do that too...
 AR>> BTW, I had Java enabled while at that site you mentioned.  So
 AR>> turning it off was not necessary.
 CS> Jupp.
 CS> But always turnin' java on and off ?
I never tried that.
 CS> Hows that if you use 4 Browser windows at a time ?
I have not tried that either.
 CS> Wow...
 CS> How could I do this to mine ?
That's easy.  
     Thanks and Good Luck,        Andy Roberts
                                  andy@shentel.net
--- Terminate 5.00/Pro*at 
---------------