Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: Notesfiles; site uicsl.UUCP Path: utzoo!linus!decvax!harpo!ihnp4!inuxc!pur-ee!uiucdcs!uicsl!gene From: gene@uicsl.UUCP Newsgroups: net.micro.cbm Subject: 64-TERM vs UNIXTERM-1.0 - (nf) Message-ID: <20000002@uicsl.UUCP> Date: Sun, 15-Apr-84 16:37:00 EST Article-I.D.: uicsl.20000002 Posted: Sun Apr 15 16:37:00 1984 Date-Received: Wed, 18-Apr-84 01:15:06 EST Lines: 30 Nf-ID: #N:uicsl:20000002:000:1949 Nf-From: uicsl!gene Apr 15 15:37:00 1984 #N:uicsl:20000002:000:1949 uicsl!gene Apr 15 15:37:00 1984 1xxxxx (excuse blank msg 26...my first attempt at this)...'thought I would relate my weekend experience with the COMMODORE 64-term emulator,vs A. Ray Millers version; when logging into vax/unix, I found that the 64-term worked at 300 but could not keep up at 1200( however it does work at 1200 when used keyboard-to-keyboard). It's big advantage(at 300) was that I could log into the vax...create a "vi" file and leave it open..waiting for text....then press stop/restore PRINT#2 (might have to type it twice if you get an "illegal quant error") CLOSE2 (now you're back to conventional features on the c64) you can now load any disc program or index whose "LIST" you want written into the vax file (perhaps to print out a copy) then OPEN2,2 CMD2 LIST and the c64 will send out the LISTing. When it is finished (I added a couple of LED send, recv indicators on my VICMODEM 1600 so I could note the activity)... contr-shift-[ (will work as ESCAPE) to stop writing ..whoops I goofed...I might goof trying to edit this so disregard the last contr-shift-[....so after the activity going out on the modem ends, press stop/restore PRINT#2 (twice if necessary) CLOSE2 then again LOAD "64-TERM",8 (if it isn't on the disc presently being copied, insert it first) RUN (now we're back talking to the vax that was left still waiting for anything more .....now the contr-shift-[ (constitutes ECAPE) will close the vi file and return you to the host % prompt. You can now "cat filename" to verify that it came thru ok. The "64-term" is not suitable for vi editing On the other hand A. Ray Miller's "UNIXTERM-1.0" works fine in vi and at 1200 baud BUT I could not succeed with it in writing to a file because I was unable to transfer back and forth between terminal mode and conventional mode....when in "terminal" mode, a stop/restore yields "baud? xxx and hangs everything up there (the only way I ever got out was to power-down).