Mail Archives: djgpp/1996/12/11/21:38:32
On Tue, 10 Dec 1996, A.Appleyard wrote:
> (1) I had v1. After compiling djgpp programs I prefixed not STUB.EXE but the
> whole of GO32.EXE to A.OUT . The result ran happily under DOS and Windows. But
> recently I changed to v2. And now, when I call those djgpp programs compiled
> by v1 from Windows, they refuse to start. But they still start OK from DOS.
<smile-mode>
Imagine a post like so:
I had a perfectly good kettle. It would boil water and let me drink my
coffee (sorry, tea in the UK) any time, even when I was running Windows.
But now I installed this DJGPP v2 thingy, and my kettle suddenly stopped
working when I invoke Windows. It just sits there and does nothing. WHY
DOES DJGPP v2 DEPRIVE ME OF MY COFFEE???
</smile-mode>
Seriously, people, don't you think you sometimes overestimate the powers
of DJGPP?
> They run OK from Windows and also from DOS on PC's that haven't got a djgpp
> system in.
Did you rename go32-v2.exe which came with v2 to go32.exe? If so, undo
that. AFAIK, stand-alone v1 programs still look for go32.exe and try
loading one if it is found.
If the above doesn't help, please post the exact message printed when you
try to invoke v1 programs on that troubled system.
> calls a separate CWSDPMI.EXE . If I write a program and compile it with djgpp
> v2, and put the resulting .EXE file on a PC that has no djgpp system on: Where
> in that PC do I put a copy of CWSDPMI.EXE?
This is explained in the FAQ (section 9.5). You can put CWSDPMI either
in the same directory as your DJGPP program or anywhere else along the
PATH.
- Raw text -