Announcement

Collapse
No announcement yet.

!!! OGL still not working with 5.50.1 on SS7-Boards !!!

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

  • !!! OGL still not working with 5.50.1 on SS7-Boards !!!

    opengl-games like quake3 are still not working with the latest 5.50.1 driver on my mvp3-board. and opengl-applications like mapleV have problems with the newest G400ICD, too.
    thief works now,
    ***BUT WHAT IS WITH US SS7-USERS. WE WANT FASTER OPEN-GL, TOO***

    now i will turn back to 5.41 + G40032.DLL from 5.30 + Turbo-GL 1.0.


    ------------------
    \\ Surfwienix //
    (German)

    My System:

    AMD K6-2/400 non-o/c
    Epox MVP3C-M Super7
    128MB SDRAM(PC100)
    -> G400 MAX (PD 5.30+TGL1.0+DX7a) non-o/c
    Terratec DMX Canyon3D
    6,4GB Maxtor HDD (UDMA33)
    ASUS 50x-CDROM (UDMA33)
    Realtek 8019 Ethernet (ISA)
    19" Monitor CTX-VL950T (95khz)
    my system:

    AMD XP 2000+
    Abit KTA7 (VIA 4.49)
    512MB SDRAM133
    Matrox Millennium G400 MAX (5.91, AGP 2x)
    Windows XP Prof

  • #2
    You are absolutely right. Remember, it's just BETA release.

    Comment


    • #3
      Awwwww!! nuts.

      I was hoping they'd have fixed that. Oh well.

      ------------------
      Chris Blake

      Home System:
      Epox MVP3G5, K6III450, 256Mb RAM, 13.6Gb ATA66 HDD G400Max DH, SBLive! Value and whole load of other stuff

      Work System:
      Dell Precision220 Dual PIII 533, 128Mb RAM, 20Gb ATA66 HDD, G400Max DH, and even more other stuff
      Chris Blake

      Comment


      • #4
        It's not just SS7, Apollo Pro133+ has the same problem.

        Comment


        • #5
          Sure, it's just a beta release. But, not only is it a very unsubtle and obvious failure, there's the scary fact that the last release of any sort which worked fine for me was 5.25, four releases and many months ago!

          My system, a G200 and VIA-based SS7 combo, isn't so bizzare, but apparently they don't own any similar machines at Matrox's testing center.

          5.30 - BSOD upon entering a 3D mode.
          5.41 - Powerdesk steals the whole CPU.
          5.50 - BSOD again.

          (not just me, but repeated reported by many people both on MURC and on usenet)

          Matrox, please spend the $300 on SS7/K6-2/G200 system, and try out your releases before hundreds of people around the world waste a lot of time each to find out for themselves that it Just Plain Crashes.

          Alec

          Comment


          • #6
            Where's Gurm when you need him! :0)



            ------------------
            AMD K6III 400 @ 476
            On a SOYO SY5EMA M/B
            Marvel G200 TV with HW/DVD Daughtercard
            CDBurner
            Creative DVD
            Promise Ultra 66 Controller
            two big WD Hdds
            Outboard 56K modem
            Parallel Port Scanner
            All stuffed into a Mid-tower ATX case
            with no device slots left!
            Greebe's juiced up Athlon @750 on an MSI Irongate Based M/B Marvel G200 TV with HW/DVD Daughtercard,
            CDBurner, Creative DVD, two big WD Hdds, Outboard 56K modem
            Parallel Port Scanner, Creative S/B AWE 64 (ISA), and a new Logitech WebCam (My first USB device)

            Comment


            • #7
              I think its pretty scary that it doesn't work on the Apollo Pro133+ chipset either (according to Compton).

              Anyone else have one of these fairly new chipsets and try this out? This could be a nasty issue, since VIA ppretty much has the only 133mhz fsb chipsets out there for *ntel and Athlon (unless you want use the crappy 840 chipset or whatever it is with the sdram compatibility chip that makes it slow as crap)

              Comment


              • #8
                rylan, it gets ever scarier, my G200 is PCI! I wouldn't think there should be that big of a difference between Via's implementation of PCI and Intel's since the big problem has always been AGP. But at least Direct3D works great (some of the time) with the new driver.

                Comment


                • #9
                  Wow.. now thats _really_ odd. You're right.. the pci implementation should be pretty much the same. Hopefully they'll get it ironed out before the final release hits. It sure would effect lots of people since its an issue on Via SS7 and now Via 133 for Intel chips.
                  Wonder if it effects the new Via Athlon 133 chipset also.

                  Comment


                  • #10
                    hehehe G200's and SS7 never seem to go hand in hand reading the forums...
                    but unfortunately im gonna have to say opengl runs fine on my system :-)
                    ive got PD5.30 at the moment (due to D3D problems) and about to install the latest beta shortly. ill post my findings when i return :-)

                    ------------------
                    AMD K6-2/450, GA-5aa (bios 1.3), 64Mb PC-100, Millenium G200 16Mb (bios 2.3), Quantum Fireball EL 10.2Gb, Pioneer 10x DVD, Realtek 8029AS, Vibra16, Mitsubishi Diamond View 17"
                    WindowsME, AMD K6-2/450, GA-5aa (bios 1.3), 64Mb PC-100, Millenium G200 16Mb (bios 2.7) - (pd5.41), Quantum Fireball EL 10.2Gb, Pioneer 10x DVD, Realtek 8029AS, Vibra16, Mitsubishi Diamond View 17"

                    Comment


                    • #11
                      The fact is that the current TGL will not run on a SS7 system with any drivers other than the 5.3x version. Matrox does know about the problem and I'm sure they are working on it but I don't think they are going to give it as much resources as the regular ICD. That's where their concentration is. For me the 5.30 + TGL combo is about 25% faster in Q2 but is 5-10% less in most D3D games.

                      Joel
                      Libertarian is still the way to go if we truly want a real change.

                      www.lp.org

                      ******************************

                      System Specs: AMD XP2000+ @1.68GHz(12.5x133), ASUS A7V133-C, 512MB PC133, Matrox Parhelia 128MB, SB Live! 5.1.
                      OS: Windows XP Pro.
                      Monitor: Cornerstone c1025 @ 1280x960 @85Hz.

                      Comment


                      • #12
                        Right Joel, but the problems on SS7 boards are with G200, not G400, so TGL isn't the issue in this case... And, yeah, with the 5.5 beta I get fatal exceptions as soon as DX initializes. Which I'm ok with, 5.41 is very stable (with Pdesk disabled so as not to eat the CPU) and fast. My framerates in Quake2 (1024x768x16, high VQ) are the same with it as they are with the 3DNow optimized driver, but the VQ is even better. I ain't gonna scream and shout about it, but it is kinda a shame that SS7 / G200 does not get the support intel / G400 gets...

                        ------------------
                        I say "Here's a monkey wrench... If you bop me over the head with it long enough I might wake up for a second."

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

                        Comment


                        • #13
                          Joel,

                          I'm a bit supprised by your comments as I am running PD v5.41 + TurboGL on an SS7 system without probs. I am using an Iwill XA100plus which uses the ALi Alladin 5 chipset, maybe the problems only occur on m'boards with the VIA chipset.
                          When you own your own business you only have to work half a day. You can do anything you want with the other twelve hours.

                          Comment


                          • #14
                            Now that would be a twist in this all considering the problems that ALI chipsets had with the G200. But I will pass this information on.

                            Joel
                            Libertarian is still the way to go if we truly want a real change.

                            www.lp.org

                            ******************************

                            System Specs: AMD XP2000+ @1.68GHz(12.5x133), ASUS A7V133-C, 512MB PC133, Matrox Parhelia 128MB, SB Live! 5.1.
                            OS: Windows XP Pro.
                            Monitor: Cornerstone c1025 @ 1280x960 @85Hz.

                            Comment


                            • #15
                              Don't fear, I'm here (always near, like beer, full of cheer)!

                              Ok, enough rhyming now.

                              The expected response, from me, would be something to the effect of "get a real motherboard". But since it's also happening with an excellent chipset (the Apollo Pro133), I will be a little more gentle:

                              "This is what you get when you don't buy Intel - a neverending battle to keep all of your components working."

                              Now, for those of you with (s)uper(s)ucky(s)even boards - get a real motherboard. However, it is not uncommon to break a feature in a new build on a new chipset (and the Apollo is a VERY new chipset).

                              So be patient.

                              - Gurm

                              ------------------
                              Listen up, you primitive screwheads! See this? This is my BOOMSTICK! Etc. etc.
                              The Internet - where men are men, women are men, and teenage girls are FBI agents!

                              I'm the least you could do
                              If only life were as easy as you
                              I'm the least you could do, oh yeah
                              If only life were as easy as you
                              I would still get screwed

                              Comment

                              Working...
                              X