Mail Archives: djgpp/1994/07/30/18:09:50
Hi everybody.
Long, long ago (at least 2 months now) I decided I wanted to tweak GO32
to do some decent command line processing for me (not just the dumb sort
done by the Borland startup code). So I went (electronically) and bought
Turbo C++ 3.0 and then Turbo Assembler 4.0 both for bargain prices.
First I built GO32 using the linker that comes with Turbo C++, which is
version 5. It built fine but then Turbo Debugger (comes with the
assembler, version 4) refused to load the program, complaining about
wrong linker version.
Somewhat surprised (after all, a _newer_ debugger should understand
_older_ symbol info?!) but still fearless I switched to the linker
included with TASM, which is version 6. The first glitch appeared when I
tried to use TCC to run the linker: a message 'Unhandled exception 000D'
followed by the D"OS" patented automatic reboot. Well, said I, no problem
- just some unfounded expectations about DPMI probably. Run TLINK by
hand, and got message like 'Bad object record from EVENT.C at or near 0x780'.
Yuck!!!!!!!!!!!!! F...!!!!!!!! Just _what_ does Borland
International, Inc. expect me to do? Please calm me before I go to Scotts
Valley with a bomb in my briefcase! :-((
PS.: Without debug info, the build succeeds with TLINK 6 and the
resulting GO32 seems to work. So the problem again seems to be debug
information format.
Ian T Zimmerman +-------------------------------------------+
P.O. Box 13445 I With so many executioners available, I
Berkeley, California 94712 I suicide is a really foolish thing to do. I
USA +-------------------------------------------+
- Raw text -