WARNING Glide2x.dll Memmap fix may damage yourcard

[Brain]

It blew up my X-24 just like that.

It worked for all of about 5 minutes and then smoke.

I used glide2x.dll from your post. Not sure if there were voltage hacks in it. If somebody has any idea what happened to my beatiful little x-24 please let me know

ballen1 at cox.net

[Brain]

I'm so sad.

Anyways
My system spec's are

AMD 2100 XP
512MB Ram DDR @ FSB 333
MSI KT333 @ 333 FSB
ATI AIW 9700 Pro
Off brand NIC 10/100
IDE ATA 133 Maxtrox HD 80 Gigs
DVD-RW TEAC
On Board Sound
Was an Enlight Powersupply 350
Now an Antec 450 Powersupply

I was testing it out with Sierra's Red Baron 3d and then Ultrahle
Mario 64 at 1024x728 the colors where so perfect ran so smooth.  Until pop.

This it the post I got the idea from : (
***********************
ok radeon guys,got a present for ya-you have desktop corruption after exiting a glide2x app? well get the original 3dfx glide2x ver. 2.56.00.0456 (its in the beta directx7 win9x voodoo2 driver,get it here),put it in your system32 folder,boom everything works.I almost cant believe the solution was so simple..
***********************

Boom was correct. As it blew up my computer
http://www.inc_exe.szm.sk/glide2x_radeon.zip
Here is the link.

I'm not blaming anybody.  Just want to know what happened to my system and to caution other people.

Is the glide2x.dll have mhz settings.  If so it must of been really high because x-24 are already clocked higher then regular voodoo2's

[Manuelson]

very sorry about it..

[ps47]

..sorry to hear that.well I havent modified that glide2x in any way (and the file does not seem to override registry settings,all my reg settings were accepted perfectly),its just a regular glide2x for voodoo2 version 2.56.00.0456 (the latest is 2.56.00.0459,so they are pretty close),and it is working great for me.note that I have a regular SLI,not the x-24..and this glide2x is NOT supposed to fix the memmap error,it ONLY fixes the radeon desktop corruption..

[Brain]

Hello

This is what my reg is for my card

[HKEY_LOCAL_MACHINE\SOFTWARE\3Dfx Interactive\Voodoo2\Glide]
"SSTV2_RGAMMA"="1.35"
"SSTV2_GGAMMA"="1.35"
"SSTV2_BGAMMA"="1.35"
"FX_GLIDE_SWAPINTERVAL"="0"
"SSTV2_FASTMEM"="1"
"SSTV2_FASTPCIRD"="1"
"FASTMEM_RAS_READS"="1"
"SSTV2_REFRESH_512x384"="60"
"SSTV2_REFRESH_640x400"="60"
"SSTV2_REFRESH_640x480"="60"
"SSTV2_REFRESH_800x600"="60"
"SSTV2_REFRESH_1024x768"="60"
"FX_GLIDE_TMU_MEMSIZE"="2"
"SSTV2_SLIM_VIN_CLKDEL"="0"
"SSTV2_SLIM_VOUT_CLKDEL"="0"
"SSTV2_SLIS_VIN_CLKDEL"="0"
"SSTV2_SLIS_VOUT_CLKDEL"="0"

I think that is from my last driver I installed I cant rememeber which driver I know though under device manager that they were installed as 3dfxZone driver or whatever.
Then i put in that glide2x.dll.  

I always had problems with my card with memmap error.  The card was in my other machine running windows ME on a older nvidia gf4 card.  It worked fine on that machine with the regular old 3dfx driver release.   Then I got the crazy idea to put it in my machine.  I probably should of tried installing the whole Koolsmokey packaged.  But the glide2x.dll was quick and easy I hate reinstalling those cards windows always freaks out when I try to change the drivers on it.

So let me know if those reg settings where fatal.  Or maybe it was just it's time to go.
I also have Ati driver of = Driver Packaging Version 8.071-041026a-018719C CATALYST™ Version   04.11 with CCC   

[ps47]

..no idea about those reg settings,doesnt look like they could cause the crackdown.is your system overclocked? are you runing anything like dynamic overclocking? I blew a card only once,and the reason was faulty PCI lot..or maybe the card simply decided it is time to go..

[Brain]

Nope not overclocked
Nothing running that would overclock anything.  My PCI bus seems to work fine.  The slot isnt burnt or anything.  The card was clean.  Case is very clean. The card was not hot.  The system runs very cool, for an Athlon 110 F Cpu temp about 100F case temp.  Plenty of air flow, sounds like a jet engine.

[ps47]

..no more ideas.