finished, you will understand how to write your own programs.
Also, get programs from the INMC library, and don’t just put
them in and run them, but read them carefully until you understand
THEY DON’T WORK – OR DO THEY?
After many hours of soldering,
Building up my Nascom one,
I waited for your newsletter,
Hoping for programs to run.
Eventually the postman called
With a letter just for me,
And I really was delighted,
With Mastermind and a mystery.
There I sat at the keyboard,
All day and half the night,
But mastermind prints MARKING ERROR,
And the lolly lady moves at the speed of light.
Well I wonder where the fault lies,
Is it you or is it me,
After which I reconsider –
There can’t be bugs at the INMC.
So, I’ve put my pen to paper,
With a cry for help, to you,
Hoping you can solve my problem
Before I burn out my VDU.
R A E Milton
We received a couple of letters saying that the programs don’t
work, but we received lots of letters saying that they do! We
can only suggest that Mr Milton check his programs again, Also
as explained in “Little known facts” in Issue 4, the L command
can be a great help in entering long programs by hand,
If you have still not got the free programs running, then we
suggest you read the letter below. All you need then do is tabulate
the non-working program, compare the checksums that are
now displayed against the listing, then correct any errors,
Simple, isn’t it!
Here is a little program to cause the ‘T’ command to print out the
check sum, for use with Nasbug monitors.
It is written in position independant code so to run it, first
load it into a convenient part of the memory then execute at the
first memory address.