win3x
« Windows 3.x Video »

Welcome Guest. Please Login or Register.
Feb 22nd, 2018, 10:05pm



« Previous Topic | Next Topic »
Pages: 1  Reply Notify Send Topic Print
 thread  Author  Topic: Windows 3.x Video  (Read 181 times)
watler
Administrator
ImageImageImageImageImage


member is offline

Avatar




Homepage PM


Posts: 164
xx Windows 3.x Video
« Thread started on: Jan 8th, 2018, 4:09pm »
Quote

This thread is for discussion of video hardware. cool

If you are uncertain what video hardware you have, use this tool to give you more information about your video card.
http://turkeys4me.byethost4.com/files/DIBDRV7.7z
« Last Edit: Jan 8th, 2018, 7:05pm by watler » User IP Logged

watler
Administrator
ImageImageImageImageImage


member is offline

Avatar




Homepage PM


Posts: 164
xx Re: Windows 3.x Video
« Reply #1 on: Jan 14th, 2018, 1:55pm »
Quote

Although the Windows 3.1 VGA driver only supports a palette of 16 colors, it is possible to select a different set of 16 colors for that palette.

EGAcol.exe should allow access to the enhanced VGA palette.
http://turkeys4me.byethost4.com/files/test/VGA16.7z
User IP Logged

deomsh
Moderator
ImageImageImageImageImage


member is offline

Avatar




PM


Posts: 109
xx Re: Windows 3.x Video
« Reply #2 on: Jan 15th, 2018, 6:36pm »
Quote

Droject1

Video card: Geforce 7950 GT

Test Windows 3.1:

0) Vesa mode=$13
1) Dispdib.dll functions and says in colored screen: "This is VESA MODE $13"
2) Get VGA mode: $0012 and after OK: 18
3) Get current VESA mode: same as 2)
4) Hardware Banks/Pages: colored/pickled screen, when program returns colors stays green/pink until reboot.
5) Show Bitmap: Requested Return is: 5; PhyssAddrHI: 12231; PhyssAddrLO: 0; Release result is 5.
6) OEMLayer Enable/Disable: black screen, program returns.
7) Windir16.dll: shows for a moment black screen with white text " Windir..", program returns, very unstable afterwards
8) Long DPMI LFB: 131072
9) Word DPMI LFB: 131072
10) byte DPMI LFB: 131072
11) LFB to Bitmap: nothing
12) death/resurrection: green image with first pink vertical planes, than a horizontal green band, than green/pink colored/pickled screen
13) Turbo debugger svga.dll: short seeing black screen with white text: "Turbo debugger text mode", program returns
14) VESA LFB address: $13
15) Impossible: forgotten cry

Test Windows 98SE:

0) Vesa mode=$13
1) Dispdib.dll doesn't function, black screen, reboot necessary
2) Get VGA mode: $0003 and after OK: 3
3) Get current VESA mode: $4003 and after OK: 16387
4) Hardware Banks/Pages: different colored screen, program returns immediately. Colors of fonts are light red except on desktop. Desktop almost normal, except bachground color: light brown
5) Show Bitmap: CopyTo result is: 11; PhyssAddr: 00FA0000; Buffer_IDd: 1; Release result is 11.
6) OEMLayer Enable/Disable: red screen, reboot necessary
7) Windir16.dll: shows black screen, hard reset necessary
8) Long DPMI LFB: 131072
9) Word DPMI LFB: 131072
10) byte DPMI LFB: 131072
11) LFB to Bitmap: nothing
12) death/resurrection: didn't try
13) Turbo debugger svga.dll: black screen with white text: "Turbo debugger text mode", reboot necessary
14) VESA LFB address: $E011
15) Impossible: $4003 & OK
User IP Logged

watler
Administrator
ImageImageImageImageImage


member is offline

Avatar




Homepage PM


Posts: 164
xx Re: Windows 3.x Video
« Reply #3 on: Jan 15th, 2018, 7:46pm »
Quote

Good to see that VGA mode is working properly. smiley
You should be able enumerate your VESA modes by clicking on the mode number box.

Looks like the windows 98 driver had some issues.
What drivers/settings were you using?

Even if your win98 driver does not support hardware mode control,
win16 programs such as David Wicker's high-color Scene16 may still be operational.

As a test of VGA 4-bit color mode, I've incorporated VGA palette commands into SVSTP.
Several tfsdata example scripts make use of the VGA palette.
http://win3x.conforums.com/index.cgi?board=Freeware&action=display&num=1502074137

« Last Edit: Jan 15th, 2018, 7:47pm by watler » User IP Logged

