Announcement

Collapse
No announcement yet.

Is there a way to raise a "clinically dead" G400?

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

  • #16
    Yes, there was a previous driver -- it was the same v5.86 but used for a 32Mb G400SH instead. I also did an uninstall from the Add/Remove Programs.

    I put back the G400SH, hit setup.exe and the driver detected G400 and it worked fine. I'm afraid it might be some internal BIOS glitch since I used the floppy rescue disk method a coupla more times but to no luck. Correct me if I'm wrong -- the drivers "look" into the BIOS chip in order to be able to identify the card during installation, yes? Thanks.

    Comment


    • #17
      Ok, try dumping the PINS file ... um, where was that address... ok, http://grafi.ii.pw.edu.pl/gbm/matrox/bios.html ... check what the BIOS value for the card type is (last table on the linked page)... then change the val to that of the G400 and program the BIOS with the new PINS file.

      ProgBIOS: http://grafi.ii.pw.edu.pl/gbm/matrox....html#progbios
      Seth, are you ok? I`m peachy Kate. The world is my oyster. - Seth Gecko

      Comment


      • #18
        Try using diagnostic utility:

        ftp://ftp.matrox.com/pub/mga/utils/t...p/makedisk.zip

        If your card is less than 3 years old and you have the receipt and diagnostic utility reports problems it's time for RMA.

        Comment


        • #19
          HOLY TOLEDO, BATMAN, IT'S ALIVE!

          After some digging around and a few tinkering with progbios.exe, Powerdesk now correctly identifies my G400 and installs without a hitch. Here's how I did it,

          After reading the old thread below,

          "Changing G400 DualHead to G400 MAX through pins"

          You need to change SUBSYS_ID value!
          The MAX SUBSYS_ID is 217d while the G400 standard one is 2179

          Edit your PINS and change SubsystemVendorId from 0x2179102b to 0x217d102b
          Now your board should be recognized as G400MAX!
          From my G400's "mypins.txt", this value somehow got hosed thus I restored it to "0x2179102b". Afterwards, everything ran like a well-oiled machine. Though Matrox Information lists my serial number as, REPAIR00able. A minor nuisance that I'll rectify one of these days.

          I'd like to thank everyone who directly assisted me in this thread (and the others who indirectly helped via the Search function). Ahhhh... life is good.

          Comment

          Working...
          X