VOGONS


First post, by ciornyi

User metadata
Rank Member
Rank
Member

Hey folks ,

Long ago i bought geforce 4ti 4200 by asus model V9280/TD/N/128M/A . Back than i tested it and stored card until i decided campare all my ti's . Unfortunately it hasnt posted and it was only one . Later i found some videos on youtube where guys bring to life dead card simply just reflash bios. I decided test my luck and put my asus along with another pci videocard and asus card appears in Device Manager . This make me think it should be lazy repair which save another good card. So does anyone would like to share bios.
PS pictures was taken from https://www.gpuzoo.com/GPU-ASUS/V9280_TD_-_V9280_TD.html

Attachments

  • L_00000364.jpg
    Filename
    L_00000364.jpg
    File size
    148.4 KiB
    Views
    404 views
    File license
    Public domain
  • L_00000365.jpg
    Filename
    L_00000365.jpg
    File size
    139.13 KiB
    Views
    404 views
    File license
    Public domain
Last edited by ciornyi on 2023-12-13, 16:07. Edited 1 time in total.

DOS: 166mmx/16mb/Y719/S3virge
DOS/95: PII333/128mb/AWE64/TNT2M64
Win98: P3_900/256mb/SB live/3dfx V3
Win Me: Athlon 1700+/512mb/Audigy2/Geforce 3Ti200
Win XP: E8600/4096mb/SB X-fi/HD6850

Reply 1 of 4, by danieljm

User metadata
Rank Member
Rank
Member

I believe I have the exact same card as you. See my pics below to confirm, if you like.

I've never used NVFlash before. I am pretty sure I did everything right, but I just felt you should be aware.

Hopefully this works for you.

Filename
V9280.zip
File size
35.05 KiB
Downloads
17 downloads
File license
Public domain

And in case you care, here's a read out of my card's BIOS when I use the "--version" flag in NVFlash.

NVIDIA Firmware Update Utility (Version 5.40)

Adapter: GeForce4 Ti 4200 with AGP8X (10DE,0281,1043,807B) H:N B:01,AGP,D:00,F:00
The display may go *BLANK* on and off for up to 10 seconds during access to
the EEPROM depending on your display adapter and output device.

Reading adapter firmware image...
Image Size : 58368 bytes
Version : 04.28.20.05.00
~CRC32 : D8B2A44E
OEM String : NVidia
Vendor Name : NVidia Corporation
Product Name : NV28 Board
Product Revision : Chip Rev A0
Device Name : GeForce4 Ti 4200 with AGP8X
Vendor ID : 10DE
Device ID : 0281
Subsystem Vendor ID : 1043
Subsystem ID : 807B
Hierarchy ID : None
Sign-On Message : ASUS V9280/TD/N/128M VGA BIOS Version 4.28.20.05.AS19
V9280 Front.JPEG
Filename
V9280 Front.JPEG
File size
761.32 KiB
Views
353 views
File license
Public domain
V9280 back.JPEG
Filename
V9280 back.JPEG
File size
838.28 KiB
Views
353 views
File license
Public domain

Reply 2 of 4, by ciornyi

User metadata
Rank Member
Rank
Member

Thank you kindly ! Unfortunately im unable to do anything with nvflash for dos as it throw me eeprom id unknown all time and refuse to do any manipulations.I will try update from windows .

Attachments

  • 20231213_204047.jpg
    Filename
    20231213_204047.jpg
    File size
    1.73 MiB
    Views
    301 views
    File license
    Fair use/fair dealing exception
  • 20231213_204209.jpg
    Filename
    20231213_204209.jpg
    File size
    1.51 MiB
    Views
    301 views
    File license
    Fair use/fair dealing exception
  • 20231213_204256.jpg
    Filename
    20231213_204256.jpg
    File size
    1.79 MiB
    Views
    301 views
    File license
    Fair use/fair dealing exception

DOS: 166mmx/16mb/Y719/S3virge
DOS/95: PII333/128mb/AWE64/TNT2M64
Win98: P3_900/256mb/SB live/3dfx V3
Win Me: Athlon 1700+/512mb/Audigy2/Geforce 3Ti200
Win XP: E8600/4096mb/SB X-fi/HD6850

Reply 3 of 4, by danieljm

User metadata
Rank Member
Rank
Member

Hmmm, I wonder if the EEPROM is bad, or maybe there's damage to a connected component or trace. There's a YouTuber called vswitchzero who did some work replacing damaged EEPROM chips from some Voodoo 3 cards if I remember correctly. That might not be a bad place to check for ideas on what to do next.

You might also just want to try checking the card with a different version of NVFlash. I needed to try a couple before I found one that wouldn't crash on me, so maybe the software can be a little finnicky. Or maybe try in another motherboard if you have one.

Reply 4 of 4, by ciornyi

User metadata
Rank Member
Rank
Member

Yeah seems like it won't be lazy repair , I have tried 5 or six versions of nvflah starting from ver. 5.13 . I definitely will try it on another board . Also will try update in windows.

DOS: 166mmx/16mb/Y719/S3virge
DOS/95: PII333/128mb/AWE64/TNT2M64
Win98: P3_900/256mb/SB live/3dfx V3
Win Me: Athlon 1700+/512mb/Audigy2/Geforce 3Ti200
Win XP: E8600/4096mb/SB X-fi/HD6850