Tseng ET4000/w32p's problems with 1024x768

Support and general discussion.
Post Reply
SA1988
Posts: 274
Joined: Wed 30 Apr, 2014 9:38 am

Tseng ET4000/w32p's problems with 1024x768

Post by SA1988 »

Under all operating systems (even Windows 3.1 as well as Windows 9x), this results in a black screen that remains in a "stopped" state, that is, the bios cursor doesn't flash and doesn't output this resolution and note, this happens with all its supported color depths (8bpp and 16bpp).
Edit: I wonder if this is a planar mode or not, if it is, that would be why it doesn't work.

Drivers used are the following: http://driverzone.com/drivers/tseng/et4kw32.zip

Edit: the screenshot (trying out 1024x768 256 color mode with the drivers above):
Attachments
et4k32p.png
et4k32p.png (34.37 KiB) Viewed 5357 times
User avatar
SarahWalker
Site Admin
Posts: 2054
Joined: Thu 24 Apr, 2014 4:18 pm

Re: Tseng ET4000/w32p's problems with 1024x768

Post by SarahWalker »

As discussed on IRC, this is probably a result of using the wrong BIOS. PCem does specifically emulate a Diamond Stealth 32, with the RAMDAC and clock chip used on that card, and using another BIOS will potentially have issues.
User avatar
BoisterousSleet75
Posts: 39
Joined: Fri 11 Aug, 2017 3:06 am

Re: Tseng ET4000/w32p's problems with 1024x768

Post by BoisterousSleet75 »

*deleted*
Last edited by BoisterousSleet75 on Sat 18 Nov, 2017 12:02 am, edited 1 time in total.
Long Live Marxism-Leninism-Maoism! ☭
User avatar
SarahWalker
Site Admin
Posts: 2054
Joined: Thu 24 Apr, 2014 4:18 pm

Re: Tseng ET4000/w32p's problems with 1024x768

Post by SarahWalker »

There wasn't a bug here. User was running the wrong BIOS.

Why did you dig up this 2 year old thread anyway?
User avatar
BoisterousSleet75
Posts: 39
Joined: Fri 11 Aug, 2017 3:06 am

Re: Tseng ET4000/w32p's problems with 1024x768

Post by BoisterousSleet75 »

SarahWalker wrote:There wasn't a bug here. User was running the wrong BIOS.

Why did you dig up this 2 year old thread anyway?
I'm sorry about that. but I know this is due to user running wrong BIOS.

I know that it's not a bug. Unfortunately I can't remove my previous post, So I can only edit my previous post anyway.
Long Live Marxism-Leninism-Maoism! ☭
Post Reply