deomsh
Moderator
ImageImageImageImageImage


member is offline

Avatar




PM


Posts: 109
xx Re: Windows 3.x Video
« Reply #4 on: Jan 16th, 2018, 5:25pm »
Quote

I was using NVIDIA 82.69: 1920x1200, 32M colors, 60Hz.

This driver has issues with full screen MS-DOS mode. Lately I found that full screen is possible by first switching to a windows with Alt+Enter and then switching back to full screen. In that way even Prince of Persia 1 runs.

New Test: Driver Standard VGA (PCI): 640x480, 16 colors.

All tests same results as test in Windows 3.1 earlier, except 5)+7)+13): same as in earlier Win98SE test.

I was not lucky in changing VESA-modes in Win98SE: black screens and reboots with time consuming scandisk operations.
I think it is a bit risky to continue with my best hardware. rolleyes
User IP Logged

watler
Administrator
ImageImageImageImageImage


member is offline

Avatar




Homepage PM


Posts: 164
xx Re: Windows 3.x Video
« Reply #5 on: Jan 16th, 2018, 6:41pm »
Quote

I am sorry if my programs have caused any problems. embarassed
Was /VESA/VROJECT1.exe able to enumerate your VESA modes?




User IP Logged

deomsh
Moderator
ImageImageImageImageImage


member is offline

Avatar




PM


Posts: 109
xx Re: Windows 3.x Video
« Reply #6 on: Jan 18th, 2018, 5:59pm »
Quote

The risk are all mine, I don't blame you. But as I am not sure to what risks my hardware is exposed, I downgraded my video card and my monitor.

Here are the results; enjoy!

Droject 1:

Video card: S3 Trio 64v+
Windows 3.1:
Test: Driver S3 1.70.04 : 640x480, 256 colors
0) Vesa mode=$13
1) Dispdib.dll functions and says in colored screen: "This is VESA MODE $13"
2) Get VGA mode: $00E9 and after OK: 233
3) Get current VESA mode : same as 0101 and after OK: 257
4) Hardware Banks/Pages: colored/pickled screen, when program returns colors stays green/pink, everything frozen reboot necessary
5) Show Bitmap: Requested Return is: 5; SegOrsel: 0; PhyssAddrHI: 6295; PhyssAddrLO: 0; Release result is 5.
6) OEMLayer Enable/Disable: black screen, program returns.
7) Windir16.dll: shows black screen with White " Windir..", program returns, very unstable afterwards
8) Long DPMI LFB: 131072
9) Word DPMI LFB: 131072
10) byte DPMI LFB: 131072
11) LFB to Bitmap: nothing
12) death/resurrection: Stable full screen green image, program returns
13) svga.dll: shows black screen with white font "Turbo debugger", program returns
14) Impossible: black screen, reboot necessary

Vroject 1:

Vesa mode 257:
Mode 257;Attr 27
WinA 7;WinB 0
Gran 64;WinSiz 64
SegA 40960;SegB 40960
Bytes 640
Width 640;Height 480
CharW 8;CharH 16
Planes 1
Bits 8
nBanks 1
Model 4;Banks 0
Pages 2;Reserved 1
RedMaskSize 0;RedFieldPos 0
GreenMaskSize 0;GreenFieldPos 0
BlueMaskSize 0;BlueFieldPos 0
RsvdMaskSize 0;RsvdFieldPos 0
DirColModeInf 0
PhysBasePtr $00000000
OffScreenMemOffset $00000000
OffScreenMemSize $0000
LinBytesPerScanLine 0
BnkNumberOfPages 0;LinNumberOfPages 0
LinRedMaskSize 0;LinRedFieldPos 0
LinGreenMaskSize 0;LinGreenFieldPos 0
LinBlueMaskSize 0;LinBlueFieldPos 0
LinRsvdMaskSize 0;LinRsvdFieldPos 0
MaxPixelClock 0

Tests: Windows 98SE; Video S3 Trio64v+; Monitor: Medion 15" max. resolution 1268x1024

Video-settings: 16-bits color, 1024x768, frequency: standard values adapter

Droject 1:

Tests: Windows 98SE; Video S3 Trio64v+; Monitor: Medion 15" max. resolution 1268x1024, 60,70,75Hz

Video-settings: 16-bits color, 1024x768, frequency: standard values adapter

Cannot find the 4 most significant bytes...

