//flex table opened by JP

Click to See Complete Forum and Search --> : Don't use Diamonds new M3D drivers..........


Plaster
05-11-1999, 06:50 AM
They'll fry your card. I had been using the 1997 drivers with my Monster 3D 1 and it was running fine. I downloaded the new drivers from Diamons website and after I installed them, they fried my card. How do I know they fried it? Well, consider that even after removing each and every reference to the card from My PC, including the Registry, the card still fails to operate. I'll start GLQuake, or Quake2 and it locks. If it does show anything at all, it's all garbbled. Even the spinning globes on the M3D display properties completely lock up the card. Diamond should by my @$$ a new card as far as I'm concerned. This is BS. So take my advice, don't get the new Monster 3D 1 drivers from Diamond. Anyone think I can run a Voodoo3 PCI on my weak little system?

AMD k6 300 w/o 3DNOW!
64MB SDRAMM
Windows 98


[This message has been edited by Plaster (edited 05-11-99).]

harddisk
05-11-1999, 01:02 PM
V3 will be fine on ur machine...

about frying ur card...
which latest driver u use for ur monster1?
I m using Glide 2.46/3.0, it works fine... http://www.sysopt.com/forum/smile.gif

Plaster
05-11-1999, 03:44 PM
Yeah, I was using glide 2.46 as well. The driver from Diamond was released on 2/25/99.
Here's the address for it. http://www.diamondmm.com/products/drivers/monster-3d.cfm

The driver version is Version: 4.10.01.1600
bad news in my opinion. Maybe my card just bit the dust after 2 years, but it's a pretty strange coincidence that it happened at the exact moment I installed the update.

Plaster
05-12-1999, 03:47 PM
I got a little better description of whats going wrong with my card. I think the Texture chip went tets up. I ran the DirectX diagnostics and the directdraw worked fine, in both software and hardware. Then I ran the Direct 3D test and the spinning cube ran in sodtware mode, but froze up in Hardware. When I run GLQuake, you can hear the sounds for about 2 seconds before it locks and the display shows grey vertical bands. You can tell that it's OpenGl because the bands are anti-aliased. HAHA.

[This message has been edited by Plaster (edited 05-12-99).]

harddisk
05-13-1999, 10:52 AM
yeah, that's pretty strange...
maybe the texelfx chip it too hot...
try to underclock it or get a fan for it..

It happened to mine once, but no more...tat was last year with old driver...the game become slow...slow down a lot...

BTW, i didnt use tat new driver(not on 2/25/99 though)
Try the old driver Glide 2.43 ...
Glide 2.46 force Trilinear filtering for monster3D 1...so, there's more cycle for the chip...and more processing...maybe this is the cause

Plaster
05-13-1999, 02:54 PM
I already tried underclocking it, I set it to 45. That didn't do anything but make the grey bands brighter. The TMU doesn't even get hot anymore. It has to have broken. I'll try using the glid 2.43 drivers, but if that doesn't work, it's time for a new card.

BBA
05-14-1999, 10:17 PM
Have you tried a fresh windows installation?

It is possible a registry corruption occured when the new driver was installed.

BBA

Plaster
05-15-1999, 05:23 AM
Good idea BBA, I had just done that. It didn't work. At first I thought it did because my windows OpenGL screensavers started working again. Turns out they were just using the Direct3d from my crappy 2D card. When I went to run anything based on Direct 3D, Glide, or OpenGL, it loked. Oh well. Thanks for the suggestions. I guess I'm just going to have to get a new card.
http://members.aol.com/llbidinous/page/buttons/rockbutton.jpg