Dennis_Grant%CMR001.bitnet@ugw.utcs.utoronto.ca (01/31/91)
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
Newcli AUX: is attempted, ROM-Wack works!
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?
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!Dennis_Grant%CMR001.bitnet@ugw.utcs.utoronto.ca (02/05/91)
... the story so far...
I couldn't get ROM-WACK to operate without first typing NEWCLI AUX:
NEWCLI AUX: would write the CLI prompt to my terminal, but refused to
take any input from it as a command (although it did correctly send-and-
receive characters from it. It is, after all, a full duplex terminal.)
Someone suggested that I use <CTRL>-P instead of <RETURN> to send the
command. Sorry, it just advanced the cursor one line.
Someone (actually, many someones) suggested I use a null modem cable.
It is true that I'm not currently using one, and that I haven't tried this
yet, but I'm suspicious about this one. If I need a null modem, then why:
a) Does ROM-WHACK correctly process all commands (including Return)
once NEWCLI AUX: has been invoked?
b) Does the AUX: CLI correctly process the full duplex echoing of
sent characters, but not sent commands?
c) Is it necessary to use a NEWCLI AUX: to get ROM-WHACK to work
at all? I was under the impression that it would work right off a boot.
d) Is it possible that ROM-WHACK requires a normal serial cable,
whereas a remote CLI requires a null modem? If so, then why c)? If not,
then why a)?
Any ROM-WHACK gurus out there? What's going on here?
-------------------------------------------------------------------------------
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!jnmoyne@lbl.gov (Jean-Noel MOYNE) (02/08/91)
In article <43676@nigel.ee.udel.edu> Dennis_Grant%CMR001.bitnet@ugw.utcs.utoronto.ca writes: > c) Is it necessary to use a NEWCLI AUX: to get ROM-WHACK to work > at all? I was under the impression that it would work right off a boot. Well, there's one thing I know: once you've typed newcli aux:, the serial.device is then loaded in memory, where it stays resident. If you haven't open the serial port before calling rom-wack maybe it needs the serial.device to be resident, and maybe it doesn't know how to load it from the disk.... It's just a guess ... JNM -- These are my own ideas (not LBL's)