VOGONS


First post, by bjwil1991

User metadata
Rank l33t
Rank
l33t

I've recapped my VooDoo2 card a couple of weeks ago, and before, the VooDoo2 card was working without issues in Windows 98SE. Was detected in every software and games, including the DirectX Diagnostics software. Currently, I'm having issues left and right. The card's detected, but, the software and games, including DirectX Diagnostics aren't detecting the card, and the Display Properties gives me this error:

v2-1000-error.png
Filename
v2-1000-error.png
File size
3.52 KiB
Views
1037 views
File comment
Error code
File license
Fair use/fair dealing exception
v2-1000.png
Filename
v2-1000.png
File size
16.16 KiB
Views
1037 views
File comment
Display Properties
File license
Fair use/fair dealing exception

And, yes, I did attempt to reinstall Windows 98SE to no avail. What's causing this and how can I fix it? There are certain games that require the VooDoo2 card as they don't like modern GPUs very well, especially Jimmy Neutron Boy Genius (only works with the Riva TNT2 card).

Specs:

Motherboard: Shuttle AV18V31
CPU: Intel Celeron 1.4GHz
RAM: 256MB SD-RAM 133
GPU: nVidia GeForce4 Ti4400
3DFX: STB BlackMagic VooDoo2 12MB
Network: RealTek RTL8139D PCI
USB: ALi USB 2.0 PCI
Monitor: NEC MultiSync LCD1850e Dual VGA
Sound: Sound Blaster Live! 5.1 Platinum SB0100
HDD: Maxtor D740X-6L 60GB
ODD0: LG CD Burner
ODD1: Samsung DVD-ROM
OS: Microsoft Windows 98SE
Speakers: JBL Platinum speakers
MPU: Roland SC-55
PSU: 250W Bestec with the ATX-ATX w/ -5V adapter
Input: Compaq Internet Ready PS/2 Keyboard, Logitech Optical Wheel PS/2 Mouse, Microsoft Sidewinder Pro (connected to the sound card)

Discord: https://discord.gg/U5dJw7x
Systems from the Compaq Portable 1 to Ryzen 5 2600X
Twitch: https://twitch.tv/retropcuser

Reply 3 of 12, by leileilol

User metadata
Rank l33t++
Rank
l33t++

The latest Voodoo2 drivers require DirectX 7 (minimum) to work in Direct3D. If you don't want DX7, you'll have to fallback to some mid-1999 driver that has a DX6.1 HAL.

I'd imagine fatal hardware failure would mean a "voodoo^2 not detected" popup at boot.

apsosig.png
long live PCem

Reply 4 of 12, by Baoran

User metadata
Rank l33t
Rank
l33t

One thing I noticed was that I had bit similar error when I tried opening display properties when the first voodoo 2 driver I installed didn't seem to work even if I tried installing other voodoo 2 drivers on top of that, but things worked when I installed win98 again and installed fastvoodoo drivers immediately without trying manufacturers drivers. I don't know if someone has figured out how to clean old voodoo 2 drivers from the system without reinstalling whole win98 because that might be helpful.

Reply 5 of 12, by bjwil1991

User metadata
Rank l33t
Rank
l33t

@Cbb: I have the FastVooDoo2 4.0 GE installed.

@blurks: This also did the same thing before the recap and the caps are the same voltage and uF ratings. The bus mastering is enabled (will have to check again).

@Baoran: I attempted to reinstall Windows 98SE (reformatting the HDD isn't an option) with the CD and still nothing. I also installed the FastVooDoo drivers and DIrectX 9.0c to no avail. Will check again.

Discord: https://discord.gg/U5dJw7x
Systems from the Compaq Portable 1 to Ryzen 5 2600X
Twitch: https://twitch.tv/retropcuser

Reply 6 of 12, by DonutKing

User metadata
Rank Oldbie
Rank
Oldbie

Looks like you are having a similar problem to me.

Faulty Voodoo 2?

I haven't got a fix, but you can try the diag tools in that thread and see if that gives you any more info.

If you are squeamish, don't prod the beach rubble.

Reply 8 of 12, by bjwil1991

User metadata
Rank l33t
Rank
l33t

1 cap was missing and the other one had a dent on the top end of it. Figured better safe than sorry.

Discord: https://discord.gg/U5dJw7x
Systems from the Compaq Portable 1 to Ryzen 5 2600X
Twitch: https://twitch.tv/retropcuser

Reply 9 of 12, by bjwil1991

User metadata
Rank l33t
Rank
l33t

Here are the logs from my PC using that utility program.

SST1_3DF.log - MS-DOS
SST1_3DFX.log - Windows 9X
VooDoo2.txt - Output from the MOJO.EXE command using MOJO > VooDoo2.txt in the command prompt.

I don't see any errors in the logs, although, the diagnostic utility was running on a Pentium III machine since my Pentium 1 machine is in storage at the moment.

Filename
VooDoo2 Logs.zip
File size
2 KiB
Downloads
37 downloads
File comment
VooDoo2 Logs
File license
Fair use/fair dealing exception

Discord: https://discord.gg/U5dJw7x
Systems from the Compaq Portable 1 to Ryzen 5 2600X
Twitch: https://twitch.tv/retropcuser

Reply 11 of 12, by bjwil1991

User metadata
Rank l33t
Rank
l33t

Sometime this weekend, my plan is to insert it into my Socket 7 system to see if it works or look at the card physically for pins shorting each other out later on today. Also, Windows ME uses the WDM drivers, which had major bugs to begin with, and Windows 98FE isn't my cup of tea (had issues the first day when it was first released in 1998).

Also, funny thing. The card worked in my Athlon 64 setup in Windows 98SE (also underclocked to 75MHz to keep it cooled down using the VooDoo2 Tweaker software) without issues. Is it because of the chipset the VooDoo2 card doesn't like, such as VIA? My Socket 754 has SiS chipsets across the board, my old Socket 7 has Intel chips, and the Socket 370 and a pair of Athlon XP (Socket A(462)) boards also have VIA chips. I have the chipset driver set installed and working correctly in Windows 98SE and did a refresh of the Windows 98SE installation (installing over the files in case they went bad).

Discord: https://discord.gg/U5dJw7x
Systems from the Compaq Portable 1 to Ryzen 5 2600X
Twitch: https://twitch.tv/retropcuser

Reply 12 of 12, by bjwil1991

User metadata
Rank l33t
Rank
l33t

Apparently, the VIA chipsets are the issues (found a forum when I was looking up VooDoo2 and VIA on Google that has a list of chipsets that everyone is having issues with).

Discord: https://discord.gg/U5dJw7x
Systems from the Compaq Portable 1 to Ryzen 5 2600X
Twitch: https://twitch.tv/retropcuser