Announcement

Collapse
No announcement yet.

RR-G, Pink/blue noise, grounding prob?

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

  • RR-G, Pink/blue noise, grounding prob?

    ok. I have a RR-G, with a G400Max. I've used it with my G200 in the past and have had the same problem all along:

    Sometimes, when I run Matrox Video Tools, the s-video input, composite, and TV input is all just pink and blue noise.

    When I point the camera at a light, the pink and blue noise gets brighter.

    Sometimes i'll reboot and it'll work. Sometimes i'll _touch the back of the computer_ and it'll start working.

    To answer everyone's questions:

    G400 is on IRQ11, nothing else is.

    Have checked ribbon cables.

    Have tried several s-video cables, but it
    has the same problem with other inputs.

    I completely uninstalled the G200 drivers,
    with the utility. But it was doing it with the G200 back then anyways.

    Has done the same thing with PD 1.2 and 1.5 beta. Driver revisions make no difference (5.15.) Nothing is overclocked.

    It isn't a loose connection because once it "goes good" by moving the cable, it can't be made bad again unless I reboot.

    To me this looks like an electrical problem that I've had since the card was put in, but I'm pretty sure that Matrox won't fix or repair it at this point because i've had it for a while.

    Can anyone help me with this, has anyone else had this problem?



    ------------------
    Ami Y. Koriuchi - foxyviolet@hotmail.com
    Asus P2B 1010 - P3-500 - And a G400Max now.
    256MB 6NS 70 GB of 10k RPM SCSI UW

    You're a ... 'guest' ... of the Master Control Program.

    Ami Y. Koriuchi - MY EMAIL IS DEAD

    SYSTEM1
    Asus K7V266 - Athlon XP 1800+ - GeForce 4 TI 4600 128MB -
    1024 MB PC2100 DDR -
    200 GB UDMA100 7200 RPM - 60GB LVD 160 10K RPM

    SYSTEM2
    Asus A7V133 - Athlon 1.4 - G400Max
    768MB PC133 - 75 GB of 10k RPM SCSI UW

    HI SOMETiMES I GO AWAY FOR LONG TIME AND COME BACK YEARS LATER HI!

  • #2
    Hey Ami,

    Next driver set is supposed to fix this.

    Haig

    Comment

    Working...
    X