Hi!...
Thx to everybody for all the post.
Reading them I really feels the possibility to have a new driver for Voodoo Banshees, but this need a real team...
The question is: who wants to help to make it real?  :D

Again, thx to everybody and long life to the Banshees... :)

already i'm testing new driver with hex hack but if you want we can put together my experience with x-mojomotion 1.0 and your bansheexp to make the best driver...for me it may be a good thing! But we must however have phoenix in team because he know very well hex hacking !

Hi mojomotion!... :D
You're totally right, together we can do it, welcome!

You have a HEX hacked version too? ;)... OK, please, check this out and tell me if you have some different.


Quote:

Raziel64's Voodoo 3 Drivers for Banshee. Based on V3 1.07.00b Win9x drivers, and hacked with PHOENIX specs. Thx dude! Status: - Installation -> OK - D3D, Glide and OpenGL accelerations -> Buggy: perfectly playable w/o crashes and all capabilities are correctly reported but some screens areas are black (2nd TMU calls issue). Log: - 3dfxdrv.ini: replaced DEV_0005 with DEV_0003 - voodoo3.inf: added %DeviceDesc%=?Driver.Install,PCI\VEN_121A&DEV_0003. Deleted the other entries, the 3dfx tools related lines and changed some installation fields. - 3dfx16v3.drv: replaced HEX value 1A A2 05 00  with  1A 12 03 00 (all ocurrencies). - 3dfxv3.vxd: replaced HEX value 1A A2 05 00  with  1A 12 03 00 (all ocurrencies). - 3dfx32v3.dll: replaced HEX value 5F FA 1E 00  with  4F 1A 00 00. Then replaced HEX 03 00 (Maximum Textures Blending Stages) with HEX 02 00. Then replaced HEX 02 00 (Textures in Single Pass) with HEX 01 00. And finally, replaced HEX 02 00 08 00 (Maximum Texture Coordinates) with  HEX 01 00 08 00 (all ocurrencies). - replaced glide2x/3x with Colourless glide files (last version). 29/0703. Raziel64.

Thx.

A team ? Good idea !

I will join your Banshee Team ;D

wrote on 29.07.03 at 19:26:23:

Hi mojomotion!... :D You're totally right, together we can do it, welcome! You have a HEX hacked version too? ;)... OK, please, check this out and tell me if you have some different. Thx.

yes i've used the guide of phoenix on 3dfxzone board ;)  

@ Raziel64

I just paid attention to your quote and discovered an error : you replaced all occurrences of HEX 02000800, OH NO !!!

You should only replace following HEX strings, because I don't exactly know what other HEX strings stand for.

Voodoo3 Win9x drivers release 1.04.00
In 3dfx32v3.dll you must search for HEX string
5F FA 1E 00 66 C7 85 00 FF FF FF 03 00 66 C7 85 02 FF FF FF 02 00 C7 85 F8 FE FF FF 02 00 08 00
Once found, replace it with
4F 1A 00 00 66 C7 85 00 FF FF FF 02 00 66 C7 85 02 FF FF FF 01 00 C7 85 F8 FE FF FF 01 00 08 00

Texture operations : 0x001EFA5F for Voodoo3, 0x00001A4F for Banshee
Maximum Textures Blending Stages : 0x0003 for Voodoo3, 0x0002 for Banshee
Textures In Single Pass :  0x0002 for Voodoo3, 0x0001 for Banshee
Maximum Texture Coordinates : 0x0002 for Voodoo3, 0x0001 for Banshee

Voodoo3 Win9x drivers release 1.07.00-beta
In 3dfx32v3.dll you must search for HEX string
5F FA 1E 00 66 C7 42 50 03 00 EB 0B C7 42 4C FF FF 1E 00 66 89 4A 50 66 89 4A 52 C7 42 48 02 00 08 00
Once found, replace it with
4F 1A 00 00 66 C7 42 50 02 00 EB 0B C7 42 4C FF FF 1E 00 66 89 4A 50 66 89 4A 52 C7 42 48 01 00 08 00

Note that these drivers autodetect number of Textures in Single Pass !

Regards

Thx PHOENIX...

It's corrected now... ;)
Later I'll post the files...

Cya.

I have banshee in my old computer. So if you need betatester: I could do some betatesting under win 9x/me...

Of course that you're welcome here, 74p54... :)

I think that will be really great new in the forum this week... ;), keep alert, ok?.

Raziel64, I could do some testing aswell if you need it.

Here's what I would like fixed for XP

Windows XP Banshee Problems

Pete Bernert's OpenGL PSX plugins won't run in a window (trying to do so results in a crash). This bug includes both Zinc and his PsemuPro compatible plugin.

The most annoying bug: More likely than not a core problem that causes crashes if game resolution and color depth matches the desktops resolution and color depth.

