Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!vsi1!altos!gumby!jerry
From: jerry@gumby.Altos.COM (Jerry Gardner)
Newsgroups: comp.os.msdos.programmer
Subject: Re: RAM Disk Problem with TC++
Message-ID: <4682@gumby.Altos.COM>
Date: 6 Feb 91 18:07:12 GMT
References: <4662@altos86.Altos.COM> <12879@hubcap.clemson.edu>
Reply-To: jerry@altos.COM (Jerry Gardner)
Organization: Altos Computer Systems, San Jose, CA
Lines: 26

In article <12879@hubcap.clemson.edu> grimlok@hubcap.clemson.edu (Mike Percy) writes:
}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.  

Further clarification:  I don't have long functions (poor programming
practice...) and I have 580KB free after loading DOS.

}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.

As I said, I have no long functions.  The program compiles fine from hard
disk (VDISK is installed in this case, just not used).  As I said in the
initial post, I have no TSRs whatsoever.