Mail Archives: djgpp/1996/08/07/13:55:22
Xref: | news2.mv.net comp.os.msdos.djgpp:6734
|
From: | John Sabean <docmani AT eng DOT umd DOT edu>
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | Allegro + Win95
|
Date: | Fri, 02 Aug 1996 11:11:23 -0400
|
Organization: | Project GLUE, University of Maryland, College Park, MD
|
Lines: | 28
|
Message-ID: | <32021A9B.606A@eng.umd.edu>
|
NNTP-Posting-Host: | pegasus.umd.edu
|
Mime-Version: | 1.0
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
Has anyone solved any of the problems associated with Allegro
and Win95.
The first problem I'm talking about is the timer warning message.
Apparently, when you install the Allegro timer, this freaks
Win95 out and Win95 gives you a message about 'Creating an full
MS-DOS session' for your program. You can happily ignore this,
and everything works fine, however it is sort of unsettling to
see this every time I run. Has anyone come up with a workaround
for this?
The other problem is that the mouse moves slower in a Win95
DOS session. This may be related to the problem above, or it
could be something else. I see in the code that a correction is
make for SVGA modes. Apparently, he multiplies all the mouse
values by 8, to compensate for a problem with SVGA. He then
divides by 8 whenever a mouse value is read. Its possible that
Win95 does not need this compensation.
The problem is that under older versions of DOS, everything works
fine. So, how do you get around this problem? Put in a 'detect'
and set the 8 pixel compensation factor based on what the 'detect'
returns. If this is the case, what should I be detecting?
Any suggestions or thoughts?
--
<docmani AT eng DOT umd DOT edu ------ http://www.glue.umd.edu/~docmani>
- Raw text -