Hello Erwin, > raise all these implications but at the price that it is very chipset > dependent, where EMM386 follows a generic line (aiming > hardware independence) that's why I did it first place
> but having to fullfill far more issues > (VDS, DPMI/EMM/XMS memory pooling, etc.) as I found out later ;) actually, I don't think I ever used EMM after ~1995, so the pooling shouldn't be much of an issue (usually) > The thing is that network clients plus drivers are usually used > as a ground layer and not as the end goal, so I try to be > cautious with resources. Many applications that need to surf > on a network client (Citrix ICA for DOS, Arachne, Powerquest > Image, etc...) can be quite hungry for conventional memory. I don't care that much about Drive Image ;) >> if the drivers are real clever, and auto-loadhigh themself, use >> >> LH /L: load network driver > Yes, that is a nice trick. Which I had to 'invent' because MS LANMANAGER *is* clever ;) tom ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
