delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1999/09/23/13:10:18

From: eplmst AT lu DOT erisoft DOT se (Martin Stromberg)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Run-Time memory usage and HIMEM.SYS
Date: 23 Sep 1999 08:39:09 GMT
Organization: Ericsson Erisoft AB, Sweden
Lines: 21
Message-ID: <7scovd$paf$1@antares.lu.erisoft.se>
References: <37E9937F DOT 73BDA51C AT videotron DOT ca>
NNTP-Posting-Host: propus-144.lu.erisoft.se
X-Newsreader: TIN [version 1.2 PL2]
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Henri Tourigny (tourigny AT videotron DOT ca) wrote:
: Building my program with DJGPP 2.02, I can access all the extended
: memory on the target machine running ms-dos 6.22. This is fine, except
: that some of that memory was already used by a ram disk. I am using
: himem.sys and ramdrive.sys, which are part of dos 6.22. So my program is
: overwriting the memory used for the ram drive.

: Is there any way for my program built with DJGPP to be compatible with
: HIMEM.SYS? If not, is there another way to get a RAM disk in extended
: memory that is compatible with a program built with DJGPP?

Eeerh... I've used HIMEM.SYS and RAMDRIVE.SYS without any problems. I
did use EMM386 too (for UMBs).

What makes you think that DJGPP programs overwrite the RAM disk? While
theoretically plausible, I don't think that is what's happening.


Shostakovich, String Quartet 15,

							MartinS

- Raw text -


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