Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!nstn.ns.ca!news.cs.indiana.edu!cica!bronze!sol.ctr.columbia.edu!emory!hubcap!grimlok
From: grimlok@hubcap.clemson.edu (Mike Percy)
Newsgroups: comp.os.msdos.programmer
Subject: Re: RAM Disk Problem with TC++
Message-ID: <12879@hubcap.clemson.edu>
Date: 1 Feb 91 17:16:15 GMT
References: <4662@altos86.Altos.COM>
Organization: Clemson University, Clemson, SC
Lines: 23

In article <4662@altos86.Altos.COM> jerry@altos86.Altos.COM (Jerry Gardner) writes:
 
[TC++ locking up using VDISK]
 
I had similar problems.  My problem had to do with how TC++ compiles
function-at-a-time in memory.  I had some long functions (generated by
compiler-compiler tool), that compiled fine until I started using more
BUFFERS= and FILES= in my CONFIG.SYS.  Seems these buffers took up just
enough room to make it impossible for TC++ to compile the large
functions entirely in memory (TC++ does not write out object code until
the whole function is compiled, and does not swap its data to disk), and
it would hang with garbled messages, required a reboot.  
 
Perhaps you have functions approaching the useful limit.  Adding VDISK
(which does take up some room in the 640K) pushes the limit down, and
now things don't work.  The best thing to in this case is to get as much
of the 640K for use as possible -- load things into high memory if you
can, balance the need for TSR's against doing useful work, etc.

"I don't know about your brain, but mine is really...bossy."
Mike Percy                    grimlok@hubcap.clemson.edu
ISD, Clemson University       mspercy@clemson.BITNET
(803)656-3780                 mspercy@clemson.clemson.edu