[CRTech] Christian Radio Tech [MSG 81952]
[Thread Prev] [-- Thread Index --] [Thread Next] [Date Prev] [-- Date Index --] [Date Next]
Re: why I like assembly
To: CRTech <crtech@crtech.org>
Subject: Re: why I like assembly
From: Dave Land <dave@klvv.com>
Date: Thu, 1 Feb 2018 10:52:44 -0600
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klvv-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=8f+9O4JDc7zqBrZkKHevJquKTr/yZJpl9Wacq6jXmTU=; b=huxudRTab7FRcLIzJsrl6tpXHXpUruD3JaVe1wh9J9i8+5WFtUUvepwqXL1zxTl/Pm gAygIvxW45O4CpbqMcsdlPBFnRG4OAgEpNK43o9YXsr+Ulw3BSjoxyGxtBlZM9oBfo/y Rkp7Qnvldsn0nQj1K1iQ5n4TiVEzU1O0E2jgTYR1WJa90dTa+pTuVy847q6QZdQD2OCW JDqYf5EyhWiEh4XAcXHYHQvCUjXXSkKoT6KedKwyzGB3AgG0hiOAiwA6y3Y15oS9swwj ypdNNprrNoY6XqFqLVS3r9wcB1k5ljbbG8GCdai1hh0m0W+B6vz4XgDyT71r2OYRRmfA DZNQ==
In-reply-to: <5a7249c6.a241240a.68cfb.2c33@mx.google.com>
References: <2d7c66e8-840d-579e-5547-1a8b5d86ab12@reyware.us> <CAOkhgWpOKXdtDsH_e8TwiYSkEVqZnVcviQEVVaAT=o93ein3kA@mail.gmail.com> <CAL=56Poz5kZ+xQirzqEPAG12WxOcaNJ1sYpx3HGMtdE8y5dY_g@mail.gmail.com> <44cc2035-76ce-4aa0-84b3-0405e9b334af@kvip.org> <5a7249c6.a241240a.68cfb.2c33@mx.google.com>
Wow! Almost the same for me, IBM360 at OBU in the 70s then my first home computer was a Sinclair ZX80 with a Z80 and 1KB of RAM! Then on to VIC20s, C64s and the SX64 version of the C64 with built in COLOR monitor and DUAL floppies! Wrote a program in basic that kept a roster of ham club members and even sold a few copies of that at the ham fest to other hams! 20$ each. Those were the good ole days... (NOT!) I still have the ZX80.

On Wed, Jan 31, 2018 at 4:56 PM, Alan Kilgore <wrvm.engineer@gmail.com> wrote:
Reading these memories makes me feel how I have aged.

At college in the 70s I programmed Fortan on the large IBM360 and ran Basic, assembly and machine code on the HP2000E time-shared mini-computer.

At home I started out with a couple of machines with only toggle switches for input and discrete LEDs for output. The CPU was something like a 6502 IIRC. That was truly programming in machine code. When you have used one of those computers, you really understood what it meant to "boot" the initial code for a computer to have I/O. That had to be done even before loading a saved program. It probably does not mean nearly as much to someone who has never really done that manually in binary using switches.

In the early 80s I got a couple Vic20s followed by a couple C=64s. I started out with cassette tape storage then added FDD shortly after it became available. By the mid-80s I got a portable C=64 with built in dual FDD and color monitor. I connected larger external drives to the portable when at the office. That seemed like the big times for personal computing... but then Tandy started coming out with their usable TRS80 computers. I stayed away from those. The C in C=64 stood for the Commodore brand. So, we called my favorite brand the "commode-door 64" computer and we called the Tandy TRS-80 computers the "trash-80".

It was amazing how much could be done with such small resources on those very early personal computers along with some programming ingenuity. A few of us used to compete writing small programs to see who could create the smallest, fastest code having equivalent results.

Ah, the memories. I wrote code for a CATV billing program using the C=64 and used Vic-20s for the video of a CATV bulletin board channel. Those were in the days when there were a lot of mom & pop systems,

I also wrote software to do FM channel studies on a better-equipped C=64 but I had to enter the station info since getting FCC data was too slow using dial-up internet (300/1200 bps (that's bits /sec, *not* kbps) modem in rural areas) back then. I later translated it to work on PC computers and added contour spacing, FCC data using faster modems (local ISP came to town), pop counts, 2nd/3rd adj channel protection radiation from xltr antennas, etc. After FCC converted to CDBS databases, for quite a number of years I still used the flat database version the FCC continued providing for legacy software.

One day I finally gave up trying to update my code for rule changes and features so I talked my employer into paying for commercial software. It is amazing how "rusty" and "behind the times" a person can get by stopping cold turkey and not keeping up with the rapidly changing world of coding.

Trivia: I read somewhere that the Apollo landing modules that landed on the moon in the 60s had a computer back then which contained only 2K RAM (magnetic core memory) and the CPU was discrete RTL gate ICs. Interesting reading at https://en.wikipedia.org/wiki/Apollo_Guidance_Computer

Alan Kilgore, CPBE
WRVM Chief Engineer

At 01:58 PM 1/31/2018, you wrote:

I remember those days! Had a Vic20 and still have a couple of C64s and a couple of monitors.


On 01/30/2018 12:28 PM, Tom Beattie wrote:
Willie did you type in a bunch of machine code from Compute's Gazette for the word processor that they published (among other things)  I too am a VIC20 refugee.  I still have a C=64. =)

Tom Beattie

For CRTech resources visit http://CRTech.org/
To unsubscribe, e-mail: crtech-unsubscribe@crtech.org
List problems?  E-mail: TechStaff@CRTech.org

References: why i like assembly
(dave allen <crtech-mail@reyware.us>, 27 Jan 2018 06:22:53 -0000)
Re: why i like assembly
(Willie Barnett <wbradiolists@gmail.com>, 29 Jan 2018 14:21:46 -0000)
Re: why i like assembly
(Tom Beattie <tom@tombeattie.com>, 30 Jan 2018 20:29:23 -0000)
Re: why i like assembly
(Paul Brown <pbrown@kvip.org>, 31 Jan 2018 19:58:51 -0000)
why I like assembly
(Alan Kilgore <wrvm.engineer@gmail.com>, 31 Jan 2018 22:57:16 -0000)
Prev by date: Re: why I like assembly
(Alan Kilgore, 1 Feb 2018 16:36:56 -0000)
Next by date: Re: Job Opening
(Pat Wahl, 1 Feb 2018 17:33:06 -0000)
Prev by thread: Re: why I like assembly
(Alan Kilgore, 1 Feb 2018 16:36:56 -0000)
Next by thread: RE: why I like assembly
(Jack Epperson, 1 Feb 2018 20:37:47 -0000)