Clarence wrote:
>So it appears to have a problem with either VESA in general or Matrox
>in particular. :(
In my experience it's a problem with the VESA interface.
>The Arachne screen is a total mess - nothing recognizeable at all - and
>it doesn't reset or clear when I exit. I have to run blind. I guess my
>card registers get screwed up. :(
Aha, just what I got when I used VESA. I changed to the one that was
correct for my card. Try and remove all except the one you want to test and
see how that goes.
The other problem, when you exit Arachne, is somehow unknown to Michael. As
a start Arachne doesn't reset the card correctly (but since you also have
the source all you need to do is fix it - locating the correct source is
very easy, just RTFM for SVGAlib). For a more permanent fix I would suggest
getting a S3 card (the best supported by SVGAlib IIRC - and the brand
Michael is using).
And just to be perfectly annoying it didn't fix all problems for me when I
fixed Arachne so it would do as SVGAlib wants when it exits. I haven't
tried Arachne since I screwed my Linux installation up by installing one of
the test versions of the new SVGAlib, and now I think I accidently
formatted the Linux bootfloppy :/