EP

wrote on 30.07.03 at 17:29:06:

@ Raziel64 I just paid attention to your quote and discovered an error : you replaced all occurrences of HEX 02000800, OH NO !!! You should only replace following HEX strings, because I don't exactly know what other HEX strings stand for. Voodoo3 Win9x drivers release 1.04.00 In 3dfx32v3.dll you must search for HEX string 5F FA 1E 00 66 C7 85 00 FF FF FF 03 00 66 C7 85 02 FF FF FF 02 00 C7 85 F8 FE FF FF 02 00 08 00 Once found, replace it with 4F 1A 00 00 66 C7 85 00 FF FF FF 02 00 66 C7 85 02 FF FF FF 01 00 C7 85 F8 FE FF FF 01 00 08 00 Texture operations : 0x001EFA5F for Voodoo3, 0x00001A4F for Banshee Maximum Textures Blending Stages : 0x0003 for Voodoo3, 0x0002 for Banshee Textures In Single Pass :  0x0002 for Voodoo3, 0x0001 for Banshee Maximum Texture Coordinates : 0x0002 for Voodoo3, 0x0001 for Banshee Voodoo3 Win9x drivers release 1.07.00-beta In 3dfx32v3.dll you must search for HEX string 5F FA 1E 00 66 C7 42 50 03 00 EB 0B C7 42 4C FF FF 1E 00 66 89 4A 50 66 89 4A 52 C7 42 48 02 00 08 00 Once found, replace it with 4F 1A 00 00 66 C7 42 50 02 00 EB 0B C7 42 4C FF FF 1E 00 66 89 4A 50 66 89 4A 52 C7 42 48 01 00 08 00 Note that these drivers autodetect number of Textures in Single Pass ! Regards

ok now it's all clear! ;)

Hm, looks like things are progressing for you guys :)

One important suggestion from me, though :

When using HEX-Edits (if you ever release a Driver set), make sure those are transparent.

e.g. Include their exact purpose, locations and details in the Readme.

Due to some pretty bad examples in the past, Users will naturally be extremely critical towards Hex-Edit's  ::)

So it's probably a good Idea to either include or Link to example/demonstration Programs where the Effects of the contained Tweaks/Changes can be clearly seen and verified as working & functional.

Otherwise, it'll be painfully difficult or impossible to build the required level of credibility...

After all, lots of people had claimed to 'make new Drivers' in the past, hyping & advertising them all over...
...but in the End, out of the many not even a handfull of people turned out to be actually capable and honest :-/

Ok...

Only for testing purposes... :).
Note (not for team members):these files are for testing purposes only, with perfectly knowed limitations and issues. Use at your own risk.


Quote:

Raziel64's Voodoo 3 Drivers for Banshee. Based on V3 1.04.00 Win9x_Me drivers, and hacked with PHOENIX specs. Thx dude! Status: - Installation -> OK - D3D, Glide and OpenGL accelerations -> Buggy: perfectly playable w/o crashes and all capabilities are correctly reported but some screens areas are black (2nd TMU calls issue). Log: - 3dfxdrv.ini: replaced DEV_0005 with DEV_0003 - voodoo3.inf: added %DeviceDesc%=?Driver.Install,PCI\VEN_121A&DEV_0003. Deleted the other entries, the 3dfx tools related lines and changes some installation fields. - 3dfx16v3.drv: Initial purpose: to replace HEX value 1A A2 05 00  with  1A 12 03 00. Then: no ocurrences founded. - 3dfxv3.vxd: replaced HEX value 1A A2 05 00  with  1A 12 03 00 (all ocurrencies). - 3dfx32v3.dll: replaced HEX value 5F FA 1E 00 66 C7 85 00 FF FF FF 03 00 66 C7 85 02 FF FF FF 02 00 C7 85 F8 FE FF FF 02 00 08 00 with     HEX value 4F 1A 00 00 66 C7 85 00 FF FF FF 02 00 66 C7 85 02 FF FF FF 01 00 C7 85 F8 FE FF FF 01 00 08 00. Explanation:            - Texture operations : 0x001EFA5F for Voodoo3, 0x00001A4F for Banshee            - Maximum Textures Blending Stages : 0x0003 for Voodoo3, 0x0002 for Banshee            - Textures In Single Pass :  0x0002 for Voodoo3, 0x0001 for Banshee            - Maximum Texture Coordinates : 0x0002 for Voodoo3, 0x0001 for Banshee - replaced glide2x/3x with Colourless glide files (last version). - replaced the 3dfxOGL.dll file w/ the Metabyte RTCW openglv3.dll file. 30/0703. Raziel64.

http://www.iespana.es/bansheexp/v3vb_1.04.00.uha

