|
|
 |
|
 |
 |
 |
 |
 |
 |
|
|
| System
v2 |
 |
| Once I started
writing Basic programs on my 64, I decided
to put them on disks with an index.
The first attempt was quickly replaced. |
 |
| more
. . . . |
|
 |
 |
 |
 |
 |
 |
|
|
| System
v3 |
 |
| Most of my machine
code programs were written for a new
system which included common routines
and menus plus disk and screen handling. |
 |
| more
. . . . |
|
 |
 |
 |
 |
 |
 |
|
|
| Infotext |
 |
| Starting life as
a diary and address book, my first full
machine code program soon developed
into a multi-purpose system in its own
right. |
 |
| more
. . . . |
|
 |
 |
 |
 |
 |
 |
|
|
| As there was little
'serious' software available for the 64 and
I wanted to do more than play games, I quickly
became absorbed in writing my own programs.
Solving problems often meant working through
the night but that was part of the fun. |
 |
 |
 |
| The Vic programs were
all written later, converted from those written
for the 64. The limitations of the Vic, particularly
the screen size, meant that I quickly upgraded
to the 64. |
 |
| Once I started writing
Basic programs on my 64, I decided to put
them on disks with an index. The first attempt
was quickly replaced. System v2 gave each
disk an index page. This was written in machine
code while all the programs were in Basic
but with an exit option to the disk index.
The disk in the drive or the drive could be
changed and the new index loaded, but there
was no built-in method of adding programs
to the index, alterations had to be made manually.
The later System v3 included a program to
update System v2 disks. |
 |
| Most of my machine code
programs were written for a new system, v3,
which included common routines and menus plus
disk and screen handling. This meant that
frequently used routines did not need to be
rewritten for each new program, but could
be called from the system which remained constantly
in memory. A revision of this system, v3.2,
was started but never completed. |
 |
| Starting life as a diary
and address book, my first full machine code
program soon developed into a multi-purpose
system in its own right and became Infotext.
Using a page numbering system similar to Teletext
any number of pages of information could be
stored on disks and called up when needed.
The ability to use up to four disk drives
made this a very flexible system. Infotext
became so much part of my daily life that
most System v3 programs were adapted to be
used within it. |
 |
 |
 |
| Please note that some
of the programs described here have been adapted
from listings in magazines or other sources.
Where possible, acknowledgements are made
on the relevant page. If I have omitted to
mention your name, please let me know and
I will gladly put this right. |
 |
|