Mail Archives: djgpp/2009/05/15/05:48:46

X-Authentication-Warning: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
Date: Fri, 15 May 2009 12:48:18 +0300
From: Eli Zaretskii <eliz AT gnu DOT org>
Subject: Re: An interrupt drived uart program dead
In-reply-to: <guja2i$83o$>
X-012-Sender: halo1 AT inter DOT net DOT il
To: djgpp AT delorie DOT com
Message-id: <>
References: <dcff139d-32b8-4f22-ab4a-6f7e78f81324 AT c18g2000prh DOT googlegroups DOT com> <Pine DOT LNX DOT 4 DOT 60 DOT 0905150327230 DOT 1746 AT narpes DOT com> <guja2i$83o$1 AT aioe DOT org>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com

> From: "Rod Pemberton" <do_not_have AT nohavenot DOT cmm>
> Date: Fri, 15 May 2009 04:48:46 -0400
> I was hoping someone could help him (and me indirectly).  I've had so many
> problems trying to create a working TSR in DJGPP that I gave up.  No matter
> what I did with the locking functions, code that worked as a non-TSR would
> just not work as a TSR.  I eventually concluded that code or data somewhere
> in the _go32* or _dpmi* calls wasn't able to be locked.

Did you try locking _everything_ in your program, by setting the
`_CRT0_FLAG_LOCK_MEMORY' bit in the `_crt0_startup_flags' variable?
Something like this:

   #include <crt0.h>

   int _crt0_startup_flags = _CRT0_FLAG_LOCK_MEMORY;

If this doesn't work, either, then locking memory is not the problem.

- Raw text -

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