From: James W Sager Iii <sager+@andrew.cmu.edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: ?Win95 crash from Allegro:Set_pallete?
Date: Thu, 26 Mar 1998 00:38:44 -0500
Organization: Junior, MCS Undeclared, Carnegie Mellon, Pittsburgh, PA
Lines: 12
Message-ID: <kp6SbYG00YUt0nzlU0@andrew.cmu.edu>
References: <gp4yERS00YUt074kU0 AT andrew DOT cmu DOT edu>
 <aKzlWDAtKPF1Ew2k AT talula DOT demon DOT co DOT uk> <wp5HOXy00WB=07EnE0 AT andrew DOT cmu DOT edu>
 <NuIgvNABerF1Ew3L AT talula DOT demon DOT co DOT uk> <gp5jEKi00YUt1EQ2w0 AT andrew DOT cmu DOT edu>
	<I1ZR5NAKbAG1Ew+I AT talula DOT demon DOT co DOT uk>
NNTP-Posting-Host: po6.andrew.cmu.edu
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

>But which drivers are you using? I need to know both which of the             
>Allegro video drivers is being detected, and assuming it is one of the        
>VESA ones, what your VESA implementation is (as displayed by the              
>vesainfo program). Without this kind of information it is impossible to      
>know even where I should start looking for the cause of the problem...        
                                                                        
In your documentation about timers and palletes, you stated that
there is some problems dealing with them so I just assumed my problem 
dealt with the timing mechanisms of win95.  I'll send you the overly
spammy vesainfo stuff if my net connection holds out. It dies from time
to time, and the reason sent so little information was because I 
had to keep retyping it as my ISP died on me many many times.