On 2002-08-28, Eric Auer wrote:
> The problem: DR emm386 still gives me nothing but "EMM386:
> insufficient memory", no matter if I load fdxxms before or
> not and no matter if I use options other then VERBOSE or not.
Still? I'm confused now. Last time you said it gave you a
"Not enough memory" message. This is quite a difference.
The "Not enough memory" message is definitely coming from
the PKLITE decompressor stub in EMM386.EXE, while the
"EMM386: Insufficient memory" is coming from one of the
EMM386 modules itself. A different scenario. I think,
in order to track down a problem, it is important to
be very specific with error messages...
When I find the time, I can look up, which conditions can
cause EMM386 to report this error message. This may give
some hints on what's going wrong under FreeDOS.
In the meantime, have you cross-checked if the problem vanishs
when you use DR-DOS 7.03 instead of FreeDOS on this very machine
(in a configuration as similar as possible to the FreeDOS
configuration)? You do not need to install DR-DOS, just
boot from the installation CD, abort to the DOS prompt,
create a boot floppy with SYS etc...
> I wonder how FreeDOS performs in making MS Windows 3.x or OS/2
> (Warp) think that they run with a compatible DOS (Windows is
> very picky about that, probably to make you get MS DOS to run
> it and not a competxing DOS).
Hm, Eric, OS/2 does *not* run on DOS. It's a genuine Protected Mode
operating system similar to Windows NT (but in many aspects it is
technically better, IMHO). [Reply to private mail: OS/2 Warp 3 and
Warp 4 are just OS/2 versions 3.x and 4.x.]
OS/2 comes with a quite good DOS emulation (although based on
older technology, in practise it is in my experience much more
compatible with DOS than the crude DOS emulation in NT), but
you can also try and boot FreeDOS (or any other DOS) in a VDM
under OS/2 - but this is a completely different story.
FreeDOS does *not* require anything extremely special in its
resident code for this to work - there might be some fuzz
with the proper format of the OEM label in the boot sector,
though. Maybe FSFILTER.SYS needs some attention, but anyway,
in the OS/2 world, DOS runs under OS/2, not the other way
around.
In contrast to this, Windows and Windows for Workgroups 3.xx
and Windows 95/98/SE/ME are totally dependent on an underlaying
DOS. They cannot work without it. So, to make this combination
work, FreeDOS must support what Windows looks for in the kernel.
"Undocumented DOS" and "DOS Internals" has most of the details.
Hope it helps carifying the issue a little.
Matthias
--?
<mailto:Matthias.Paul@xxxxxxxxxxxxxxxxxxx>; <mailto:mpaul@xxxxxxxxx>
http://www.uni-bonn.de/~uzs180/mpdokeng.html; http://mpaul.drdos.org
"Programs are poems for computers."
---
Help the victims of the disastrous Danube, Moldau, and Elbe floodings
of the century in the Czech Republic, Austria, and Germany: www.ct1.cz;
www.orf.at; www.tagesschau.de; www.drk.de for latest news & donations.
----------
list options/archives/etc.: http://www.topica.com/lists/fd-dev
unsubscribe: send blank email to: fd-dev-unsubscribe@xxxxxxxxxx
==^================================================================
This email was sent to: gofd-fd-dev@xxxxxxxxx
EASY UNSUBSCRIBE click here: http://topica.com/u/?bz8Rv5.bafB3U
Or send an email to: fd-dev-unsubscribe@xxxxxxxxxx
T O P I C A -- Register now to manage your mail!
http://www.topica.com/partner/tag02/register
==^================================================================
|