0) Vesa mode=$13
1) Dispdib.dll functions and says in colored screen: "This is VESA MODE $13"
2) Get VGA mode: $00ED and after OK: 237
3) Get current VESA mode: $00ED and after OK: 261
4) Hardware Banks/Pages: colored/pickled screen, when program returns colors stays red until reboot.
5) Show Bitmap: Requested Return is: 11; PhyssAddrHI: 00FA0000; Buffer_ID: 1; Release result is 11.
6) OEMLayer Enable/Disable: black screen, program returns, colors are normal again.
7) Windir16.dll: shows black screen with White " Windir..", program returns
8) Long DPMI LFB: 131072
9) Word DPMI LFB: 131072
10) byte DPMI LFB: 131072
11) LFB to Bitmap: nothing
12) death/resurrection with VESA index 261: stable full screen green image, program returns
13) Turbo debugger svga.dll: short seeing black screen with white text: "Turbo debugger text mode", program returns
14) VESA LFB address: $E011, changes after a few tests to zero's
15) Impossible: 105 -> : Black screen, then no screen, only monitor message: "Analog RGB; 81Khz/155Hz; Out of Range"

Vroject 1:

get vesa info: 256-263, 265, 266, 279-282, 288;
text: VESA Version: 1 2 S3 Incorporated. Trio64V+ ModeList 2471 Video Memory: 1024 Kb

Smallest mode: 132x25, biggest mode: 1600x1200 (never tried on this monitor)

mode info 261:
Mode 261
Attr 27
WinA 7;WinB 0
Gran 64;WinSiz 64
SegA 40960;SegB 40960
Bytes 1024
Width 1024;Height 768
CharW 8;CharH 16
Planes 1
Bits 8
nBanks 1
etc, all zero

Watler, both in Windows 3.1 and in Windows 98SE values RedMaskSize and below are all zero's. Has that any meaning? huh


User IP Logged

watler
Administrator
ImageImageImageImageImage


member is offline

Avatar




Homepage PM


Posts: 164
xx Re: Windows 3.x Video
« Reply #7 on: Jan 18th, 2018, 7:03pm »
Quote

Thanks deomsh.
I've not done much testing on PCI hardware.

The windows 3.1 Trio64v+ driver could already make use of the other modes.
You can manually edit system.ini to set the smaller resolutions.
I think the supported modes are listed in the back of your S3 manual.

A few years have passed since I've worked on this.
I guess I'll have to download my program and see what is wrong with it. tongue

My program does not reprogram or overclock your card.
None of the AGP or PCIE cards I've tested this on have failed or shown damage.

Most of the LCD screens I have been given are dead or not working properly.
Do you suppose that modern Windows drivers are responsible for the destruction of these monitors?


http://turkeys4me.byethost4.com/files/DIBDRV8.7z
« Last Edit: Jan 19th, 2018, 5:39pm by watler » User IP Logged

deomsh
Moderator
ImageImageImageImageImage


member is offline

Avatar




PM


Posts: 109
xx Re: Windows 3.x Video
« Reply #8 on: Jan 19th, 2018, 6:03pm »
Quote

You downloaded your old project? grin

I noticed there is a new version, after the weekend I have time to test. Are there special outcomes you are interested in?

When the program opens, I should insert somewhere 4 digits... Can you explain a bit?

I googled a bit about LCD-monitor overclocking (not video card!), but didn't find a real clue yet.

I once repaired a TFT-monitor, it was the power supply. Luckily there was an adapter cable between monitor and power supply, so when I finally found a (cheap) 20V/5A Laptop power adapter with the same fit, the monitor wake up again. And it's still in use!

If you like electronic repairs, maybe you would like: http://neoxy-yx.blogspot.nl/2011/12/tips-and-tricks-on-repairing-lcd.html

For the time being I will continue testing video programs with the old hardware I mentioned. I will try better resolutions in Windows 3.1 on this 22 years old card. I shall look if I can find the manual. I experienced that blind testing doesn't bring not succes. cry
« Last Edit: Jan 20th, 2018, 06:11am by deomsh » User IP Logged

watler
Administrator
ImageImageImageImageImage


member is offline

Avatar




Homepage PM


Posts: 164
xx Re: Windows 3.x Video
« Reply #9 on: Jan 19th, 2018, 8:51pm »
Quote

Thanks for the link, deomsh.
The manufacturers are about as prudent as the purchasers.
Most inexpensive LCD screens are of such poor quality that few regret their loss.

Much to my surprise I found that some PCIE cards have very good legacy support.
Some PCIE graphics cards are even capable of herculean feats.
Have you tested the legacy modes of your PCIE cards? (CGA,EGA,Hercules,MCGA,etc...)
There are Windows 3.1 drivers for many classic modes.

