Hi @all

does anybody now, what's the powerconsumation of this board? i've got one, but it crash after a while  ??? (some seconds or minutes). perhaps the powersuply isn't strong enough (230W). i havn't another one to test. what do you think?

Hm, the Power Consumption of these older Cards (usually) was far below that of more modern ones...

230W should be enough, but that heavily depends on the rest of your Hardware.

Also, the Quality of the Power Supply is actually more important than Wattage alone. If available, have a look at the Hardware Monitoring... All Voltages should be more or less rock stable, and close to their ideal numbers.

What kind of crash is it? Bluescreen, Error Window? Can you soft-reset? If you can soft-reset then start the program that produces the crash again and  after it crashes plug the monitor cable into your 2D card to read the error message. This method helped me to find out wich program (in my case it was a vxd from the voodoo drivers) caused the crash.

Regards,
Andreas

P.S.
I've found free- and shareware programs that optimize chipsetregisters (those get 20% more power and 120% more crashes) often leave the system in an instable state.

at first ervrithing is well, then it looks like interleave. and than it crashs. No message, no blue screen, just freeze. special opengl games (quake) don't run longer than a minute.

i've only the obsidian card, no 2d. it has an MGV 2000 daughter Card.

OS: Win95b
CPU: Celeron 366
SB128PCI
FastEthernetAdapter
HD: 1x3GB (Quantum), 1x10GB (IBM)
and CD-ROM-Drive
an old Gigabyte MotherBoard

Hmm....

To rule out Motherboard/CPU/Chipset and RAM (or timings), I recommend running the Self-/Torture Test of Prime95 :

http://www.mersenne.org/freesoft.htm

If you suspect a faulty Bit in your RAM, you could also run a thorough checkout with Memtest86 :

http://www.webattack.com/get/memtest86.shtml

If nothing turns up, I'd check for possible Temperature problems (CPU and Case in general). If leaving the case open while running tests results in a stable system, it is mostly an overtemperature for sure...

the system runs well before (with voodoo 3).
and now i just wanted to test the "new" overkill obsidian.
so i think there are not temperature problems (the case is open all the time).
i'll check Prime95 now.
ps: is there any way to test the memory of the videocard?

I only know one program to test videomemory but it only tests the 64K Buffer at A000 and not the linear memory.This is useless as the Voodoo1 and Voodoo2 only have a linear frame buffer. On the other hand it shoud be easy to write a program that fills and reads the video memory. The most importent thing to test Voodoo memory is that the program don't test the full  memory-range as the voodoo has it's io section at the beginning of the linear framebuffer.

Regards,
Andreas

P.S.
When i had problems with my voodoo1 it never crashed totally. I was always able to do a warm start. Because quake runs for a minute and then crashes i agree with falconfly that this could be a stability problem.

i've testen some things, here are the results:

Prime95: no problems found
Unreal1 with Glide: runs very good, no crash
some old glide games run well
Madonion 3DBench (99,2000,xl-r8r): crashs
Forsaken: crashes
GLQuake with MiniGL 1.49: crashes
GLQuake with MiniGL 1.1: no problems ???

an old Voodoo1 board (Monster3D) has no problems.
i see no chance to bring the obsidian work in this computer. i think there is a compatibility problem with other hardware (Motherboard). i'll test the obsidian again if i have an other computer.

thx for helping

I used the Q3D-Drivers from the Falconfly-Archive (12.Feb. 1998).
I tried DirectX5 first, then DirectX8.0: nothing changes.

PS: with WinNT4 sp6 are the same problems.

3DMARK runs on my Voodoo² only for 30 seconds then it crashes. Because everything else, d3d, glide and ogl gsmes and prime work perfect for hours i think it is a bug in the driver (3dvxv2.drv crashes). I don't know quantum drivers but maybe you should check alternate (older driversets). There are also BIOS parameters that affect Voodoobased Boards. You should try "conservative" settings in the BIOS (if i use slowest ram-setting 3dmark nearly makes it to the loop) to check if the runtime of "problem-games" will increase.

Regards,
Andreas

YES  ;D
I've got it!

A friend gave me an ATX Mainboard (Elitegroup) and an ATX PowerSupply. I use the same BIOS Setting as on the other Mainboard, the same Gfx-Drivers, the same Win95B, the same Programs...

And now everything works fine.

Yea, yea, yea. It's PARTYTIME   ;D  ;D  ;D