> > I am experiencing troubles with EMM386 on WATTCP > > applications over 16bit ODI + ODIPKT packet driver.
> loading high network drivers isn't supported by emm386 > standard due to missing VDS support. > depending on the protokoll layer above (and a couple of other things), > it might also be nessessary to load the protokoll driver low. Aha, I see. Yes, only after I "loadlow" LSL.COM (Link Support Layer) and "loadlow" my nic things work again. So I conclude that UMBPCI has a very different approach which does not raise all these implications but at the price that it is very chipset dependent, where EMM386 follows a generic line (aiming hardware independence) but having to fullfill far more issues (VDS, DPMI/EMM/XMS memory pooling, etc.) 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. > if the drivers are real clever, and auto-loadhigh themself, use > > LH /L: load network driver Yes, that is a nice trick. Erwin ------------------------------------------------------- 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
