Am 28.06.2016 um 22:55 schrieb Abe Mishler <>:

>> is pretty unstable, at least for me.
> It seems like you should be excluding a different region of memory. From your 
> screenshot: E300-EDFF.

The packet driver works, but FDAPM is still crashing when I exclude E300-EDFF.  

>> But the default line didn’t work for you at all. Hmm.
> Strange, right? And not just on one computer, but three separate ones; each 
> running different hardware and software (host OS). Although I would expect 
> that the underlying differences are abstracted away by VirtualBox.

I created the VirtualBox „FreeDOS" image in February. Immediately five 
people complained (very politely) about crashes. No boot menu option worked 
that included JEMMEX or JEMM386.

As temporary fix, I replaced JEMMEX with the obsolete HIMEM.EXE and EMM386.EXE 
from FreeDOS 1.0. There has been no complaint since. (The "FreeDOS 1.1net" 
VirtualBox image has been downloaded 815 times in 2016). 

> Am 29.06.2016 um 00:24 schrieb Eric Auer <>:
> To explain the different memory types:

Thank you! Clears things up and refreshes the memory. This should be part of 
the FreeDOS wiki. Reminds me of the time, when I was reading the MS-DOS 5.0 
manual in 1992. Got my first computer the day before and intended to read the 
manual first. So I sat on a river bench and read about optimizing the use of 
UMBs. :-)

> UMB - provided by EMM386 - lets you load various drivers
>  high, can also be provided by UMBPCI or other hardware
>  drivers, can cause stability issues in conflict cases

This is the reason I want some EMM. For DOS networking I need to load drivers, 
especially for MS Client.
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
Freedos-user mailing list

Reply via email to