Path: utzoo!utgpu!watmath!clyde!att!rutgers!sunybcs!bingvaxu!vu0112 From: vu0112@bingvaxu.cc.binghamton.edu (Cliff Joslyn) Newsgroups: comp.sys.ibm.pc Subject: Turbo C 2.0 and EMS Message-ID: <1624@bingvaxu.cc.binghamton.edu> Date: 4 Dec 88 05:39:57 GMT Organization: SUNY Binghamton, NY Lines: 28 So I have TC 2.0 and I just got 256K of EMS, and I *really* want to be able to use it during compilation and linkage in the integrated environment. Once I get the MKS shell, Sidekick, and Superkey (all of which are critical to my productivity) all loaded in, and then add in the 290K for tc.exe, I've got about 100K left for compilation and linkage. I bomb with out of memory for even very small programs. I'd run from command line, but then I lose the debugger. I find no obvious way to get the thing to link in EMS or have it swap pieces to disk during linkage. I mean, that shouldn't be a problem, right? Doesn't it run my target .exe from disk anyway? I find it necessary now to 'exec command.com' (25K vs. 73K for sh.exe) before loading tc.exe. But this can only be a temporary fix anyway, because once my target .exe grows by 50K I'm still dead. Even if I were running lean and mean without sh.exe and my TSRs, tc.exe only leaves some 300K for the user's program, with debug code. This seems to leave the integrated debugger useless for seriously large code unless TC 2.0 can use above 640K. Help!? -- O----------------------------------------------------------------------> | Cliff Joslyn, Cybernetician at Large | Systems Science, SUNY Binghamton, vu0112@bingvaxu.cc.binghamton.edu V All the world is biscuit shaped. . .