Helpful thread
https://msfn.org/board/topic/97588-modern-mot … ssion/#comments

I think for A64 you will be best off with a board with a VIA chipset. NForce3 is quirky with anything other than XP. SATA can also complicate matters so ideally stick to PATA. Win98 also has a 128GB limitation. And ≤ 512MB RAM is also ideal. There are patches for these limitations if you feel like getting into that.
Ex https://msfn.org/board/topic/78592-enable48bi … -137gb-barrier/ (have not tried myself)

The only reason I would consider Athlon XP is if you want a board with 3.3v AGP support for pre-4x AGP cards.

Also, note that Voodoo2 needs special drivers to work with Athlon CPUs. Voodoo1 probably won't work.

swaaye wrote:

Also, note that Voodoo2 needs special drivers to work with Athlon CPUs. Voodoo1 probably won't work.

Is this also true with the original Slot A Athlons? That would explain the struggles I went through while trying my Voodoo2 cards on a FIC SD11+A650 setup. As soon as I installed drivers, windows would lock up on boot.

quicknick wrote:

swaaye wrote:

Also, note that Voodoo2 needs special drivers to work with Athlon CPUs. Voodoo1 probably won't work.

Is this also true with the original Slot A Athlons? That would explain the struggles I went through while trying my Voodoo2 cards on a FIC SD11+A650 setup. As soon as I installed drivers, windows would lock up on boot.

I think I first ran into it with a Slot A machine. My guess would be it happens with any K7 CPU and possibly K8 too. I don't remember all the combinations of hardware I've tried Voodoo2 with.

Over here there is a Win9x driver pack for Athlons that works.
http://falconfly.vogonswiki.com/voodoo2.html

This is great, thanks. Never heard of this problem before, will try those drivers next time I feel like playing with the Voodoo(s).