From: "news.det.ameritech.net" Newsgroups: comp.os.msdos.djgpp Subject: Windows 2000 and DJGPP Lines: 27 Organization: Test Products, Inc. X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.00.2919.5600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.5600 Message-ID: Date: Thu, 7 Oct 1999 13:43:00 -0400 NNTP-Posting-Host: 206.141.213.223 X-Trace: nntp0.detroit.mi.ameritech.net 939318543 206.141.213.223 (Thu, 07 Oct 1999 13:49:03 EDT) NNTP-Posting-Date: Thu, 07 Oct 1999 13:49:03 EDT To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com I'm using DJGPP 2.02 (gcc 2.95.1) on Windows 2000 RC2 build 2128. Here's the problem: DJGPP-built programs that call other programs have a tendency to crash with a message similar to the following (this was made by DJGPP's stock `make'): --- cut here --- ntvdm.exe - Application Error The instruction at "0x0f048cfc" referenced memory at "0x01c00ffc". The memory could not be "written". --- cut here --- The problem appears to be in the VDM, but I thought perhaps someone might have ideas about what could be causing the problem and how it could be circumvented. If not, at least you'll be warned about it in case the VDM problem isn't fixed when Win2k ships... I've seen this with Windows 2000 Beta 1, Beta 2, RC1, and RC2; DJGPP 2.02 with gcc 2.8.1, egcs, and gcc 2.95.1; LFN in djgpp.env set to `n' (Win2k supports the LFN API for DOS programs); the shell as command.com, cmd.exe, 4nt.exe, cmd.exe running command.com, and 4nt.exe running command.com. `make' is the most noticeable program with this problem, but I've also seen it occur occasionally while running gcc directly. Any ideas? Other than running a non-beta OS? :)