Announcement

Collapse
No announcement yet.

Geforce MX

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

  • #16
    Well, something is up, because the manufacturer seems to have thought it wasn't possible, and apparently it is.

    These EVGA guys seem particularly nice. I couldn't imagine a company handling the 7 ns RAM situation better. I think they were so forthcoming and accomodating, they turned a potentially very bad situation into something that might bring them a lot of good will.

    Paul
    paulcs@flashcom.net

    Comment


    • #17
      Probably the same place it left you when MANY murcers were having their G400's bios altered by your PowerStrip

      Hugh G

      Comment


      • #18
        Dat's Kold Mon
        ROTFLMAO
        [size=1]D3/\/7YCR4CK3R
        Ryzen: Asrock B450M Pro4, Ryzen 5 2600, 16GB G-Skill Ripjaws V Series DDR4 PC4-25600 RAM, 1TB Seagate SATA HD, 256GB myDigital PCIEx4 M.2 SSD, Samsung LI24T350FHNXZA 24" HDMI LED monitor, Klipsch Promedia 4.2 400, Win11
        Home: M1 Mac Mini 8GB 256GB
        Surgery: HP Stream 200-010 Mini Desktop,Intel Celeron 2957U Processor, 6 GB RAM, ADATA 128 GB SSD, Win 10 home ver 22H2
        Frontdesk: Beelink T4 8GB

        Comment


        • #19
          Hugh - Ouch... You mean they will drop support for Matrox cards? Or they'll switch the blame from Microsoft over to PowerStrip?
          LOL

          Comment


          • #20
            Ashley,

            Actually I was just trying to make a point that sometimes things aren't as they seem. Just becaus you have a couple of guys who say that such and such is possible and happening, doesn't make it true. I can't get my MX to use different resolutions, but I am still trying.

            Hugh G.

            Comment


            • #21
              Agree completely Hugh... What I was
              thinking was that, if it works, a TwinView with independent resolutions under Win2K is a good thing for Matrox DH users - maybe not for Matrox itself, but certainly for Matrox customers who could then push for - and probably get - similar functionality.

              Comment


              • #22
                They won't.

                I am not exactly familiar of the details on Matrox' and nVidia's implementation of Dualhead and TwinView, but I did read this a while back:

                Matrox G4x0 implementation of Dualhead relies on a 'bug' in Win98, which enables dualhead with different resolutions in Win98. However, this 'bug' was not implemented in Win2k, so no independent res. here!

                nVidia implementation obviously is different than this (or not.... but let's conclude it is for now, until those rumours about different res in Win2k are proven wrong), and enables the use of different res. in win2k.

                What I read is that the only way to enable different res. in Win2k is for Microsoft to implement the same 'bug' again, or for Matrox to change their implementation of Dualhead. This would require a lot of rework on their cards, and very likely is not feasible at all for the current dualhead cards.

                Now, maybe that what I read was completely wrong, or misinterpreted by me... if not, I really hope Matrox will change their DualHead implementation in the G800, so that you can use different res. in Win2k. Maybe this even is one of the reasons the G800 is not yet out?

                Comment


                • #23
                  Hmmm... Independent resolutions under Win2K with TwinView, but not DualHead. Now where does that leave Matrox with their oft-repeated claim that this just ain't possible under Win2K and its all MS's fault?

                  Comment


                  • #24
                    OK, whose going to go out and buy one, so we can get reliable verification?

                    Paul
                    paulcs@flashcom.net

                    Comment


                    • #25
                      Paul, Hugh has one at home right now and is trying to duplicate this (and I might add can't but hasn't given up
                      "Be who you are and say what you feel, because those who mind don't matter, and those who matter don't mind." -- Dr. Seuss

                      "Always do good. It will gratify some and astonish the rest." ~Mark Twain

                      Comment


                      • #26
                        dZeus, I really can´t believe Matrox would have based one of their most impressive features on a Win98 bug. Just imagine MS decides to fix that bug (i.e. windows update) and boom, all the G400 DH around would stop functioning. Not very likely...

                        Comment


                        • #27
                          here is a refenrence as a partial answer to your post:
                          http://forum.matrox.com/mgaforum/For...ML/000410.html

                          read the message posted by Toyer ( August 4, 7:52) and Alex' reply to it.

                          I am sure that if you do a search on something like dualhead, exploit and win98, that you'll find a thread where they explain how dualhead works in Win98.

                          I guess this is one of the few bugs in Win98 that actually is a 'feature', instead of a annoyance.

                          oh, and my answer to this one:
                          Just imagine MS decides to fix that bug (i.e. windows update) and boom, all the G400 DH around would stop functioning. Not very likely...
                          What about Win2k? Since the functionality needed to use different res. on 2 monitors with the G400 dualhead implementation is embedded deep into the OS (in the kernel), a windows-update wouldn't fix this. A new OS however could....

                          I would like to know if MS fixed this on purpose to annoy Matrox, that this is a result of miscommunication between Matrox and MS or because MS failed to properly test their OS before they made a built 'final'.

                          Of course, if nVidia TwinView does NOT work in Win2k with 2 different res., then most of my conclusions and assumptions are wrong.

                          [This message has been edited by dZeus (edited 19 September 2000).]

                          Comment


                          • #28
                            I think MS could update kernel32.dll if they wanted to. Let´s hope now Microsoft is in bed with Nvidia they do it just to please all the GF2 MX owners out there.

                            Comment


                            • #29
                              that's only if nVidia TwinView works the same way as Matrox Dualhead.... let's hope so!

                              Comment


                              • #30
                                With a sinister grin, lets hope so!
                                "Be who you are and say what you feel, because those who mind don't matter, and those who matter don't mind." -- Dr. Seuss

                                "Always do good. It will gratify some and astonish the rest." ~Mark Twain

                                Comment

                                Working...
                                X