Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!mit-eddie!uw-beaver!ubc-vision!alberta!calgary!ingoldsby
From: ingoldsby@calgary.UUCP
Newsgroups: comp.sys.m6809
Subject: Re: LOAD those PACKed RUNB files!
Message-ID: <890@vaxb.calgary.UUCP>
Date: Tue, 28-Apr-87 12:46:50 EDT
Article-I.D.: vaxb.890
Posted: Tue Apr 28 12:46:50 1987
Date-Received: Fri, 1-May-87 01:00:23 EDT
References: <1639@ihwpt.ATT.COM>
Organization: U. of Calgary, Calgary, Ab.
Lines: 40
Keywords: BASIC09, Level 1 and 2, RUNB
Summary: A different fix

In article <1639@ihwpt.ATT.COM>, knudsen@ihwpt.ATT.COM (mike knudsen) writes:

> Problem is this: You PACK several Basic09 procedures
> into one file (or MERGE them together later, maybe
> adding some machine-code routines like INKEY or GFX2
> or your own).
> 	With this file in your /CMDS, say named ZORCH,
> you should be able to type just "ZORCH" and OS9 will
> pull in RUNB to execute it.  Well, not quite.
> You'll get the "unknown procedure" error.
> 	Reason: OS9 (or Shell) loads the first module
> in the file and immediately starts to execute it,
> forgetting about the rest of the file.  That is,
> once RUNB is loaded, OS9 looks for the rest of the
> procedures in /CMDS and your pwd, but ignores the
> rest of your merged file! 

I haven't yet played with Basic09 on Level II, but the key to overcoming
this is the order in which the modules are specified to the PACK command.
I don't have the documentation with me, but it seems to me that one can
either specify the first module to be executed is the last in the file
(meaning that all others are loaded first) or that (here my memory gets
foggy) the trick is to make certain that the first module to be executed
is the last module edited (ie. the one with the * beside it when you do a
dir), then pack *.  I know it can be made to work automatically since
my text formatter (tformat) works just fine this way, even under level II
(it was `compiled' under Level I).  If anyone wants the details I will
look them up for you.

Does anyone know if there is some trick to making the bit banger serial
port read data.  It is really weird.  I'm using the same cable as I used
for level I, but it can't read.  What is really weird is that if I say
        copy  /T1  /TERM
then typing at a terminal causes the character typed to be echoed back to
the terminal (implying that the computer received and understood the
character) but never does anything appear on the screen.  I also tried
sending it to /w and /w7 but that didn't help.  Can anyone help me?

                                  Terry Ingoldsby
                              ihnp4!alberta!calgary!ingoldsby