Mail Archives: djgpp/1994/08/30/19:00:45
On Tue, 30 Aug 1994, DJ Delorie wrote:
> EMM386 uses protected mode. GO32 uses protected mode. EMM386 is a
> TSR. GO32 is not. It's not a matter of easy or hard, go32 just
> doesn't know how to deal with a program that wants to be a TSR.
Discrimination against aspiring TSRs. ;)
Is there some way to get my program started and then tell go32 it's no
longer needed? I promise not to use go32 functions. ;) No, go32 does
interrupt stuff, right? So I suppose it wouldn't be easy to just get rid
of it... In DJGPP version 2, there won't be a go32 so would it then be
okay to make TSRs?
BTW: how exactly are you going to get rid of go32? what about all the
programs that use the go32_* functions? Will my executables grow by 70k
by just sticking the go32 stuff into my program? I assume once you've
eliminated go32, it would be quite a bit harder to make a communal go32
that all DJGPP programs could use... What's the point of getting rid of
go32? Right now I can distribute say five little programs and a copy of
go32 for them all to use. If you stick it in each program, my little
bundle will be quite a bit bigger I would think. Or are you only going to
include the parts of go32 that the program actually uses? If there's no
go32, how are you going to debug your programs? How long do you think
it'll be before version 2 comes along? After 1.12, 1.13, 1.20, 1.50? I
could think of a million more questions, but that's enough for now. :)
Kim
- Raw text -