DAYTONA PCI IBM MOD @32Mb PROJECT.

This project is based on 2 MODS. One IBM V4-2 4200 PCI 16Mb DDR will be modified with 64Bits memory and the other with 128Bits memory. Both cards will be upgraded to @32Mb DDR.

[03/02/2014]
Here Gino's card. It will be mod with extra 16Mb DDR 64 Bits.



DDR memory 64Bits ready for soldering.


04/03/2013

Bios mod done and card shows 32Mb DDR once added extra ram.



Card still shows artifacts.


10/03/2014

I still having problems- trying differents settings via hack bios my card is 'dead'. Not really dead since PCI.exe detects it but seems I used a bad parameter for hacking bios and once in the flash process it failed. I have tried to flash back my card with original bios but flash utility shows a message is not possible since card is detected as  unknown card.

PCI.EXE detects it as:



In the right top left where FF is present there must have 1A / 12 / 0X but SW does not let me to change it manually.

I have tired to reset the chip bios but not way either.

So wahat I decided, I always wanted to do it, is to add a socket bios:



I used a programmer SW tool for flashing the chip with original bios but not way either. Card not wake up.

My question is if VSA-101 has small rom in the die chip with info about ID VENDOR from the card. How is possible once added a new chip PLCC with original bios card continue without boot up. Seems as I changed something related ID VENDOR card.

Today my tests.


11/03/2014

I found the problem and I fixed it. Seems hacking the bios with an HEX I modified some id string ans flash utiliy detected the Card as a Voodoo but bios is Naplam/Napalm2. Across the PCI.EXE modified some parameters taking as reference the other Daytona (Not all the values can be changed) but it was enough for flashing tool detects again as a NAPALM/NAPALM2. My error was the first time I used a V5 as reference thinking it was a Napalmd2.



Finally with a new hack biios the card works perfect.

BOOTING UP


IN BIOS


HERE SOME MS-DOS TESTS BASED IN DIFFERENT VGA MODE 




Now I need to test both DAYTONAS in Win98SE but at the moment seems all is correct and not glitches.

14/03/2014

Installed Win98SE with reference driver using a KT333 elitegroup motherboard.

Not artifacts in 2D mode. Info driver detects correctly the card with 32Mb.


In 3DMode there are not artifacts either but in OpenGL (Quake3) card locks up and in 3DMark2001SE I got a black screen in first test.



I think the problem is based on drivers. I need more testing.

19/03/2014


I found the problem why card freezes and downclock speed @143MHz and now is very stable.

Quake 3 1024x768


3DMark2000 1024x768 16Bits



I found dirver is not optimized for Daytona cards. 3DMark2000 has glitches if depth color is set to 32Bit, 16Bits is perfect. 3DMark2001SE has artifacts and only work more or less well with depth color 16Bits.

Today I will do some comparative between both daytonas and different memory size.

Regards,
Oscar.

ultima wrote on 05.02.14 at 07:48:36:


Yes, I will do different test before and later of the rework

Just little of delay here  with a problem of  different brand memory and waiting to fix it.

Regards,
Oscar.

Great Projekt Osckhar, as always

I thought Daytona only supported 64bit DDR?

Loeschzwerg wrote on 07.02.14 at 07:19:36:


True, but we all know the "facts"  about the 3DFX hardware can be not 100% true..used to be fact that a vsa-100 supported max 64MB per.chip....so....never hurts to try ofcourse

Beside all the reports back in 2000 it is very unlikely the VSA-101 does have a 128Bit DDR memory interface. The performance of the architecture itself wasn't competitive anymore back in the days and it would've made the DIE too expensive for what it was meant. Transistorcount and DIE size needs to stay very low for low-end market segment.
Also 3dfx didn't have the ressources to waste on a "complexe" VSA-101, Rampage was the way to go

But you can surely give it a shot.

Great work as usual Oscar!

Thanks Gary and Radu!

I am having problems. First post updated.

Regards,
Oscar.