Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!ucsd!ogicse!emory!gatech!udel!mmdf
From: Dennis_Grant%CMR001.bitnet@ugw.utcs.utoronto.ca
Newsgroups: comp.sys.amiga.tech
Subject: Fun With AUX: (Summary)
Message-ID: <43676@nigel.ee.udel.edu>
Date: 4 Feb 91 16:19:51 GMT
Sender: mmdf@ee.udel.edu
Lines: 34


     ... 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!