Msg: 2937 *Conference*

07-30-92 18:20:40

From: RICHARD HANSON

To : DERWOOD TWIGG

Subj: REPLY TO MSG #2918 (LIB XFER W/ YMODEM BATCH)

-----
Derwood: I've got the strangest feeling that you are using Lapdos II to
transfer an ASCII file with a .BA extension into your Model 100.  When you do
that, your Model 100 will cold start, and that's a fact.  Sounds a little like
what's happening, huh?!
 
Using the method you've described, wherein you use your DOS computer do batch
download files, you end up with BASIC program files on your DOS computer with
the wrong extension for your Model 100 computer.  FACT: You've done nothing
wrong.  So far so good... but... all files on this BBS as in ASCII (.DO) even
when they have a .BA extension.  Your DOS computer does not care, but your
Model 100 computer will cold start on any ASCII file with a .BA extension.
Here is a sequence of events you MUST follow to keep from cold starting your
Model 100 with files downloaded via your DOS computer from this BBS.
 
---
 
Let's take a program called BUD.BA from the music category of the library as an
example.
 
1) You download BUD.BA to your DOS computer via ymodem batch and the
filename.extension comes with the file.
 
2) Rename BUD.BA to BUD.DO.
 
3) Use Lapdos II to move BUD.DO into your Model 100.
 
4) Go into BASIC on your Model 100 and issue the command: LOAD"BUD.DO" or just
LOAD"BUD ... this will load the BUD.DO (ASCII) file into the BASIC interpreter,
where it will become a tokenized file.
 
5) Wait for the WAIT light to stop flashing and the OK to return.  Then, issue
the command: SAVE"BUD.BA" or jist SAVE"BUD ... this will save the now tokenized
code as a "real" .BA file from the Model 100's point of view.  When you return
to the menu you will have a BUD.DO and a BUD.BA file in the menu.
 
6) Use Lapdos II once again to move the BUD.BA file from your Model 100 to your
DOS computer for stoarge.  You may delete the BUD.DO file from both computers
at any time after tokenization.
 
---
 
So, now you know the score.  You MUST perform the tokenization task for EVERY
program file you download from the Club 100 BBS.  But that's not the end of the
story.
 
When you encounter a program file and its associated documentation file, you
have a bit more work.  After downloading both files onto your DOS computer you
may have something like (example) MINIVC.BA and MINIVC.DO.  The .BA file is the
program code in .DO (ASCII) format, and the .DO file is the
documentation--which must remain in ASCII.  But wait, if you rename .BA to .DO
you can't have to MINIVC.DO files in the same directory!!  What do you do?  I
suggest the following scheme:
 
1) Rename the .DO file to .DOC and the .BA file to .DO
 
2) Lapdos the .DO file over to the Model 100, tokenize it, then Lapdos it back
to the DOS computer as a true .BA file.
 
3) Delete the .DO version from both computers.
 
Happy tokenizing... -Rick-
 
PS: Remember when you asked me what I would charge for a tokenized version of
the Club 100 library of over 1,000 files on diskettes?  Do you now understand
why I said "no way!"