🚀 go-pugleaf

Leigh Milne <lmilne@adelaide.on.net> wrote:

[code works  under Win95, crashes under XP]

>I am not asking with help on my specific code (unless that seems the 
>only way to progress), rather I am asking if there is information 
>somewhere that documents problems likely to arise in situations like this.
>
>Is there??

Not that I'm aware of. The problem you probably have is that the Windows
NT operating system family (NT 3.51, NT 4, NT 5 (aka 2000), NT 5.1 (aka
XP)) have true inter-process barriers, true memory protection, etc. etc.

The 16-bit Windows family, including Windows 3.0, Windows 95, Windows 98
and Windows ME, don't. You can write to memory that a different program
owns. You can read from it. You can accidentally have a pointer pointing
off into the middle of nowhere, and yet you can store data there (as
long as that memory physically exists).

Basically, the problem you (almost certainly) have is that your code has
always had a bug in it, it's only that the strict rules brought in with
the 32-bit OS now mean that it's your program that crashes, not some
other program some time later.

Alan Bellingham
-- 
ACCU Conference 2006 - 19-22 April, Randolph Hotel, Oxford, UK