(1) is this safe (or functional)? Having a SUB thus in my
include-in-everything-INC file:
...or would such tactics only work if the ASM code were physically
located in each UNIT's proceures?
(2) is there a way, I presume it would be with a DOS interrupt service,
to allocate memory to an EXE (from within a UNIT procedure), and
have the procedure directly access it? What I mean is, to duplicate
the functionality of the Win32 "HeapAlloc()" API? If there is a DOS
service that does this, then do not go to the trouble of spelling it
out for me, as I can do the research, myself. A simple "yes" or "no"
will be sufficient.
Thank you for any replies.
------------------
include-in-everything-INC file:
Code:
SUB GetDS () ! push ss ! pop ds END SUB SUB GetES () ! push ss ! pop es END SUB
located in each UNIT's proceures?
(2) is there a way, I presume it would be with a DOS interrupt service,
to allocate memory to an EXE (from within a UNIT procedure), and
have the procedure directly access it? What I mean is, to duplicate
the functionality of the Win32 "HeapAlloc()" API? If there is a DOS
service that does this, then do not go to the trouble of spelling it
out for me, as I can do the research, myself. A simple "yes" or "no"
will be sufficient.

Thank you for any replies.

------------------
Comment