home *** CD-ROM | disk | FTP | other *** search
Wrap
id m0u4mSx-0007rOa; Thu, 4 Apr 96 03:40 MST Sender: owner-executor Received: by ftp.ardi.com (Smail3.1.29.1 #3) id m0u4mEl-0007rPC; Thu, 4 Apr 96 03:25 MST Content-transfer-encoding: quoted-printable Received: from Pentium (i175.arrakis.es [194.224.18.175]) by arrakis.es (8.7.5/8.7.1) with SMTP id MAA22451; Thu, 4 Apr 1996 12:24:46 +0200 Priority: Normal References: Conversation <c=US%a=_%p=msft%l=RED-99-MSG-960403203251Z-1888@red-06-imc.itg.microsoft.com> with last message <c=US%a=_%p=msft%l=RED-99-MSG-960403203251Z-1888@red-06-imc.itg.microsoft.com> Mime-version: 1.0 Message-id: <MAPI.Id.0016.006570616c7a61404133333130303030@MAPI.to.RFC822> Subject: Re: Follow-up: Matrox Millenium problems with 800x600 Cc: executor@ardi.com Content-type: text/plain; charset=US-ASCII; X-MAPIextension=".TXT" In-reply-to: <c=US%a=_%p=msft%l=RED-99-MSG-960403203251Z-1888@red-06-imc.itg.microsoft.com> To: Chris Hedberg <chrished@microsoft.com>, Date: Jue, 04 Abr 96 11:42:18 +0100 (MET) From: Juan Jose Epalza <jepalza@arrakis.es> Sender: owner-executor@ardi.com Precedence: bulk >> 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 640x48= 0. I did think in this fact than the resolution it was a fail of the Exe= cutor, 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=3Dffffffff ebx=3D00294ffc ecx=3Dfc4f2900 edx=3D001b8a1e esi=3Dfffffff= f edi=3Dfc4f2900 ebp=3D0020e87c esp=3D0020e870 cs=3D00a7 ds=3D00af es=3D00af fs=3D008f gs=3D= 00cf ss=3D00af 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-))