16.04.2012 16:39, Bart Oldeman wrote: > I'm not sure I like this approach. Now two handles are permanently > allocated, visible by "mem/e", etc. Well, I am afraid there are not too many ways around this. You either permanently allocate (and how would one handle be better than 2 handles with this regard?), or you allocate per-client, which is: 1. Excessive (separate handles for every client are not needed) 2. Unreliable (some prog may eat up all handles before you do) So I choose permanent allocation, and what is wrong with the fact that the handles are visible? Any TSR can allocate a handle if it wants to, so when you boot everything up to DosNavigator, a few handles may be allocated. Our DPMI server is the one of those TSRs. :) if you disable it, handles are free.
> I wonder if msdos.c could use the > special OS handle to do its work. It doesn't span to UMA, so how? ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Dosemu-devel mailing list Dosemu-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dosemu-devel
