Message-Id: <3.0.1.16.19990124133814.1d7f6a6e@shadow.net>
X-Sender: ralphgpr AT shadow DOT net
X-Mailer: Windows Eudora Light Version 3.0.1 (16)
Date: Sun, 24 Jan 1999 13:38:14
To: djgpp AT delorie DOT com
From: Ralph Proctor <ralphgpr AT shadow DOT net>
Subject: Re: DOS Box clear-up
In-Reply-To: <Pine.SUN.3.91.990124192330.9257B-100000@is>
References: <3 DOT 0 DOT 1 DOT 16 DOT 19990124113513 DOT 26af1cee AT shadow DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Reply-To: djgpp AT delorie DOT com

At 07:26 PM 1/24/99 +0200, you wrote:
>
>On Sun, 24 Jan 1999, Ralph Proctor wrote:
>
>> Now, would you state if it is true that it is possible to run in DOS on a 
>> Windows 95 and above machine WITH NO INTERFERENCE OR
>> INVOLVEMENT FROM Windows?
>
>I'm not really sure what you are asking about.
>
>In general, Windows will *always* have something to say when you run your 
>programs from Windows.  All the business of creating virtual machines, 
>servicing interrupts, handling files, disk cache, etc.--all of this is 
>done by parts of Windows on your behalf.  You cannot avoid Windows.
>
>Now, what specific details bother you in this setup?
>
>> I have my doubts that you can EVER have DOS with clean memory with
>> Windows 95. If I am wrong, I will be so happy to hear it.
>
>What exactly do you mean by ``clean memory''?

>I'm not really sure what you are asking about.
>
>In general, Windows will *always* have something to say when you run your 
>programs from Windows.  All the business of creating virtual machines, 
>servicing interrupts, handling files, disk cache, etc.--all of this is 
>done by parts of Windows on your behalf.  You cannot avoid Windows.
>
>Now, what specific details bother you in this setup?

>What exactly do you mean by ``clean memory''?

Here is a real and tested example:

Some perfectly good DOS flight simulators that have quite sophisticated
sound and graphics just will not work under the following conditions--

1. boot up
2. bring up windows (and do whatever)
3. get out of windows by alt-F4 or the file menu. Window is now OFF!!
4. you are now back in DOS.

Now, some the the memory is still being held onto by Windows.

None of my worry has anything to do with RUNNING anything from Windows

In the above case the programs work perfectly in DOS before you turn on
Windows.

This problem has been confirmed by other programmers that know more about
it. I cannot explain it except to say that Windows does not let go of some
of its
memory

I am afraid that this will ALWAYS be case with Windows95 whether you
use a Win95 application or not before you work with your DOS code or
run your DOS program.