RAB, I think we're getting somewhere

[Muad'Dib]

I've just tried those things and nothing helped. The CAS 2 brought about a lot of REALLY FUNKY lines and crap like that. Video shadowing did nothing either. I've just asked for my RMA now as opposed to waiting till I get an Athlon with the epox k7xa board to test it. Hopefully that will work. In the mean time, it's back to the productiva for a while I'm thinking.... Thanks again RAB and others for all the energy you've put into my system.

Dimitri

P.S.: I'm still trying various combinations of those enable disable stuff, but there's only so many times one can reset their computer in a day... I'll keep trying though. Thanks

[RAB]

dimitri,
Sorry that nothing we tried worked. If nothing else, you know a lot more than when you started. I, too, think it's something simple and may not be hardware. But since we've tried everything we can think of, its worth trying another G400.

The CAS 2 setting makes your memory run a little faster, but also makes it a little more unstable. If you have some older memory, its probably just not fast enough to run at CAS 2. So set it back to 3 for now.

Start a new thread when you get the new G400 and let us know what happens. Before you send it back, though, try the G100 and see if you get the same freezing problems. If you do, then maybe we have some more work to do. You might have to run UT at 640x480x16 to get decent speed, but give it a try first at your current resolution setting and see if it freezes. Remember to use the uninstaller to get the G400 drivers out before you put the G100 back in.

RAB

P.S. We probably should have tried this a long time ago, doh!!

[Muad'Dib]

Well I'm back to the productiva... I guess that means I'll be playing old school games like Diablo. Oh damn. What a shame... Yes RAB you're right. I learned a lot about computers from this "thing." I'll let you know what happens with the new one.

[paul]

Rab - the sb emulation seemed to change in either 2.0 or 2.1 (it used to be in the startup before windows got started somehow. I'd re-boot to dos prompt, delete sb references, save autoexec, re-boot, and sb would startup in autoexec again! They did away with that, thankfully