From: "A. Sinan Unur" Newsgroups: comp.os.msdos.djgpp Subject: Re: Exclusive access to drive Date: Thu, 05 Jun 1997 12:12:18 -0400 Organization: Cornell University Sender: asu1 AT cornell DOT edu (Verified) Message-ID: <3396E562.141@cornell.edu> References: <5n6bav$l1f AT news DOT ox DOT ac DOT uk> 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: 44 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Precedence: bulk George Foot wrote: > > Eli Zaretskii (eliz AT is DOT elta DOT co DOT il) wrote: > > Hmm, I've been following this for a while, and I just booted into > Win95 and tried a few things I haven't seen discussed yet. Firstly I > confirmed the problem existed on my system. Then, I wrote a short > program which waited for a keypress, and tried running chkdsk in > another DOS box - it worked fine. Then, I made a program to > system("command") and ran chkdsk from that command prompt. The problem > recurred. > > These show a few things: > > 1) It's not just Windows' reaction to running DPMI programs (chkdsk > still works when a DPMI program is running) > > 2) It's not because chkdsk is being directly spawned by the DPMI > program > > I also tried using PFE to execute CHKDSK (worked fine) and to start a > DOS prompt and chkdsk there (again, it worked fine). > > Perhaps someone with Watcom could try a similar program there and see > whether it suffers the same way? i also verified all those. however, i think what is more significant is the fact that the program #include int main(void) { return system("chkdsk"); } works correctly when compiled using gcc -Zwin32 chk.c -o chk.exe (using the original ld.exe) with rsxntdj 1.3.1. i am not sure what this shows. any ideas? -- Sinan