Same screen mode - different refresh values

Lord Aga · 08 June 2016, 19:31

Now this is odd.

I play around with three WB installs.
All three are set to use DblNTSC 640x400 no flicker.
The thing is, that in all three systems it has different refresh values, which results in slightly different display.

Fresh WB 3.1 install, done by me (yes copyright police, I have the original disks) has 58Hz 27.66KHz.

6 months old WB 3.1 install, also done by me, has 61Hz 30.01KHz.

Classic WB full has 62Hz 29.57KHz.

What's the deal with this ?

EDIT:
Another peculiarity - if I copy the DblNTSC file from 'Monitors' from one system to another, the host system 'absorbs' the new file and keeps the old values.

thomas · 08 June 2016, 20:24

Check if VGAOnly driver is in Devs/Monitors, it slightly changes frequencies of Dbl* modes.

Also check tooltypes of files in Devs/Monitors. IIRC modes can be adjusted by tooltypes.

Leffmann · 08 June 2016, 21:31

Is there driver somewhere that gives the 640x480 60Hz VGA signal with industry standard timings? Or this is what the DblNTSC+VGAOnly gives?

thomas · 08 June 2016, 22:43

This should be Multiscan:Productivity, either with or without VGAOnly. DblNTSC is 640x400.

Leffmann · 09 June 2016, 23:51

Thanks, VGAOnly + Multiscan:Productivity was the right combination. If anyone knows of a single driver that does the same, I'd still be interested in it.

Lord Aga · 10 June 2016, 14:39

Hmm well whaddayaknow it was VGAOnly that was making problems. Differences I mean. Someone could prefer to use WB with or without it.

Thank you very much Thomas !

SyX · 10 June 2016, 15:30

Quote:

Originally Posted by Leffmann

Thanks, VGAOnly + Multiscan:Productivity was the right combination. If anyone knows of a single driver that does the same, I'd still be interested in it.

Maybe this? (At least include sources, notes and a disassembly of VGAOnly that can be helpful

)

daxb · 10 June 2016, 16:47

You can try MonSpecsMUI (Aminet) to build/change screenmodes. With TotClk/TotRow the H/V frequence (lines/rows will change too) can be changed but be careful. Wrong values can destroy your Monitor. Good is when your monitor works with < 30 kHz. The lower the more lines can a screenmode have.

Leffmann · 14 June 2016, 11:12

Thanks I'll take a look.

08 June 2016, 19:31	#1
Lord Aga MI clan prevails Join Date: Jul 2010 Location: Belgrade, Serbia Posts: 1,443	Same screen mode - different refresh values Now this is odd. I play around with three WB installs. All three are set to use DblNTSC 640x400 no flicker. The thing is, that in all three systems it has different refresh values, which results in slightly different display. Fresh WB 3.1 install, done by me (yes copyright police, I have the original disks) has 58Hz 27.66KHz. 6 months old WB 3.1 install, also done by me, has 61Hz 30.01KHz. Classic WB full has 62Hz 29.57KHz. What's the deal with this ? EDIT: Another peculiarity - if I copy the DblNTSC file from 'Monitors' from one system to another, the host system 'absorbs' the new file and keeps the old values. Last edited by Lord Aga; 08 June 2016 at 19:42.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Full-screen mode black screen with Default refresh rate	mark_k	support.WinUAE	4	16 February 2016 20:29
Detecting screen mode	arti	Coders. General	2	11 January 2016 20:19
ASM-One screen refresh in RTG mode	Diz_57	support.WinUAE	10	07 December 2015 21:57
screen mode	Jherek Carnelia	support.WinUAE	1	03 July 2003 09:36
Screen refresh problems	tomcat666	support.WinFellow	3	26 December 2001 17:42

08 June 2016, 20:24	#2
thomas Registered User Join Date: Jan 2002 Location: Germany Posts: 7,026	Check if VGAOnly driver is in Devs/Monitors, it slightly changes frequencies of Dbl* modes. Also check tooltypes of files in Devs/Monitors. IIRC modes can be adjusted by tooltypes.

08 June 2016, 21:31	#3
Leffmann Join Date: Jul 2008 Location: Sweden Posts: 2,269	Is there driver somewhere that gives the 640x480 60Hz VGA signal with industry standard timings? Or this is what the DblNTSC+VGAOnly gives?

08 June 2016, 22:43	#4
thomas Registered User Join Date: Jan 2002 Location: Germany Posts: 7,026	This should be Multiscan:Productivity, either with or without VGAOnly. DblNTSC is 640x400.

09 June 2016, 23:51	#5
Leffmann Join Date: Jul 2008 Location: Sweden Posts: 2,269	Thanks, VGAOnly + Multiscan:Productivity was the right combination. If anyone knows of a single driver that does the same, I'd still be interested in it.

10 June 2016, 14:39	#6
Lord Aga MI clan prevails Join Date: Jul 2010 Location: Belgrade, Serbia Posts: 1,443	Hmm well whaddayaknow it was VGAOnly that was making problems. Differences I mean. Someone could prefer to use WB with or without it. Thank you very much Thomas !

10 June 2016, 16:47	#8
daxb Registered User Join Date: Oct 2009 Location: Germany Posts: 3,307	You can try MonSpecsMUI (Aminet) to build/change screenmodes. With TotClk/TotRow the H/V frequence (lines/rows will change too) can be changed but be careful. Wrong values can destroy your Monitor. Good is when your monitor works with < 30 kHz. The lower the more lines can a screenmode have.

14 June 2016, 11:12	#9
Leffmann Join Date: Jul 2008 Location: Sweden Posts: 2,269	Thanks I'll take a look.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)