in win2k on my g200, i get error that resolution manager can't access the registry.. i am using latest drivers... it did work before, maybe its not compatible with 5.82 ?!?!?
Announcement
Collapse
No announcement yet.
PowerDesk Resolution Manager doesn't work in win2k
Collapse
X
-
PowerDesk Resolution Manager doesn't work in win2k
<font size="1">Gigabyte GA-6VXC7-4X MoBo
VIA Apollo Pro 133a (694x/686A) chipset (4x agp, UDMA 66)
Celeron II 733 CPU (coppermine 128)
128meg (2x64) 133mhz SDRam
Matrox Milleniumm G200 AGP 16 mb
Creative Sound Blaster Live! 5.1 Digital model 0100 (MP3+, Gamer)
Quantum LM 30 gig HD 7200 RPM UDMA 66
Realtek 8029A NIC Card
Optiquest V775 17" Monitor
Actima 36X CD-Rom
Advansys 510 SCSI Card (ISA, but good enuf for my burner)
Yamaha 6416 CD-RW
Windows 2000 (primary)
Slackware Linux 9.0(secondary/emergency)</font>Tags: None
-
Are you using the latest 4.1 version of PowerDesk Resolution Manager? I have no problems using it with the 5.82 drivers on Windows XP, which should be the same as Windows 2000.
If not, get 4.1 from here http://www.murc.ws/Utils.html.Mark Veneziano
-
yes ... 4.1<font size="1">Gigabyte GA-6VXC7-4X MoBo
VIA Apollo Pro 133a (694x/686A) chipset (4x agp, UDMA 66)
Celeron II 733 CPU (coppermine 128)
128meg (2x64) 133mhz SDRam
Matrox Milleniumm G200 AGP 16 mb
Creative Sound Blaster Live! 5.1 Digital model 0100 (MP3+, Gamer)
Quantum LM 30 gig HD 7200 RPM UDMA 66
Realtek 8029A NIC Card
Optiquest V775 17" Monitor
Actima 36X CD-Rom
Advansys 510 SCSI Card (ISA, but good enuf for my burner)
Yamaha 6416 CD-RW
Windows 2000 (primary)
Slackware Linux 9.0(secondary/emergency)</font>
Comment
-
Well the way PowerDesk Resolution Manager works is by searching certain known areas of the registry for information that looks like it's related to Matrox PowerDesk. Are you familiar with editing the registry? If so, make sure the following registry key exists:
HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\VIDEO
Look at the values under that key, and one of them should look something like:
\REGISTRY\Machine\System\ControlSet001\Services\G2 00\Device0
If you have that, go to the key with that name, substituting HKEY_LOCAL_MACHINE for \REGISTRY\Machine, as follows:
HKEY_LOCAL_MACHINE\System\ControlSet001\Services\G 200\Device0
Now under that key, you should have a value called Mga.SingleResolutions.
If you have all the keys and values described above, I have no idea what the problem is! However, if you are missing any of them, do a complete uninstall and then reinstall of the 5.82 drivers. I have seen cases in the past where just installing new drivers over old ones without uninstalling first does not create the Mga.SingleResolutions value.
Good luck!Mark Veneziano
Comment
-
i dont have the key Mga.SingleResolutions
i uninstalled 5.82, then rebooted and reinstalled, no luck, key still not there,
maybe someone can tell me what is in the key, maybe i will add manually<font size="1">Gigabyte GA-6VXC7-4X MoBo
VIA Apollo Pro 133a (694x/686A) chipset (4x agp, UDMA 66)
Celeron II 733 CPU (coppermine 128)
128meg (2x64) 133mhz SDRam
Matrox Milleniumm G200 AGP 16 mb
Creative Sound Blaster Live! 5.1 Digital model 0100 (MP3+, Gamer)
Quantum LM 30 gig HD 7200 RPM UDMA 66
Realtek 8029A NIC Card
Optiquest V775 17" Monitor
Actima 36X CD-Rom
Advansys 510 SCSI Card (ISA, but good enuf for my burner)
Yamaha 6416 CD-RW
Windows 2000 (primary)
Slackware Linux 9.0(secondary/emergency)</font>
Comment
-
The Mga.SingleResolutions value should be a REG_BINARY value that contains the hex values for each of the resolutions that are enabled. For each resolution, the horizontal value appears followed by the vertical. Each value is 16 bits in little endian format. On my machine, the value looks like:
80 02 E0 01 20 03 58 02 .....
80 02 = 0280 hex in little endian = 640 decimal
E0 01 = 01E0 hex in little endian = 480 decimal
20 03 = 0320 hex in little endian = 800 decimal
58 02 = 0258 hex in little endian = 600 decimal
So this means I have 640x480 enabled, then 800x600 enabled, and so on.
Hope this helps!Mark Veneziano
Comment
-
ok, this is what i did,
uninstalled 5.82, rebooted, installed 5.33, rebooted,
checked if key was there, it was, I exported the key,
ran pdesk resol-man, it worked!
so, i uninstalled 5.33, rebooted, installed 5.82, rebooted
checked if key was there, it was! tried running pdesk
resol-man, it did not work.... i merged the key from 5.33,
and tried that, to my suprise, still, it did not work, i
think it is something more than the key...
note that if pdesk res-man gives you the error
"cannot access the registry" it will erase the key
Mga.SingleResolutions
maybe it works for you because im guessing
you installed 5.82 on top of 5.33, ie, did not
uninstall 5.33 first ?!?!
any other clues?<font size="1">Gigabyte GA-6VXC7-4X MoBo
VIA Apollo Pro 133a (694x/686A) chipset (4x agp, UDMA 66)
Celeron II 733 CPU (coppermine 128)
128meg (2x64) 133mhz SDRam
Matrox Milleniumm G200 AGP 16 mb
Creative Sound Blaster Live! 5.1 Digital model 0100 (MP3+, Gamer)
Quantum LM 30 gig HD 7200 RPM UDMA 66
Realtek 8029A NIC Card
Optiquest V775 17" Monitor
Actima 36X CD-Rom
Advansys 510 SCSI Card (ISA, but good enuf for my burner)
Yamaha 6416 CD-RW
Windows 2000 (primary)
Slackware Linux 9.0(secondary/emergency)</font>
Comment
-
Hmmm, this is an interesting problem. I definitely did not have 5.33 installed before, I had whatever version was available in January 2002, which was when I most recently installed Windows. I'm guessing it was one of the 5.8x betas.
I think it would be easier to debug this problem if we talked in real-time. I see you have an ICQ number, so I'll add you to my contact list. You can get my contact info from my profile as well. If I catch you online, maybe we can get this solved!Mark Veneziano
Comment
-
In case anyone's reading this thread besides nehalmistry and myself, the problem was that 4.1 is not the latest version of PD ResMgr...it's 4.2! I wrote the program and I don't even know what version it's up to!
Doh!
Hey Ant...how come the MURC Utils page doesn't have the latest version???
If anyone's looking for the latest, get it here:
Mark Veneziano
Comment
Comment