home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky alt.msdos.programmer:2716 comp.os.msdos.programmer:10540 comp.sys.ibm.pc.programmer:577
- Newsgroups: alt.msdos.programmer,comp.os.msdos.programmer,comp.sys.ibm.pc.programmer
- Path: sparky!uunet!destroyer!ncar!noao!coyote!jmh
- From: jmh@coyote.datalog.com (John Hughes)
- Subject: ARRRGH! Turbo-C++ is driving me NUTS!
- Message-ID: <1992Nov11.194032.8128@coyote.datalog.com>
- Followup-To: comp.sys.ibm.pc.programmer
- Keywords: borland turbo c++ dos migraine
- Organization: order is illusion, chaos is reality.
- Date: Wed, 11 Nov 92 19:40:32 GMT
- Lines: 41
-
-
- I really do need some help with this one...
-
- It all started when I discovered that I couldn't run Turbo C++ over a
- two machine network (Artisoft Lantastic). That was dealt with by
- installing a thingy that allowed me to send a command to the server,
- which would then run the compiler (via make or whatever) for me. Very
- clumsy, and I get tired of peering across the room to see what the
- compilation messages say. So, in a burst of inspiration, I moved the
- tcc binaries, libraries, and sources to the workstation, which I
- really didn't want to do (kinda defeats the purpose of having a file
- server with lots of disk space, you know what I mean?).
-
- It *still* won't work correctly. Even if I shut the net down and don't
- load the netbios TSR's, tcc gives me a bizarre error when run on the
- workstation machine. The linker says that I have an invalid group
- definition *in one of the Borland library modules* !!! Not only that,
- but the compiler and linker work just fine on the server. Ah, but it
- gets better... the error "moves" from module to module (I'm really
- starting to twitch and slobber).
-
- I'm the only person using the network, and its primary role in life
- is to test multi-user database packages, so it's not like there's any
- kind of major load on it. I've also run every diagnostic I have on
- both machines (and I have a LOT) and they both come up with a clean
- bill of health. The config.sys has plenty of buffers and files
- defined, and the command line shell on both is 4DOS 4.0 running on
- top of MSDOS 3.3 (if you do commercial software development you'll
- understand why MSDOS 3.3 is being used here). The only real diff.
- between the two is that the server has 1.5 Mb of extended memory.
- That, however, shouldn't make a difference. I've run tcc on what is
- now the workstation for over two years, with no bizarre problems.
-
- Someone, somewhere, help me... please!
-
-
- --
- ==============================================================================
- | John M. Hughes P.O. Box 43305 Tucson AZ 85733 USA |
- | ......... Insert _your_ favorite witty quote here ......... |
- | jmh%cerberus.uucp@noao.edu ...noao!cerberus!jmh jmh@moondog.datalog.com |
-