I wanna demonstrate you that Banshee hardware is very close (identical ?) to Voodoo3 hardware.

Website: http://homepage.swissonline.ch/tinyasm/v3.htm
Theme  : V3  programming voodoo 3 (aka avenger) in DOS with assembly
Author : daniel_hagmann@swissonline.ch

First steps
-----------
1. Download file v3.zip
2. Unzip it in a directory

How to patch
------------
You need a hex editor

1. Open v3.exe with hex editor
2. Find and replace HEX 66B9050066BA1A12 with HEX 66B9030066BA1A12
3. Save changes

Do the same for v33.exe and v3rot.exe

N.B.
121A (HEX 1A12) is PCI VendorID for 3dfx Interactive
0003 (HEX 0300) is PCI DeviceID for 3dfx Banshee
0005 (HEX 0500) is PCI DeviceID for 3dfx Avenger (aka Voodoo3)

Test it yourself
----------------
All three executables work under DOS with your Banshee. Under DOS environment, there are no API calls, only direct hardware commands...

Well, I am sure that Voodoo3 is a Banshee with second TMU. I wonder if Banshee has got 2 TMUs, because Banshee has got Voodoo2 core and V2 has got 2 TMUs (Bruce and Chuck). In the BIOS SETUP from Mainboard you can disable L2 cache. Diagnostic program will report no L2 cache, although it is physically present...

OK, PHOENIX...

I believe that it's time to unify efforts then...
Thx for all the info... :)

This is also interesting


Quote:

** *****************  Version 32  ***************** ** User: Andrew       Date: 3/10/99    Time: 4:30p ** Updated in $/devel/h3/Win95/dx/minivdd ** Changed so that Banshee VDD will not work on Avenger and visa versa

Source: C:\3DFX\H5\WIN9X\DX\MINIVDD\DEVTABLE.C (from 3dfx source code)

3dfx/STB was the dark side of 3Dfx Interactive, Inc. >:(

Regards

I saw same topic in x-3dfx forum. Maybe there is something new:

So Voodoo3, is a Voodoo Banshee?.
http://pub43.ezboard.com/fx3dfxfrm1.showMessage?topicID=15491.topic

:D

No problem ! My ego doesn't suffer ;D