Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!usc!zaphod.mps.ohio-state.edu!sunybcs!bowen From: bowen@cs.Buffalo.EDU (Devon Bowen) Newsgroups: comp.sys.cbm Subject: Re: Kermit 2.2 Message-ID: <17775@eerie.acsu.Buffalo.EDU> Date: 15 Feb 90 02:48:55 GMT References: <6683@ucdavis.ucdavis.edu> Sender: nobody@acsu.Buffalo.EDU Reply-To: bowen@cs.Buffalo.EDU (Devon Bowen) Distribution: usa Organization: State University of New York at Buffalo/Comp Sci Lines: 43 In article <6683@ucdavis.ucdavis.edu>, ez001287@deneb writes: > I figure that once I get the termcap working, I should just be able to give > the "sysline" command to activate the 25th line status line. When I do > that now, I also get the error above. Does anyone know how these things > work? The best way to set up the termcap by yourself (without have the system administrator doing anything) is to set the environment variables in a file that is sourced during your .login (or you can even put the file *in* your .login file if you want). Attached is a uuencoded file that has all the commands you need to activate the kerm64 termcap. Just clip it out with your favorite editor and run it through uudecode. This will create a file named kerm64_init. Then add the line "source kerm64_init" to the end of your login file and the next time you log in the system will automatically set things up for kermit. Let me know if you have problems with this. Devon --------------------------------cut here---------------------------------- begin 644 kerm64_init M33IC23IT93U<15L_ M-V@Z=&D]7D]<15L_-VPZ=',]7$4W7$5;)6DR-3LE9$A<15MM7$5;,4LZ=64] M7$5;;3I54#U<15LE9$$Z=7`]7$5;03IU