Announcement

Collapse
No announcement yet.

BIOS fixed, now stuck in 16 color, 640X480

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • BIOS fixed, now stuck in 16 color, 640X480

    Thanks to Hunsow having current PINs files posted on his page, I got my folks G400 DH fixed and mailed back to them, flashing it to the current BIOS release (1.6-??) in the process. Booted it up in my machine, everything worked fine. So, I express mailed it back to them (very carefully packaged), Dad put it back in the system and... As soon as Win loads, it gives that damn error message - "There is a problem with your Display Adaptor, it does not support your current settings...".
    Now, I have had this happen before with my G200 when doing a fresh install or completely removing all PD settings / files, then reinstalling PD. Basically, 16color, 640 is below it's recognized settings, so I just set it to 16bit color, reboot, and everything is fine, I can then set the resolution as high as I like. This is the first thing I tried with Dad, no dice. So, I thought maybe there was a "conflict" between the new G400 BIOS and the timings in System BIOS. Had him go in and reduce the timings for the AGP bus (Master 1WS read, etc). AGP 4X would never work on this board, so it has always been disabled, along with Fast Write support (of course). Still no dice. This is driving me nuts cuz I don't know what happend and cuz I'm having to try and walk Dad through troubleshooting it over the phone. I know it's not the card since it worked fine in my system and I'm pretty sure it's not otherwise hardware related, seems as though Win has gotten confused somehow. Anyone able to help?

    Affected system: Abit KA7 (beta BIOS ry.b01), K7 750 (@750 for the time being), 128MB Mushkin RAM, G400 DH vanilla (BIOS 1.6, PD 5.52, non-OCed, 4X capable). Using Via GART 4.03 and Inf update 1.02.

    ------------------
    "I wrestled with reality for 27 years and I'm happy to say I finally won out over it."
    "I wrestled with reality for 27 years and I'm happy to say I finally won out over it."

  • #2
    Normally thats a screwed up driver or a conflict. Try checking in safe mode to see if you haven't got two G400's listed.
    Chief Lemon Buyer no more Linux sucks but not as much
    Weather nut and sad git.

    My Weather Page

    Comment


    • #3
      Ehh, sorry, should have mentioned that was another thing we tried. Booted in safe mode, removed the driver (only one listed), and reinstalled. Next up gonna try removing all listings in the registry (for the card, software, and AGP bridge) and see what it does. Hoping to find a simple answer that I am overlooking though.

      ------------------
      "I wrestled with reality for 27 years and I'm happy to say I finally won out over it."
      "I wrestled with reality for 27 years and I'm happy to say I finally won out over it."

      Comment


      • #4
        I presume you've used the matrox uninstaller to remove the drivers.
        Chief Lemon Buyer no more Linux sucks but not as much
        Weather nut and sad git.

        My Weather Page

        Comment


        • #5
          I might as well add that it maybe worth re-flashing your bios in case thats got stuffed again.
          Chief Lemon Buyer no more Linux sucks but not as much
          Weather nut and sad git.

          My Weather Page

          Comment


          • #6
            Please check the card with MXINFO utility from my website. This may detect the problem.

            Comment

            Working...
            X