From: "A. Sinan Unur" <asu1 AT cornell DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: chkdsk, djgpp and win 95 (was Re: Exclusive access to drive)
Date: Sun, 08 Jun 1997 12:57:32 -0400
Organization: Cornell University
Sender: asu1 AT cornell DOT edu (Verified)
Message-ID: <339AE47C.301B@cornell.edu>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 970608175451 DOT 14590D-100000 AT is>
Reply-To: asu1 AT cornell DOT edu
NNTP-Posting-Host: 128
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 40
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Eli Zaretskii wrote:
> 
> On Wed, 4 Jun 1997, A. Sinan Unur wrote:
> 
> > work correctly when compiled with 16 bit msvc 1.52 and 32 bit msvc 4.0,
> > it also works correctly when compiled using
> >
> > gcc -Zwin32 chk.c -o chk.exe
> 
> This probably means that Microsoft still needs chkdsk to run from
> Windows-aware programs, since otherwise it won't run from the DOS box
> either.  What we need is to understand how do they differentiate
> between the different programs.  It would be interesting to see what
> happens when you compile that trivial 5-liner with a real-mode DOS
> compiler such as Turbo C and then run it from the DOS box on Windows
> 95.

well, msvc 1.52 _is_ 16-bit, and the program was compiled as COM. i
really do not see what additional information compiling with Turbo C
would provide. here is the summary once again:

the program:

#include <stdlib.h>

int main(void)
{
 return system("chkdsk");
}

results:

plain djgpp exe                         ... not ok
msvc 4.0 win32 console exe              ... ok
msvc 1.52 16-bit com                    ... ok
rsxntdj 1.3.1 + djgpp win32 console exe ... ok

all programs run in different dos boxes.

 -- Sinan