LL> DS> Does anyone know the error message of GP0000 AT Pdoxwin:B4:00C4 mean?
LL>Yeah!  Nothing much, other than there was a general protection fault at
LL>that address.  This is Windows' rather unhelpful way of saying that 
something
Just a dare... ...perhaps it's the Forest not the Trees.
I went through an outrageous session with a similar problem,
used Borland C's 'InSpecter' which really sent me into and
endless research loop.  A memory glitch/overrun at that specific
address may be caused by something else more basic, like....
some Windows-Phobe asked me, "what's your STACKS= in CONFIG.SYS??
Windows is sensitive here where others handle their own stacks."
So!  I increased the default (9,128 means nine stacks, 128 bytes deep)
to 12, 256 and have had no repeat problems (knock, knock).
This was most likely the problem since my error happened when
clicking between windows/apps.  Unless stacks are at 0,0 each
hardware interrupt (mouse, disk call, etc) causes MSDOS to use
a stack. (see online DOS propaganda).  Maybe some technocrat
can tell you what the REAL PROBLEM is, but checking your stacks
can be a cheap, low-tech solution to get you moving.
---
 * SLMR 2.1 * today's classroom philosophy is tomorrow's governments'
--- QScan/PCB v1.16b / 01-0024
---------------