Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!tektronix!hplabs!ucbvax!ULKYVX.BITNET!RDROYA01
From: RDROYA01@ULKYVX.BITNET (Robert Royar)
Newsgroups: mod.computers.68k
Subject: A typo in my last message
Message-ID: <8605222103.AA19126@ucbjade.Berkeley.Edu>
Date: Thu, 22-May-86 16:41:00 EDT
Article-I.D.: ucbjade.8605222103.AA19126
Posted: Thu May 22 16:41:00 1986
Date-Received: Thu, 29-May-86 07:45:21 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: University of Louisville
Lines: 24
Approved: info-68k@ucbvax.berkeley.edu

Taking out tabs to make the file go through BITNET, I added a mistake to the
ASM language section
This is the way it actually reads:

regs1:     ds.l    14
regs2:     ds.l    14    * says 15 above
regs3:     ds.l    15    * says 14 above

So, besides these typos which were not in the original version, what else
am I doing wrong.  BTW more experimentation shows that multiple command lines
like
ar68 rv uemail.arc ueasm.o!link68 [abs,tex[20000]]uemail=uemail . . .
are where the thing breaks.  I also discovered that a bios call to WARM START
leaves trap vectors intact.  Only a trap #2 function 0 resets the traps DRI
promised to leave alone.  The trap re-init bug is in the BDOS itself.  On
function 0 it resets all vectors from 2-11, Trap 0 and 1 (guaranteed not to
be reset, according section 4.6 of the programmer's guide) and traps 4-15.
All other interrupts are left alone.

I am beginning to believe that cp/m-68k has more potential than I at first
realized, especially for small systems where fancy mice and windows are
distracting and useless.  Anyone up to writing a *Soul of CP/M-68K*?

                            rdroya01@ulkyvx.bitnet