From: "Florian Xaver" <dos DOT fire AT aon DOT at>
To: <opendos AT delorie DOT com>
Subject: Re: BASIC & EMS (was: Optimizing CONFIG.SYS...)
Date: Mon, 4 Dec 2000 20:55:32 +0100
Message-ID: <01c05e2c$2905ecc0$1c60b7d4@default>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="koi8-r"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.71.1712.3
X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3
Reply-To: opendos AT delorie DOT com

>> Wrong. DPMS is an API which moves most of an driver into RAM/Extended
>> memory.
>
>I am assuming by driver you mean Task Manager, the program itself. tes that
>is what it does.. You don't need a frekking EMS memory or page frame for
>Task manager. You only lose a few K of memory from what you have in
>conventional when you start a task. I have not really bothered to check it
>recently, why I lose that few K of memory, but it is probanly to the
>resident portion of COMMAND.COM that each task would need. I'll have to
>check that sometime. But I only lose something like 7K and when I am well
>over 600K to start with, it does not hurt anything.


I think you missunderstood me...

TASKMGR doesn't need DPMS! DPMS is only a driver extension like DPMI in
normal applications.
So you can write drivers using Protected mode.

Maybe you mean VXD, which is used in TASKMGR. But they are mostly for
supporting hardware in TASKMGR.

BTW: I don't think that Win9x/ME _can_ support pre-emptive multitasking _in_
the GUI.
It could be provided with DOS programs, but this isn't important for the
Windows world.

WinNT and Linux should have pre-emptive multitasking, like in Dr-DOS.

I hope you understand my poor English.

Bye, Florian
www.drdos.org
www.seal.de.vu