Back to "Programming the Tomy Tutor" | Back to the main page
| Err# | Manual Definition | Which Really Means |
| 1 | NUMBER TOO BIG FOR COMPUTER | In conventional BASIC terms, this is an overflow error. |
| 2 | COMPUTER DOESN'T UNDERSTAND WHAT YOU TOLD IT | Syntax error. |
| 3 | YOU FORGOT A QUOTATION MARK ON THE LINE | Syntax error, but a bit more specific. |
| 4 | NAME OF VARIABLE IS TOO LONG -- 15 CHARACTERS MAX | Says it all. |
| 5 | NOT USED YET | Undocumented error. |
| 6 | YOU MAY HAVE FILLED UP THE COMPUTER'S MEMORY (SHORTEN YOUR PROGRAM) | Out of memory; could also be due to a stack overflow, though that would take a lot of work. |
| 7 | LOOPS NOT DONE PROPERLY | Crossed loops (something like FOR X=1 TO 10/FOR Y=10 TO 10/NEXT X/NEXT Y). |
| 8 | HAVE A "NEXT" BUT NO "FOR" IN A LOOP | Like it says. |
| 9 | HAVE A "RETURN" BUT NO "GOSUB" | Idem. |
| 10 | YOU TOLD COMPUTER TO WORK WITH A LINE # NOT IN PROGRAM | Undefined statement error. |
| 11 | ERROR IN WRITING LINE # | Bad line number (probably negative). |
| 12 | LINE # TOO BIG (32767 IS LARGEST ALLOWED) | Bad line number (overflow). |
| 13 | COMPUTER CAN NOT DO CONTINUE YOU ASKED FOR | That was a verbatim sentence. Can't continue from the breakpoint (probably you modified the program and tried to CONT from there). |
| 14 | YOU PUT A LINE # ON SOMETHING THAT CAN ONLY BE COMMAND (10 LOAD) | Illegal direct error. Direct mode commands (see Command Summary) are illegal in programmatic execution. |
| 15 | THERE IS NO PROGRAM TO RUN | Stupid, huh? |
| 16 | BAD VALUE | Uncertain. Never encountered. |
| 17 | INPUT ERROR -- COMPUTER CAN'T READ WHAT YOU GAVE IT | Entered alphanumerics when it was expecting just numbers; equivalent to C64 ?REDO FROM START or Apple ][ REENTER. |
| 18 | DATA ERROR -- WRONG # ELEMENTS OR WRONG TYPE IN DATA | You tried to READ in data and caused a type mismatch (read a string into a numeric variable) or you ran out of data. |
| 19 | NOT USED YET | Undocumented error. Dave Brain's experimentation with the # operator for the Tomy's non-existent I/O, plus ROM disassembly I performed for developing Tutti II, implies this is really a generic I/O error. |
| 20 | PRINTER NOT CONNECTED TO COMPUTER | Triggered by LLIST and LPRINT because the printer for the Tutor never emerged, plus various iterations with the # token. |