←back to thread

In the 1980s we downloaded games from the radio

(newslttrs.com)
286 points spzb | 1 comments | 28 Mar 25 22:14 UTC | HN request time: 0.25s | source
Show context
coreyh14444 ◴[31 Mar 25 10:49 UTC] No.43533429[source]▶
I definitely had cassette based games on the TRS-80, but most of the "wireless" transmission in my youth was via BASIC printed in the back of computer magazines. You had to type in the entire app yourself. I did this for basically every app they listed. Sometimes it was like tax prep software, but I didn't care, even though I was like 9 at the time. Yes, it took a very long time. Yes, you could easily introduce typos and bugs.
replies(18): >>43533473 #>>43534190 #>>43534420 #>>43534655 #>>43534805 #>>43535259 #>>43535577 #>>43535687 #>>43536185 #>>43537570 #>>43538062 #>>43538702 #>>43539139 #>>43539623 #>>43539720 #>>43541831 #>>43543690 #>>43547857 #
mysterydip ◴[31 Mar 25 10:55 UTC] No.43533473[source]▶
Sometimes the typos were in the magazine itself, and you wouldn't figure out the problem with the code you triple-checked you typed in properly until the errata in next month's issue :)
replies(3): >>43534839 #>>43535117 #>>43539196 #
jonwinstanley ◴[31 Mar 25 13:56 UTC] No.43535117[source]▶
The compiler/interpreter couldn’t even tell you what line the error was on!

You’d just get a big error message for the whole program.

replies(2): >>43536420 #>>43537609 #
aaronbaugher ◴[31 Mar 25 15:52 UTC] No.43536420[source]▶
After a while, magazines like Commodore Run and Compute started including a short program that would checksum each line as you entered it, so you could check that against a checksum in the magazine. Of course, you had to get that program typed in correctly first before you could use it to enter others.
replies(3): >>43538009 #>>43538499 #>>43540775 #
tantalor ◴[31 Mar 25 18:18 UTC] No.43538009[source]▶
I'm curious, can you say more about "as you entered it"?

Do you mean like, "for lines 1-20 the checksum should be 0xDEADBEEF"? This would let you find the error before finishing the program.

Or just at the end, it would checksum the whole thing?

replies(2): >>43539670 #>>43540214 #
1. onre ◴[31 Mar 25 20:37 UTC] No.43539670[source]▶
I remember borrowing a book from the library, which had a type-in checksum program of this sort. It was done like was common for C=64 things of this kind - there's a BASIC FOR-loop iterating through a memory area, reading in bytes from DATA statements you've typed in and POKEing those bytes into memory, not completely unlike entering a program manually from the front-panel switches of an older computer.

So, after typing that in and probably SYSing (C=64 BASIC command for executing machine code from arbitrary memory location) to some address, it did print out a two-digit (eight-bit) hex checksum after every BASIC line I entered on the C=64 and the program listing in the book had the correct checksums for every line, so spotting errors was more or less instantaneous.

This stuff brings memories.

  FOR I=40960 TO 49152:POKE I,PEEK(I):NEXT I
  POKE 1,54
From top of my head; loop through the BASIC interpreter area, reading byte by byte with PEEK and POKEing those bytes back to the same addresses. Sounds nonsensical? Not so, because the C=64 does have full 64 kB of RAM, but some of it is overlapped by ROMs. What happens here is that you're reading from ROM but writes always go to RAM, so you're copying the BASIC interpreter from ROM to RAM. After that, the POKE statement turns off the ROM overlap and the interpreter is now run from RAM, so you can edit it live - and obviously cause all sorts of interesting crash situations.

It sure did help later with career in IT to have understood this kind of stuff at age of around ten.