BIOS needed for A-Trend BX mobo

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • SteveC
    Super MURCer
    • Aug 1999
    • 3540

    #1

    BIOS needed for A-Trend BX mobo

    Hi all,

    One in a million chance, but anyone got the last BIOS for A-trend's 6220 (rev 2) motherboard? Atrend's site (www.atrend.com.tw) no longer seems to exist (have they gone bust?)

    A ping or traceroute gives "Source quench received."
  • Greebe
    Super MURCer
    • Aug 1999
    • 8555

    #2
    Will either of these work Steve?

    "Be who you are and say what you feel, because those who mind don't matter, and those who matter don't mind." -- Dr. Seuss

    "Always do good. It will gratify some and astonish the rest." ~Mark Twain

    Comment

    • SteveC
      Super MURCer
      • Aug 1999
      • 3540

      #3
      Thanks Mike! I honestly thought I'd not get a response!

      Trying now - wish me luck

      Comment

      • SteveC
        Super MURCer
        • Aug 1999
        • 3540

        #4
        Hurrah! I panicked for a few seconds when awdflash told me that the BIOS wasn't the right one, but I said do it anyway, and it worked a treat. (I needed a PIII to work in it)

        Comment

        • RichL
          Restored Super MURCer
          • Apr 2003
          • 1348

          #5
          Re: BIOS needed for A-Trend BX mobo

          Originally posted by SteveC

          A ping or traceroute gives "Source quench received."
          It means the server is either too damn busy to respond to such trivial things as an ICMP echo request or has had a threshold set above which it refuses to reply to a ping.

          Bloody annoying when trying to troubleshoot connection issues on the HP servers at work and they stop responding after a few seconds of intensive Pinging..
          Athlon XP-64/3200, 1gb PC3200, 512mb Radeon X1950Pro AGP, Dell 2005fwp, Logitech G5, IBM model M.

          Comment

          • SteveC
            Super MURCer
            • Aug 1999
            • 3540

            #6
            It's been doing that for the last few days though, at any time of the day.

            I think a router's buggered.

            Comment

            Working...