Announcement

Collapse
No announcement yet.

Marvel G200 resource conflicts hanging powerdesk

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

  • Marvel G200 resource conflicts hanging powerdesk

    My system:

    FIC VA503+ motherboard, Award BIOS, all patches installed.
    AMD K6-2 300 Mhz processor
    96 Mb EDO RAM
    Maxtor 91728D8 17.2 Gb hard drive,
    UDMA Mode 2 Master, IDE 1
    Goldstar CRD8160B CDROM, Slave, IDE 1
    SAF CDRW 4424A CDROM, Master, IDE 2
    Media Vision Pro Audio 16 Basic ISA Legasy Sound card
    Matrox Marvel G200 AGP Display Adapter
    Matrox Powerdesk ver. 5.41
    Matrox Video Tools ver. 1.52e
    Windows 95 B

    My Problem:

    System has been working fine for a year with no conflicts or problems. Installed Powerdesk 5.41, Video Tools 1.52e, DirectX 7.0, and DX Media 6.0 in January with no problems.

    Friday, 4-14-00 I was attempting to record video through PC-VCR from a camcorder as I had a dozen or more times previously. During the attempt, I lost control over PC-VCR audio levels. No adjustments to any audio controls had any effect.

    Investigated in Control Panel and found memory resource conflicts under Display Adapter properties where none had existed before. Could not alter any of the memory resource settings. Finally I attempted to re-install Windows. During installation, I selected "Standard VGA Adapter (VGA)". After installation, in Device Manager, display adapter showed conflicting device:
    "PCI Standard PCI to PCI Bridge".
    Conflicting memory ranges:
    A8000000 - A8FFFFFF
    D8000000 - D8003FFF
    D9000000 - D97FFFFF
    I was able to change the memory settings so no conflict appears, but when I try to run Powerdesk setup, system hangs on restart.

    On second attempt, I left conflicts unresolved, and installed DirectX 7.0. Ran Powerdesk setup successfully, but conflicting device persisted. Reinstalled Video Tools but program hanged system. Attempted to change settings for Display adapter in Control Panel to eliminate conflicts:

    Changed:
    A8000000 - A8FFFFFF
    to:
    D0000000 - D7FFFFFF
    changed:
    D8000000 - D8003FFF
    to:
    A0000000 - A7FFFFFF

    Created a New Conflict:

    "System Board Extension for PNP BIOS"
    00000000 - 00FFFFFF
    00000000 - 00003FFF
    00000000 - 007FFFFF
    Settings could not be modified in device manager under device name.

    Attempting to change memory range of G200
    From:
    00000000 - 00FFFFFF
    to:
    FE000000 -FEFFFFFF
    from:
    00000000 - 00003FFF
    to:
    FFFDC000 - FFFDFFFF
    from:
    00000000 - 007FFFFF
    to:
    FF000000 - FF7FFFFF
    Hangs system on reboot. Had to enter Safe Mode and restore automatic settings for G200.

    Attempted to change G200 memory range
    From:
    00000000 - 00FFFFFF
    to:
    06000000 - 06FFFFFF
    from:
    00000000 - 00003FFF
    to:
    000A0000 - 000A3FFF
    from:
    00000000 - 007FFFFF
    to:
    06000000 - 067FFFFF
    Resulted in scrambled screen and distorted colors and hang on restart.

    Changing settings
    From: to:
    00000000 - 00FFFFFF FD000000 - FDFFFFFF
    00000000 - 00003FFF FFfDC000 - FFFDFFFF
    00000000 - 007FFFFF FF000000 - FF7FFFFF
    hangs on reboot.

    Removed Matrox drivers using Matrox Uninstall Utility. Restart prompted installation of "Standard PCI VGA Adapter" which I was able to change to "Standard VGA Adapter".

    Removed Matrox Marvel G200 card from system and replaced with Cirrus Logic 5446 PCI VGA Adapter. Restarted system. Adapter auto-detected & installed correct drivers, rebooted, and Device Manager shows NO CONFLICTS.

    What could possibly cause the Marvel G200 AGP Adapter to suddenly start conflicting with other devices after a year of normal use? Does this indicate a problem with the Matrox hardware, or some wierd driver conflict? Is this conflict the reason Video Tools would not function and hanged the system when I tried to reinstall it?
    And is this covered under warranty (purchased 3-26-99)?

    Thanx all for input.

    Kevin
    KRSESQ@Netscape.net

  • #2
    WIN95B Needs an Patch to work with AGP Cards!
    Its the same as the USB patch!!!!

    ------------------
    INTEL PIII550 MSI 6163
    G400Mill 32MB SGRAM + RRG
    SBlive
    256 MB RAM CAS2
    43GB HDD Space!(Actual 40GB) (13+30 Quantum drives)
    Pioneer 104S DVD 10x CD 40x SLOT IN
    SONY CRX100E 4/2/24 CDRW

    If there's artificial intelligence, there's bound to be some artificial stupidity.

    Jeremy Clarkson "806 brake horsepower..and that on that limp wrist faerie liquid the Americans call petrol, if you run it on the more explosive jungle juice we have in Europe you'd be getting 850 brake horsepower..."

    Comment


    • #3
      As noted: All patches, INCLUDING Latest AGP driver from FIC, are installed.

      [This message has been edited by KRSESQ (edited 16 April 2000).]

      Comment


      • #4
        I think you missed one patch that is required, though. It's the USB supplement patch for windows95 to allow it to properly recognize an AGP slot in your system, you can download it from microsoft, or look for it on your Win95 OSR 2.1 cd.

        Rags

        Comment


        • #5
          Thanx Rags. I will try the USB patch, although I must point out that the system worked (nearly)flawlessly for a year without it.

          Comment


          • #6
            Fixed it. The fix: Downloaded utility to reset factory BIOS settings on the AGP card. Ran It and then deltree'd Windows and reinstalled. So far, all is well. The Question: Which was the true fix? Or were the planets just aligned right?

            Comment

            Working...
            X