delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1997/08/03/12:32:06

From: Shawn Hargreaves <Shawn AT talula DOT demon DOT co DOT uk>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Allegro Timer and Win95
Date: Sat, 2 Aug 1997 17:21:46 +0100
Organization: None
Distribution: world
Message-ID: <uAzIUTAa614zEwgC@talula.demon.co.uk>
References: <33E02DC1 DOT B1007C69 AT imag DOT net>
NNTP-Posting-Host: talula.demon.co.uk
MIME-Version: 1.0
Lines: 26
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

Chris writes:
>   Sometimes when I run an Allegro app (in Win95) which calls
>install_timer() at startup, I get this error message:
>"Your program accessed memory in use by 000004CC from C000:783D"
>   Then it asks if I want to continue. If I say Yes, Windows crashes, if
>I say no, the app will terminate. 

That's very strange. The timer code doesn't touch any BIOS area memory
like that (the only possibility I can think of is that the original DOS
timer handler, which my routine chains to, might be located there, but I
can't think why that would be causing a crash).

Are you 100% sure that the problem is with install_timer(), and not the
graphics code? In particular, does ex7.exe, which uses the timer from
text mode, ever cause this error? Also, does it ever lock up when run
from DOS mode rather than under Win95? Finally (a long shot, but it
might yield something interesting...) what does Win95 think the memory
at 0xC783D is being used for? Right click on "my computer", go to
properties, select the "device manager" tab, highlight the top
"computer" entry, click the properties button, select "memory", and see
what that address range is being used by...


--
Shawn Hargreaves - shawn AT talula DOT demon DOT co DOT uk - http://www.talula.demon.co.uk/
Beauty is a French phonetic corruption of a short cloth neck ornament.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019