🚀 go-pugleaf

Here's the best suggestion I've gotten so far (though I haven't tried CB yet):


Check on abcfd20.larc.nasa.gov in the incoming/amiga dir.  You should
find a relatively new program called DCMD.lzh (I am not sure of the
case).

If I remember the readme file correctly, this is Matt Dillon's version
of CMD. Only it works on a console.  I have yet to try it.

Good luck.

Jeff

-- 
Jeffrey D. Parker(no philosopher)| By all means marry; if you get a good wife, 
INET: parker@vela.acs.oakland.edu  | you'll become happy; if you get a bad one,
BITNET: PARKER@OAKLAND             | you'll become a philosopher.      Socrates
UUCP: ...!umich!vela!amiga1!fanatic| (Or get an AMIGA - You'll be Happy!)



The DCMD utility (Thanks, Matt Dillon!) works well for capturing
CLI I/O.

However, there are a couple of problems.  Unless your input is
echoed to the terminal, it won't be captured in the log file.  

Benchmark's Input routines do echo the input string, so this
isn't a problem for me.


---

Robin,
	I tried your pipe: idea, and it sounds doable, but after
four or five hours of working on it, I decided to give up.  Seems
that the 1.3 pipe: and me don't get along, and I think that there
are some problems with the pipe: device.


---

Does anybody know if Commodore is including a log file
capability as part of the 2.0 CLI environment?

I think that something like this would be a very useful part of
the system software.  

For example, to print out a CLI session, you could type STARTLOG
PRT: and the printer is sent a copy of whatever you're doing.





Thanks to all who responded.  I really appreciate it.