Mail Archives: djgpp/1997/08/28/07:05:46
From: | Gal <wribak AT usa DOT net>
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | TSR
|
Date: | Wed, 27 Aug 1997 21:29:38 -0700
|
Organization: | Spamless Society
|
Lines: | 26
|
Message-ID: | <3404FEAB.19EF@usa.net>
|
Reply-To: | wribak AT usa DOT net
|
NNTP-Posting-Host: | lap-ca4-46.ix.netcom.com
|
Mime-Version: | 1.0
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
I hope I think I'm posting in the right news forum...
Under DJGPP, examining DJGPPTSR.ZIP, I found two things that were a bit
vague: 1) being used to real-mode, "interrupt" was missing; which saves
registers and etc. 2) to terminate and stay resident, all that was done
is calling AX=3100, DX=(256)/16, INT 21.
Alrighty, thinking a bit stray, I feel that DJGPP handles interrupt
procedures automatically, and that after my little codes have ran, it
will restore the registers, yeah?
The second issue, TSR. I thought DX=(program size / 16)+1, isn't that
true? Hrm.. I can't figure out program size, even if I needed it, or
not. But being a assembler programmer also, I feel that it's a great
waaste to have the entire image loaded into memory, why not just load
the TSR data which I really need. Does DJGPP set aside pmode memory for
itself?
One last inquery, ...correct me if I'm wrong, DJGPP and DPMI, changes
INT 21's in inline assembly or calls to INT 31.
The nature of all this is to squeeze every bit of this little sucker of
it's juice :) Don't we all want a little more speed? :>
Wozzie
- Raw text -