From: andreww@uniwa.uwa.edu.au (Andrew Williams)
Newsgroups: comp.os.os2.misc
Subject: Re: Tseng SVGA - still trying (was: New TSENG LABS drivers)
Keywords: NEW TSENG LABS DRIVERS
Date: 13 Sep 92 17:11:44 GMT
Organization: The University of Westrn Australia
NNTP-Posting-Host: uniwa.uwa.edu.au

shurr@cbnews.cb.att.com (larry.a.shurr) writes:

>In article <hatton.716173370@cgl.ucsf.edu> hatton@socrates.ucsf.edu (Tom Hatton) writes:
>An alt-home from a DOS window brings me to a full screen of total hash.
>Another alt-home restores me to the WPS desktop in good order.  After 
>starting a full screen session (DOS or OS/2), this improves from garbage
>to... wierd.

>When I start a full screen DOS session, it looks fine.  If I alt-home or
>alt-esc, I end up back at the desktop appropriately, but when I alt-home
>the window back to full screen or select a full screen DOS session I
>switched away from, the display is distorted.  It's like the horizontal
>sync timing is off a bit -- the beam coms back on a moment before it's 
>been restored to the left margin.  That's with a 25 line display.  With
>a 50 line display, I have two flickery copies of the screen combined
>with the horizontal sync timing still lookiing a bit off.  I can clear
>these problems up temporarily by entering the appropriate mode commands,
>but the next time I switch away and come back, the problem will be back.

I have EXACTLY this problem. I haven't tried to alt-home a dos window
BEFORE starting my first full screen app, but everything else is
familiar. I thought I was going mad- nobody else seemed to have this
problem. What the HELL is tseng doing with their chipset docs? How many
ways can you put their chips into a SVGA card? I have a genuine Tseng
Mega Eva, and the sods won't even release their generic drivers- they
give them to orchid, and the other manufacturers, who hack them into
card-specific ones. Everybody is reporting different problems. Anyone
know any good vodoo dances I can perform before I try out the next
driver release? I'm ready to try just about anything...

>As I've read this thread today, I noticed that some people have run
>VMODE in a DOS session.  In order to get 1024x768x60Hz non-interlaced
>in DOS, I have to run VMODE, but I haven't done that in a VDM.  Maybe
>I need to do that and rerun SVGA ON.  What do you think?  I think I'm
>going to try it this weekend.  Is there anything else I should try?

I've tried that half a dozen times- varying which modes I change to with
vmode, and also which mode I run 'svga on' in. If I'm REALLY lucky, it
clears up the problem- for one boot cycle. After that, it goes back to
'normal'. (I've also heard a rumour about turning off ansi.sys in the
dos session- doesn't seem to make any difference to me.)


>BTW: I have the the fx3 version of the VSVGA.DLL fix installed.  I 
>also have the patch BVHSVGA.DLL (I think I spelled that right) as well
>as a number of other non-video patches thanks to ftp-os2.nmsu.edu.  I'm
>happy to say that I havn't experienced any trap 2's, 5's, or E's lately.

I've got the latest versions too. (But I've NEVER experienced any traps,
even with the old ones- maybe I should try them again?).

>-- 
>Larry A. Shurr (las@cbnmva.att.com or att!cbnmva!las) speaking only for myself.
>EOR (end-of-ramble)


	Andrew Williams,
	Physics, Uni of West Australia.
Newsgroups: comp.os.os2.misc,comp.os.os2.apps