X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Achieving 486 Compatibility
Date: 8 Feb 2004 21:34:42 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 17
Message-ID: <c06a1i$hgh$3@nets3.rz.RWTH-Aachen.DE>
References: <c9d8c82b DOT 0402061604 DOT 50f50de8 AT posting DOT google DOT com> <200402070057 DOT i170v6Rn017051 AT envy DOT delorie DOT com> <c9d8c82b DOT 0402070922 DOT 560051ba AT posting DOT google DOT com>
NNTP-Posting-Host: accip02.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 1076276082 17937 137.226.33.41 (8 Feb 2004 21:34:42 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 8 Feb 2004 21:34:42 GMT
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Radical NetSurfer <RadSurfer AT yahoo DOT com> wrote:
> Could you please shed some light on perhaps why this appears
> to run just fine on a P4, yet only crashes on "lower" machines?

No -- that's something *you'll* have to do, because it's your program,
and only you have the source code necessary to do the bug hunt.  You
didn't even tell what that program is doing, in the first place.

What DJ was trying to tell you was that your suspicion of some
processor type-specific code being the reason of that problem was
probably remature, at least from the few facts you posted so far.  You
effectively used a crystal ball to find the reason of that bug, DJ
suggested you use a proper tool instead.

-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.