Solution for opengl icd problems with g200 (pdesk 5.15)

[Zwisch]

Hi,

have you tried removing your memory module? I wouldn`t be surprised if this is what is causing your problems!

Ciao

Z

[ZokesPro]

Actually it does the same thing with or with out the memory module, I recently poseted a message about my problem when I had an 8mb card. The first tiem I put the module in OpenGL ICD worked fine for about 4hours then poof back to it's old self. Someone told me that this was a popular problem and there was going to be a fix but all my hardware works fine.

Explain to me this though, if the OpenGL iCD works in 8bit and 24bit then why does't it work in 16bit or 32bit? I've only started to get this problem ever since I put my G200 on my new motherboard.

If someone can find a fix for my problem I will be truly greatful. (keeping in mind that the only thing I haven't tried yet is trying out a different Millennium G200)

Besides my OpenGL ICD anomoly I love the G200 and think it's the best and fastest card out there because unless your a hardcore 3D animator you really don'y need anything more powerful!

[armyworm]

What you are saying makes no sense at all. A game will simply not work in 8 bit color and a vasta vast majority of OGL games will not run also in 24 bit. There is something that you are doing wrong or your system is gone to waste.

What games have you tried? What are your settings? Are you using Default OpenGL? You desktop is in what res and color? What else do you have in your system? What are you IRQ's listing?

Your problem simply doesn't make sense!

Ben

[ZokesPro]

Ok ok, it doesn't make much sense, but the program I use to see if I can use the OpenGL ICD driver is a standard OpenGL screensaver that uses the ICD driver. Now that screen saver runs in all modes all resoultions and that's what I mainly use to see if my OpenGL ICD driver works or not.

Now I know that say for instance, Quake doesn't run at 8bit or 24bit. I've talked to Matrox themsleves about this and haven't got a response yet. My IRQ's are fine, nothing in my system is conflicting with anything else. If my problem was a resolution or an IRQ conflict of some sort I would be posting a message here, I'm not computer illeterate, in fact I know more than most computer technicians in my town!

[armyworm]

yeah, but the question is : how many people live in your town... 5 ? 20 people ? just kidding...

Alright now, let's talk games, not screen savers!!! your CPU can do the decoding since it is not demanding enough... I have OGL screen saver running in NT and my card didnt support OGl... Now GAMES!! Which one did you try and what results are you getting? What DO you have in your system? I am asking this to try to help you out, not robb your house!! maybe I can see something that you overlooked! On what IRQ is your card? What else is on that same IRQ? At least an IRQ HOLDER FOR PCI STEERING I hope!! How fast is your system?? So you have a SS 7 or an Intel CPU??

We need some info if you want us to help you out!

Ciao

Ben

[Zwisch]

hi ZokesPro

armyworm is right, we would need some more info on your system and actual results with OpenGL games such as Quake2 in order to help you out.

regards

Z

[ZokesPro]

My system:
Celeron 366MHz (not overclocked)
Asus P2-99 rev 1.10 Bios 1009.A
Millennium G200 AGP 16mb SGRAM Bios 2.6 (PD 5.15)
128 megs SDRAM PC100 (generic)
SB PCI128
USR Winmodem 33.6 (upgraded to 56k)
Windows 98 Full with SP1 and IE5

Video Card on IRQ 11, as foro IRQ Holder for PCi steering. I can give you all my IRQ's if you want.

Hey guys I've got a wierd but interesting developpement about my problem. First I reboot my computer then I try out is an OpenGL screen saver I get that memory parity error and if I run everything else that requires OpenGL I get the same error. But if I reboot again and play Quake II in OpenGL then try out the same screen saver suddenly it works and keeps working until I reboot again.

By the way, when Quake II works it runs real smooth at 16bit 1024x768.

P.S: Sorry for pissing you off, I'm kinda tired of getting that damn error, sorry again.

[Apachez]

I heard about that parity error for half a year ago...

Someone said that a possible (read: possible) solution could be to put the memory (RAM) into another slot then its right now.

Why? dont know... but many problems with parity errors was solved by that.

However: whats your bios settings (dont post them in here - make a homepage with them on it), tried to disable ecc checking or shadowing etc. ?

[armyworm]

HI ZokesPro,

I think that we found your problem!!!! There is a problem with ECC memory in Asus Motherboards!!!! Go in your BIOS and set your RAM to NON-ECC. I am pretty sure at 90% that this will solve your lockups!!

Please let us know if that works!

Ciao

Ben

[ZokesPro]

Cool, a lot of possible solutions but sadly none of them work on mine. First of all I only have 2 slots for ram and they are filled, secondly the only ECC setting for my computer is CPU L2 cache ECC. I've tried all the other bios settings you recommended so far without any success.

I wish I had ECC settings for my RAM in my bios so I could disable them and end these weird lockups but I don't.

But I did put a text file with the main bios settings that interest people. It's at http://www3.sympatico.ca/md.audet/Bios.txt (it's case sensitive)

Sorry guys I've had no success so far.

[ZokesPro]

Looks like Apachez has the solution except you don't need to re-install the drivers at all!!!

Here's what I did, first I installed PD 5.15 and then I rebooted, without checking to see if the ICD worked I then downloaded the PD5 reg hacks and set it to AGP X2, and then rebooted again. That was my problem I guess, the message error I kept getting was a "memory parity error". Frustrated after weeks of trying to find that elusive solution I then tried to set the AGP back to default, then to AGP X1 then finally to AGP X2 and after many reboots it finally works!

But for how long? If it's a one time thing I will post a progress report. But at least now I know it's not my RAM (from cpu, video card or system) that's at fault, it never was! I give most of the credit to Apachez for is message, it suddenly clicked afte that. And for those who are pissed off and frustrated with me well, I thank you for your helpa dn I'm sorry for the grief I gave you.

Now for some testing to see if it's permanently fixed!

[ZokesPro]

Ok looks like it was a quick fix, in fact a very quick fix. Now when I boot and try Quake II I get that damn error.

I have no clue what to do about it anymore.

[armyworm]

HI Zokes..

I am still sure that it is related to the ECC settings. Let me check into this tomorow, I have a friend that has the same Mobo as you...

ciao

Ben

[armyworm]

Hi again,

I looked around but couldn't find the info I am not letting you down on this, I will try to find out otherwise...

Ciao

Ben

[ZokesPro]

I really appreciate the help, I am starting to lose hope that this problem will never get fixed.