TIP: Click on subject to list as thread! ANSI
echo: os2_z3
to: Paul Edwards
from: Peter Knapper
date: 1996-12-25 09:28:04
subject: slackos

Hi Paul,

PE> 3. copy command caused corruption.
LE> Never seen this.

Never seen this either. 

However with repsect to...

PE> 5. Some doubling of characters.
LE> Never seen this. Where do they get doubled? 
LE> Windowed sessions, fullscreen, 
LE> what?

 PE> With 3.0 they were getting doubled even on the normal 
 PE> screen, ie when you right click, instead of seeing 
 PE> "Shutdown" on the menu, you might see "Shuudoon" or 
 PE> something (maybe that was just the Australian version? 
 PE> :-)), but with 4.0, I have only spotted it in one place 
 PE> so far - the Epson printer driver setup.

... and ...

PE> 9. vio of blue causes overscores.

LE> News to me, considering I have MsgedSQ/2 configured 
LE> to use blue for quoted 
LE> text, and the top and bottom status bars are yellow 
LE> on blue text. What 
LE> environment - video driver? windowed or fullscreen session?

 PE> I see it in Binkley, which gets auto-started.  video 
 PE> driver is Tseng Labs ET4000 one.  Fullscreen session.

These ones I have _heard_ of, perhaps not in exactly the same situation but
with _VERY_ similar results. The problem was resolved by replacing the
ET4000 card with another ET4000. There was no obvious difference between
the 2 ET4000 cards other than the manufacturing date was about 9 months
apart. The earlier card had the problem, the later one didn't. Using
different versions of the same driver did NOT change the problem. The same
ET4000 also exhibited some oddities like the above in some Win3.11 apps
when running plain Win3.11, not OS/2, however not all Win applications
experienced the problem. The problem also only seemed to be present in
selected video modes, plain 640x480x256 was fine. Its so long ago I can't
remember the exact details now.

 PE> /* The following program demonstrates a presumed-bug in OS/2 */
 PE> /* If this program is run from the startup, or if the program is
 PE>    run from a shell that was started from the startup, it prints
 PE>    ABC in blue, with a line *above* it.  If run from a screen that
 PE>    is started manually (ie after startup), it simply prints ABC in
 PE>    blue, as expected.

And I strongly suspect this relates directly to the same ET4000 problem. 

I hope ths helps...........pk.


--- Maximus/2 3.01
* Origin: Another Good Point About OS/2 (3:772/1.10)
SEEN-BY: 622/407 632/339 690/347 711/409 410 808 809 934 955 712/624 714/906
SEEN-BY: 770/115 771/1320 772/1 10 20 30 40 90 100 135 140 235 350 380
SEEN-BY: 774/605 30185/10
@PATH: 772/1 20 711/955 808 934

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.