Adj Monitor Refresh Rate

Buffalo wrote:

Tried it. Still at 60Hz even though I get choices in Display
Manager to change it. The monitor still stays at 60Hz.
I tried the Super VGA 1280x1024@75 and it was recognized in
Display Manager with refresh rates up to 75Hz. Still no luck.

There seems to have been an issue with catalyst drivers related to
refresh rates and DDC.

http://www.codycafe.com/Files/detail...hannel= Files

ATI CATALYST 5.4 drivers (possibly released only for XP and 2K) was
released 4/20/2005 and this is one of the problems that it fixed:

- Attempting to apply a higher refresh rate to a non-DDC
monitor no longer results in the refresh rate reverting
to 60hz

Perhaps there is no updated win-98 catalyst driver that fixed that
problem (or if there is, you don't have it). The way I see it, you
need to look into not using the Catalyst driver, or find the absolute
most recent version for win-98, or pursue this in an ATI-specific
video card group or forum.

Or get your monitor's DDC working again. Maybe it can be turned on
and off via the setup buttons / menus?

Have a look he

http://fileforum.betanews.com/detail...e/1058330408/2

http://www.majorgeeks.com/ATI_Cataly...8Me_d4037.html

http://oldapps.com/old_version_ati.php

On Sun, 10 Jun 2007 09:10:07 -0600, "Buffalo"
put finger to keyboard and composed:

Franc Zabkar wrote:

The fact that your monitor works OK with Win2K suggests that the
monitor is not limiting itself as a consequence of its corrupted EDID.

That appears to be the case.

The limitation is in your OS or display driver. Having said that, your
display driver should be able to function properly with earlier
monitors that don't support DDC/EDID, so I can't see that as your
problem.

I just wonder what the registry change was in Win2000 that the ATI Catlyst
Control Center made that allowed it to work?
Perhaps it is Win98SE that is limiting the monitor timing since the EDID is
bad,
I tried installing a default monitor in Win98SE, but I still haven't been
able to get above 60Hz even though Display Properties lets me try different
refresh rates.

After reading 98 Guy's latest post, it seems that your display driver
is reverting to 60Hz for non-DDC capable monitors. I'd say that was a
bug.

The INF file for your monitor contains the following information. It
appears that its allowable refresh rates lie in the range of 50Hz to
160Hz.

================================================== =======
[1600]
HKR,,MaxResolution,,"1600,1200"

[EPI-910.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30.0-95.0,50.0-160.0,+,+"
================================================== =======

The above data appear to be written to this registry key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\Class\Monitor\000n\MODES

A list of allowable resolutions and refresh rates for your graphics
card is located at this key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\Class\Display\000n\MODES

If you can find your original EDID block in your registry (Win98 or
Win2K), then export it to a .reg file and post it here.

I'm not sure what key it is in. If you can tell me, I will export it both
from 2000 and 98 and post it here.

In my case it is located in a sub branch of this key:
HKEY_LOCAL_MACHINE\Enum\MONITOR

If you can't see it, then Edit - Find "EDID". Then use Registry -
Export - Selected Branch to write the EDID to a file.

It should then
be just a matter of finding a utility (eg PowerStrip) that can write
these data to your monitor. All that we would need to do would be to
present the data in a format that this utility requires.

I wouldn't know what format to use.

That's not a problem. Just use the utility to create a dummy EDID
block, or retrieve a known good one. Then use this dummy as your
template. I've already done this on my Win98 box for an EDID block
which I retrieved from a friend's Win XP machine.

See my recent post entitled "Ping Buffalo (re Monitor
MicroProcessor)":
http://groups.google.com/group/micro...b275ed0?hl=en&

When I originally installed PowerStrip, that was when the problem started. I
did not change any refresh rates, at that time, but had PowerStrip check the
EDID for my monitor (I was in 2000 at the time) and then the computer
basically slowed down to a crawl.
When I finally got to shut it down properly and restarted it, the refresh
rate was at 60Hz and the EDID was bad.
The makers of PowerStrip said that there was no way their software could
have caused the problem and they had no solution or suggestions for a
work-a-round.

See this article:

"Hacking a PSOne LCD into thinking it’s a monitor"
http://freespace.virgin.net/john.lau...SOne%20LCD.htm

The author writes that "the registered version [of Powerstrip] is
required to write the EDID to the eeprom".

- Franc Zabkar

Thanks again,
Buffalo

I wonder whether you could experiment in Windows 98 by unchecking
"Automatically detect Plug & Play monitors" in Display Properties -
Settings - Advanced - Monitor.

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

"Franc Zabkar" wrote in message
..
..
Interesting ideas,
Thanks
I will try them tomorrow and I really appreciate your time and suggestions.

"98 Guy" wrote in message ...
Buffalo wrote:

Tried it. Still at 60Hz even though I get choices in Display
Manager to change it. The monitor still stays at 60Hz.
I tried the Super VGA 1280x1024@75 and it was recognized in
Display Manager with refresh rates up to 75Hz. Still no luck.

There seems to have been an issue with catalyst drivers related to
refresh rates and DDC.


http://www.codycafe.com/Files/detail...hannel= Files

ATI CATALYST 5.4 drivers (possibly released only for XP and 2K) was
released 4/20/2005 and this is one of the problems that it fixed:

- Attempting to apply a higher refresh rate to a non-DDC
monitor no longer results in the refresh rate reverting
to 60hz

Perhaps there is no updated win-98 catalyst driver that fixed that
problem (or if there is, you don't have it). The way I see it, you
need to look into not using the Catalyst driver, or find the absolute
most recent version for win-98, or pursue this in an ATI-specific
video card group or forum.

Or get your monitor's DDC working again. Maybe it can be turned on
and off via the setup buttons / menus?

I sure would like to be able to turn it on again, but I am at a deadend.
I think it would take a flash utility, similar to flashing your BIOS or your
video card to accomplish that.
I think I will have ANOTHER beer.
Appreciate you interest and your time.


Have a look he


http://fileforum.betanews.com/detail...e/1058330408/2

http://www.majorgeeks.com/ATI_Cataly...8Me_d4037.html

http://oldapps.com/old_version_ati.php

I may try reverting to older drivers for the adapter card as it can't really
hurt anything.
Thanks again.

On Sun, 10 Jun 2007 17:08:46 -0600, "Buffalo"
put finger to keyboard and composed:

"98 Guy" wrote in message ...

Or get your monitor's DDC working again. Maybe it can be turned on
and off via the setup buttons / menus?

I sure would like to be able to turn it on again, but I am at a deadend.
I think it would take a flash utility, similar to flashing your BIOS or your
video card to accomplish that.

If you can retrieve your EDID data from your registry, then I'm
prepared to try to turn my old 17" Diamond View CRT into an Envision
EN-910.

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

Franc Zabkar wrote:
On Sun, 10 Jun 2007 17:08:46 -0600, "Buffalo"
put finger to keyboard and composed:

"98 Guy" wrote in message
...

Or get your monitor's DDC working again. Maybe it can be turned on
and off via the setup buttons / menus?

I sure would like to be able to turn it on again, but I am at a
deadend.
I think it would take a flash utility, similar to flashing your BIOS
or your video card to accomplish that.

If you can retrieve your EDID data from your registry, then I'm
prepared to try to turn my old 17" Diamond View CRT into an Envision
EN-910.

- Franc Zabkar

Can you really change the EDID in a monitor without some kind of flash utility?

I believe this is it. It was in the HKLM\Emum\monitor section.
I'm not sure I should post it as an .reg attachment, so I will just post it
this way from notepad.

Does the ATI vid card query the monitor all the time in Win98SE?
It really seems that in Win2000Pro, the Catylst Control Panel overrides the vid
card query to the monitor.

Also, just to clear things up, using a default monitor in Win2000Pro really
doesn't make a difference because using Catylst Control Panel lets my monitor
have different refresh rates with the Envision monitor also, as long as I
uncheck the 'use EDID or driver default' box and set the max resolution and max
refresh rate manually.

REGEDIT4

[HKEY_LOCAL_MACHINE\Enum\MONITOR\EPIA995\PCI_VEN_10 DE&DEV_0221&SUBSYS_A3413842&R
EV_A1_000800_1]
"Capabilities"=hex:14,00,00,00
"InitMonitorPowerState"="0d"
"EDID"=hex:00,ff,ff,ff,ff,ff,ff,00,16,09,95,a9,2b, 51,00,00,2d,0b,01,02,68,24,\
1b,78,2a,4f,29,a0,57,49,9b,26,10,48,4c,a4,43,00,31 ,59,45,59,61,59,81,59,81,\
99,a9,4f,01,01,01,01,86,3d,00,c0,51,00,30,40,40,a0 ,13,00,68,0e,11,00,00,1e,\
00,00,00,fc,00,45,4e,56,49,53,49,4f,4e,20,0a,20,20 ,20,00,00,00,fc,00,45,4e,\
2d,39,31,30,65,0a,20,20,20,20,20,00,00,00,fd,00,32 ,a0,1e,5f,14,00,0a,20,20,\
20,20,20,20,00,77

Franc Zabkar wrote:
[snip]
See my recent post entitled "Ping Buffalo (re Monitor
MicroProcessor)":

http://groups.google.com/group/micro...b275ed0?hl=en&

Just read it. Sorry, last night I didn't look at it, but now there is hope.
Strange, I was sure the folks at PowerStrip told me their program couldn't have
effected the EDID in my monitor, and now it seems that their 'paid' version can
reprogram the EDID in the monitor.

When I originally installed PowerStrip, that was when the problem
started. I
did not change any refresh rates, at that time, but had PowerStrip
check the
EDID for my monitor (I was in 2000Pro at the time) and then the computer
basically slowed down to a crawl.
When I finally got to shut it down properly and restarted it, the
refresh
rate was at 60Hz and the EDID was bad.
The makers of PowerStrip said that there was no way their software
could
have caused the problem and they had no solution or suggestions for a
work-a-round.

See this article:

"Hacking a PSOne LCD into thinking it's a monitor"
http://freespace.virgin.net/john.lau...SOne%20LCD.htm

I am in the process of digesting that article. Very good.
I may need some more help on this, but thanks for the lead.

The author writes that "the registered version [of Powerstrip] is
required to write the EDID to the eeprom".

- Franc Zabkar

Thanks again,
Buffalo

I wonder whether you could experiment in Windows 98 by unchecking
"Automatically detect Plug & Play monitors" in Display Properties -
Settings - Advanced - Monitor.

I did uncheck 'detect Plug & Play monitors' in Display Properties. Since my EDID
seems corrupted, it is no longer Plug & Play recognized and whether the box is
checked or not doesn;t seem to make a difference when I boot up.

- Franc Zabkar

On Sun, 10 Jun 2007 09:10:07 -0600, "Buffalo"
put finger to keyboard and composed:

The makers of PowerStrip said that there was no way their software could
have caused the problem and they had no solution or suggestions for a
work-a-round.

Short version:

I believe I have reproduced your EDID corruption problem. In
Powerstrip's pstrip.ini file, I can see two EDID blocks, neither of
which match the EDID block in my registry. Both appear to be corrupt.
I believe that your solution is to rebuild Powerstrip's EDID info
using the data from your registry, and to then update your monitor's
EDID using Powerstrip's Update EDID option.

Long version:

My configuration is Windows 98SE, Powerstrip 3.74, SiS Xabre 400 AGP
card, AOC LM721A 17" LCD monitor.

Here are my registry data:

"EDID"=hex:00,ff,ff,ff,ff,ff,ff,00,05,e3,81,a7,b8, 8a,00,00,16,0e,01,03,68,22,\

1b,78,2a,a6,9c,a1,5a,4b,98,24,16,4c,57,bf,ef,00,81 ,80,01,01,01,01,01,01,01,\

01,01,01,01,01,01,01,30,2a,00,98,51,00,2a,40,30,70 ,13,00,78,2d,11,00,00,1e,\

00,00,00,ff,00,30,38,30,34,35,4a,41,30,33,35,35,31 ,32,00,00,00,fd,00,37,4b,\

1e,53,0e,00,0a,20,20,20,20,20,20,00,00,00,fc,00,4c ,4d,37,32,30,2f,4c,4d,37,\
32,30,41,0a,00,fa

Here is one of my pstrip.ini EDID blocks:

EDID.Data.03.00=00,FF,FF,FF,FF,FF,FF,00,05,E3,81,A 7,B8,8A,00,00
EDID.Data.03.01=FF,FF,FF,00,E3,A7,8A,00,0E,03,22,7 8,A6,A1,4B,24
EDID.Data.03.02=FF,FF,05,A7,00,0E,68,78,9C,4B,16,B F,81,01,01,01
EDID.Data.03.03=FF,00,A7,00,03,78,A1,24,BF,80,01,0 1,01,2A,00,70
EDID.Data.03.04=FF,E3,00,03,2A,4B,57,80,01,01,30,0 0,13,00,00,30
EDID.Data.03.05=FF,A7,0E,78,4B,BF,01,01,01,00,00,1 E,30,41,32,37
EDID.Data.03.06=FF,8A,68,A1,57,01,01,2A,30,00,00,4 1,00,1E,20,FC
EDID.Data.03.07=00,00,78,24,80,01,2A,70,1E,30,35,3 7,20,FC,4C,FA

I notice that the first 16 bytes are identical, but all the others,
apart from the very last one, are different. If you refer to the
EDID/DDC spec, you will notice that the last byte (FA) is a checksum
of the previous 127 bytes. In the first case the checksum is correct,
in the second it is incorrect, which indicates that Powerstrip's data
are corrupt. Furthermore, the second last byte should indicate the
number of additional 128-byte blocks. In the first case there are
none, but in the second case there are 4C, ie 76 decimal. Clearly this
is nonsense.

You can also view the EDID blocks using the Phoenix utility, but you
will need to edit the data so that it looks like this:

EDID BYTES:
0x 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
------------------------------------------------
00 | 00 FF FF FF FF FF FF 00 05 E3 81 A7 B8 8A 00 00
10 | FF FF FF 00 E3 A7 8A 00 0E 03 22 78 A6 A1 4B 24
20 | FF FF 05 A7 00 0E 68 78 9C 4B 16 BF 81 01 01 01
30 | FF 00 A7 00 03 78 A1 24 BF 80 01 01 01 2A 00 70
40 | FF E3 00 03 2A 4B 57 80 01 01 30 00 13 00 00 30
50 | FF A7 0E 78 4B BF 01 01 01 00 00 1E 30 41 32 37
60 | FF 8A 68 A1 57 01 01 2A 30 00 00 41 00 1E 20 FC
70 | 00 00 78 24 80 01 2A 70 1E 30 35 37 20 FC 4C FA

Save the above as a file with a .dat extension.

Phoenix EDID Designer is happy to view this corrupt EDID (as long as
the data are in uppercase shrug), but it produces some nonsensical
results, eg Mfg Week 255, Mfg Year 2245, Version 255, Number of
extensions 76.

Note that I did not use Powerstrip to modify my display configuration.
I only used it to "read data from registry", "read data from stored
EDID", or "read data directly from monitor". Note also that while
Powerstrip does not recognise its own EDID blocks as corrupt, it does
complain that "EDID data is corrupt" if I make changes to the EDID
parameter at this registry key:

HKEY_LOCAL_MACHINE\Enum\MONITOR\AOCA781\PCI_VEN_10 39&DEV_0330&SUBSYS_0C651019&REV_01_000800

References:

VESA E-EDID Implementation Guide
http://www.stellae.fr/wiki/_media/ef...en&cache=cache

Powerstrip
http://entechtaiwan.net/files/pstrip.exe

Phoenix EDID Designer
http://file.softsea.com/System_Utility/Phoenix_1_3.zip

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

On Tue, 12 Jun 2007 07:26:59 +1000, Franc Zabkar
put finger to keyboard and composed:

If you refer to the EDID/DDC spec, you will notice that the last byte (FA) is a checksum
of the previous 127 bytes.

Sorry, the spec states that the last byte "is programmed such that a
one-byte checksum of the entire 128-byte EDID equals 00h".

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

On Mon, 11 Jun 2007 07:09:09 -0600, "Buffalo"
put finger to keyboard and composed:

Franc Zabkar wrote:
On Sun, 10 Jun 2007 17:08:46 -0600, "Buffalo"
put finger to keyboard and composed:

"98 Guy" wrote in message
...

Or get your monitor's DDC working again. Maybe it can be turned on
and off via the setup buttons / menus?

I sure would like to be able to turn it on again, but I am at a
deadend.
I think it would take a flash utility, similar to flashing your BIOS
or your video card to accomplish that.

If you can retrieve your EDID data from your registry, then I'm
prepared to try to turn my old 17" Diamond View CRT into an Envision
EN-910.

- Franc Zabkar

Can you really change the EDID in a monitor without some kind of flash utility?

Powerstrip can, and did, do it. This Update EDID feature appears in
the release notes.

In my case I have a device programmer that programs all sorts of chips
including serial EEPROMs. In the event that I was unable to find a
free utility to perform the update, I was going to make a cable to
connect my monitor to my programmer and then tell my programmer that
it was talking to an Atmel 24LC21 DDC capable serial EEPROM chip.

I believe this is it. It was in the HKLM\Emum\monitor section.
I'm not sure I should post it as an .reg attachment, so I will just post it
this way from notepad.

Does the ATI vid card query the monitor all the time in Win98SE?

I would have thought that the monitor is enumerated at each bootup,
unless PnP is disabled.

It really seems that in Win2000Pro, the Catylst Control Panel overrides the vid
card query to the monitor.

Also, just to clear things up, using a default monitor in Win2000Pro really
doesn't make a difference because using Catylst Control Panel lets my monitor
have different refresh rates with the Envision monitor also, as long as I
uncheck the 'use EDID or driver default' box and set the max resolution and max
refresh rate manually.

REGEDIT4

[HKEY_LOCAL_MACHINE\Enum\MONITOR\EPIA995\PCI_VEN_10 DE&DEV_0221&SUBSYS_A3413842&R
EV_A1_000800_1]
"Capabilities"=hex:14,00,00,00
"InitMonitorPowerState"="0d"
"EDID"=hex:00,ff,ff,ff,ff,ff,ff,00,16,09,95,a9,2b ,51,00,00,2d,0b,01,02,68,24,\
1b,78,2a,4f,29,a0,57,49,9b,26,10,48,4c,a4,43,00,31 ,59,45,59,61,59,81,59,81,\
99,a9,4f,01,01,01,01,86,3d,00,c0,51,00,30,40,40,a0 ,13,00,68,0e,11,00,00,1e,\
00,00,00,fc,00,45,4e,56,49,53,49,4f,4e,20,0a,20,20 ,20,00,00,00,fc,00,45,4e,\
2d,39,31,30,65,0a,20,20,20,20,20,00,00,00,fd,00,32 ,a0,1e,5f,14,00,0a,20,20,\
20,20,20,20,00,77

I've reorganised the above data as follows:

EDID BYTES:
0x 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
------------------------------------------------
00 | 00 FF FF FF FF FF FF 00 16 09 95 A9 2B 51 00 00
10 | 2D 0B 01 02 68 24 1B 78 2A 4F 29 A0 57 49 9B 26
20 | 10 48 4C A4 43 00 31 59 45 59 61 59 81 59 81 99
30 | A9 4F 01 01 01 01 86 3D 00 C0 51 00 30 40 40 A0
40 | 13 00 68 0E 11 00 00 1E 00 00 00 FC 00 45 4E 56
50 | 49 53 49 4F 4E 20 0A 20 20 20 00 00 00 FC 00 45
60 | 4E 2D 39 31 30 65 0A 20 20 20 20 20 00 00 00 FD
70 | 00 32 A0 1E 5F 14 00 0A 20 20 20 20 20 20 00 77

After saving the above as a .dat file and viewing it with Phoenix EDID
Designer, I see that the EDID block looks OK. For example, I can see a
vendor and product ID of EPI A995, and a manufacture date of week 45,
2001. I have also verified that the 8-bit checksum is correct (the sum
of all 128 bytes is 2100h).

I suggest you edit your pstrip.ini file using the above data and then
try updating your monitor's EDID with Powerstrip.

In my case pstrip.ini would look like this:

EDID.Data.03.00=00,FF,FF,FF,FF,FF,FF,00,16,09,95,A 9,2B,51,00,00
EDID.Data.03.01=2D,0B,01,02,68,24,1B,78,2A,4F,29,A 0,57,49,9B,26
EDID.Data.03.02=10,48,4C,A4,43,00,31,59,45,59,61,5 9,81,59,81,99
EDID.Data.03.03=A9,4F,01,01,01,01,86,3D,00,C0,51,0 0,30,40,40,A0
EDID.Data.03.04=13,00,68,0E,11,00,00,1E,00,00,00,F C,00,45,4E,56
EDID.Data.03.05=49,53,49,4F,4E,20,0A,20,20,20,00,0 0,00,FC,00,45
EDID.Data.03.06=4E,2D,39,31,30,65,0A,20,20,20,20,2 0,00,00,00,FD
EDID.Data.03.07=00,32,A0,1E,5F,14,00,0A,20,20,20,2 0,20,20,00,77

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.