Kermit 95 Survey Responses - What do you use Kermit 95 for?

1. ssh terminal emulation
2. Have used Kermit for well over 15 years as an intercomputer file sharer and terminal program. Also used K95 from the start and still use it for Secure FTP.
3. I use K-95 as my terminal of choice and SSH and Telnet client for accessing several *nix systems from Windows workstations. I also use K-95 to keep files synchronized between a desktop and a laptop computer. I use K-95 every day.
4. scripting terminal emulator
5. telnet/ssh client
6. Great for scripting multi-hop ssh sessions through firewalls and into systems at work, and since the kermit file transfer protocol works across all the hops, I can use it to send files back and forth without also needing complex multi-hop scp command syntax. Also supports the secure FTP I need to talk to my ISP's web server to update my web pages.
7. telnet to a bbs, as a telnet/ssh client for diagnostic purposes
8. Inter-OS compatibility
9. Primary Terminal Emulator for connection between windows and VMS systems
10. I am a programmer/consultant (30 years experience)
11. SSH/Telnet connections to our many lab machines
12. file transfer;
13. We used Kermit as part of the automation running on a WinXP system to collect data from a remote embedded system. I chose it for its reputation of robustness and flexibilty.
14. mostly telnet access to work computers (VMS and Unix)
15. I use it as a replacement Telnet client and as a packet radio terminal program.
16. Terminal-style connection to a timesharing computer that is a central part of our business
17. Workplace: Data Entry and Tracing
18. Secure FTP scripting
19. needed secure login (ssh and Kerberos) with good terminal emulation support, especially fond of Kermit 95's easy-to-use scrollback buffer.
20. we purchased kermit95, but have not used it yet. we are working on a new fisheries data communication system, which could depend on tcp/ip or voice communications. currently, we use ComspecDPI JFT.
21. To FTP large batches of files. Chose Kermit for the scripting features that let us trap FTP errors and retry puts, exit gracefully, etc.
22. PBX Support
23. industry standard
24. I've been a Kermit user since 1991, on Unix and Windows.
25. Nowadays my K95 is primarily for ssh sessions to my Linux boxes. Recently I also started connections to various Unix boxes (HP-UX/Tru64/Linux/VMS) at work using a VPN connection. In the old days I just needed a good terminal emulation for modem connections.
26. I have moved to Putty and Winscp for the most part, but since Kermit is the ONLY industrial strength Terminal Emulator AND file transfer protocol that works across mutliple links, it is still nice to be able to tunnel through a maze of Nix boxes behind a firewall and grab files in one one step, end to end transfer. Long live Kermit!
27. Mainly for terminal emulation.
28. Remote connectivity via telnet & SSH. Occasional use for serial connectivity (such as backups of my HP calculators). It is simply the best telnet/ssh client I have ever used.
29. Powerful and flexible. I am generally a linux user and I have come to love kermit.
30. Telnet with integrated file transfer. Excellent terminal support across Solaris, AIX, and Linux. Excellent command-line FTP client.
31. Possibility to control via VB programme
32. Management and remote eaccess of network equipment with telnet/SSH based CLI (Cisco, Juniper, Netscreen, Nortel, Sun/Solaris).
33. FILE TRANSFER VIA SSHD AND SECURE FTP
34. Transfer files from a Win 95 computer
35. To send stock purchase orders from retail supermarkets to a mainframe.
36. modem to modem transfer files
37. We use Kermit as a replacement for ICE 10 terminal emulation for our old office serial LAN.
38. FTP transfers between Windows and VMS servers, both at home and at work.
39. I like the flexibility of the scripting language that supports Telnet or SSH, and the terminal emulation.
40. I need it for my HP49G
41. access to linux boxes via ssh mostly, some serial port connections too.
42. pc to VAX communication
43. Windows dialin. Have been a Kermit user for 20 years.
44. SSH client, serial
45. Own use for personal ftp
46. Securely log onto my SSH enable Linux-based router.
47. Connect to the FPGA b'd
48. Terminal Emulation & File Transfer
49. Connection to a cp/m-Computer
50. to communcate with my 68HC11
51. VT320/220 terminal emulation for serial connection to a Digital Alphastation 200 4/166 running OpenVMS 7.3-1 (hobbyist system); ssh to Solaris systems; file transfers to/from computers and devices without an Ethernet connection.
52. ftp copy
53. Access to UNIX, OpenVMS and MS Windows/SUA to do software development.
54. for realiable, stablish to bigsize file as details billing records of telephone switching (hundreds of MBytes.
55. to access unix based applications from windows workstations. works well, flexibly configurable keys, secure fail transfer... a wonderful product.
56. All sorts of logical communication tasks
57. Connecting to UNIX hosts on my LAN and, with prior arrangement, to our customers machines via the Internet. In the past I used K95 extensively for modem dialing and serial communication.
58. I use for transfering data between PC (Windows XP) and HP48GX. I use it because of its compatibility
59. Serial communication with lots of devices, like routers, switches, servers.
60. I use Kermit95 almost every time I connect via telnet or ssh. I chose Kermit95 because it was the available kermit on Windows.
61. Wanted accurate VT100 emulation for OS/2 and Win95
62. It's simply the best client for power users as it supports FTP, Telnet, SSH, etc. One scripting langauge provides easy glue to tie all the protocols together, and only one program to learn. The terminal emulation is top-notch.
63. For work.
64. I need upload image linux into the flash of embedded system.
65. interface with chemical instrument
66. Accessing our Linux / Unix Servers
67. Telnet and SSH connections, integrated FTP client and support for file transfer over existing telnet/ssh connection
68. file transfert
69. Reading I2C capture files
70. I chose Kermit95 to have a consistent terminal emulator to use on dialup and network sessions.
71. university
72. terminal emulation
73. "host access" - because it is (still) the best tool for this purpose
74. Terminal emulation
75. I use Kermit95 as a terminal emulator when I'm forced to use a Windows machine. I choose Kermit because I have used Kermit for file transfers on UN*X, VMS, MS-DOS and just about every other system I've ever used.
76. Internationalization
77. Communications, and other automated programs.
78. program cisco equipment
79. Connection to legacy system
80. A very good file transport.
81. ftp transfers
82. Serial Connection
83. FTP transfers between rs6000/AIX and Windows
84. Mainly for the terminal emulation for QNX.
85. terminal emulation
86. I use Kermit 95 to transfer medical information to insurance companies and other health care organizations. I chose Kermit 95 because of the large experience base that the developers of Kermit bring to the software. I also like that the scripting language is stable and when changes are made to Kermit the older scripts still work. The scripting allows us to automate complex procedures so are clients who are not rocket scientist can get their job done.
87. unix to windows interface
88. Manejo estación sismica Quanterra [I manage the Quanterra seismic station]
89. remote access to VMS and Unix/Linux operatin systems. Chosen for simplicity uniformity across platforms and robust scripting
90. connctions to a variety of c-kermit systems
91. dumb terminal use in laptop
92. Excellent terminal emulation and scripting for many years and many OSs. I use it on eComstation all the time.
93. Transfer files
94. Kermit file transfer on windows to embedded systems. I chose kermit 95 because the kermit software is still better than other software.
95. I use it to connect to a large variety of computers and terminals that other programs will not handle. Also, convert Procomm Aspect scripts to Kermit scripts.
96. Needed effective scripting for FTP on a Windows server, and have used kermit on HP-UX
97. Does what I need.
98. win2000
99. I use kermit for ssh access to servers
100. To install programs on my HP 48G, and HP48GX scientific graphing calculators.
101. Connecting to a variety of UNIXoid and mainframe systems, as well as scripted data transfer
102. Familiarity with Kermit, and it's rock-solid foundations.
103. accessing cisco kit
104. ssh
105. Communication with Unix servers at work through VPN.
106. I use it for terminal emulation.
107. terminal access
108. telnet and ftp in business.
109. File transfer of weather reports
110. scripting capacity
111. To connect pc's to a sco unix server so that an analytic balance connected to the pc will communicate with the unix server. Because of the transparant printing and that it will emulate a wyse 60 terminal.
112. unix host access
113. Remote access to various Unix servers, technical support, field reports, data upload and download. Chose Kermit 95 because I have used C-Kermit on Unix for years, helped (in a small way) with development.
114. terminal emulation to all kinds of devices-switches, routers, wireless, PBX, .... Use it because it works and the Xmodem function is easiliy scriptable for loading images to non-functioning devices.
115. Vendor required it
116. Scripted Download and delete recursively
117. I have not.. but I intend to cause it is the only RFC compliant ip to serial client
118. In place of Hyperterminal to troubleshoot modems
119. Need to command line ftp from a windows 2000 box and need passive mode.
120. Scripting and completeness of protocol usage. It is such a good communications program.
121. AS A TERMINAL FOR OUR MEDICAL BILLING SOFTWARE
122. ssh scripting
123. I've used kermit since I bought Hays 300 modem.
124. connection to an hp48 calculator
125. ftp
126. Emulator for DataTrac system called STATIS.
127. Laboratory Equipments
128. for job reason
129. xfer files
130. SSH terminal connections to mostly OpenVMS systems at work. I choose K95 because it simply works and has features that, while not used often, I know are there.
131. Kermit is used as an interface to rs232 ports, both local and networked. It also provides a command line interface to networked computers.
132. I am fimilar from a former work place.
133. Telnet/ssh access to unix type systems. I've kept using K95 because of the excellent terminal emulation support
134. First to automate interactions with console software, second to trasfer files, third as flexible terminal.
135. Terminal emulation
136. to maintenance solaris
137. To download files at a remote connection.
138. To save old data from ancient laptop to my PC
139. Remote Terminal Emulation
140. Taking to and transfering files from my PC to my Hp48GX calculator
141. Telnet to UNIX/Linux/Windows (character based applications)
142. I use Kermit95 for the development of a embedded system based on arm linux. A great number of documents on the Internet recommend Kermit95 to me. therefore.
143. To access our Informix database system on a Sun Ultra 10 using Solaris 9 via PCs
144. I use K95 to connect to remote devices; Paging Transmitters mostly. The dialer makes this extremely easy. I also use Kermit's Telnet feature to get to other devices over the Internet. I use K95 because it runs on a windows platform. I've been using Kermit since DOS 3.1
145. I want to use it for submitting medical claims. I chose Kermit 95 because I recognized the name.
146. Scriptable feature
147. Running our application on Unix servers. We chose it because of price, functionality, and support.
148. Bootloader only supports Kermit download protocol
149. QNX emulation. Kermit is the best at QNX emulation
150. VMS Terminal emulatiom
151. Robust, well-documented ssh client incorporating file transfer
152. Access to SCO servers
153. I needed a scriptable solution for work ... I need to write a program at work that will page me when a server goes down. I'm using Kermit 95 as part of the solution.
154. Telnet, ftp, ssh, http
155. Use it for Programatic file transfer.
156. Serial communication with Cisco devices
157. Script/error tracking auditing of file creation and transfer on SCO servers.
158. Communications ( ftp, kermit protocol )
159. Thin client on a 100 user PRO-IV application under VMS
160. I'm using it for QNX terminal connections. Just because it has the best emulation. And Kermit file transfer is available for Windows, Unix and QNX and works also on bad connections.
161. GSM Programing
162. Bullet-proof terminal emulation.
163. embedded controller programming
164. ACUCOBOL
165. I use it to communicate with Linux servers from my Windows XP desktop
166. OpenVMS terminal emulation and file transfer
167. Programming, file transfer rates
168. Talking with switches
169. Terminal emulation on Unix Enterprise network. I prefer Kermit over other emulators because it is simpler to configure, deploy, and use.
170. To download husky scaler
171. On the job. necessary
172. It has been used in the company I work for for at least 10 years.
173. File transfer & terminal emulation into Unix
174. Core use is general user access to payroll, patient admission and laboratory results systems.
175. Connect to Linux over serial port from a PC
176. Terminal emulation & File transfer to/from VMS & Unix systems
177. Kermit is good tool
178. Hyperterm is not supported on win2003
179. Reading at the net to search my modem.
180. FTP
181. Linux to WXP link
182. Connecting to Unix servers.
183. Programme downloaded required it
184. Easy Scripting
185. I use V1.1.20 terminal within an application (DOS based) and V2.x for SSH terminal emulation. Use both versions for universal file transfer capabilities.
186. ftp files
187. Good protocol for unix server access when network is down
188. Love it, easy to use and It always works.
189. I want to use it to receive alpha numeric pager that i will listen to...with kermit and a modem
190. Support sites
191. I still support a 'legacy' customer using Wyse60 emulation in Brooklyn NY
192. It is used across campus for secure communications between users and servers. By purchasing the site license it was a very good price. The kermit scripting language allows us many options.
193. Education
194. I use K95 on Vista Ultimate 64-bit with Kerberos everday to connect to my ISP UNIX box. K95 is easy and fast. And I love that it is encripted.
195. Remote shell access. Access of remote server databases. Secure sessions.
196. Ease of use. Not bloated. It has multiple uses as a terminal client.
197. Used to upload medical claims to a clearinghouse.
198. To interface with a 68hc11 project
199. Telnet and file transfer with Solaris and Linux systems, serial comm to lab equipment with management interfaces
200. For using terminal emulation, secured shell, ftp all in one.
201. To upgrade cisco IOS
202. Customization options / bulk license pricing
203. I use it mostly for talking to embedded devices, many of which use serial ports for configuration and setup. I also use it to diagnose modems when they don't work as expected. Why Kermit? Because it is the most solid, is flexible, has scripting, and supports all the file-transfer protocols that I use. It is comparable to well equiped commercial packages.
204. Transferring data
205. Windows based connections to text based servers
206. For check I can use. Vista work without Hyperterminal. Serial over virtual USB connection.
207. I would like to automate some daily operation
208. For testing purposes
209. Terminal emulation over ssh
210. scriptable telnet and ssh sessions
211. Terminal for Linux
212. telnet into unix system for administration
213. Configuring network devices via RS232.
214. For transfering boot images
215. Submit and retrive medicare claims
216. Its scripting capabilities.
217. I use k95 for communciations. I chose Kermit because of the scripting ability, and reliability.
218. Command line functionality
219. We use it in our order entry activities
220. Communicate with HP48GX calculator
221. I use kermit for file transfer over the internet and between machines connected by serial cables; I use kermit as my ssh and telnet client.
222. ASCII file transfer
223. Terminal emulation connection to our inventory and accounting software.
224. Host for transferring files to a older (DOS) laptop.
225. To console into our Antenna Control Unit (ACU) on the Mobile Battle Command On The Move (MBCOTM) platform. This allows us to change satellites, edit, lock on, and shutdown.
226. I have some old serial devices I have to control.
227. For unix
228. we are thinking of using it to collect pbx call information and delivering it to another process.
229. For see data transfer on serial protocol
230. It does TVI950
231. Transfer data from a CMT MV-5
232. Connection to legacy equipment.
233. Common access to remote device via rs232 serial or ethernet terminal servers.
234. VT terminal facilities and file transfers
235. Found it to be a very functional and cost effective product. Easy to install and customize.
236. Linux install
237. SSH access and file up/download.
238. The best
239. Been using for approx 12 years. Originally need Async modem scripting with ability to access any com port available in windows, where we were using DIGI muti-port adapters to expand our modem pool. Since, have continued to find uses for scripts in my job as an EDI specialist for variety of file transfers, job flow control, control data driven common scripts, file handling, data cleanup, re-formatting, merging, splitting. And as key tool for beginning migration from Async Modem to FTP file transfers.
240. I use kermit95 to transfer files between and Windows server and a Data General AVOS.
241. Reliable file transfer from Windows to Unix.
242. General terminal emulation - access Unix platforms from Windows.
243. Business file transfer
244. Logging data from various equipment...currently a YORK chiller. Retaining data in case of machine failure.
245. We are a healthcare company and we use Kermit to automate the transfer of healthcare claim files to McKesson
246. Scriptable serial transfers
247. To fulfill my duty, it is good
248. For micro contoller comunication
249. To transfer files
250. As a terminal emulator
251. Connection to various servers (OpenVMS, Tru64, Solaris). As a long term user, starting with serial connections to VMS and using the script feature, I am too lazy to change if it is not necessary.
252. vt100/220 emulation to talk w/our linux boxes, local printer support
253. Communications - it works
254. To login to a SCO box
255. Been using for a while and liked the emulator
256. download a file to slow computer via serial link
257. Remote access from WinXP office workstations to remote VAX and Sun machines. Chosen originally for faithfulness of VT100/VT200 emulation in VAX/VMS environment.
258. Cisco required serial transfer app.
259. CFE (Common Firmware Environment), RedBoot and other Embedded Serial-to-TTL interface. GPS, handheld programming.
260. VT320 emulation and file transfer.
261. For SSL upgrades
262. Reset router
263. Old Win 311 contains critical data that has to be copied. Testing possibilities.
264. Ease of scripting. Universal terminal emulation. Bullet proof connectivity in any environment.
265. I use it to connect to my HP calculators, and moving files between windows and unix systems
266. pic programming
267. vt220 Terminal Emulation for legacy application running on HP-UX. We chose Kermit for its simplicity and keymapping capabilities.
268. Due to huge support various terminal emulations.
269. Testing a banking application for IBM
270. file transfer
271. To send programs to other users
272. manage modem
273. manage modem
274. fun
275. secure remote backup
276. Excellent telnet & SSH client, highly scriptable, convenient with HP calc serial support
277. trying out a few ideas
278. File transfer between Windows XP and OS/9 (European operating system operating on a Bruker electron paramagnetic resonance machine.)
279. Infrastructure management - chosen for flexibility, one package for all devices
280. RS-232 configuration
281. To connect to Serial Communication equiptment
282. looking for scriptable ftp client
283. file backup and transfer
284. Connecting to PocketPC
285. Get data for cobol application
286. To connect to an Alph DS-10 running OpenVMS. Kermit has been used since version 1.1 to interface with this OpenVMS platform. I just continued its personal use so that I could maintain connectivity from home.
287. For HP48 Calculator File Transfer.
288. To communicate with computers:-) and diffrent OSs, mostly M$XP-Unix(Linux)-VMS-MacOS-X10-a.s.f...
289. I use it to connect from Windows to a wide variety of UNIX hosts. I have not found any other Windows terminal program that has full support for both SSH and UTF-8. I also occasionally need to take my laptop into the data center and hook it up to the serial port on a headless system when the console server network isn't working for whatever reason.
290. Terminal emulator for headless server consoles. (Also use ms-kermit on HP200LX palmtop.
291. Kermit is....a WAPOW
292. PBX
293. Login to Personal Server, telnet, SSH shell access.
294. When I initially bought kermit, I used it to preview scripts being developed for a company's international data transfers. I use it now mainly on underpowered old laptops being used as console-access devices (RS-232 serial ports).
295. Lock Haven University uses it as the standard emulator to access IBM AIX machines. Our administrative back offices and IT use it to access our ERP system in a straight forward and FAST manner.
296. Connecting to QNX systems via terminal
297. TErminal Emulation.
298. Connectivity to VMS systems and Kermit file transfers from Windows PC to/from other systems
299. ssh client
300. I use it to script file transfers for firmware uploads.
301. serial port testing
302. For download imgae to my board using serial port.
303. Communication to Embedded microcontrollers
304. Try to Transfer files from unix system
305. terminal emulation and file transfer. been a user since 1980 at the university of Akansas
306. basic serial port communication needs not met by HyperTerminal
307. terminal emulation when connecting to a linux server, good support for pass-thru printing
308. For uploading configs to my switches.
309. yes,because is more effective and reliable
310. e911 file transfer to at&t
311. It's the best and most versatile emulator I've found. Also, the custom keyboard mapping rocks.
312. Connect to Linux hosts: use copy&paste, use file up/download through same connection.
313. Transfer information from toprografic and other equipment.
314. File Transfer from hanheld pc
315. testing this software for interface
316. binary to ascii file conversion during ftp
317. unicode handling
318. file transfer
319. Connect AS400
320. File transfer from one pc to another via serial port
321. Serial communications, maintenance of printservers and routers etc.
322. QNX 4.2x Terminal emulations... It was the best and only at the time.
323. Survey software transfer to HP 48
324. Install programs on a psion revo
325. Grabbing configs off of cisco stuff
326. I have been using kermit for terminal emulation and file transfers for more than 20 years and find it far more flexible and convenient to use than any other similar program I have tried.
327. Terminal program to program routers, firewalls and switches
328. HIPAA compliant file transfers. Chose due to interoperability w/ skermit and skermit capabilities.
329. Transmit data beetwen two industrial robots
330. I have been a long time Kermit user (very early VMS 2.x systems)
331. File transfer, no other choice.
332. File transfer
333. New client who uses kermit. So we will to have it available. Can't answer most
334. Software development
335. As a terminal emulator with download facility.
336. Need com port access
337. We use K95 for a mutli user Network Operations center. It allows us to have one easy place to keep our programs that need to access the CMD prompt.
338. Networking coroprate computers
339. I am having vms5.5-2 os without UCX.
340. Serial connection with built in file transfer
341. Still the best ftp client around!
342. Good solid scripting support and good general use terminal emulation
343. For connecting to Tops-20. Kermit use on Tops-20. LAT connections. FTP regression testing.
344. It was provided to us by a software vendor.
345. IOS upgrade
346. Good range of network protocols supported
347. Alpha VMS to Windows Telnet
348. SCADA
349. Good reputation
350. Terminal interface
351. Land Survey file transfer
352. Accurate terminal emulation.
353. Terminal emulation via RS-232.
354. Access to varios workstations/servers (VMS, Tru64, Linux). Known for a very long time and superior scripting facilities. In the beginning it was the program of choice to connect to mailbox systems.
355. Occasional telnet connections to Linux machines.
356. cisco router config
357. Configuration of a gateway
358. Interfacing programming of Cincinnati equipment to PC storage.
359. Test lab automation and product testing.
360. Serial data transfer to Acorn BBC-B and master micros
361. Terminal emulator and Telnet client. I've been using Kermit for years. Love the program
362. Hotel Industry
363. It's GOOD!
364. Tranfer files through same connection
365. I wanted to download study material from my class ftp server, maximizing coverage of curriculum. But the ftp was going to stay open only a few days, and I was low on disk space. So I had to customize and automate the download. DOS batch had its limitation: the ftp output could not be used as a queue for analysis of file specification.
366. Testing site
367. To up/download motorola 6560 configs
368. Porque es el mejor [because it's the best]
369. To connect from my PC as a virtual terminal to our store's POS system. Not my choice to make. Preferred by the Wordstock people.
370. Transfer file
371. Medical software
372. Because Tera term does not work in my case.
373. I Reapir all types of Electronics and I need to connect to several types of units. Such as AINS sys and marine radios. They have a RS232 port.
374. Linux terminal emulation
375. HP-48GX file transfer
376. Bruker EPR ESP300 communication
377. ERP App developed for Kermit
378. I've used Kermit for more years than I prefer to
379. For transfert files from and to calculator HP
380. For trying to controlling DSL router via Telnet script, if possible
381. I have used Kermit for many years.
382. Managing/deploying network equipment (switches,routers, firewalls) as well as unix hosts
383. I've been using Kermit since the mid 1980s. it is like an old friend.
384. Terminal emulator for older phone systems (e.g., ROLM)
385. I do not currently use K95, but would consider buying it if there was an updated version. As such, all of my answers are given in the frame of "what WOULD be the case if I could buy an updated version."