Some of the VESA features that my program expects may not exist on your trio64v+.
The VESA standard has grown much since it's first release.

User IP Logged

deomsh
Moderator
ImageImageImageImageImage


member is offline

Avatar




PM


Posts: 109
xx Re: Windows 3.x Video
« Reply #10 on: Jan 20th, 2018, 06:18am »
Quote

That's realy interesting, I didn't know. I will try as soon as I am finished with the S3 Trio 64v+.

The only thing I know about PCIe is that it's backward compatible with PCI, but that there is a different latency-mechanism. I think I have to read Scott-Muller's hardware-bible again on this subject. undecided
« Last Edit: Jan 20th, 2018, 06:19am by deomsh » User IP Logged

deomsh
Moderator
ImageImageImageImageImage


member is offline

Avatar




PM


Posts: 109
xx Re: Windows 3.x Video
« Reply #11 on: Jan 21st, 2018, 1:09pm »
Quote

I tested DIBDRV8...

Video card: S3 Trio 64v+
Windows 3.1:
Test: Driver S3 1.70.04 : 800x600, 32K colors
0) Vesa mode=$13 But: changed to $0105 see {...} below
1) Dispdib.dll functions and says in colored screen: "This is VESA MODE $13"; after change to $0105 only yellow screen with pickles band on top of it
2) Get VGA mode: $00ED and after OK: 237
3) Get current VESA mode : $0105 and after OK: 261. No problem anymore to change vesa-index from 256 to 261 (earlier have to return to main program with Ctrl+alt+del (no reboot necessary!)
4) Hardware Banks/Pages: colored/pickled screen, when program returns colors stays brown/red, everything frozen - reboot necessary VESA address is $0000
5) Show Bitmap: (VESA LFB address $0105) Requested Return is: 5; SegOrsel: 0; PhyssAddrHI: 4079; PhyssAddrLO: 0; Release result is 5
6) OEMLayer Enable/Disable: black screen, program returns.
7) Windir16.dll: shows black screen with White " Windir..", program returns, very unstable afterwards
8) Long DPMI LFB: 131072, Dialog with "small?" => does nothing. With VESA LFB address $0105 no dialog
9) Word DPMI LFB: 131072, Dialog with "small?" => does nothing. With VESA LFB address $0105 no dialog
10) byte DPMI LFB: 131072, Dialog with "small?" => does nothing. With VESA LFB address $0105 no dialog
11) LFB to Bitmap: nothing
12) death/resurrection: Stable full screen green image, program returns
13) svga.dll: shows black screen with white font "Turbo debugger", program returns
14) Impossible: black screen, program crashes, Windows returns after cltr+alt+del
15) Longest Word: Dialog with "small?" => won't disappear after OK, reboot necessary.

{Vroject:}

Mode 261;Attr 27
WinA 7;WinB 0
Gran 64;WinSiz 64
SegA 40960;SegB 40960
Bytes 1024
Width 1024;Height 768
CharW 8;CharH 16
Planes 1
Bits 8
nBanks 1
Model 4;Banks 0
Pages 0;Reserved 1
RedMaskSize 0;RedFieldPos 0
GreenMaskSize 0;GreenFieldPos 0
BlueMaskSize 0;BlueFieldPos 0
RsvdMaskSize 0;RsvdFieldPos 0
DirColModeInf 0
PhysBasePtr $00000000
OffScreenMemOffset $00000000
OffScreenMemSize $0000
LinBytesPerScanLine 0
BnkNumberOfPages 0;LinNumberOfPages 0
LinRedMaskSize 0;LinRedFieldPos 0
LinGreenMaskSize 0;LinGreenFieldPos 0
LinBlueMaskSize 0;LinBlueFieldPos 0
LinRsvdMaskSize 0;LinRsvdFieldPos 0
MaxPixelClock 0

Switching VESA-mode seems to be stable now. smiley
User IP Logged

watler
Administrator
ImageImageImageImageImage


member is offline

Avatar




Homepage PM


Posts: 164
xx Re: Windows 3.x Video
« Reply #12 on: Jan 21st, 2018, 8:19pm »
Quote

Everything looks to be in order.
Thank you for testing my program with your Trio64V+.
User IP Logged

Pages: 1  Reply Notify Send Topic Print
« Previous Topic | Next Topic »

Donate $6.99 for 50,000 Ad-Free Pageviews!

| |

This forum powered for FREE by Conforums ©
Sign up for your own Free Message Board today!
Terms of Service | Privacy Policy | Conforums Support | Parental Controls