home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.programmer.tools
- Path: sparky!uunet!think.com!yale.edu!jvnc.net!nuscc!vms1.iscs.nus.sg!nuscss1
- From: nuscss1@vms1.iscs.nus.sg (Vax BULLET-IN-Board SysOps)
- Subject: Re: Problem with Borland's Turbo Debugger for Windows : HELP!
- Message-ID: <19NOV199201082045@vms1.iscs.nus.sg>
- News-Software: VAX/VMS VNEWS 1.41
- Sender: usenet@nuscc.nus.sg
- Organization: National University of Singapore Dept. of Computer Sc.
- References: <16NOV199223050853@vms1.iscs.nus.sg> <1992Nov16.162408.23622@mksol.dseg.ti.com>
- Date: Wed, 18 Nov 1992 23:08:00 GMT
- Lines: 29
-
- In article <1992Nov16.162408.23622@mksol.dseg.ti.com>, mccall@mksol.dseg.ti.com (fred j mccall 575-3539) writes...
- >
- >You are apparently running an old version of Borland C++ (telling us
- >the versions of Borland C++ and Windows you are running would have
- >been helpful). I am assuming you are running Borland C++ 3.0 and
- >Windows 3.1 on these machines.
-
- you're right on target: I am running BC++ 3.0 with Windows 3.1.
-
- >You need to either patch the debugger
- >(which still leaves some things not working quite well between Borland
- >C++ and Windows 3.1, as I understand it) or you need to upgrade to the
- >current version of Borland C++ (3.1).
-
- o rats! more $$$. the guys in the office won't be happy when they
- hear this... =-)
- >
- >Just by the way, where did you get 3 OLD copies of Borland C++ that
- >you are just now trying to load on machines?
- >
- My employer bought them. But then again, these copies
- were bought a while back when they were coding for Windows 3.0.
- I guess upgrading the compiler was not high on their priority list...
-
- >--
- >"Insisting on perfect safety is for people who don't have the balls to live
- > in the real world." -- Mary Shafer, NASA Ames Dryden
- >------------------------------------------------------------------------------
- >Fred.McCall@dseg.ti.com - I don't speak for others and they don't speak for me.
-