Path: utzoo!mnetor!uunet!cbmvax!rutgers!ames!amdahl!dlb!dana!rap
From: rap@dana.UUCP (Rob Peck)
Newsgroups: comp.sys.amiga
Subject: CON: lockup on typing * <CR> at CLI prompt
Message-ID: <279@dana.UUCP>
Date: 7 Jan 88 18:10:30 GMT
Organization: Dana Computer, Inc., Sunnyvale, CA
Lines: 20

Yesterday, Harv Laser asked me a question:

    "Why does the CLI lockup solidly if you just type

	* <CR>

I was about ready to explain to him that * refers to the console
window itself; about how you do the COPY * TO FILENAME puts anything
you type into the file and so on.   But the first thing on the
command line is usually interpreted by the CLI as a command and
not as a "place", so I really did not have any explanation to
give him.   Is the console trying (and succeeding at) executing
itself?  (It really gets killed, it seems).  :-) :-) :-)

Anybody got any ideas as to what causes this?
Matt?  Steve D?    Not that I plan on doing this in the
future, (and not worth bothering CATS about) but it seemed
interesting anyway.

Rob Peck			...ihnp4!hplabs!dana!rap