Hi Don,

you probably misunderstood me. I said that DOS in general has security
code in the kernel to make sure that the HMA is activated before parts
of the kernel which are stored in HMA get used. The security code itself
is kept outside the HMA... What exactly were you testing with FAT32 and
Compaq and FreeDOS and which test results and differences did you see or
expect in that testing now?

Regards, Eric

> I just tried this on Compaq DOS 5.0 with Compaq Himem only with no errors
> and no missing paths. So unless it's a FAT32 problem it must go back to
> FreeDOS somehow???

> On Wed, Jun 8, 2016 at 3:30 PM, Don Flowers <donr...@gmail.com> wrote:
>> I'm going to try a couple of things in DOS 5.0 and DOS 6.20, I'll be back.

>> On Wed, Jun 8, 2016 at 2:52 PM, Eric Auer <e.a...@jpberlin.de> wrote: ...
>>> the problem of using but not reserving memory for the kernel in FreeDOS
>>> sounds vaguely similar to the problem of HMA usage in DOS in general:
>>> DOS installs trampoline handlers outside HMA which make sure that the
>>> HMA is actually enabled before DOS calls code there. Maybe a similar
>>> approach could be used for the unallocated FreeDOS memory?


What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
Freedos-user mailing list

Reply via email to