Postman5 wrote on 2025-07-08, 11:34:I watched the video without sound and didn't realize that different programs were being compared. I thought it was a random clip that got into the video.
Unfortunately, i get this error while trying to flash the bios
rcarkk wrote on 2025-07-08, 22:30:Postman5 wrote on 2025-07-08, 11:34:I watched the video without sound and didn't realize that different programs were being compared. I thought it was a random clip that got into the video.
Unfortunately, i get this error while trying to flash the bios
I could be wrong, but those flash IDs reported suggest that the flash chip might be faulty.
darry wrote on 2025-07-09, 03:26:rcarkk wrote on 2025-07-08, 22:30:Postman5 wrote on 2025-07-08, 11:34:I watched the video without sound and didn't realize that different programs were being compared. I thought it was a random clip that got into the video.
Unfortunately, i get this error while trying to flash the bios
I could be wrong, but those flash IDs reported suggest that the flash chip might be faulty.
That or the 3dfx flash program is seeing the S3 PCI card that i´m using, instead of the banshee. Already tried 3 diferent PCI slots. Same error.
Important to note that both cards are recognized in windows, and voodoo banshee is recognized on some system detection dos tools.
rcarkk wrote on 2025-07-09, 10:49:darry wrote on 2025-07-09, 03:26:rcarkk wrote on 2025-07-08, 22:30:Unfortunately, i get this error while trying to flash the bios
I could be wrong, but those flash IDs reported suggest that the flash chip might be faulty.
That or the 3dfx flash program is seeing the S3 PCI card that i´m using, instead of the banshee. Already tried 3 diferent PCI slots. Same error.
Important to note that both cards are recognized in windows, and voodoo banshee is recognized on some system detection dos tools.
There are other versions of the 3dfx flash utility. No idea if they are model specific or not, but maybe a newer one
(higher version number) would give different results.
https://youtu.be/H2rIfqd_-rg?si=czEoFDump_gqo2Zo&t=1045
This guy had the same issue on a voodoo 3, but was able to solve it changing the card from PCI slots
darry wrote on 2025-07-09, 10:53:rcarkk wrote on 2025-07-09, 10:49:darry wrote on 2025-07-09, 03:26:I could be wrong, but those flash IDs reported suggest that the flash chip might be faulty.
That or the 3dfx flash program is seeing the S3 PCI card that i´m using, instead of the banshee. Already tried 3 diferent PCI slots. Same error.
Important to note that both cards are recognized in windows, and voodoo banshee is recognized on some system detection dos tools.There are other versions of the 3dfx flash utility. No idea if they are model specific or not, but maybe a newer one
(higher version number) would give different results.
Yes, will try today, that´s for sure. I guess i can only use the 1.xx versions for the banshee, right?
To check that Flash.exe ver.1.04 can work with AT29C010A I flashed sm512.rom in Asus Banshee V3200/8M with RAM VG4616321AQ and ROM AT29C010A. I was surprised that BIOS Winfast S310 correctly identified the memory size of 8MB and the Asus V3200/8M card works fine.
Postman5 wrote on 2025-07-09, 13:43:To check that Flash.exe ver.1.04 can work with AT29C010A I flashed sm512.rom in Asus Banshee V3200/8M with RAM VG4616321AQ and ROM AT29C010A. I was surprised that BIOS Winfast S310 correctly identified the memory size of 8MB and the Asus V3200/8M card works fine.
I think the problem is the S3 PCI card being the one who is being detected by 3dfx flash 1.04. Or a faulty eeprom. I will have to try this on another system, to see if the 3dfx flash detects the banshee eeprom.
3dfx flash does not work with S3 cards. You can check this by removing Banshee from the motherboard, leaving only the S3 card. I think you need to check the supply voltage, the contacts in the ROM socket, the integrity of the PCB tracks and resistors connecting the ROM and the GPU.
Postman5 wrote on 2025-07-09, 13:58:3dfx flash does not work with S3 cards. You can check this by removing Banshee from the motherboard, leaving only the S3 card. I think you need to check the supply voltage, the contacts in the ROM socket, the integrity of the PCB tracks and resistors connecting the ROM and the GPU.
Resistors are all fine. Measured them. The C24 cap near the regulator showed 3.42v. I saw the legs of the vbios socket. They seem fine and well soldered. The ROM socket seems to be fine after removing the eeprom.
Regarding PCB tracks, i have inspected them and applied some solder on some that were scratched, just to make sure there is continuity.
I know that 3dfx flash doesn´t support S3 cards. I linked a video, were he tries to flash a voodoo 3, and same error appears. Seems that the program was not seeing the banshee or seeing the S3 instead. He did a rom dump, and the S3 bios was the one that was downloaded.
He then changed the PCI slot, and the 3dfx flash successfuly flashed the V3.
Tried a diferent system. No avail. Same error trying to flash. I think there is something wrong with the eeprom or somewere in the card.
Still seems odd that they bothered to create two distinct versions, and again by adding the warning to the off-site ftp mirror directory index for the S310 - https://web.archive.org/web/19991125133539/ht … 310/00index.txt
PC Hoarder Patrol wrote on 2025-07-10, 11:27:Still seems odd that they bothered to create two distinct versions, and again by adding the warning to the off-site ftp mirror directory index for the S310 - https://web.archive.org/web/19991125133539/ht … 310/00index.txt
I agree with you. Maybe due to more tight timmings in one version compared to the other. I did tried a reference AGP SGRAM vbios, but same error. I guess i need to inspect the card a little more.
Is there any software to force flash the vbios on another card, for example an nvidia TNT? I could always remove the eeprom, install on another nvidia card with same socket and eeprom compatibility, but i guess i can damage the card, that way, right?
It would be very good to carefully read the contents of the ROM AT29C010A and save it to a file. The best way to do this is with a programmer. Maybe you know someone, a neighbor on the street for example, who has a programmer?
Or postpone the repair until you buy a programmer MiniPro TL-866 . They are not expensive at all, but they make you feel like a master, they give you confidence, power and strength in relation to computer hardware:)
Postman5 wrote on 2025-07-10, 18:01:It would be very good to carefully read the contents of the ROM AT29C010A and save it to a file. The best way to do this is with a programmer. Maybe you know someone, a neighbor on the street for example, who has a programmer?
Or postpone the repair until you buy a programmer MiniPro TL-866 . They are not expensive at all, but they make you feel like a master, they give you confidence, power and strength in relation to computer hardware:)
I never thought on buying a programmer. I need one. Do you have any specific model you can recomend? I saw lots of variations of that one.
I use an outdated TL-866CS. Its support by the manufacturer has stopped, but its capabilities are completely sufficient for me. Now on sale there is a newer version of XGecu T48 (TL866II Plus). You will also need an adapter "PLCC32 to DIP32" and perhaps others, if you need them. I made for myself an adapter "SOP4_28pin to DIP28" for checking logic chips, the programmer can do this too.
Postman5 wrote on 2025-07-11, 13:41:I use an outdated TL-866CS. Its support by the manufacturer has stopped, but its capabilities are completely sufficient for me. Now on sale there is a newer version of XGecu T48 (TL866II Plus). You will also need an adapter "PLCC32 to DIP32" and perhaps others, if you need them. I made for myself an adapter "SOP4_28pin to DIP28" for checking logic chips, the programmer can do this too.
Excelent. I really need to dig about this and choose the programmer i need.
