[Prev][Next][Index][Thread]

Re: Follow-up: Matrox Millenium problems with 800x600



>>	I decided to try 800x600 mode at home on _my_ Matrox card (also 4 megs,
>>running the latest BIOS, v.1.9, latest drivers as well) on 1.99q, and
>>got the following results:

>>1) When Executor's run shelled from Win 95, I get four trails of screen
>>trash instead of a normal mouse cursor, as reported.

    In my Matrox Milleniun with two megs, it do it only in 1024x768. (the same thing)
    but in DOS. (I don't has WIN95)

>>2) Under straight DOS, I get an immediate crash before even seeing the
>>info screen.

    It's then same with my (see below for crash text)

>>Executor -info reports that I have plenty of memory and recognizes that
>>the Millenium has VBE 2.0 support.

    And mine. (but two megs, in my Card)

>>Can somebody pass along (to me, not the digest) the cmd. parameter to
>>force Executor to send traceback info to a file instead of to the
>>screen? Unfortunately, I don't have time to root thru my old digests and
>>dig up the info.

>>				-Chris Hedberg

    I hope than Ardi can to solve our problem. It nasty to work in 640x480.
    I did think in this fact than the resolution it was a fail of the Executor,
    but i see than it don't certainly to the Executor:  it's of Matrox Millenium....
                      Puf, Puf ..   8'-(

 -------------------------------------     Cut here   ------------------------------------------
      this text is for the Ardi developers:   EXECUTOR -SIZE 800x600

eax=ffffffff ebx=00294ffc ecx=fc4f2900 edx=001b8a1e esi=ffffffff edi=fc4f2900
ebp=0020e87c esp=0020e870 cs=00a7 ds=00af es=00af fs=008f gs=00cf ss=00af
Call frame traceback EIPs:
  0x000af104
  0x000af237
  0x00079e10
  0x00079c40
  0x000adddb
  0x0016e561
                                        In my Matrox Millenium with two megs Vesa 2.0
P.D.: I am spanish...   you must be complaisant with me. My english is very, very, bad.  8-))



References: