Re: pet 2001 repair

On Sat, Jan 6, 2018 at 8:29 PM, Ethan Dicks <ethan.dicks@gmail.com> wrote:
> On Sat, Jan 6, 2018 at 1:37 PM, Francesco Messineo
> <francesco.messineo@gmail.com> wrote:
>> On Sat, Jan 6, 2018 at 7:36 PM, vossi <vossi@ceffy.de> wrote:
>>> There is no source code!
>>> I'm coding such small things with a monitor on the c64 ;)
>>
>> wow, I code in ASM, but I would not do it without a proper macro assembler ;-)
>
> That's what I used to do when my only computer was a PET 2001-N/3032.
> I was so excited the first time I accidentally got into TIM (because
> prior to that, my experience was on an old Static PET with BASIC 1
> ROMs and no TIM - I thought you always had to load from tape).  I
> wrote many programs on paper and typed them into TIM in hex.  Moving
> up to a Micromon monitor ROM with the on-screen inline
> assembler/disassembler was *amazing* after that.

Ok, I've never said I did never do that, my first computer was a
VIC-20 (with tape only), so I quickly learned to write code on paper
and poke it away (I remember the pain very well when the first sys
would freeze everything because maybe I didn't calculate some branch
address correctly). I would not do it nowadays until I'm really forced
to.
I also did PCBs on paper, then taped it to the copper board, painted
it after cutting the traces on the paper, then etch, clean the paint,
make the holes. Why would I do that anymore when I can send a file on
the other side of the world and get nice PCBs on my mailbox a month
later? I still remember when I debugged a clone of the promenade C1
because it was left too much time in the etching bath and some traces
resulted unconnected. It still works BTW, it's just a bit ugly :)
Frank

       Message was sent through the cbm-hackers mailing list