Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!batcomputer!cornell!vax5.cit.cornell.edu!b39y
From: b39y@vax5.cit.cornell.edu
Newsgroups: comp.databases
Subject: Re: CLIPPERS87 RUN help needed
Message-ID: <1991Apr19.090610.4145@vax5.cit.cornell.edu>
Date: 19 Apr 91 09:06:10 EDT
References: <22328@gremlin.nrtc.northrop.com>
Distribution: comp
Organization: CIT, Cornell University
Lines: 31

In article <22328@gremlin.nrtc.northrop.com>,
maurit@nrtc.nrtc.northrop.com (Mark Aurit <maurit>) writes: 
> Im writing a utility for a user in which they can perform selective
> archiving, and decided to use the DOS BACKUP/RESTORE commands. I wrote
> a standalone program, linking it with TLINK. After getting it working
> I linked it into the main program (using BLINKER), which is fairly
> large (>526K disk space), and the sucker blew on the misc_error about
> RUN processing (on the line prior to the "RUN BACKUP" a MEMORY(0)=64).
> Since I believe it could find command.com, which was comspec'ed, I assume
> its a memory problem.
>  

My first question is: how much memory do you have on this machine.  Second, do
you have a Clipper environment variable set?  If not, try the following before
your program begins:

SET CLIPPER=R48;Fxx;E000   - where xx is the number of files open you need.

Finally, I would strongly urge you to reconsider using DOS BACKUP/RESTORE as
your data backup routines.  If your data are imporant to you, write some
routines in Clipper to do the backup yourself, or use a different backup
program.  I have had very little luck in getting data off of disks written to
by DOS BACKUP.

Good luck, and post or email if you have more questions/clarifications.

Dave Rodger
Applications Programmer, Cornell University
b39y@vax5.cit.cornell.edu