🚀 go-pugleaf

In <5d15o5$3s6$2@nargun.cc.uq.oz.au>, cs321509@student.uq.edu.au (Z) writes:
>In <5cvp2g$5kh@nnrp1.news.primenet.com>, khamann@primenet.com writes:
>
>[...HiColour modes with Tseng ET4000AX...]
>
>>I'm guessing here, so please don't get too mad if this doesn't
>>work *grin*, but have you tried using the ET4000/w32,w32i,w32p
>>driver to see if that would work?  If it doesn't, hitting alt f1
>>when the block comes on in the upper right corner on bootup
>>will allow you to switch back to vga and then you can install
>>the original drivers.
>
>I use these drivers with my ET4000/w32p and they only offer 256-colour
>modes up to 1024x768 even though my card and monitor are capable of
>1280x1024, and HiColour modes at lower resolutions. So I doubt that
>these would solve the original poster's problems.
>
How much memory do you have on the card?  With 1 MB that sounds
correct, but with 2 MB you should be able to get 1280x1024x256 and
1024x768x65k.  The reason why OS/2 doesn't allow some of the
resolution/color modes that Windows allows is because OS/2 uses
32 bit color while Windows also allows 24 bit color.  There is/was
also a problem that some ET4000/W32P cards used different 
RAMDACs which didn't work well with the  OS/2 drivers.  Me I had
a ET4000/w32i which had the problem you're discussing, but in
my case it was a hardware problem with the ET4000/w32i
chipset only allowing 1024x768x65k colors interlaced.

Kevin