The Voodoo 3/4/5 Win2k problem...

[Val_Parthen]

I have a question regarding the problem of the topic. As we know, any driver set that isn't Chrisilla/Askii64's set doesn't seem to run MilkDrop in Windows 2000.

What d3d call (be it missing or included) would cause the "not enough memory" error that it gives?

The driver that Chrisilla used for that set came from Windows update, so I believe it's from before the 1.04.00 driver set for Win2k (which supposedly had some DirectX 8 things added/hacked into it). If the DirectX 8 additions are what's causing it, then we have a starting point as to getting them fixed.

For those of you with v3/4/5's, I HIGHLY recommend that you hit up the x3dfx community (http://pub43.ezboard.com/bx3dfx) OR the 3dhq forums (http://3dhq.mine.nu:81/forums/). Both are hardcore 3dfx groups, and the 3dhq group is working on an ACTUAL new driver release. It's a promising project. I'm going to see if they can get milkdrop to run with their 1.09 set.

Thanks!

[Rovastar]

I don't know what D3D call is causing the problem for the Voodoo cards but what I do not understand from the driver people is what they removed/amended/updated/wrecked from the original Microsoft drivers so that no other versions work with MilkDrop?

Also MD uses the DX7 command set from what I understand so the new DirectX 8 features are not really relevant. (Ryan only started using DX* programming in the last 3 months :eek:)

I was posting on the 3dfx underground forums (have since changed there name I think) but they decided to wipe out all the threads that hadn't been posted in for 10 days. So all the info was lost.

FFS how stupid is that?

I am trying to help from the product side of things but they seemed not to care and they did not seem to care about D3D support for their drivers (I thought one of the most respected ones) until a few versions later.

Anyway because of all this I am reluctant to register at another forum again to help people out who use a moribund graphics card.

[Val_Parthen]

Yeah, 3dfx-U is now 3dhq. They didn't wipe out everything, they had a computer problem, from what I understand.

Their main concentration is on OpenGL for the driver set, at the moment, and since there really aren't that many people working with them, it doesn't surprise me that they're not working with d3d at the moment. Although, I have read in Aquoues' update logs that some d3d things have been worked on... They're being tightlipped overall, so it's hard to know for sure.

Also, Microsoft didn't make the "original" drivers. The drivers from 3dfx with the 1.03.00 D3D file (I /think/... I haven't heard back from Chriszilla on which one he used) are the ones that work. they updated (to the 1.04 set) the drivers to DirectX 8, and since MD uses dx7, they must have changed the way something is handled.

That, or however Ryan is programming somehow reads the card/drivers wrong? I don't know. I /do/ know that there shouldn't be a problem, though. :)

[AlejandroNOVA]

I've made two little discoveries after messing up with 3dfx drivers: the first is that you cannot uninstall the 3dhq drivers without messing up your computer, and the second is: ALL THE PARTS ARE INTERCHANGEABLE.

So, if you want to run MilkDrop under Win2K, you can either install Chrizilla/Askii64's set, or you can REPLACE THE D3D PART WITH THE ONE THAT WORKS WITH MILKDROP. This part is no other than the D3D part of the Microsoft original 3dfx driver.

Download this little zip and install it, following the instructions inside it.

AND ENJOY MILKDROP!!!!

The zip file is splitted in three parts. I had to upload them with "ZIP" extension due to forum limitations, but it is a RAR self-extracting file. The real filenames are:

PART 1. ESCRITORIO.PART1.EXE
PART 2. ESCRITORIO.PART2.RAR
PART 3. ESCRITORIO.PART3.RAR

Here goes PART.1

[AlejandroNOVA]

PART 2
ESCRITORIO.PART2.RAR

[AlejandroNOVA]

PART 3
ESCRITORIO.PART3.RAR