G
Guest
Guest
Ok, before I get into the actual problem I'm having, I'll start off with a bit of background information...
Almost 3 years ago I bought a Compaq Presario, with a pII 350, and a then state-of-the-art Diamond Vipper 550 (16MB TNT, AGP.) This system lasted about 3 months before I started gradually replacing Compaq parts with my own. About a month ago this was my setup:
pII 350
384 pc-100 SDRAM
Sound Blaster Live
ELSA Erazor X (32MB GeForce 256)
Original Compaq MB
(And a few other insignifacant things, like CD-ROM, etc)
At this point I was starting to have some serious problems, which I attributed to my pitiful 165-watt power supply and Compaq Motherboard.
So, I got a nice new case w/ a 300 watt power supply, and a TYAN Trinity 400 S1854 motherboard. After I got everything installed into the new case and motherboard, I spent several hours running various games and programs, everything worked fine and I was happy.
Well, almost. The computer still *thought* it was a Compaq, even though my CD-ROM drive is now the only Compaq part left.
So, I backed up all my important "stuff", formatted, and then re-installed. Everything seemed to install fine, but when I tried to run a 3D game on my new install it crashed horribly.
After a few tests I discovered that the problem is only with Direct 3D. Direct Draw works ok, as does Software rendering, and OpenGL.
I've installed all the drivers for my motherboard, and the latest bios version is already pre-installed. Also, I've got the latest nVidia drivers, and am using Direct X 8.0. (Plus, since everything was working before I re-installed windows, it can't be a Hardware or BIOS issue.)
As for *how* it doesn't work: If I run DXDiag.exe and run the 3 Display tests, the two 3D hardware tests (hardware spinning cube, and hardware spinning cube with textures) result in a blank black screen for a couple seconds, then I am asked if I saw the cube. No errors, just no picture either.
I've tried changing all the D3D options in the Display Properties, and nothing seems to change the situation.
If anyone has anything they think would help, or has had a similar problem, PLEASE let me know
Thanks in advance for any help.
- Jektal
(jektal@sunlink.net)
Almost 3 years ago I bought a Compaq Presario, with a pII 350, and a then state-of-the-art Diamond Vipper 550 (16MB TNT, AGP.) This system lasted about 3 months before I started gradually replacing Compaq parts with my own. About a month ago this was my setup:
pII 350
384 pc-100 SDRAM
Sound Blaster Live
ELSA Erazor X (32MB GeForce 256)
Original Compaq MB
(And a few other insignifacant things, like CD-ROM, etc)
At this point I was starting to have some serious problems, which I attributed to my pitiful 165-watt power supply and Compaq Motherboard.
So, I got a nice new case w/ a 300 watt power supply, and a TYAN Trinity 400 S1854 motherboard. After I got everything installed into the new case and motherboard, I spent several hours running various games and programs, everything worked fine and I was happy.
Well, almost. The computer still *thought* it was a Compaq, even though my CD-ROM drive is now the only Compaq part left.
So, I backed up all my important "stuff", formatted, and then re-installed. Everything seemed to install fine, but when I tried to run a 3D game on my new install it crashed horribly.
After a few tests I discovered that the problem is only with Direct 3D. Direct Draw works ok, as does Software rendering, and OpenGL.
I've installed all the drivers for my motherboard, and the latest bios version is already pre-installed. Also, I've got the latest nVidia drivers, and am using Direct X 8.0. (Plus, since everything was working before I re-installed windows, it can't be a Hardware or BIOS issue.)
As for *how* it doesn't work: If I run DXDiag.exe and run the 3 Display tests, the two 3D hardware tests (hardware spinning cube, and hardware spinning cube with textures) result in a blank black screen for a couple seconds, then I am asked if I saw the cube. No errors, just no picture either.
I've tried changing all the D3D options in the Display Properties, and nothing seems to change the situation.
If anyone has anything they think would help, or has had a similar problem, PLEASE let me know
Thanks in advance for any help.
- Jektal
(jektal@sunlink.net)