From: Rick Balkins on

"comp.sys.cbm" <cm_easy(a)yahoo.com> wrote in message
news:1140122787.196367.102440(a)g44g2000cwa.googlegroups.com...
>
> Mark Smith wrote:
>> It's got to be the bouncing balloon thing in the C64 User Manual ...
>> you know the one that doesn't work properly and introduces you to
>> debugging at a early age :-)
>
> Dang! I always thought it was me typing that program in wrong. :(
>
> Jeri

Several years ago, I typed that stupid thing in but I fixed it and finally
got the C64 balloon sprite to function. That was a good example of not
screwing up a single letter, number or symbol in a program listing given by
the programmer.

In short, a good example of needed proof-checking everything. You don't
really need to know how to program to proof check. You just need to check
the product with that of the original.

However, knowing how to program and checking it out before making big
production would help.



From: Payton Byrd on

Alan wrote:
> Nothing beats Compute!s Speedscript for me. My fingers still hurt from
> typing that thing in, first for the VIC and later again for the C64.
> Totally worth it though, I used Speedscript for years. What a great program
> that was.
>

I agree. Speedscript actually caused a small revolution in the
Commodore word processing scene as many commercial companies touted the
ability to import SS files as a reason to upgrade to their product.

From: anoneds@netscape.net on

Charles Richmond wrote:

> >
> There was an assembly language type in that I got from some
> Commodore-centric magazine. It was written by Jim Butterfield,
> and it played Pachabel's "Canon in D". I typed in the assembly
> language and used an actual assembler on the C64 to produce
> the executable. I thought that the resulting music was quite
> impressive!!!
>

Heck, in 99'er Magazine, we had a program about 5 lines long that
played "Pachebel's Canon in D" as a three-part round. Beautiful,
absolutely beautiful. In plain old TI BASIC, IIRC.

From: Craig Taylor on
Rick Balkins wrote:
> Several years ago, I typed that stupid thing in but I fixed it and finally
> got the C64 balloon sprite to function. That was a good example of not
> screwing up a single letter, number or symbol in a program listing given by
> the programmer.
>
> In short, a good example of needed proof-checking everything. You don't
> really need to know how to program to proof check. You just need to check
> the product with that of the original.
>
> However, knowing how to program and checking it out before making big
> production would help.

There's a book that had a C database program that allowed simple
retrieval and entry of data within a file that I typed in from a book. I
ended up spending the summer going over the listing (about 10 pages)
about 10 times before I found the reason it wasn't working - a
semicolon. I ended up learning the language pretty well from just that
exercise.

--
==========================================================================
C Taylor ctalkobt(a)gmail.com

http://www.ctalkobt.net - Random mumblings of a disturbed mind
==========================================================================
From: Bruce Thomas on

"Macintosh Dragon" wrote ...
>
> I would love to hear what programs others thought were good!

Two months after buying my first C-64 system I typed in SpeedScript from the
January 1984 Gazette. Then I realized I had better buy a printer. With all
of the add-on programs and upgrades that got published for SpeedScript in
later years it probably took up the most space in the magazine of any of
their programs. It was also a top notch productivity program that I used for
4 years until I switched to geoWrite which I used for a short time before
switching to The Write Stuff which I used for a number of years until I got
my accelerators (first a 4 MHz Schnedler TurboMaster and then a 20 MHz CMD
SuperCPU) which made using geoWrite bearable.
SpeedCalc, from the Jan 1986 Compute!, was a useful spreadsheet program that
I did my taxes with for a number of years. I still wish I could do
if/then/else with geoCalc.

As for games, I really enjoyed 'Spike' from the Dec 1983 Gazette (their
first all-ML game) and 'Astro Panic' from the Feb 1984 Gazette.

Anything that Tony Brantner wrote for Ahoy! impressed me as he crammed a lot
into a very small amount of code.

Cleve Blakemore's 'Vault of Terror' (10/86), 'Crypt of Fear' (02/88) and
'Tomb of Horror' (07/88) from Ahoy! were also quite good. All of the 35
games Cleve wrote for Ahoy! are available on the download page of the CUE
Web Site at http://members.shaw.ca/cue64/

'Laser Chess' from the June 87 Compute! was also a very good game.

'Star Strike' from the June 1986 Ahoy! was a good blast-the-aliens game with
a 3-D twist to make it more appealling than others of this type.

'Islands' from the August 1988 RUN issue was quite entertaining.

And I'll end by saying I also enjoyed 'Royal Rescue' from the Jan 1990
Gazette.

Bruce Thomas


First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5 6
Prev: Lantronix UDS-10
Next: Manual for Super Graphix jr ?