I have an fic-2013 motherboard with 160 megs of pc-100 memory and a diamond viper II card. I bought a Geforce 2 mx card yesterday. The machine ran perfectly with the viperII card but the mx locks up. I tried downloading the newest drivers from nvidia. Didn't help. It lockups up when I try to run the high detail portion of 3dwinmark 2000. I thought maybe it was memory so I replaced the memory with a different dimm.. Still no luck. When it locks up, it's a total lockup and can only re recovered by turning the power off. Any help would be surely appreciated.

well here's a suggestion... what driver version are u using... there have been reports that the newer detonator drivers are causing that exact symptom in a few peoples systems. Try removing those drivers (if u have them) and installing an older version, I unfortunately don't have the versions in question at hand... as im at school... but it's something to look into

------------------
Who let ma Moose out! Huaaannnngnggnggg :P

Muahahahaha I'm amazing here's that link

http://www.tweakpages.cjb.net/

------------------
Who let ma Moose out! Huaaannnngnggnggg :P

I installed the detonator 3 drivers from invidia's web site. The 6.5 drivers.

This is exactly the same problem I'm having. Thank you for the information. But I have what is surely a dumb question.. What is the "FSAA"?

Maybe disabling this will help my problem.
2/08/01 - w00t! I got another H|OCP mention today. It looks like quite a few people are having problems with the nVidia 6.50's official drivers. Here's what I sent in to Hard|OCP:
After installing the official 6.50's, 3DMark 2000 quits in the middle of game test 2: high detail. I've tried several times and the crash has occurred each time. This is happening just after I reformatted and installed a fresh install of Win98SE. I get the same crashes when I overclock my Celeron 566 too high.

I found today, however, that 3DMark doesn't crash anymore when I disable FSAA for D3D. I sent in a second email stating:
I noticed that some Win2K users had problems with FSAA on the 6.50's, so I checked if I had FSAA enabled (even though I use Win98). It turns out that after I reformatted, I forgot to disable FSAA (I usually disable it for the extra performance). I disabled it and ran 3DMark again. My system went through all the tests without crashing. It seems like there's something wrong with FSAA in the 6.50's.

FSAA is "full screen anti-aliasing"

Put simply, it's a way of getting rid of "jaggies." You know when you look at the edge of an object, or any other line in computer graphics for that matter, and how it isn't "smooth", how you can see it's pixilated?

Well, there are a couple ways of doing anti-aliasing to get rid of the "jaggie's", one that 3dfx used (and now Nvidia has access to due to the buyout), and the one that Nvidia and ATI have been using.

3dfx effectively draws the image more than once, with slight "shifting" to get the lines to look smoother and blend better.

The way that Nvidia does it is to draw the one image just once, but to do it at a higher resolution, and then to scale the image back down to the resolution that you have it set at. This also helps to eliminate the "jaggie's".

Though quality is in the eye of the beholder, both methods produce very similar results, with the 3dfx version, perhaps, being slightly superior in terms of quality. Both end up with the same performance hit (that is, given the same settings).

If you have an mx, I don't suggest using FSAA (not to mention it locks up on you), because in order to get use FSAA, you use more graphics power, and more memory bandwidth (proportional to the FSAA setting you use). The mx doesn't exactly have bandwidth to spare, so I'd stay clear from it, just because it will decrease your frames quite a bit

I know my discussion of FSAA is crude at best, but I don't feel like writing a report :P

I'm reading that there seems to be many problems with the detonator 3 drivers 6.50. Would it help to go back to an early verion driver? Also, where do I turn off the FSAA?

Well I fixed the problem by buying a new motherboard. Everything works fine now with the procomp motherboard with the via 133 chipset. Got that at fry's with a celeron 633 and board for 129.

At least the problem is solved

__________________
ActiveTuning - Partner & Director Of Sales & Marketing

Here's another suggestion. I recently bought a MX board for my Mom. I noticed that it didn't come stock with video heatsink/fan combo. It only has a heatsink. I wonder since FSAA is an intense load on the videocard that this could be an issue with overheating. Maybe the newer mobo has better heat management. I know it's a shot in the dark, but you never know.

__________________
"Smith & Wesson: The original point and click interface"