www.delorie.com/archives/browse.cgi | search |
Date: | Wed, 22 Jan 1997 00:18:50 -0800 (PST) |
From: | Gene Buckle <geneb AT web DOT wa DOT net> |
To: | Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> |
cc: | djgpp AT delorie DOT com |
Subject: | Re: Passing a parameter to interrupt handler. |
In-Reply-To: | <Pine.SUN.3.91.970122085048.29370J-100000@is> |
Message-ID: | <Pine.LNX.3.93.970122001709.8019B-100000@web.wa.net> |
MIME-Version: | 1.0 |
> > > > The whole program is locked in memory via the CRT0 flags. My problem is > > that the program calling the interrupt (0xef in this case) won't be the > > same one that has the code for the actual ISR in it. ;) > > Allocate some DOS memory and pass the data through that buffer. You will > have to devise a mechanism to publish the address of that buffer, so the > program which allocated them could tell the address to the other programs. > One possibility to pass this address is an environment variable; another > is a disk file. > The allocation of DOS memory would be the way to go. This handler is going to be hit hundreds (if not thousands) of times per second. A disk file would make it equal to Win95 in performance. ;) Any clues as to how I can make the dos buffer address known to both programs? g.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |