Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uunet!zaphod.mps.ohio-state.edu!usc!snorkelwacker.mit.edu!bloom-beacon!eru!hagbard!sunic!dkuug!diku!bombadil
From: bombadil@diku.dk (Kristian Nielsen)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Fun with AUX:
Message-ID: <1991Jan31.140336.17245@odin.diku.dk>
Date: 31 Jan 91 14:03:36 GMT
References: <43237@nigel.ee.udel.edu>
Sender: news@odin.diku.dk (Netnews System)
Organization: Department of Computer Science, U of Copenhagen
Lines: 46

Dennis_Grant%CMR001.bitnet@ugw.utcs.utoronto.ca writes:


>     OK, I got the RKMs for X-Mas this year, and one of the wonderful new
>discoveries I made was ROM-Wack. Seeing the potential usefulness of it, I
>borrowed a Volker-Craig VT3100 from the CS dept, and hooked it up to my
>A2000 according to the instructions in the RKM. I then invoked Debug off
>the 'bench and got - nothing. I tried various combos of dip switches and
>Preferences settings, and nothing ever worked. So I tried a Newcli AUX:,
>and I got the "New process" message and the CLI prompt on the monitor.
>Aha! However, any command I enter on the remote terminal is ignored.
>(The cursor just returns to the start of the line) Even stranger, once

Could it be that the terminal is sending the wrong code for the return key,
ie. 13? Try to end lines with CTRL-M and CTRL-J and configure the terminal
accordingly if that is possible.

>Newcli AUX: is attempted, ROM-Wack works!

Sounds like the use of AUX: configures the serial port registers of the
amiga and then these registers retain their values under ROM-Wack. As far as
I remember, ROM-Wack uses exec/calls like RAwPutChar() for IO, and these
rutines are pretty low-level, talking directly to the hardware (at least in
KickStart v1.2).


>So:    1) Why do I have to NewCli AUX: to get ROM-Wack to work?
>       2) Why won't the remote CLI process my commands?

>I'm using full duplex, 9600 baud, 8 bits, 1 stop, no parity on the
>terminal.

>Also: If I GURU the machine, how can do I find where the program that
>caused it is living?

The second 32-bit number in the guru (after the error number) is supposed to
hold the address of the task that caused the problems.

>Thanx in advance,

>-------------------------------------------------------------------------------
>  Dennis Grant   3rd year CS student at le College Militaire Royal de  St-Jean
>  DETUD595@CMR001.BITNET
>  How much do I love thee? My accumulator overflows!

	Kristian