Why bother with the larger .do copy? Just load "foo" and then save "foo2". Now you have both foo.ba and foo2.ba, both in small tokenized form.
On Sun, May 27, 2018, 3:27 PM Peter Vollan <[email protected]> wrote: > Perhaps they mean that you should print it out? > > > On 27 May 2018 at 11:06, David Szasz <[email protected]> wrote: > > Jason: > > > > Sorry about that as NAME only renames the existing file (I forgot). The > old > > tried and true model 100 method is to save the BASIC file as text using > the > > ".DO" appendage > > > > from within the BASIC program type > > > > SAVE "newfilename.do" > > > > Then as needed open the text file and rename it as a BASIC program using > the > > ".BA" appendage > > > > On Sun, May 27, 2018 at 1:20 PM, David Szasz <[email protected]> wrote: > >> > >> jason: > >> > >> You can just save the file under another name. See the NAME command. > >> > >> NAME "old filename" AS "new filename" > >> > >> I hope that helps a little. > >> > >> D. Szasz > >> > >> On Sun, May 27, 2018 at 12:23 PM, Jason Benson < > [email protected]> > >> wrote: > >>> > >>> Hey guys, is there anyway to make a copy of a BASIC file so that you > have > >>> a backup other than saving it to another machine or external storage? > >>> > >>> Per the manual : > >>> > >>> In the Model 100 there usually is no backup copy. You > >>> should make one for important documents as early as > >>> possible. > >>> > >>> But that seems crazy. Would it be possible copy the text of the program > >>> and then paste it in a new ram file? That would give it a new memory > >>> address, but I'm not sure how. > >>> -Jason > >>> > >>> > >>> > >> > > >
