Path: utzoo!attcan!uunet!microsoft!alonzo
From: alonzo@microsoft.UUCP (Alonzo GARIEPY)
Newsgroups: comp.sys.handhelds
Subject: Re: Introduction to HP 48SX Internals
Keywords: HP48
Message-ID: <53592@microsoft.UUCP>
Date: 15 Mar 90 19:23:28 GMT
References: <52058@microsoft.UUCP> <52059@microsoft.UUCP> <1990Mar14.152221.25597@santra.uucp>
Reply-To: alonzo@microsoft.UUCP (Alonzo GARIEPY)
Organization: Microsoft Corp., Redmond WA
Lines: 21

In article <1990Mar14.152221.25597@santra.uucp> jmunkki@kampi.hut.fi (Juri Munkki) writes:
> In article <52059@microsoft.UUCP> alonzo@microsoft.UUCP (Alonzo GARIEPY) writes:
> >The obvious way to enter machine code is with scan mode.  You don't 
> >need to waste time with hex string converters and other silliness.
> 
> I disagree. The obvious way to enter machine code is to compile it on
> a computer and then use kermit to transfer the binary. The scan mode
> entry system is extremely error-prone and easily results in crashes.

The trouble with needing a computer is that they cost more than $300 and
aren't very portable.

It isn't really obvious to me how to compile HP 48 machine code objects.
I suppose you would have to write a program for the computer.  Will you
distribute yours?  

You are dead right about the dangers of machine code.  Good thing it's
so easy to backup the HP 48 before messing with memory.

Alonzo Gariepy
alonzo@microsoft