>
>
> On Tue, Jan 20, 2026 at 12:44 PM B9 <[email protected]> wrote:
>
>> I'm glad you figured it out. Yes, MAXFILES is one of the things we should
>> warn people new to the Model-T about. By the way, most of the commands that
>> can refer to devices have sane defaults, so if you just specify a filename
>> for OPEN, it presumes "RAM:".
>>
>
On Tue, Jan 20, 2026 at 1:36 PM John R. Hogerhuis <[email protected]> wrote:
>
> The other ones everyone inevitably stubs a toe on:
>
> - How to use CLEAR to reserve space for a CO and for strings
> - DIM
> - BA versus DO
> - Only two-character significant identifiers for a given sigil (and only
> if given / not using DEFINT/DEFSTR)
> - Doing a cold start to clear corrupted memory
>
Yup, those have all bit me at one time or another. CLEAR to reserve string
space has bitten me several times. Also, I still get mixed up on
the symbols ("sigils" you say?) to make variables integer/single/double
precision.
- The filesystem is in RAM
- Cold restart clears RAM, erasing all files
- Once SAVEd to a .BA, future edits are saved immediately
- FILES shows the current BASIC filename with an asterisk*
- Power button doesn't work? Change the backup battery
- The AC adapter is *negative* tip
—b9
