Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!pacbell!att-ih!ihnp4!ihlpm!njd
From: njd@ihlpm.ATT.COM (DiMasi)
Newsgroups: comp.sys.atari.8bit
Subject: Re: Re: vt100 emulators
Message-ID: <1814@ihlpm.ATT.COM>
Date: 31 Mar 88 23:55:51 GMT
References: <2506@bsu-cs.UUCP>
Organization: AT&T Bell Laboratories - Naperville, Illinois
Lines: 23

> ....
> However, I found that OmniCom's PRINT SCREEN function (an option that can be 
> turned ON or OFF to "print all incoming data," as I distinctly remember it)  
> was unsatisfactory, because it wasn't able to do anything effective with the
> escape sequences typically sent to a VT100 for screen and cursor control.  
> Even "stripping out" the escape sequences would be better than PRINTING them,
> but not even THAT is done.  I found it completely impossible to print a data-
> base form-entry screen, once screen-painting was completed.  Did I miss a 
> feature that lets you print an image of an EXISTING DISPLAY?
> ....
I think you have the Capture and Print-screen features mixed up.  Print screen
(I forget the key combination!  I think it's [SELECT][OPTION]) dumps, to the
P: device, whatever is on the screen.  Capture mode puts a copy of all 
incoming characters (or at least most of them) to a user-specified device.
Print screen works fine for me, but not Capture.  I think I'm on to a BIG clue,
though - when I tried capture to a D: file instead of to P:, many of the
characters were inverse video when I looked at the file.  Hmm, 8th bit flipping
around, eh?  Parity?  I have to make parity=none to get xmodem (binary files)
to work, so I wonder what's going on.

Nick DiMasi
Uni'q Digital Technologies (Fox Valley Software subsidiary;
   ^          working as a contractor at AT&T Bell Labs in Naperville, IL)
(  | this is an accent mark, supposed to replace the dot over the 'i')