SY.CHRISTINE@CU20B.COLUMBIA.EDU (Christine M Gianone) (12/19/87)
Info-Kermit Digest Fri, 18 Dec 1987 Volume 6 : Number 27 Today's Topics: Departments: ANNOUNCEMENTS - IBM PC Kermit with Tektronix 4010 Emulation Available for Testing Info-Kermit BITNET Subscribers Moved to LISTSERV Changes to Okstate Kermit Distribution Service Kermit Available for the HP-125 CP/M Business Computer MS-DOS KERMIT - Kermit-MS and >25-Line EGA Modes More Comm Ports for MS-Kermit? UNIX KERMIT - Suspending C-Kermit under 4.2 BSD C-Kermit Problems MISCELLANY - Trouble Building CMS Kermit Kermit-PE (Concurrent 3200, OS/32) Bug Fix Need Kermit on a VAX 730 under VMS 4.0 Red Ryder's Kermit Send Fails Re: BOO File Problems Kermit 3.79 on Apple 2c Kermit Found for Convex Need Kermit for IBM System 9000 Kermit Wanted for Old RSX-11m v3.2 ---------------------------------------------------------------------- Date: Thu, 17 Dec 87 00:11 MST From: <JRD%USU.BITNET@CUVMA.COLUMBIA.EDU> (Joe Doupnik) Subject: IBM PC Kermit with Tektronix 4010 Emulation Available for Testing Keywords: Tektronix Emulation, MS-DOS Kermit, EGA File MSTIBM.BOO, dated 16 Dec 1987, is on the way. It includes Tektronix 4010 graphics terminal emulation (plus Tek 4014 line-drawing commands) for the IBM PC with EGA, CGA, or Hercules graphics adapter, or no graphics board at all (Kermit automatically senses which board is in place). Tek emulation can be invoked in two ways: (1) SET TERMINAL TEK (or by toggling terminal type with Alt-Minus), and (2) from within DEC or Heath mode when the host transmits ESC-Formfeed. Return to DEC/Heath mode upon receipt of Ctrl-X, or SET TERM VT102 (or anything other than Tek). On color systems, the prevailing fore- and background colors are used. On systems with sufficient graphics memory, both the text and graphics screens are saved for restoral after escaping back and reconnecting. There's also a corresponding version of "generic" MS-DOS Kermit, MSTGEN.BOO, naturally without the Tek emulation. Joe D. [Ed. - Many, many thanks, Joe! This is a great piece of work. It is based on Brian Holley's (Cambridge U, UK) adaptation of Tek code that was originally written for the TI PC version of Kermit by Joe Smith (Colorado School of Mines). Joe has seamlessly integrated it into the mainline Kermit, and added many features in the process. We've tested the result on PCs, XTs, and ATs, and it works, and it goes fast! So far, the manual (MST29C.DOC) does not describe the Tek emulation in any detail, but a few preliminary notes can be found in MSTIBM.HLP. The new Kermit version itself is in MSTIBM.BOO. These files are in KER: on CU20B.COLUMBIA.EDU, available via anonymous FTP, or available as MSTIBM * from KERMSRV at CUVMA on BITNET. If no serious problems are encountered, this could be "it" -- the real 2.30 release.] ------------------------------ Date: Thu 17 Dec 87 17:15:03-EST From: Frank da Cruz <SY.FDC@CU20B.COLUMBIA.EDU> Subject: Info-Kermit BITNET Subscribers Moved to LISTSERV Keywords: BITNET, LISTSERV As announced a while back, the WISCVM mail gateway between BITNET and the other networks (Internet, CSnet, CCnet, etc) ceased operation on December 15th. There were still 105 subscribers of Info-Kermit using this gateway. Some of these subscribers were lists in themselves, so it's hard to know how many people at how many sites are involved. Before this edition of the Info-Kermit Digest was sent, all of these subscribers were moved to a new LISTSERV-based distribution, I-KERMIT@CUVMA. If this happened to you, you should have received by now a notification from your friendly neighborhood LISTSERVer. From now on, anyone who wants to subscribe to the Info-Kermit Digest from a BITNET site should send mail to LISTSERV@CUVMA, with the body of the message as follows: SUBSCRIBE I-KERMIT your personal name Similarly, if you are getting Info-Kermit mail from a LISTSERVer, and you want to cancel your subscription, send mail to I-KERMIT@CUVMA, with the body of the message saying UNSUBSCRIBE I-KERMIT For more information about LISTSERV, send mail to LISTSERV@CUVMA, with the message body saying "HELP" (for a short getting-started message) or "INFO GEN" for a longer explanation of what LISTSERV is, along with the most common commands. Most of the subscribers that were moved had to be entered as "Name Unknown" because the personal names were not kept in our present distribution list. If you receive mail that refers to you in this manner, you can tell LISTSERV your actual name by sending it a SUBSCRIBE request that includes your name. It should correct the current entry, rather than make a duplicate one. ------------------------------ Date: Mon, 14 Dec 87 12:57:22 -0600 From: Mark Vasoll <vasoll@a.cs.okstate.edu> Subject: Changes to Okstate Kermit Distribution Service Keywords: Okstate We have made some changes in our communications system that will now allow us to offer 2400 bps access as well as the old 300/1200 access via both Kermit and UUCP. The login information has not changed, except that upon receiving a carrier, you should send the following <carriage return> <delay about 2 seconds> <carriage return> In UUCPeese, that's: "" \r\d\d\r ogin: uucpker word: thefrog or in a C-Kermit script: ~0 ~r~d~r ogin: kermsrv work: piggy Since new hardware is involved, there may be problems. It would be most helpful if you could send uucp-support@a.cs.okstate.edu a message describing any problems with approximate time (don't forget the timezone) and date. Also, your UUCP system name would be helpful if you were trying to use UUCP. Thanks, Mark Vasoll Computing and Information Sciences Internet: vasoll@a.cs.okstate.edu Oklahoma State University UUCP: {cbosgd, ihnp4, Stillwater, Oklahoma rutgers}!okstate!vasoll [Ed. - Thanks Mark. This information has been added to the file KER:AANOKS.HLP.] ------------------------------ Date: Tue, 8 Dec 87 13:45 PST From: <MAILER@UWALOCKE> Subject: Kermit Available for the HP-125 CP/M Business Computer Keywords: CP/M Kermit, HP-125 I have a version of CP/M Kermit for the Hewlett-Packard HP-125 (a short-lived CP/M machine produced in the early 1980's and intended for the business office.) It is based on version 4.05 of 1985. It will send/receive files over both Data Comm Port 1 and Data Comm Port 2 (although the latter can only be done in 7-bit bytes -- HP's restriction) and will emulate a VT52 as well as responding to HP terminal escape sequences with VT52-Emulation OFF. Would you be interested in this version, even though it is not current? By the way, I am using an HP-125 because a company called Maryland Computer Services (now part of a company called Enabling Technologies) modified it for voice-access with special software for the blind. I am a blind systems programmer on a DECsystem-10 here. Please send any reply to MAILER@UWALOCKE. Please place on the subject-line of your message the phrase dec10%"bpa". Michael Freeman-MORF Bonneville Power administration P.O. Box 491 Vancouver, Wa 98666 [Ed. - Thanks! The system-dependent hex file, plus the above message, have been installed in KER:CP4HP1.* on CU20B. Michael will be sending the sources to Bertil Schou in England, who's been working on CP/M-80 Kermit, so that HP-125 support will be in the next release.] ------------------------------ Date: Wed 2 Dec 87 21:43:18-EST From: Jim Celoni S.J. <su.Celoni@CU20B.COLUMBIA.EDU> Subject: Kermit-MS and >25-Line EGA Modes Keywords: MS-DOS Kermit, EGA I'm using Kermit-MS now on an AT compatible w/ EGA & ECD in 34x80 mode. I've also used it at 42x80 and 57x80, all as heath-19 (except changing the termcap li entry), using ega35, ega43, and ega58 mode-setting programs. I'm happy Kermit-MS 2.29c handles more than 24 lines intelligently! ------------------------------ Date: Mon, 14 Dec 87 17:34 EST From: <JBLAIR%LOYVAX.BITNET@CUVMA.COLUMBIA.EDU> Subject: More Comm Ports for MS-Kermit? Keywords: IBM PC Comm Ports, COM3 and COM4, MS-DOS Kermit I was attempting to alter the MS-DOS version of Kermit so that it would access COM3: or COM4:, but to no success. I was wondering if there were any standards to the interupt vector addresses and the end-of-int value. I have the addresses of the data/status/port for com 3 & 4, but the values of MDINTC3/4, MDINTO3/4, MDINTV3/4, and EIOCOM3/4 are a mystery. Can anyone help with an explanation of how these values are obtained? Is there someone else that I should be asking? Thank you Bryan Blair a.k.a JBLAIR@LOYVAX [Ed. - There are indeed no standards. The current prerelease of MS-DOS Kermit, 2.29C (soon to be 2.30), includes hooks to allow users to access their COM3 or COM4 ports. These are documented in the MS Kermit manual, MST29C.DOC, which must be used in conjunction with your expansion board's technical manual.] ------------------------------ Date: Wed, 9 Dec 87 14:28:25 -0500 (EST) From: ww0n+@andrew.cmu.edu (Walter Lloyd Wimer, III) Subject: Suspending C-Kermit under 4.2 BSD Keywords: C-Kermit Has anyone fixed C-Kermit so that it can be suspended using ^Z (SIGTSTP) without leaving the terminal in cbreak and no-echo mode? If not, I believe I have. Let me know and I'll send the changes. Walt Wimer Data Communications Carnegie Mellon University [Ed. - We've received a number of fixes for this. They're listed in KER:XKUKER.BWR on CU20B, and will be added to the next release.] ------------------------------ Date: Sun, 8 Nov 87 21:59:05 EST From: Phil Ritzenthaler <ritzenth%andy.bgsu.edu@RELAY.CS.NET> Subject: C-Kermit Problems Keywords: C-Kermit I have had a small problem occur with the new C Kermit (4E(067)). I was uploading a 92K file from my PC (using 2.29b) to a VAX 11/785 running Unix 4.3 BSD using a packet length of 500 bytes. This was a VERY local call. I had 3 errors that occured during transmission and whin doing a 'diff' against the original file there were problems . . . some "Y#5"'s, many "#"'s, and then many more "@"'s. It looked to be the length of 1 500 byte packet. Could you clue me in on what occured? Are the larger packet lengths unresonable and not possible in the "real world"? Again, thanks . . . Phil Ritzenthaler |USnail: University Computer Services Computer Graphics Research Specialist | 241 Math-Science Bldg. UUCP :.!cbosgd!osu-cis!bgsuvax!ritzenth | Bowling Green State University CSNET: ritzenth@bgsu.edu | Bowling Green, OH 43403-0125 ARPA : ritzenth%bgsu.edu@relay.cs.net | Phone: (419) 372-2102 [Ed. - If anybody can reproduce this problem, please send in the exact scenario so we can fix it!] ------------------------------ Date: Thu, 29 Oct 87 11:53:41+0700 From: indovax!ranti@uunet.uu.net (Benny Ranti ) Subject: Trouble Building CMS Kermit Keywords: CMS Kermit I am research assistant at Comp. Sc. Center Univ. of Indonesia. I have tried to compile Kermit CMS source program (sixth edition, rev. 2 based on IBM 360/370 Assembly Lang) on IBM 4361 (under VM/CMS). We found an error during the compilation, the error was "undefined code" for STAX instruction within INTINI routine. We have looked at IBM's book but we didn't find STAX as a mnemonic. Another thing, do you have Kermit source for VSE/SP ? I am looking forward to hearing a good news from you. Please contact me: my uucp address is: uunet!indogtw!indovax!ranti [Ed. - The STAX macro is in the TSOMAC macro library. Like it says in the intallation instructions for CMS Kermit, you have to GLOBAL TSOMAC before assembling. There is presently no Kermit for DOS/VSE. But with the new "portable 370" Kermit nearly ready for release, it should be a simple (?) matter for a DOS/VSE programmer to add support for that system, following the methods used for VM/CMS and MVS/TSO. Watch Info-Kermit for announcements.] ------------------------------ Date: 8-DEC-1987 14:54:26 GMT From: Diane Lowe, CAP Industries. Via: SYSKERMIT%vax1.central.lancaster.ac.uk@NSS.Cs.Ucl.AC.UK Subject: Kermit-PE (Concurrent 3200, OS/32) Bug Fix Keywords: Perkin-Elmer Kermit I have recently discovered a bug in our version 2.0 of Kermit-PE (Concurrent 3200, OS/32). At the OS/32 Mainframe end, when trying to SET DEBUG ON, the following Fortran error message occurred; ERR 301 (OOC8AO) :ON VALUE 20 FOR SPECIFIER > MAX VALUE ALLOWED:14 TASK PAUSED This can be resolved by adding the following line to KERMIT.LNK OPTION LU=21 Regards, Diane Lowe. [Ed. - Thanks Diane. Although are currently sending out 2.1 (9/11/86) of PE-Kermit, we have created a KER:PERKIN.BWR to add your fix.] ------------------------------ Date: 25 Nov 87 16:57:23 GMT From: oldeng@gpu.utcs.toronto.edu (Dictionary of Old English) Subject: Need Kermit on a VAX 730 under VMS 4.0 Keywords: VAX/VMX Kermit I need to get any version of Kermit up on our DEC VAX 11/730. It is running VAX/VMS 4.0, right now, and the only compiler we have is a version of a C compiler from Whitesmiths. We can transfer ASCII to it right now, through various means, but binaries so far have been a problem. Also, the only removable media we have are RL02 cartridges, and the tiny DECTAPE II's. RL02 aren't very popular, and I am not sure if we can directly read or write DECTAPE II's. If we can get a binary of a kermit on an RL02, it could be a solution, but so far, we haven't been able to find anyone. Another alternative is to do something similar to "uuencode" a binary of kermit, transfer it via ASCII, then "uudecode" it on the VAX. The only problem is, we don't have such utilities. We might need a source for that in Whitesmith's C, or get the binary... which brings us back to the same problem. SO, if anyone can suggest anything that we can do to get Kermit running on our VAX, it would be much appreciated. Also, please respond by Email if possible. --Tak Ariga Internet: oldeng@gpu.utcs.toronto.edu BITNET: oldeng@UTORGPU Phone: (416) 978-8883 {office} ++ Dictionary of Old English == University of Toronto == Toronto, Canada ++ [Ed. - VMS Kermit is available in hex file format as VMSMIT HEX, available from KERMSRV at CUVMA, along with a Macro-32 decoder program, VMSDEH MAR, which you can assemble, link, and run, to produce a runnable Kermit. See the file VMSAAA HLP. Or, if anybody wants to volunteer to send Kermit on an RL02 or tape cassette...] ------------------------------ Date: Wed, 09 Dec 87 13:27:53 -0800 From: Alastair Milne <milne@Q2.ICS.UCI.EDU> Subject: Red Ryder's Kermit Send Fails Keywords: Red Ryder I have been trying to send a textfile created with IdeaLiner from a 512K Mac to C-Kermit under a UNIX copy called DYNIX, running on a Sequent. The file goes across, and no error is reported, but when I look at it on the UNIX system, there are no linebreaks at all. In fact, "wc" counts 0 lines for it I can't even use "vi" on it: the single undelimited line is far too long. But the linebreaks are definitely there on the Mac. Apart from the fact that MockWrite shows that text properly broken, a byte-level examination with ViewEdit in MacTools shows an ASCII 13 at the end of each line. I doubt whether it can be anything do to with the UNIX kermit. I've already used it often for exchanging files with DOS (Kermit 2.29C) and the p-System, and the files go across perfectly intact. I am using the Kermit built into Red ryder 9.2; I don't know which version of C Kermit is on UNIX. I have tried all the switch settings I can find that might add CR's or LF's at linebreaks, but they make no difference. I've even tried fiddling with newline mode in the VT100 emulation, even though Kermit should have all terminal emulation turned off. This is a considerable and unexpected hindrance. Could somebody please tell me how to get the line breaks preserved across the transfer? My work on the Mac is for nothing if I can't get it to where our group works on the Sequent. I have tried getting a file from UNIX, using Red Ryder Kermit receive. It works fine: all the linebreaks are where they're supposed to be. But sending is hopeless. Please help. Thanks again, Alastair Milne [Ed. - I can't comment on Red Ryder, but if it were Mac Kermit, I'd guess that you were sending the text in binary mode, so that the CRs which are used on the Mac to delimit text lines were not being translated into CRLFs during transmission, which means that Unix Kermit won't see any line breaks, and so will just store the bare CRs, which are not line delimiters in Unix.] ------------------------------ Date: 11 Nov 87 From: RECK@DBNUAMA1.BITNET (Gisbert W.Selke) Subject: Re: BOO File Problems Keywords: MS-DOS Kermit, .BOO Files Xref: BOO Files, See .BOO Files I was doubting my sanity some time ago when I had serious problems with MS-Kermit boo files, too. It turned out to be a local EBCDIC -> ASCII conversion problem, and after some experimenting I found a way to get my boo files transferred in a reliable way - the un-booed executables do work. The problem is mainly that the boo format uses all the characters from ASCII-zero (ASCII 48) to ASCII-tilde (ASCII 126). Included in this set are some characters for which no standard EBCDIC <-> ASCII conversion rule exists; assuming that characters and digits are OK (they will be, won't they?!?), the extra characters needed are: colon ":" semicolon ";" less than "<" equals "=" greater than ">" question mark "?" at-sign "@" left square bracket "[" (at our place, EBCDIC hex 'AD') backslash "\" right square bracket "]" (at our place, EBCDIC hex 'BD') caret, up-arrow "^" (in EBCDIC, usually negation sign) underscore "_" accent grave "`" left curly brace "{" vertical bar ":" (maybe "|" in some EBCDIC places) right curly brace "}" tilde, quiggle "~" You should check if all these characters are transferred properly with whatever procedure you use to get files to your Amiga. The ones that caused trouble here were the up-arrow/negation-sign, the vertical bar and the square brackets. So I used XEDIT to translate these particular characters into inconspicuous sequences which got transferred properly; I wrote the following XEDIT macro file to accomplish this: SET LRECL 255 SET TRUNC 255 SET ARB OFF SET HEX ON TOP * For transferring boo files to PC via IRMA board and IRMA software: * translate characters which will not transfer properly otherwise: :0 C /^/`not`/ * * :0 C /|/`vba`/ * * :0 C /X'AD'/`lbr`/ * * :0 C /X'BD'/`rbr`/ * * Remember to invoke XEDIT with a greater width, i.e. XEDIT <file name> <file type> (width 255 noprof This also makes sure you're not hampered by any profile which sets trunc or lrecl to something inconvenient. Executing the above macro file results in a file with greater line lengths: your file transfer utility should be able to cope with that. Also note that at some places, apparently ASCII left and right square brackets are translated to EBCDIC "" (cent) and "|" (continuous vertical bar), respectively; you might have to check that, although I never encountered that with CUVMA files. Well, I hope this at least gives you some clues, even if it isn't a ready solution to your problem. Happy kermitting, \Gisbert P.S.: I am enclosing a brief description of the boo format which I prepared for a booing programme - for what it's worth. C BOO FORMAT FILES C C IT IS NOT MEANT TO BE A TRANSFER PROTOCOL REPLACEMENT; IT C JUST MAKES TRANSFER POSSIBLE ACROSS LINES (E.G., DATA NETWORKS) C WHEN NO KERMITS ARE AVAILABLE OR ONE OF THEM CAN'T COPE WITH C BINARY STUFF. C C BEWARE OF GREMLINS, THOUGH; ESPECIALLY EBCDIC <-> ASCII C TRANSLATION MAY BE A PROBLEM FOR SOME OF THE CHARACTERS ... C C BASICALLY, 3 BYTES = 24 BITS ARE ENCODED INTO 4 CHARACTERS C BY DIVIDING THEM INTO 6-BIT-PIECES AND THEN ADDING ASCII-ZERO C TO MAKE THESE PIECES PRINTABLE. THE RESULT LIES IN THE RANGE C ASCII-ZERO TO ASCII-SMALL-O. - IN ADDITION, NULL COMPRESSION C TAKES PLACE; CONSECUTIVE NULL BYTES (WHICH OCCUR FREQUENTLY C IN EXECUTABLE FILES, E.G.) ARE ENCODED WITH A TILDE LEAD-IN C FOLLOWED BY THE NUMBER OF NULLS (UP TO 78), AGAIN RENDERED C PRINTABLE BY ADDING ASCII-ZERO. THE RESULTING CHARACTER IS IN C THE RANGE ASCII-ZERO (WELL, ASCII-TWO OR -THREE, REALLY) TO C TILDE (ASCII CODE 126). - CHUNKS OF FOUR CHARACTERS BELONGING C TOGETHER (RSP. TILDE AND NULL REPEAT COUNT) SHOULD NOT BE C DIVIDED ACROSS LINES. A LINE HAS A MAXIMUM LENGTH OF 76 C CHARACTERS. - IN ADDITION, THE FIRST LINE OF THE FILE CONTAINS C THE NAME OF THE ORIGINAL FILE (IF KNOWN - OTHERWISE A DUMMY NAME) C AND NOTHING ELSE. C ------------------------------ Date: Thu, 5 Nov 87 22:31:58 EST From: ciaraldi@cs.rochester.edu Subject: Kermit 3.79 on Apple 2c Keywords: Apple II Kermit I have been using Apple Kermit 3.79 on an Apple 2c and find it works great! Terminal emulation and transfers at 2400 baud with no missing characters, VT100 emulation including keypad, the works! But there's one minor problem... While characters received from a remote system over the modem come through OK at 300, 1200, and 2400 baud, those generated by the modem itself are often garbled. For example, when you type "AT" the modem is supposed to reply "OK". Sometimes this works and sometimes it comes out as "O+". Similarly, when you reach the other machine the modem sends you "CONNECT", but this NEVER comes through on the screen--it's always something like "CO%&T" (sorry, don't remember the exact sequence). It looks like the computer cannot handle characters that arrive too close together. I tried this on two different 2c's, and one has a much bigger problem than the other. Has anyone seen this problem? Is it a Kermit or a 2c problem? At first I thought it was a matter of not responding to interrupts in time, but since it even happens at 300 baud this doesn't seem likely. I though it might be that the 2c was looking for 2 stop bits, but the source code seems to be initializing the port properly (not that I'm a 2c expert!). The 2c manual says something like "Peculiarities in the 2c's baud rate generator may require changes in the data format" in the section on setting data bits, stop bits, and parity. Could that be it? Did different revisions of the 2c have different peculiarities? Is there a workaround? I foresee this will be a problem if a script facility is ever added to Apple Kermit, as it will be hard to do input matching to look for prompts if they cannot be received reliably. Reviewing the manual, I realized that this problem of not getting the modem prompts correctly will also mess up the MODEM command in Apple Kermit, since it waits to receive the string "CONNECT" from the modem. Mike Ciaraldi University of Rochester Computer Science Department ciaraldi@cs.rochester.edu [Ed. - This report has been added to KER:APPKER.BWR.] ------------------------------ Date: Mon, 7 Dec 87 15:22 EST From: <ACCESS@ALCANKTN.BITNET> (Shawn Allin - Alcan KRDC Computer Services) Subject: Kermit Found for Convex Keywords: Convex Kermit I sent a question to you concerning the availability of Kermit for a Convex supercomputer some months ago, and at that time you were unaware of a version for it. I just thought I'd get back to you with the news that there is now a version running on it. The only identification I have found on it so far is "UCL Remote-only Kermit, V15B, March 1986". I can look into it more, if you want further information. Regards, Shawn Allin Alcan International Ltd., P.O. Box 8400, Kingston, Ont., Canada K7L 4Z4 (613) 541-2178 Bitnet: ACCESS@ALCANKTN (ALLIN@QUCDNSUR is alternate address if routing tables aren't updated yet) [Ed. - We don't seem to have it in our collection. If someone can send it in, along with some more information about the machine and operating system (apparently this is not the Convex that runs Unix), we'd be glad to add it to the Kermit distribution.] ------------------------------ Date: Wed, 25 Nov 87 15:32 EST From: GARTLEY%alcoa.com@RELAY.CS.NET Subject: Need Kermit for IBM System 9000 Keywords: IBM System 9000 Kermit Please help. I am looking for a version of Kermit that will run on an IBM System 9000 Pascal V1.2 CSOS. I do not know what all that means but that was on the operating manual (This is not my system ). Thanks John Gartley Gartley@alcoa.com (CSnet) or Gartley@aldncf.alcoa.com (ARPAnet)...after 1-DEC-87 ------------------------------ Date: Wed, 18 Nov 87 22:14 EST From: Bryan Lally <M014BL02@VB.CC.CMU.EDU> Subject: Kermit Wanted for Old RSX-11m v3.2 Keywords: RSX Kermit, PDP-11 Help! For reasons we won't go into, I need a KERMIT for a PDP-11 system running RSX-11m v3.2. This means RMS v1, not v2. Anyone got one? The new ones won't work, 'cause they need RMS v2. Replies to: bryan lally M014BL02@cmccvb.cc.cmu.edu M014BL02@cmccvb.bitnet ------------------------------ End of Info-Kermit Digest ************************* -------