delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1997/04/02/11:31:30

Date: Wed, 2 Apr 1997 11:12:17 -0500 (EST)
From: Peter Berdeklis <peter AT atmosp DOT physics DOT utoronto DOT ca>
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
cc: djgpp AT delorie DOT com
Subject: Re: Interrupt handlers and page locking
In-Reply-To: <Pine.SUN.3.91.970402111824.23151R-100000@is>
Message-ID: <Pine.SGI.3.91.970402110747.1182A-100000@atmosp.physics.utoronto.ca>
MIME-Version: 1.0

On Wed, 2 Apr 1997, Eli Zaretskii wrote:
> No amount of TSRs will cause your DJGPP program to page, because TSRs all 
> load into conventional memory whereas the absolute majority of DJGPP 
> installations use extended memory to load data and code of DJGPP 
> programs.
> 

Smartdrive uses extended memory for its disk cache buffers.  You can make 
those buffers as large as you want (I think) and use up lots of extended 
memory.  Also if you use a memory manager like QEMM you can load many of 
your TSRs into extended memory with the loader (LOADHI for QEMM).

In general though you're right, and I should have been more specific.

I still think that the best way is to pop out some of your RAM - although 
these days with 16MB SIMMs you still need to waste some memory.

---------------
Peter Berdeklis
Dept. of Physics, Univ. of Toronto

- Raw text -


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