1-Oct-91 21:04:03-GMT,26831;000000000001 Return-Path: <@cuvmb.cc.columbia.edu:I-KERMIT@CUVMA.BITNET> Received: from cuvmb.cc.columbia.edu by watsun.cc.columbia.edu (5.59/FCB) id AA03006; Tue, 1 Oct 91 17:03:55 EDT Message-Id: <9110012103.AA03006@watsun.cc.columbia.edu> Received: from CUVMB.COLUMBIA.EDU by CUVMB.COLUMBIA.EDU (IBM VM SMTP R1.2.1) with BSMTP id 3954; Tue, 01 Oct 91 17:05:21 EDT Received: from CUVMA.BITNET by CUVMB.COLUMBIA.EDU (Mailer R2.07) with BSMTP id 7242; Tue, 01 Oct 91 17:05:13 EDT Date: Tue, 1 Oct 1991 17:01:43 EDT Reply-To: Info-Kermit%watsun.cc.columbia.edu@cuvmb.cc.columbia.edu Sender: INFO-KERMIT Digest From: Christine M Gianone Subject: Info-Kermit Digest V14 #8 Comments: To: Info-Kermit@watsun.cc.columbia.edu To: Multiple recipients of list I-KERMIT Info-Kermit Digest Tue, 1 Oct 1991 Volume 14 : Number 8 Today's Topics: New Patch File for MS-DOS Kermit 3.11 New Serial Printer Driver for MS-DOS Kermit Printing from MS-DOS Kermit on a Novell Printer Problems with DOS 5, DesqView, and MS-DOS Kermit Running MS-DOS Kermit 3.11 under DesqView MS-DOS Kermit 3.11 and Packet Drivers DEPCA Success with MS-DOS Kermit 3.11 MS-DOS Kermit 3.11 Packet Size Problem with TCP/IP Kermit 3.11 TCP/IP Connections Dropping PC Kermit 3.11 Q&A: A Small Correction Something Good in DOS 5.0 for MS-DOS Kermit MS-DOS Kermit Keyboard Problems MS-DOS Kermit and Hebrew? MS-DOS Kermit and Horizontal Scrolling? Digest submissions may be sent to Info-Kermit@WATSUN.CC.COLUMBIA.EDU or KERMIT@CUVMA.BITNET. Requests for addition to or deletion from the Info-Kermit subscriber list should be sent to LISTSERV@CUVMA.BITNET or LISTSERV@CUVMA.CC.COLUMBIA.EDU. These messages must be of the form: SUBSCRIBE I-KERMIT (To start a subscription) UNSUBSCRIBE I-KERMIT (To cancel a subscription) REGISTER I-KERMIT (To correct your name) Kermit files may be obtained over networks and by mail order. On the Internetwork, use FTP to log in to host WATSUN.CC.COLUMBIA.EDU, a SUN-4/280 running UNIX (SUNOS 4.1), IP host number 128.59.39.2. Login as user anonymous (note, lower case), any password, and GET or MGET (MULTIPLE GET) the desired files. The Kermit files are in directories kermit/a, kermit/b, kermit/c, kermit/d, and kermit/e. Test versions are in kermit/test. All files in these directories should be transferred in text (ASCII) mode. Binaries are in kermit/bin (use ftp in binary mode). You can also get Kermit files over the BITNET/EARN network; to get started send a message with text HELP to KERMSRV, the Kermit file server, at host CUVMA. For detailed instructions, read the file kermit/a/aanetw.hlp (AANETW.HLP on KERMSRV). To order by mail, request a complete list of Kermit versions and an order form from Kermit Distribution, Columbia University Center for Computing Activities, 612 West 115th Street, New York, NY 10025 USA. ---------------------------------------------------------------------- Date: Sun, 29 Sep 91 21:35:02 EDT From: "Joe R. Doupnik" Subject: New Patch File for MS-DOS Kermit 3.11 Keywords: MS-DOS Kermit 3.11 Patches Here is a new patch file containing patches 1 to 4 for MS-DOS Kermit 3.11, IBM PC version. Patch 1 (optional): Supply an alterate video mode for the Orchid Designer Professional VGA board when switching from 80 to 132 columns. Patch 2: Correct unwanted double echo from TCP/IP Telnet negotiations. Patch 3: Correct cursor indexing problem with scrolling region setup. Patch 4: Correct nested curly brace matching in Kermit commands. Joe D. [Ed. - Thanks, Joe. The new patch file is in kermit/a/mskermit.pch on watsun (Internet) and MSKERMIT PCH on KERMSRV@CUVMA (BITNET/EARN). To apply these patches, store this file in the same directory as your MSKERMIT.INI file and uncomment the PATCH command in your MSKERMIT.INI file.] ------------------------------ Date: Tue, 1 Oct 91 12:00:00 EDT From: Christine M Gianone Subject: New Serial Printer Driver for MS-DOS Kermit Keywords: Printers, Serial Printers, MS-DOS Kermit and Serial Printers One of the most common questions about MS-DOS Kermit is how to use it with a serial printer. In the words of Joe Doupnik: "MS-DOS Kermit prints by sending material straight to DOS. It does so by gathering up to 128 bytes in a buffer, sends an XOFF to the host (if flow control is being used), does a buffer write to DOS, and then sends an XON to the host. In the buffer writing process there are also checks on whether DOS thinks the printer is ready and that all the characters were accepted, etc. "By using DOS rather than the IBM PC BIOS interrupts or even particular hardware we gain the ability to write the code once for many kinds of machines, remove a mountain of code necessary to manipulate either serial or parallel ports (if they exist), and most importantly we can write to networked printers and print-to-disk TSRs and whatnot. We can also change the name of the print channel used by Kermit from PRN to any legal DOS name (SET PRINT command)." But DOS does not include any provision for flow control with a serial printer (parallel printers do this in hardware, automatically). Therefore it is common to have printing problems when your communication speed with the host is faster than your printer's speed. The solution is to install a printer driver that provides the needed flow control between the PC and the printer. Joe Doupnik recently found such a (public domain) utility and sent it in. Originally called XONXOFF.COM, it was written by Frank Whaley in 1989. It works only for COM1, so it would be nice if somebody fixed it to allow any COM port (address and IRQ) to be specified on the command line. It can be picked up from Kermit Distribution as kermit/a/mspspd.* on watsun (Internet) or MSPSPD * from KERMSRV on CUVMA (BITNET/EARN). The files are mspspd.asm (the assembler source file), mspspd.hlp (a help file), and mspspd.boo (a "boo" encoding of the binary .COM file). Also, on watsun only, the binary .COM file is available in kermit/bin/mspspd.com. ------------------------------ Date: Mon, 16 Sep 91 14:29 EST From: Clement Lepoutre Subject: Printing from MS-DOS Kermit on a Novell Printer Keywords: Printers, MS-DOS Kermit and Printers, Novell Networks We have a PC which is hooked up to an old Novell network system. It connects to our mainframe where the person does some lists. We have been able to print those lists on the networked printer but get some errors at higher speeds (e.g. 9600). In other words, at 9600 the whole list does not get printed whereas at 1200 the list comes out fine. We feel the higher speed is too fast for the network or Kermit to handle. Is there something settable in Kermit for it to take a larger or smaller hunk of information before it gets sent to the printer? We would like to work at a speed faster than 1200, obviously. Thanks for any suggestions. [from jrd - Plan A: It's neither the network nor Kermit having the problem, but rather the PC. Whatever is doing the printing on the PC is keeping interrupts off for long periods and that prevents the serial port from notifying Kermit that a new character has arrived. The slower the machine the more likely this will be. I try very hard to avoid this specific problem by first buffering characters within Kermit, up to 128 of them, then when the buffer fills I first tell the host XOFF, then ask DOS to print them, finally tell the host XON. If you have turned off flow control in Kermit then these hold-ups are not sent. If you use a print spooler in the PC to pass information to the printer then (a) that spooler will eat lots of CPU cycles, alas, and (b) it may do so well after Kermit has done the stop/print/start work. If this is the case then please don't use the spooler (the DOS PRINT command is such a beast too). Another case is using a printer on a serial port and the serial port driver is consuming the machine so that Kermit's port can't get through. In that case try a different serial port driver, or use a parallel port. Beware of having TSRs present which consume lots of CPU cycles. Plan B: If the "mainframe" in your message is an IBM one, and your connection to it is a half-duplex linemode connection, flow control can't be done. The only workaround in this case is to send printed material to your disk instead of to the printer (SET PRINTER filename) and later print the file by ordinary means. Without flow control, the mainframe will easily overrun the printer.] ------------------------------ Date: Thu, 12 Sep 91 19:25:34 MEZ From: Erich Neuwirth Subject: Problems with DOS 5, DesqView, and MS-DOS Kermit Keywords: DOS 5.0, MS-DOS Kermit and DOS 5.0 Keywords: DesqView, MS-DOS Kermit and DesqView I have problems with MS-DOS Kermit since I installed DOS 5. Not under plain DOS, but when I am running DesqView under DOS 5. I tried DesqView 2.31 and DesqView 2.34, and in both cases it does not work. (Additionally I am running QEMM 5.11, I do not yet have a later version.) When I open a DesqView window containing Kermit the machine simply hangs and does not accept any keyboard input any more. Even Ctrl-Alt-Del does NOT work, so I really have to switch off. The problem occurs both with Kermit 3.10 and Kermit 3.11. The problem also occurs when I use TAME (i.e. TAME-RES.COM) before running Kermit. My machine is a Mycomp 25 MHz 386 with 4 MB of memory and an AMI BIOS. Usually I have not experienced any compatibility problems. Am I alone with this kind of problem or are more people experiencing something similar? [Ed. - Later, Erich writes:...] The DesqView people solved my problem, and you might be interested in the solution. You have to set Optimize communications in the Advanced Setup menu to NO. Then it works. The manual, though, states, that then you might have problems with higher baud rates (4800 and higher). Since currently I am running at 2400 bps, this is no problem. ERICH NEUWIRTH BITNET (EARN): A4422DAB@AWIUNI11 INTERNET: A4422DAB@VM.UNIVIE.AC.AT Institute for Statistics and Computer Science UNIVERSITY OF VIENNA, UNIVERSITAETSSTR. 5/9, A-1010 VIENNA, AUSTRIA ------------------------------ Date: 23 Sep 91 16:48:18 GMT From: w8sdz@rigel.acs.oakland.edu (Keith Petersen) Newsgroups: comp.binaries.ibm.pc.archives,comp.os.msdos.desqview Subject: Running MS-DOS Kermit 3.11 under DesqView Keywords: DesqView, MS-DOS Kermit and DesqView I am running MS-DOS Kermit v3.11 in a DESQview window. It takes more memory than the previous version but works fine for me. Change a Program Program Name............: Kermit COM2 Keys to Use on Open Menu: KR Memory Size (in K): 265 Program...: \bin\kermit.exe Parameters: take kermit2.ini Directory.: \incoming Options: Writes text directly to screen.......: [N] Displays graphics information........: [N] Virtualize text/graphics (Y,N,T).....: [N] Uses serial ports (Y,N,1,2)..........: [2] Requires floppy diskette.............: [N] Change a Program Advanced Options System Memory (in K).......: 0 Maximum Program Memory Size (in K)..: Script Buffer Size.......: 0 Maximum Expanded Memory Size (in K): 0 Text Pages: 1 Graphics Pages: 0 Initial Mode: 3 Interrupts: 00 to FF Window Position: Maximum Height: 25 Starting Height: 20 Starting Row...: 5 Maximum Width.: 80 Starting Width.: 40 Starting Column: 5 Shared Program Pathname..: \dv\noff.shp Data......: Close on exit (Y,N,blank)......: [Y] Uses its own colors..............: [Y] Allow Close Window command.....: [N] Runs in background (Y,N,blank)...: [Y] Uses math coprocessor..........: [N] Keyboard conflict (0-F)..........: [0] Share CPU when foreground......: [Y] Share EGA when foreground/zoomed.: [Y] Can be swapped out (Y,N,blank).: [N] Protection level (0-3)...........: [0] In AUTOEXEC.BAT I have this, to minimize Kermit's use of memory: set KERMIT=ROLLBACK 0 Keith Petersen Internet: w8sdz@rigel.acs.oakland.edu or w8sdz@vela.acs.oakland.edu Uucp: uunet!umich!vela!w8sdz BITNET: w8sdz@OAKLAND ------------------------------ Date: Sat, 21 Sep 91 06:36:36 EDT From: Russ Nelson To: Info-Kermit@watsun.cc.columbia.edu Subject: MS-DOS Kermit 3.11 and Packet Drivers Keywords: Packet Drivers, MS-DOS Kermit 3.11 and Packet Drivers Keywords: DEPCA Ethernet Interface Q: Why can't I make a TCP/IP connection with Kermit when I am also running PC-NFS? A: Because the packet driver allows each protocol (such as ARP, RARP, IP, UDP, IPX, etc) to be used by only one application at a time. This is a limitation of packet drivers. A2: Strictly speaking, it's a limitation of protocol stacks. You can only run one protocol stack per node. Otherwise, you'll have problems, e.g. which TCP/IP stack would answer ICMP messages? Q: I can't make Kermit work with the Clarkson DEPCA.COM packet driver and a DEC DEPCA Ethernet board. A: We have had several reports like this. So far nobody has reported success with this one. A2: The DEPCA.COM packet driver version 9.0 is known to fail on Turbo DEPCAs (DE-200), and old DEPCAs. There is an interim release of it that fixes the Turbo DEPCA problem on sun.soe.clarkson.edu, in pub/ka9q called depca.com. I am working on reverse-engineering the differences between the new and old DEPCAs, so eventually it will be made to work on the old DEPCAs also. [Ed. - Thanks, Russ! More about the DEPCA below...] ------------------------------ Date: Mon, 23 Sep 1991 13:19 +1200 From: "John Davis" Subject: DEPCA Success with MS-DOS Kermit 3.11 Keywords: Packet Drivers, MS-DOS Kermit 3.11 and Packet Drivers Keywords: DEPCA Ethernet Interface >Q: I can't make Kermit work with the Clarkson DEPCA.COM packet driver and > a DEC DEPCA Ethernet board. > Well, you now have at least _one_ success story :-) I just ftp'd MS-DOS Kermit 3.11 and installed it on my machine, which runs one of the older DPECA's (full length, 8 bit model - predates the current LC/TURBO models). I'm using the v9.1 clarkson DEPCA driver (which does work even though it doesn't really support the older card - only probs are the ethernet address is set to a ridiculous number, and promiscuous mode doesn't work), installed on interrupt 0x7e (as SOSS requires that interrupt vector for the packet driver), card is set for IRQ=5, IO=300h, and full 64K of memory at D000:0000. This setup works just fine with NCSA telnet, and after filling in the appropriate section in MSKERMIT.INI it also works fine with MS-DOS Kermit 3.11... John Davis - CHEM194@csc.canterbury.ac.nz (Depart)mental Programmer,Chemistry Department University of Canterbury, Christchurch, New Zealand [Ed. - From a similar message from Robert L. Divany, : "Old and new DEC cards seem to be referred to collectively as DEPCA cards, even though they are quite different. DEC refers to the new cards as Etherworks controllers. The DEPCA packet driver was released at about the end of 1990, and was based on specifications supplied to Clarkson by DEC. A note from DEC is included with the Clarkson PD distribution in a file named DEPCA.NOT. Quoting from that file, "The Driver supports our most current technology, and not, unfortunately, older DEPCA's". In spite of this, I have used the Clarkson DEPCA driver from release 8 and 9 with success on some, but not all, new DE cards and on an older DEPCA (series E02) card. I have used release 9.1 of the driver with success on ALL DE and DEPCA cards tested. This includes the DE100 LC card, the DE200 Turbo, the DE210 Microchannel card and older DEPCA cards, both series D and E. I suggest that version 9.1 of the driver be tried if earlier versions fail. Note that version 9.1 is not the same as the driver supplied with the last release of the packet driver collection (version 9). Version 9.1 is available for anonymous FTP from SUN.SOE.CLARKSON.EDU in /pub/packet-drivers/depca.com. Be sure to use binary (Image) mode."] [Ed. - And from Andy Evans, Plymouth State College, Plymouth, NH : "I have more than 100 of the 'old' DEPCA cards on our campus. We have site license for PathWorks V4.0 and I picked up DEC's Client TCP/IP package for evaluation. It contains just what you are looking for, an NDIS driver for that card. Packet-Drivers run quite nicely with it, and I haven't found a Packet Spec. application that didn't! If you chose to run just packets, you can retain 605K+ of low DOS memory on a 386 with Quarterdeck. This is the only way I've successfully run TCP/IP on that card (DEC's driver). The full implementation of DEC's Client TCP/IP is a bit of a memory hog. Allows redirection of disks (file services) and printers - a big plus. DEC's TCP/IP NDIS suite was written by someone else (3COM / Hewlett Packard) When I had some initial bugs the folks in Atlata (DEC Tech Suppt) expressed dissatisfaction with it and the fact a replacement might be considered (by DEC). In time I have grown to like it, Packet Drivers over NDIS with DIS_PKT.DOS works quite well. We are heavy Kermit users and have been enjoying the new version regardless of communication protocol - it does 'em all doesn't it!??!!"] ------------------------------ Date: 24 Sep 91 17:20:26 GMT From: ccastd2@prism.gatech.edu (Dale Phurrough) Subject: MS-DOS Kermit 3.11 Packet Size Problem with TCP/IP Keywords: Packet Drivers, MS-DOS Kermit 3.11 and Packet Drivers Keywords: TCP/IP, MS-DOS Kermit 3.11 and TCP/IP I remember the problem in 3.10 with packet sizes using the Ungermann Bass ports and such. Does this problem persist in 3.11 using the packet drivers with the TCP/IP port? It seems to. I had to reduce my sending packet size to 128. My receive packet seems to be OK at any size. Any ideas out there? [From jrd - Kermit will try to fill a TCP packet, about 512 bytes of data, until a short timer expires. A straight UB connection gets offered up to 512 bytes of data (or to the end of a Kermit packet). The indications are some part of your UB network cannot stand such long packets. That is also true of some other terminal-like network pathways, such as LAT and TES, at roughly 256 and 512 bytes respectively. And they too are able to send longer material to us than vice versa. The reasons are in the way those pieces of software are designed; they expect more terminal activity than long file transfers.] ------------------------------ Date: 25 Sep 91 00:33:24 PST From: "Terry McKiernan" Subject: Kermit 3.11 TCP/IP Connections Dropping Keywords: TCP/IP, MS-DOS Kermit and TCP/IP I'm having a problem maintaining MS-DOS Kermit 3.11 TCP/IP connections. Can you lend a hand? Here is my setup: MS-DOS Kermit (MSVIBM) 3.11, from watsun.cc on September 19. various PCs, XTs, ATs HP EtherTwist 10-baseT adapters, HP hubs NetWare 3.11, TCPIP.NLM loaded, rip=yes, forward=yes BYU packet-driver IPX v. 2.01 Clarkson packet driver v. 9.0.0 Internet connection via PS/2 ethernet-to-token bridge (AIX) The problem is, we can make connections to Internet sites, but as soon as we connect, the connection is dropped. The "connected" screen appears for a split second (clear screen, status bar at bottom, beep), then the connection drops and we are back at the MS-Kermit> prompt. [From jrd - I don't want to create wrong ideas by speculating, but it is possible the NetWare 3.11 server is not transmitting all the packets in both directions. That is typically a subnet mask error. I have not yet had a chance to route TCP through my NW 3.11 server so I offer this only as speculation.] ------------------------------ Date: Tue, 24 Sep 91 00:54 PDT From: Denis DeLaRoca Subject: PC Kermit 3.11 Q&A: A Small Correction Keywords: Packet Drivers, MS-DOS Kermit 3.11 and Packet Drivers Keywords: Token Ring, SLIP The latest Kermit digest contains a very useful Q&A summary for the newly released TCP-based PC-Kermit... it points out that it doesn't run on SLIP or Token Ring Packet drivers as framing for those protocols has not yet been implemented in the TCP/IP code. True for the SLIP case and only half true for the TR case. The current TR PD is a "fake" Ethernet driver (type=1) and thus quite compatible with the TCP/IP code in Kermit! -- Denis DeLaRoca UCLA Office of Academic Computing [Ed. - Thanks, Denis. Many people said this. Yes, Kermit does indeed work over the IBMTOKEN.COM packet driver because IBMTOKEN.COM is an Ethernet class driver. But it does not work over Token-Ring class packet drivers, nor over ODIPKT over Token Ring.] ------------------------------ Date: Mon, 23 Sep 1991 10:56 GMT-0200 From: Petri Kaukasoina Subject: Something Good in DOS 5.0 for MS-DOS Kermit Keywords: MS-DOS Kermit and DOS 5.0 Keywords: National Keyboards, MS-DOS Kermit and National Keyboards In previous versions of DOS the foreign keyboard program KEYB caused trouble. Kermit could not receive all characters if the keyboard was used at the same time. But in MS DOS 5.00 the bug does not exist! (By the way, I don't have extended memomy, so I do not use the new memory managament capabilities of DOS 5.) ------------------------------ Date: Sat, 24 Aug 1991 19:11:20 GMT From: s33672e@puukko.hut.fi (Mikko Leino) Subject: MS-DOS Kermit Keyboard Problems Keywords: National Keyboards, MS-DOS Kermit and National Keyboards I have 2 problems here: 1) How can I put a '|' -character into a "set key"-definition? ex. set key \2323 get file.txt "| less" ^^^ the above example results in a "v"-character instead of "|". [Ed. - Such a SET KEY command works on US keyboards, so this is probably an artifact of your Finnish keyboard or driver. Instead of using a literal vertical-bar character, insert its character code \124. If that doesn't work, you might also have to give the command SET TRANSLATION KEY OFF.] 2) Is it possible to make Kermit go to command line from interactive mode? ie. if you enter the command "connect" you enter into the interactive mode, but it seems that you cannot return. [Ed. - The normal advice is: "Type Ctrl-] followed by the letter C to return to the prompt". But with certain national keyboards or drivers, it is physically impossible to type the Ctrl-] combination, however there is usually some other key combination that generates the same code. Ctrl-], Kermit's normal escape character, is ASCII code 29. On the German keyboard, for example, this may be entered by typing Ctrl-+ (hold down the Ctrl key, marked "Strg" on the German keyboard) and press the plus (+) key. On IBM PCs and compatibles, you can also escape back by holding down the Alt key and pressing the lowercase letter 'x'.] Mikko Leino s33672e@puukko.hut.fi ------------------------------ Date: Sun, 1 Sep 91 19:33:12 +0200 From: oren alex Subject: MS-DOS Kermit and Hebrew? Keywords: Hebrew, MS-DOS Kermit and Hebrew Is there a way to use Hebrew characters (8-bit) in Kermit's VT emulation? I tried the translation table feature - no go. [Ed. - Yes, it can be done. First, your PC must have a Hebrew code page loaded (CP862?). Second, you must construct a file on your PC of the form: SET TERMINAL CHARACTER-SET TRANSPARENT SET TERMINAL BYTESIZE 8 SET TRANSLATE INPUT \xxx \yyy SET TRANSLATE INPUT \xxx \yyy ... SET TRANSLATE INPUT ON SET TERMINAL DIRECTION RIGHT-TO-LEFT In the SET TRANSLATE INPUT commands, \xxx is a host character code (for example, in the ISO 8859-8 Latin/Hebrew Alphabet) and \yyy is a PC character code to translate it into. You need one of these commands for each Hebrew character and other 8-bit character. If you have a Hebrew keyboard, you can make a SET KEY command for each Hebrew key to make it translate the PC key code into the corresponding host character code before transmission. This technique works for any code-page / terminal-character-set combination that is not directly supported by MS-DOS Kermit, such as Cyrillic, Greek, etc. The only thing that is particular to Hebrew (and Arabic) about this example is the command SET TERMINAL DIRECTION RIGHT-TO-LEFT. Complete examples of how to do this for Cyrillic character sets can be found in the *.ini files in the kermit/charsets directory on watsun (Internet only). MS-DOS Kermit does not yet support Hebrew text file translation during file transfer.] ------------------------------ Date: Mon, 9 Sep 91 15:10:12 PDT From: "Trevor Warwick" Subject: MS-DOS Kermit and Horizontal Scrolling? Keywords: 132 Columns, MS-DOS Kermit and 132 Columns, Horizontal Scrolling My PC (a DEC VAXmate) doesn't support 132 column mode, and I guess that quite a few older PCs, as well as newer laptop/portable PCs also only support the simple video modes. It would be very useful if MS-DOS Kermit had a way of scrolling the screen from side to side. So, when presented with a line that is longer than 80 characters, it would be nice if you could press a key and see the text that has disappeared off the right hand edge of the screen, and be able to modify it. The model is of the terminal screen as a window which you move over the text that is actually on the larger underlying surface. [Ed. - This is actually a common request, and falls into the category of "better support for 132 column mode" mentioned in the wish-list section of the MS-DOS Kermit 3.11 announcement. This would be a major undertaking, as would the various other possible solutions for the EGA and VGA. The wish-list for MS-DOS Kermit is long, and many of the items on it are major development projects. At this point, the best way to get these features into Kermit is to encourage your company to fund the Kermit development effort.] ------------------------------ End of Info-Kermit Digest *************************