Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!sdd.hp.com!caen!uwm.edu!ux1.cso.uiuc.edu!news.iastate.edu!sharkey!tygra!dave From: dave@tygra.Michigan.COM (David Conrad) Newsgroups: comp.lang.pascal Subject: Re: Just for kicks Message-ID: <1991May27.044742.5844@tygra.Michigan.COM> Date: 27 May 91 04:47:42 GMT References: Organization: CAT-TALK Conferencing System, Detroit, MI Lines: 33 In article mg2n+@andrew.cmu.edu (Martin G. Greenberg) writes: >So far I have gotten a number of suggestions/comments including: > > 1) You need the "/B" to tell DOS that its a binary file > 2) Make sure the printer is hooked up right, turned on, etc. > 3) Make sure there is a "Files = nnn" in the CONFIG.SYS file. > 4) Check the available memory (i.e. $M directive problems) ~~~~~~~~~~~~~~~~~~~~~ > 5) Path length exceeding maximum > >Unfortunately, all these have been checked repeatedly (the lack of >a "/B" was a oversight in the post and is present in the code) or >do not apply due to the fact that the installation routine takes >care of directory/path setup. > >Further ideas? > > MGG Check the available DOS! memory. Is there enough memory left over for DOS to start up another COMMAND.COM? If there isn't, it won't work. Let's say your program uses 200k of code+data and 100k of heap, so 300k altogether. If there's only 301k of memory available before your program runs then it isn't going to work. If there's 500k free to begin with, then it will. Even though you may have, say, {$M 16384,65536,131072}, DOS may still not have sufficient memory to perform the copy. -- David Conrad, dave@michigan.com -- = CAT-TALK Conferencing Network, Computer Conferencing and File Archive = - 1-313-343-0800, 300/1200/2400/9600 baud, 8/N/1. New users use 'new' - = as a login id. AVAILABLE VIA PC-PURSUIT!!! (City code "MIDET") = E-MAIL Address: dave@Michigan.COM