bill@bilver.uucp (Bill Vermillion) (05/30/91)
In article <1991May30.083643.25468@thunder.mcrcim.mcgill.edu> mouse@thunder.mcrcim.mcgill.edu (der Mouse) writes: >In article <15710006@hpdmd48.boi.hp.com>, markw@hpdmd48.boi.hp.com (Mark Wolfe) writes: >> Well, I have my answer, and I was very surprised at the responses I >> got. Most of the "wizards" said this was impossible to do in most >> cases and difficult at best. I guess terminals with their own memory >> are rare outside HP (hah!). >No, terminals with their own memory are not rare; every terminal must >have somewhere to store the stuff displayed on the screen, and most use >ordinary RAM for this. >What *is* comparatively rare is terminals that provide any way for the >computer on the other end of the serial line to get at this data. And >of those that do, the required actions vary widely. Just saw a new terminal last week that is nearly in release. It's the MC6 from Link. It is the first terminal I have seen that knows what to do (to a limited extent) with the memory it has in it (64k ram I seem to recall). One of it's "neat" features is a cut&paste mode. You can cut&paste in the same window, or between two different windows (split screen that connects to different hosts simultaneously). To cut you press a key sequence, highlight the material, press another key. To paste you go to the position you wish to paste and press a key. The ram is dumped to screen and to the host. With one of these and short command sequence or pipe to lp, a screen dump should be easy. Whole sequence could be programmed to a function key - which if I remember correctly takes up to at least 64 bytes per key.. I will probably be getting one of these for testing and evaluation later this summer. Disclaimer - I am not an employee or related to Link in any way. I was just blown away by the capabilities of this terminal on my initial exposure to it. And it was being demoed for me by the person who wrote the programming for it - so he knew all the tricks - and showed me a few he hadn't announced. P.S. - I just cross-posted this to comp.terminals so edit your followups appropriately - particularly for non-wizard answer/question. -- Bill Vermillion - UUCP: ...!tarpit!bilver!bill : bill@bilver.UUCP
les@chinet.chi.il.us (Leslie Mikesell) (05/31/91)
In article <1991May30.152823.25779@bilver.uucp> bill@bilver.uucp (Bill Vermillion) writes: >Just saw a new terminal last week that is nearly in release. It's the MC6 >from Link. >One of it's "neat" features is a cut&paste mode. I've been doing this for a little while now by running several copies of MSDOS kermit 3.10 under Windows 3.0 on a 386. I'm connecting over a starlan network to several unix hosts with PIF files set up to name the windows/icons for the hosts and select the script for auto-login. Serial port links or the other networks that kermit knows about should work just as well. >You can cut&paste in the same window, or between two different windows >(split screen that connects to different hosts simultaneously). MSkermit gives you n-screen rollback so you can even back up to find the piece you want and then use the Windows cut&paste tools. >I will probably be getting one of these for testing and evaluation later >this summer. If you happen to have a 386 with windows sitting around it might make an interesting comparison. BTW, does anyone know where to get a terminfo entry for kermit 3.10? I've been using vt102, but this version is supposed to be a near vt320 with color support etc. Les Mikesell les@chinet.chi.il.us