Mail Archives: djgpp/2001/03/05/09:34:19
On Mon, 5 Mar 2001, Michael Allison wrote:
> > Well, what's so surprising in that? Separate processes are created
> > for each program even on plain DOS. As long as the processes run in
> > the same Virtual Machine, we should be okay. (If they don't run in
> > the same VM, all heck will break lose on us much sooner...)
>
> If you're convinced that its a wild goose chase, I'll turn away from
> investigating that.
It seems a rather improbable cause to me.
> > Even if this is true, we still need to explain how come it never
> > shows on any other platform, including NT4. Spawning child
> > processes is by far the most frequent thing people do with
> > DJGPP, since compiling programs involves it.
>
> A rather odd set of statements, since the same thing could be
> said of *whatever* is causing this problem. Something is
> obviously different under Windows 2000. What was your point here?
My point was that creating separate processes is something that happens
on all platforms, and yet only W2K crashes because of that. Since W2K
is juts another version of NT, it seems unlikely that just creating a new
DOS process will cause the crashes.
> http://support.microsoft.com/support/kb/articles/Q288/1/65.ASP
> The fix replaces the ntvdm.exe. I tried it out.
> While it does fix the problem the other folks were having,
> it does not fix the djgpp problem unfortunately.
Yes, 16-bit DPMI memory management is not relevant for DJGPP.
> If anyone has a new lead, I can put more time towards this,
> but I'm leaving it for now.
The lead I can suggest is to try to disable and/or modify the way DJGPP
programs set up exceptions and hardware interrupts in their startup code
(see the files dpmiexcp.c and exceptn.S in djlsr203.zip), as Charles
Sandmann suggested here a few days ago. I hope that someone with access
to a W2K machine and motivation to solve this problem will pursue this.
Using programs compiled with MSVC is not a work-around I would suggest to
DJGPP users.
- Raw text -