From: Eli Zaretskii Newsgroups: comp.os.msdos.djgpp Subject: Re: DJGPP and Win2K Date: Sun, 2 Apr 2000 09:25:32 +0200 Organization: NetVision Israel Lines: 27 Message-ID: References: <3vkvdso90jkqkdvo4jqhrshe5tch725ahr AT 4ax DOT com> NNTP-Posting-Host: is.elta.co.il Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: news.netvision.net.il 954660485 19115 199.203.121.2 (2 Apr 2000 07:28:05 GMT) X-Complaints-To: abuse AT netvision DOT net DOT il NNTP-Posting-Date: 2 Apr 2000 07:28:05 GMT X-Sender: eliz AT is In-Reply-To: <3vkvdso90jkqkdvo4jqhrshe5tch725ahr@4ax.com> To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Mon, 27 Mar 2000, Damian Yerrick wrote: > On Sun, 26 Mar 2000 08:57:25 GMT, "NLS" wrote: > > >when I compile with DJGPP under win2k, ntvdm crashes.. > > This is because NTVDM 5 doesn't like DJGPP programs calling DJGPP > programs. It's also because Micro$$$oft would rather that you use > Micro$$$oft Visual Crap++. Here's an idea (and a plea ;-) for a simple but very useful project: find out what exactly causes NTVDM to crash when a DJGPP program invokes another DJGPP program. This involves downloading the library sources (v2/djlsr203.zip), pulling dosexec.c file out of it, writing a small test program that invokes another DJGPP program, then tracing the execution of dosexec.c functions, either in a debugger or with added printf statements, and reporting here where exactly does that crash happen. I don't have access to Windows 2000, so I cannot do this myself. Knowing where the crash happens is a necessary first step towards looking for a work-around. If you care about DJGPP being workable on W2K, please help us solve this nuisance. Thanks in advance!