How to extract: use WinUha. [url=www.winuha.com[/url]]www.winuha.com[/url]

Quote:

Raziel64's Voodoo 3 Drivers for Banshee. Based on V3 1.07.00b Win9x_Me drivers, and hacked with PHOENIX specs. Thx dude! Status: - Installation -> OK - D3D, Glide and OpenGL accelerations -> Buggy: perfectly playable w/o crashes and all capabilities are correctly reported but some screens areas are black (2nd TMU calls issue). Log: - 3dfxdrv.ini: replaced DEV_0005 with DEV_0003 - voodoo3.inf: added %DeviceDesc%=?Driver.Install,PCI\VEN_121A&DEV_0003. Deleted the other entries, the 3dfx tools related lines and changes some installation fields. - 3dfx16v3.drv: replaced HEX value 1A 12 05 00  with  1A 12 03 00 (all ocurrencies). - 3dfxv3.vxd: replaced HEX value 1A 12 05 00  with  1A 12 03 00 (all ocurrencies). - 3dfx32v3.dll: replaced HEX value 5F FA 1E 00 66 C7 42 50 03 00 EB 0B C7 42 4C FF FF 1E 00 66 89 4A 50 66 89 4A 52 C7 42 48 02 00 08 00 with     HEX value 4F 1A 00 00 66 C7 42 50 02 00 EB 0B C7 42 4C FF FF 1E 00 66 89 4A 50 66 89 4A 52 C7 42 48 01 00 08 00. Explanation:   - Texture operations : 0x001EFA5F for Voodoo3, 0x00001A4F for Banshee   - Maximum Textures Blending Stages : 0x0003 for Voodoo3, 0x0002 for Banshee   - Textures In Single Pass :  0x0002 for Voodoo3, 0x0001 for Banshee   - Maximum Texture Coordinates : 0x0002 for Voodoo3, 0x0001 for Banshee - replaced glide2x/3x with Colourless glide files (last version). - replaced the 3dfxOGL.dll file w/ the Metabyte RTCW openglv3.dll file. 30/0703. Raziel64.

http://www.iespana.es/bansheexp/v3vb_1.07.00b.uha

Raziel, the driver seems don't go! :o

My betatester said:

Windows start and work well and also 3d app but the fillrate is the same of a normale banshee drv!

Of course ! Your betatester is right !

My 3dfx32v3.dll patch aims to turn off driver calls to 2nd TMU, because Voodoo3 is a Banshee with 2nd TMU.

If you want to test ~200 MTexels/s Multi-Texturing Fill-Rate, you need to use the original, not patched 3dfx32v3.dll file.

Regards

ok phoenix! ;D

p.s Now it's possible to use Geometry assist?? :D

Keep up the good work, I'm even starting to salivate at the thought of NEW I repeat NEW Banshee drivers!!

:) :D ;D :D :)

wrote on 02.08.03 at 11:08:16:

Of course ! Your betatester is right ! If you want to test ~200 MTexels/s Multi-Texturing Fill-Rate, you need to use the original, not patched 3dfx32v3.dll file. Regards

i must use original 3dfx16v3.drv and 3dfxv3.vxd too??

@ galah

Welcome !

@ mojomotion

Relax ! You must use original file 3dfx32v3.dll with patched files 3dfx16v3.drv and 3dfxv3.vxd.

Well, I'm trying to patch V3 drivers so that they work 100% on Banshee. But it's a hard work and I am only an advanced user.

A reliable way to use V3 drivers is to patch only 3dfx16v3.drv (needed for other versions than 1.00.00 to 1.04.00) and 3dfxv3.vxd. You replace HEX 1A120500 with HEX 1A120300. By doing so, you change only PCI DeviceID, nothing else.

Is it so amazing that Avenger (aka Voodoo3) drivers work on Banshee ? No !

Voodoo3 databook page 11


Quote:

2.2.8 Software • Full BIOS and driver compatibility with Voodoo Banshee for a mature, robust solution

Regards

NOW with 3dfx16v3.drv  and 3dfxv3.vxd  patched my tester got 200mgtx :D ;D

But it has a lot of sys crash and some games screens become black :-/

We must resolve that!

Do I have to learn to program the c? ;D
The actual language i know is pascal but i don't know how to program .dll or graphic!!
But the next year i'll begin study c++ in elettronic application because i'm studing in eletronic institute ;)! But until nxt year i can't give an help to develop v3-vb driver! i can help you only in hex hack or inf editing!

Interesting text:

SSTH3_GEOMETRY_ASSIST

Functionality      Value      Comment
Disable      0      Driver T&L disabled.
Enabled (Dev)      1      Reference C code T&L. Only for Development use.
Enabled (User)      2      Optimised assembler T&L.


has someone tried the C code T&L??