This file lists bugs or other problems in Kermit 95 and its operating environment. There is a lot of information here, organized chronologically, and so it is recommended you use a text editor or Web browser to do case-insensitive searches for keywords to turn up what you are looking for.

Bugs that have been fixed are listed here by number and name, but, except for the bugs that were fixed since version 1.1.16, the descriptions of fixed bugs have been moved to a separate file.

If you do not have the current version of Kermit 95, please upgrade to it:

  http://www.columbia.edu/kermit/k95patch.html

if you are experiencing bugs or problems, they might already be fixed. Also, the BUGS.TXT / BUGS.HTM file that comes with the current release will have a more up-to-date list of bugs and hints than an older copy. If you do have the current version of K95, also consult:

• The Kermit 95 FAQ (Frequently Asked Questions).
• The newbugs.txt file on the Kermit website, which lists bugs discovered since the last release of K95.

In this document, except where otherwise noted, the term Windows 95 or Windows 9x refers to Windows 95, Windows 98, or Windows ME, but not to Windows NT, 2000, or XP. Similarly, the term Windows NT also includes Windows 2000 and XP, but not Windows 95, 98, or ME.

[ Index ] [ Bug Descriptions ] [ K95 Home ] [ Kermit Home ]

BUG CATEGORY

(M) Microsoft Windows bug.
(I) An IBM OS/2 bug.
(X) A feature that is disabled in Kermit 95 because of an operating-system bug.
(Z) A bug in the Dialer caused by a bug in the GUI development system that was used to build it.
(V) Bug or restriction in vendor code, e.g. in 3rd-party TCP/IP stacks.
(K) A Kermit 95 limitation or bug.
(D) A documentation error.
(C) A hardware / System / Drivers Configuration problem.
( ) Not a bug.

NOTE: The February 1996 Service Pack from Microsoft did NOT fix any of the bugs in the M and X categories. The September 1996 OEM SR2 release fixed at least one of these bugs (Bug #79) but is not available as a patch to earlier releases.

IMPORTANT: Windows NT 4.0 for Intel shipped with a dangerous but little-known bug that can randomly corrupt your data. Microsoft has fixed the problem in Service Pack 1 for Windows NT 4.0. It is strongly recommended that users of Windows NT 4.0 download and install this and all later fixes.

BUG STATUS

[ ] Indicates an item that is still open or current
[+] Indicates the bug is fixed or worked around as of the current release
[-] Indicates bug is partially fixed or a workaround is given
[*] Information and/or not really a bug

BUG LIST

1. [-] (M) Ctrl-C Interruption in Command Screen
2. [+] (X) Video Attributes vs Terminal Screen Size in Windows 95
3. [+] (K) Microsoft Telephony (TAPI)
4. [*] (K) Registration
5. [ ] (M) Changing Code Pages
6. [-] (M) Keyboard Scan Codes, Caps Lock, and Dead Keys
7. [-] (D) "Kermit 95" Keyboard Verb table
8. [ ] (M) PUSH and related commands do not work in Windows NT 3.50
9. [-] (M) Don't Use the Auto Font Setting in Windows 95
10. [+] (Z) Blotchy Dialer Fields
11. [ ] (K) Missing Features
12. [*] (C) Hardware / system / drivers configuration
13. [-] ( ) Miscellaneous Dialer peculiarities
14. [*] ( ) Miscellaneous Hints and Tips
15. [*] ( ) Debugging Tips

       ----(Version 1.1.1)----
    

16. [+] (Z,M) K-95 Dialer Vertical Scrolling
17. [+] (K) ZMODEM Downloads
18. [+] (K) ZMODEM and TELNET
19. [+] (K) Alphabetization of Dialer Entries
20. [+] (K) K95 Sometimes Thinks a Connection is Open When It Starts Up
21. [+] (K) Download Directory Doesn't Work
22. [+] (K) SET MODEM commands in K95CUSTOM.INI have no effect
23. [+] (K) Kermit 95 sometimes can't find its script or key mapping files
24. [+] (K) The Dial Prefix also becomes the Dial Suffix
25. [+] (K) Dialer complains unnecesarily about range of certain numbers
26. [+] (K) Kermit BBS entry in Dialer has wrong backspace key setting

       ----(Version 1.1.2)----
    

27. [*] (C) Screen updates updates are slow on some PCs
28. [+] (K) ZMODEM Recovery
29. [+] (K) ANSWER command crashed Kermit 95
30. [+] (K) Kermit always turned off autoanswer in the modem
31. [+] (K) Compose Key problems
32. [+] (K) SET TERMINAL CHARACTER-SET TRANSPARENT did not show all characters
33. [+] (K) Various other VT emulation problems
34. [+] (K) Printer problems
35. [+] (K) \v(keyboard) variable improperly set
36. [+] (K) XMODEM file transfer problems
37. [+] (K) MOVE and MMOVE command did not work right with XYZMODEM
38. [+] (K) Ctrl-C interruption nonfunctional in certain cases
39. [+] (K) File transfer recovery after Ctrl-C
40. [+] (K) SET FILE DOWNLOAD-DIRECTORY didn't work with server mode
41. [+] (K) Filenames could not be parsed from variables
42. [+] (K) Choosing terminal character-set in the Dialer
43. [+] (K) The EMACS.INI file was not properly patched in version 1.1.1
44. [+] (K) The 1.1.1 patch versus READ.ME files in multiple directories
45. [+] (M) Xon/Xoff flow control doesn't work in Windows 95
46. [-] (M) Server mode sometimes locks up in Windows 95
47. [-] (M,K) Kermit 95 file naming conventions in conflict with Windows
48. [+] (K) The Dialer Login page does not show LOGIN.SCR in the text box
49. [ ] (K) The K-95 icon does not show up in Windows NT 3.5x
50. [+] (K) SEND and RECEIVE as-names ignored by XYZMODEM
51. [*] (D) Missing files
52. [+] (K) Title bar not properly set from "kermit -j host"

       ----(Version 1.1.3)----
    

53. [ ] (M) Can't interrupt SET HOST or TELNET or RLOGIN command
54. [+] (K) SET FILE DOWNLOAD-DIRECTORY does not work with XYZMODEM
55. [+] (K) Crash when pasting voluminous material into terminal window
56. [+] (K) Problem with SET FILE DOWNLOAD-DIRECTORY<Enter>
57. [+] (K) Terminal reset kills K95 if TERM CHARACTER-SET is TRANSPARENT
58. [+] (K) Cursor-type selection made in Dialer not saved
59. [+] (K) PBX-related entries in the Dialer's Dialing Location page not saved
60. [+] (K) No choice for location of Kermit 95's temporary files
61. [ ] (M) The "Paste" button on the Terminal Windows Toolbar doesn't work.
62. [+] (K) EMACS.INI Alt-x = Meta-x doesn't work
63. [+] (K) INPUT could not be canceled from the keyboard
64. [+] (K) SET ALARM / IF ALARM doesn't always work
65. [+] (K) \v(cpu) always says "unknown".
66. [+] (K) Invalid escape sequence ESC [ ? 6/7 i caused problems
67. [+] (K) Problems with transparent printing and accented letters
68. [+] (K) Microcom Deskporte modem configuration wrong
69. [+] (K) Cursor-type selection not saved by Dialer
70. [+] (K) PBX material from Locations & Codes Dialer page not saved
71. [+] (K) SET TERM CHAR TRANSPARENT, then terminal reset, causes crash
72. [+] (K) Spurious "Connection might still be active on COM1..." messages
73. [+] (K) SET PORT<Enter> gives spurious error message
74. [+] (K) DIAL timeouts sometimes caused an "access violation" crash
75. [+] (K) Modem list in SETUP program PPI / Multitech mixup
76. [+] (K) Incorrect default assignment for Ctrl-Space key combination
77. [+] (K) "k95 filename" requires fully specified filename
78. [+] (K) XYZMODEM Transfers didn't work over RLOGIN connections
79. [+] (M) PCMCIA or Plug-and-Play Modem Problems
80. [ ] (V) RLOGIN vs FTP Software OnNet-32
81. [ ] (K,V) "set host 0" vs FTP Software OnNet-32
82. [*] (V) Kermit 95 and Digital UNIX 3.2
83. [ ] (M) Extraneous characters on terminal screen in Windows 95
84. [+] (M) Special keys on national keyboards don't work
85. [+] (K) VT220/320 Erase Character (ECH) bug
86. [*] (K) Intel Modems without Fax
87. [+] (K) LOGIN.SCR renamed to LOGIN.KSC to avoid conflicts with screen savers
88. [?] (V) Uploads on LAT connections tend to fail
89. [+] (K) XYZMODEM and Kermit file transfer screens and stats are inconsistent
90. [ ] (M) Printing to network printers in Windows 95 or NT might not work

       ----(Version 1.1.4)----
    

91. [+] (K) Messed up colors on initial Terminal screen
92. [+] (K) Colors behave differently than in MS-DOS Kermit
93. [+] (K) Printing to PostScript printers doesn't work
94. [+] (K) Redialing on a SET HOST / SET MODEM / DIAL connection didn't work
95. [+] (K) Command-file line numbers not reset
96. [+] (K) ASSIGN/DEFINE failed to fail if definition too long
97. [+] (K) Dialer temporary files called .SCR instead of .KSC
98. [+] (K) The MSEND command did not work with ZMODEM
99. [+] (K) Backspace key didn't work with "set term char finnish"

       ----(Version 1.1.5)----
    

100. [ ] (K) Kermit 95 requires long filenames
101. [-] (K) Host-controlled status lines
102. [+] (K) Wyse screen-transmit functions not implemented
103. [+] (M) Windows 95 Dead key and Caps Lock bugs are fixed! (mostly)
104. [*] (K,M) East European keyboard features might not work in Windows 95
105. [+] (K) VT emulation DCS/OSC/APC/etc bugs
106. [+] (K) Terminal color bugs in version 1.1.4
107. [ ] (K) VT220/320 downloadable fonts / soft character sets don't work
108. [+] (K) SET TERMINAL CHARACTER-SET PORTUGUESE didn't work
109. [+] (K) VT emulation and SET TERMINAL CHARACTER-SET FINNISH (etc) bug
110. [+] (K) Autodownload versus SET TERM CHARACTER-SET
111. [+] (M) Keyboard doesn't work if I start K95.EXE from Netscape
112. [+] (Z) Dialer radio buttons not lined up
113. [+] (K) Multiple sessions to same Dialer entry don't work
114. [+] (M,K,Z) Can't select a Dialer entry from the keyboard
115. [+] (K) Dialer crash after editing an entry entry name
116. [+] (K) Dialer PBX configuration problems
117. [ ] (M) Ctrl-C doesn't work in NT when K95 started from the Dialer
118. [+] (K) No way to make LAT connections from the Dialer
119. [*] (M) Kermit 95 and Internet firewalls, SOCKS, etc
120. [+] (K) Unreasonable delays in SET HOST / TELNET to numeric IP address
121. [ ] (V) Kermit 95 does not work with LWP 5.0 TCP/IP in Windows 95
122. [ ] (M) No way to select split-speed serial communication
123. [+] (K) Errors in built-in modem support
124. [+] (K) SEND did not work with filename completion
125. [+] (K) OUTPUT could not send backslash characters
126. [+] (K) OUTPUT could not send long strings
127. [+] (K) Extraneous material in session log during INPUT
128. [+] (K) INPUT buffer too short
129. [+] (K) SEND foo\%a did not work
130. [+] (K) No way to print on A4 paper using textps
131. [+] (K) Invalid Page Fault after using command recall a lot
132. [ ] (M) Alt- doesn't work.
133. [-] (K) Interruption keys are ignored during XYZMODEM transfers

        ----(Version 1.1.6)----
     

134. [*] (C) Tone dialing changes to Pulse after first digit
135. [+] (K) VT100 reverse scrolling broken
136. [+] (K) SET KEY commands became slow
137. [*] (C) Terminal bell doesn't work as before, or at all
138. [+] (K) SET MSKERMIT KEYCODES ON did not work with some gray keys
139. [+] (K) Array elements could not be used for file names
140. [+] (K) Keyboard modes can't be modifed
141. [-] (M,K) Control keys on national keyboards in Windows 95
142. [+] (K) SCOANSI and AT386 emulation vs Code Page 437
143. [+] (K) SCOANSI and AT386 emulation vs CSI 10/11/12 m
144. [+] (K) Bad characters in Registration name
145. [+] (K) SET MODEM commands in K95CUSTOM.INI are ignored by Dialer
146. [ ] (K) Completion does not work with directory names
147. [ ] (K) Command-line editing doesn't use PC editing keys
148. [ ] (K) The DIRECTORY and TYPE commands are too slow
149. [+] (K) DIRECTORY command gives spurious error message
150. [+] (K) XYZMODEM transfer statistics are off
151. [+] (K) SET TERMINAL ESCAPE-CHARACTER DISABLED didn't work
152. [ ] (K,M) Command screen messed up after Ctrl-C
153. [+] (K) Cursor disappears after Ctrl-C interruption of file transfer
154. [+] (K) \v(sysid) was garbage
155. [+] (K) SHOW KEY ALL did not show keys that had string definitions
156. [+] (K) Dialer File Transfer page items spuriously grayed out
157. [+] (K) SET TERM COLOR ERASE CURRENT-COLOR didn't work
158. [ ] (K) Patching up from version 1.1.3 might not work
159. [+] (K) XYZMODEM file transfers gave incorrect status codes
160. [+] (K) XYZMODEM transfers made no transaction log entries
161. [+] (K) TELNET negotiations were sometimes skipped
162. [+] (K) Data loss during file transfer
163. [+] (K) K95 could not send a file that was already open
164. [+] (K) Dynamic packet timeout values were sometimes too high
165. [+] (K) Character attributes not shown in Televideo emulation
166. [ ] (V) PATCH.EXE only works with FAT filenames
167. [+] (K) TEXTPS.EXE was broken in version 1.1.5
168. [+] (K) File transfer efficiency number is misleading

        ----(Version 1.1.7)----
     

169. [+] (K) VT220/320 DCS string cancellation didn't work
170. [+] (K) SCOANSI and AT386 emulation conflict with Dialer
171. [+] (K) Server GET fails if a SEND-LIST had previously been used
172. [+] (K) PUSH from Terminal screen to shell could not be returned from
173. [+] (Z) K95DIAL window minimizes to desktop instead of task bar
174. [*] (K) Referring to directory names that start with digits
175. [+] (K) Televideo and Wyse printing didn't work right
176. [+] (K) Wrong default character-set for VT terminals in Dialer

        ----(Version 1.1.8)----
     

177. [ ] (M) The Dialer database can be corrupted by other applications
178. [-] (K) The Dialer can seem to disappear
179. [+] (K) The "Chess" entry in the Dialer is wrong
180. [*] (K) XMODEM-CRC, YMODEM-CHECKSUM, and ZMODEM-CRC16 are not supported
181. [+] (K) Renaming downloaded files with XYZMODEM doesn't work
182. [+] (K) XYZMODEM downloads are somewhat slower than expected
183. [+] (K) Scroll Lock doesn't work in version 1.1.7
184. [+] (K) No way to change the default key map for each terminal type
185. [+] (U) CTRL2CAP instructions misleading
186. [+] (K) LOG SESSION erroneously translates character sets
187. [+] (K) VT102 insert character function doesn't work
188. [+] (K) Spurious keyboard locks in VT220/320 emulation
189. [+] (K) Improper handling of Alternate ROM in VT emulation
190. [+] (K) Erroneous VT emulator Secondary and Tertiary DA Reports
191. [+] (K) Erroneous DECID reports in VT220/320 emulation
192. [+] (K) VT emulation Horizontal Position Absolute (HPA) ignored
193. [+] (K,C) Failure of K95 to start on certain Windows NT systems
194. [+] (K) Simultaneous LAT sessions don't work
195. [ ] (X) No redirection of standard input
196. [+] (K) SHOW KEY does not properly display C0 and 8bit characters
197. [+] (K) "set command more-prompting" could not be parsed
198. [+] (K) No way to specify 0 or no timeout in INPUT
199. [+] (K) INPUT ignores autodownload sequences
200. [+] (K) Problems entering commands that end with backslash
201. [+] (K) Spurious invisible Z command that does nothing
202. [ ] (M) Close box in K95 title bar doesn't work in Windows 95
203. [*] (K) Dialer startup is slow
204. [*] (K) Dialer toolbar buttons might "wrap around"
205. [+] (K) Statusline OFF vs TELNET NAWS bug

        ----(Version 1.1.9)----
     

206. [+] (K) Page faults in K95 version 1.1.8
207. [+] (K) Keyboard translations don't work in Windows NT in K95 1.1.8
208. [+] (K) Printing did not work right in version 1.1.8
209. [+] (K) Dead-key and Alt-Gr broken in 1.1.8
210. [+] (K) APC during INPUT broken in 1.1.8
211. [+] (K) Redundant terminal-type change in 1.1.8
212. [ ] (K) CD to nonexistent directory can cause errors
213. [+] (V) Problems with host-based WordPerfect
214. [+] (K) Russian and Hebrew keyboard modes don't work
215. [*] (M) Why does Dialup networking pop up whenever I make a Telnet connection?
216. [*] (K) Why does the termimal status line say "Script:" instead of "Prompt:"?
217. [*] ( ) Why is my login prompt missing?
218. [+] (K) VERSION command did not display copyright notice
219. [+] (K) Alt-: and Alt-; missing from EMACS mode
220. [+] (K) Dialer would not start if any database entries were corrupt
221. [+] (K) Russian and Hebrew keyboard mode conversions broken
222. [+] (K) Latin-2 Compose sequences broken in 1.1.8
223. [*] (M) Windows 95 QuickEdit interferes with Kermit 95's mouse functions
224. [ ] (M) Caps Lock state can change when moving between windows
225. [+] (K) LOGIN.KSC broken in version 1.1.8
226. [+] (K) ADD SEND-LIST followed by MOVE did not delete source files
227. [+] (K) Marking text on bottom line of terminal screen didn't work
228. [+] (K) Sending data from terminal screen when SEND-DATA OFF
229. [+] (K) Kermit file-transfer packets sent out of window
230. [+] (K) VMS SET TERM/WIDTH did not clear the screen
231. [+] (K) k95 "file name with spaces" did not work in 1.1.8
232. [+] (K) k95 command screen could be frozen or corrupted in 1.1.8

        ----(Version 1.1.10)----
     

233. [+] (K) Spurious cursor in 1.1.9
234. [*] (M) Appearance of horizontal scrolling indicators
235. [*] (K) Network editing hints
236. [+] (M) Windows 95 long screens don't work in 1.1.9
237. [+] (V) Problems with TES32
238. [ ] (M) Keystrokes might be transmitted out of order in Windows 95
239. [ ] (V) Conflicts with CompuServe, AOL, etc
240. [+] (K) HPTERM and HP2621 screens were fractured
241. [+] (K) Overzealous recording in session log
242. [+] (K) VT100/102 keypad not mapped to PC keypad by default
243. [+] (K) Assorted window sizing problems in 1.1.9
244. [+] (K) SET TERMINAL CURSOR did not enable the cursor
245. [+] (K) Autoupload problems with XMODEM and YMODEM (K)
246. [+] (K) Data General DASHER terminal emulation problems
247. [+] (K) Default editor set in K95.INI might be wrong
248. [+] (K) Dial-in host mode did not agree with user-defined modems
249. [ ] (K) Not all SET TERMINAL settings are shown by SHOW TERMINAL
250. [ ] (C) PUSH, RUN, and similar commands might not work
251. [+] (K) Unwanted alert box from K95CINIT
252. [+] (K) Problems when switching from VT to ANSI terminal type
253. [*] (V) HINT: Using SCOANSI emulation with SCO hosts
254. [ ] (M) Environment variables are not case sensitive
255. [+] (M) Data loss in dialup host mode
256. [+] (K) Problems with automatic login from certain Dialer entries
257. [+] (K) Problems with arrow keys and command recall
258. [+] (K) Misleading Dialer error message about screen dimensions
259. [*] (K) HINT: How to disable scrollback
260. [+] (K) Wildcard sends don't work right in XYZMODEM
261. [*] (K) EXPLANATION: Changes in the operation of the numeric keypad
262. [+] (K) DEC NRCs are forgotten in Multinational Mode
263. [+] (K) ZMODEM crash recovery versus some FILE COLLISION settings
264. [+] (K) ZMODEM autodownload doesn't work with Wyse, VC, or DG
265. [*] (C) HINT: Kermit mouse buttons versus nonstandard mouse setups
266. [+] (K) VT terminal emulation wrapping problem
267. [+] (K) WP51.INI (WordPerfect 5.1 key mapping file) had a typo
268. [*] (K) HINT: Using the NETEDIT macro with GUI editors
269. [ ] (M) Yellow background change after !edit in K95
270. [+] (K) Popup printer-error boxes causes Kermit 95 to hang
271. [+] (K) Host-directed printing did not work in DG emulation
272. [+] (K) INPUT/MINPUT did not handle Telnet negotiations correctly
273. [+] (K) Dialer Options..Dialing page PBX values handled incorrectly
274. [+] (K) Wyse character graphics bug
275. [+] (K) Transparent printing of binary files did not work
276. [+] (K) VT100 terminal ID was incomplete
277. [ ] (K) Kermit/2 keycodes are different from OS/2 C-Kermit 5A(191)
278. [ ] (C) Kermit/2 conflicts with SWAPDCP on OS/2

       ----(Version 1.1.11)----
     

279. [*] (M) RLOGIN versus Microsoft's "WINNUKE" Patches
280. [+] (K) DIALINF.DAT can't be read-only
281. [ ] (M) Caps Lock state can be lost when switching between windows
282. [+] (K) Serial-port file transfer fails with large packet x window size
283. [ ] (M) Can't change keyboard language in Windows 95
284. [+] (K) K95 does not delete startup file generated by the Dialer (K)
285. [+] (K) Dialer can leave temporary files behind (K)
286. [+] (K) Kermit 95 TELNET.EXE stub works only if K95 directory in PATH
287. [+] (K) Problems with incoming TCP connections in OS/2
288. [+] (K) Dialer could crash if an entry's view status changed
289. [+] (K) SHOW KEY did not always give accurate results
290. [+] (K) REDIRECT command didn't work
291. [+] (K) Incoming NUL (0) characters confuse INPUT command
292. [+] (K) RECEIVE as-name did not work with XYZMODEM
293. [+] (K) Various EMACS mode bugs
294. [+] (K) Kermit protocol might send packet out of window
295. [+] (K) MOVE from SEND-LIST did not delete original files
296. [+] (K) Application filename could not contain spaces
297. [+] (K) Hayes high-speed-modem init string problem
298. [+] (K) READ command does not fail if file not open
299. [+] (K) Problems with long function arguments
300. [+] (K) Certain \function()s can misbehave
301. [+] (K) X MOD 0 crashes program
302. [+] (K) ANSWER doesn't automatically CONNECT
303. [+] (K) Overzealous EXIT warning
304. [+] (K) OUTPUT doesn't echo when DUPLEX is HALF
305. [+] (K) Minor problems with REMOTE DIRECTORY/DELETE/etc
306. [+] (K) CHECK command broken
307. [+] (K) Problem with SET TRANSMIT ECHO
308. [+] (K) Dialing results were sometimes incorrect
309. [+] (K) IF EXIST and IF DIRECTORY versus spaces in filenames
310. [+] (K) CD, SET FILE DOWNLOAD-DIRECTORY, etc, don't provide full service
311. [+] (K) READ command too picky about last or only line in file
312. [*] (K) No way to include braces in function arguments
313. [+] (K) DIALINF.DAT file opened in READ/WRITE mode
314. [+] (K) Missing and incorrect key definitions in EMACS mode
315. [+] (K) NULs were being stripping during file transfers and printing
316. [+] (K) XYZMODEM RECEIVE was ignored
317. [+] (K) SET STARTUP-FILE DISCARD did not always delete the file
318. [+] (K) SHOW MODEM didn't quote backslashes
319. [+] (K) WIN32 COMM TX BUFFER SIZE set too small
320. [+] (K) K2DC.EXE accidently closed socket of incoming connection
321. [+] (K) Auto-print Formfeed bug
322. [+] (K) SAVE KEYMAP and SHOW KEY replaced RS with ESC
323. [*] (M) How can I use SSH, SSL, CHAP, etc, to make secure connections?
324. [*] (M) Why can't I pick any Windows font I want?
325. [+] (V) Data loss on Meridian Technology SuperLAT connections
326. [*] (K) Hints on dialing toll-free numbers
327. [*] (K) Hints on "blind dialing"
328. [*] (K) Log files in multiple sessions
329. [+] (K) Hazeltine 1500 emulation did not work at all
330. [+] (K) Problems with Wyse 50 emulation
331. [+] (K) Problems in DG DASHER 217 emulation
332. [+] (K) HPTERM emulation did not handle line-drawing & math
333. [+] (K) Many Dialer entries were obsolete
334. [+] (K) Unwanted triangles in Wyse, TVI, and Hazeltine emulation
335. [+] (K) Spurious spaces in ANSI emulations
336. [+] (K) Data loss/corruption on Windows 95 serial connections

       ----(Version 1.1.12)----
     

337. [ ] (K) Commands like "RUN D:\FOO\BAR\BAZ.BAT" don't work in Windows
338. [ ] (M) "RUN /K...." hangs K95 in Windows
339. [+] (K) Commands like "SEND \\K95\\TMP\\OOFA.TXT" did not work
340. [+] (K,M) Problems with help and completion in filenames with \\
341. [ ] (M) CTL3D32.DLL is missing
342. [ ] (M) K95 might take a long time to start and stop
343. [+] (M) K95 might not be able to exit on some Windows 95 systems
344. [+] (K) Dialer might crash if no modem was defined
345. [+] (K) Memory leak in Dialer
346. [+] (K) URL hot spot could fail if URL at end of sentence
347. [+] (K) EDIT and NETEDIT might have stopped working in 1.1.12
348. [+] (K) Telnet negotiations could become frozen
349. [+] (K) K95 could become stuck in marking mode
350. [+] (K) HP terminal emulation problems in 1.1.12
351. [+] (K) Wyse terminal emulation problems in 1.1.12
352. [+] (K) K95 could hang upon screen-size change request
353. [+] (K) SET MOUSE ACTIVATE command broken in 1.1.12
354. [+] (K) Character set versus copy/paste from/to Clipboard
355. [+] (K) (void)
356. [ ] (M) Paste to host using Toolbar Paste sends Esc O P when Num Lock on
357. [ ] (K) Reverse screen-writing direction not supported
358. [+] (K) Transparent print problems using 8-bit CSI
359. [+] (K) APC did not block terminal emulator
360. [+] (K) Conflict between INPUT and APC

       ----(Version 1.1.13)----
     

361. [+] (V) K95 might not work with certain third-party TCP/IP stacks
362. [+] (K) Another problem with filenames containing spaces
363. [+] (K) CONNECT mode hangs when host drops connection or \Kquit is used
364. [+] (K) Problem with Num Lock and SET MSKERMIT KEYCODES ON
365. [+] (K) Problem with OUTPUT command when there is no connection
366. [+] (K) END from within SWITCH doesn't work
367. [ ] (V) URL hot spots might not work
368. [+] (K) (void)
369. [+] (K) (void)
370. [+] (K) (void)
371. [+] (K) (void)
372. [+] (K) (void)
373. [+] (K) (void)
374. [+] (K) (void)
375. [+] (K) (void)
376. [+] (K) (void)
377. [+] (K) (void)
378. [+] (K) (void)
379. [+] (K) (void)
380. [+] (K) (void)
381. [+] (K) (void)
382. [+] (K) (void)
383. [+] (K) (void)
384. [+] (K) (void)
385. [+] (K) (void)
386. [+] (M,K) Problems with Dead Keys and Alt-Gr keys in Windows 95
387. [+] (K) Kermit vs TAPI Dialing in the Dialer
388. [ ] (M) K95 vs Num Lock, Caps Lock, and Scroll Lock
389. [*] (M) Parallel Port Communications
390. [+] (K) Wrong system type in Telnet NEW-ENVIRONMENT negotiation
391. [+] (K) IF ALARM might not work
392. [+] (K) SET TERM REMOTE-CHAR LATIN6 doesn't work
393. [+] (K) Single-click mouse actions generate an extraneous error beep
394. [+] (K) Various terminal emulation bugs
395. [+] (K,V) Ctrl-C caught by 4NT.EXE instead of K95 in Windows NT
396. [+] (K) OS/2 K2DIAL loses data in the Login Script text box
397. [+] (K) Various errors in the Windows Telephony (TAPI) implementation
398. [+] (K) Dialing fails due to garbled modem command
399. [+] (K) Dialer Modem Commands reset when modem selected for editing
400. [+] (K) SHOW KEY interrupted by Ctrl-C would cause keyboard problems
401. [+] (K) SET HOST * results in 100% CPU Utilization
402. [+] (K) Telnet to non-23 port might fail to produce a login prompt
403. [+] (K) SET MODEM TYPE to certain types didn't work
404. [+] (K) SETUP.EXE would crash while displaying summary of choices
405. [+] (K) Default AT386 and SCOANSI keymaps reference DEC Kverbs
406. [+] (K) SET TERMINAL DEBUG ON interferes with TELNET negotiations
407. [+] (K) OS/2 FTP PC/TCP stack would cause K2 to crash
408. [+] (K) K95's -N command-line option in OS/2 would not accept parameters
409. [+] (K) SET BROWSER ignored by \KmouseURL keyboard verb
410. [+] (V) K95 could not be the Telnet client for Netscape Communicator
411. [*] (K) The PRINT command no longer uses DOS COPY to print a file
412. [+] (K,M) DIAL DISPLAY ON didn't work with TAPI modems
413. [+] (K) TAP alpha paging script was not robust enough
414. [+] (K) Incorrect setup of Telebit modems
415. [+] (K) File transfers could fail when using very short packets
416. [+] (K) Screen-printing problems in Windows NT
417. [*] (V) Incorrect characters on screen when accessing SCO or AIX hosts
418. [ ] (V) K95 is unable to print to WinPrinters
419. [ ] (K) Host mode requires VT100 or ANSI client
420. [+] (K) HPTERM and VIP7809 selection didn't work in the Dialer
421. [+] (K) File-transfer problem using undefined variable for as-name
422. [+] (K) Overzealous EXIT WARNING
423. [+] (K) K95 program exit status codes were not always correct
424. [+] (K) Various misleading file-transfer error messages
425. [+] (K) EDIT command succeeds only on first attempt
426. [ ] (M) "WINOLDAP - This program has performed an illegal operation..."
427. [+] (K) Mixups in certain terminal-specific line-drawing character sets
428. [+] (K) Unnecessarily difficult to get big window and packet sizes
429. [+] (K) Host mode would not send file groups
430. [-] (K) Problem using Swedish (etc) NRC and DEC Special Graphics

       ----(Version 1.1.14)----
     

431. [+] (K) Various problems with the 1.1.14 Patch
432. [+] (K) SET TELNET TERMINAL TYPE affects actual terminal type
433. [+] (K) Problems with Kermit transfers on some Telnet connections
434. [+] (K) AIX and HFT arrow keys didn't work in the Command screen
435. [+] (K) AIX and HFT emulation versus Autowrap

       ----(Version 1.1.15)----
     

436. [+] (M) Assorted problems caused by faulty optimization
437. [-] (M) Problems with Winsock 2
438. [+] (K,M) Redirection of Standard Output
439. [*] (M,C) Illegal operations caused by lack of swap space
440. [*] (M) Roaring Fan
441. [+] (K) Failure to detect default printer in Windows NT
442. [+] (K) Console mode changed from text to binary and not restored
443. [-] (M) Trouble with EXIT under certain circumstances
444. [+] (K) Overzealous EXIT warning (again)
445. [+] (K) RUN command did not return status
446. [+] (K) Problems with DIRECTORY command filename completion
447. [+] (K) The DIRECTORY command would return one file too few
448. [+] (K) MKDIR command did not work in OS/2
449. [+] (K) SET TITLE effect was delayed
450. [*] (M) BEEP command can be delayed
451. [+] (K) CONNECT should not work if TAPI connection not open
452. [+] (K) TAPI device not released when closed
453. [+] (K) Various SET TCP command problems
454. [+] (K) \v(ipaddr) didn't work before a connection was made
455. [+] (K) Assorted Telnet initialization and negotiation problems
456. [+] (K) Spurious NUL characters on Telnet connections
457. [+] (K) Failure to recognize RLOGIN URLs
458. [+] (K) Problems with Wyse graphics character sets in Windows NT
459. [+] (K) QANSI graphics characters displayed as ASCII
460. [+] (K) Problems with DG transparent printing
461. [+] (K) Scrolling failures in ANSI X3.64 emulations
462. [+] (K) Incorrect appearance of VT220/320 characters after erasure
463. [+] (K) SCOANSI and AT386 function-key programming broken
464. [+] (K) Various problems in HPTERM emulation
465. [+] (K) Problems in Siemens/Nixdorf BA80 emulation
466. [+] (K) Spurious red lines on debug-mode terminal screens
467. [*] (K) Alt-x, Alt-h, etc, don't seem to work in AIXTERM
468. [+] (K) Difficulties pasting
469. [+] (K,M) Echoing delays
470. [+] (K) MSKERMIT keycode for Ctrl-Enter was incorrect
471. [+] (K) APC command containing SET TERM TYPE would stop
472. [+] (K) Failure to receive files with long names on some systems
473. [+] (K) Autodownload failures with parity mismatch
474. [+] (K) File transfer thermometer might not complete
475. [+] (K) XYZMODEM statistics counted each file twice
476. [+] (K) SET TERMINAL TYPE might mishandle 7-bit NRCs
477. [+] (K) Problems typing 7-bit national characters
478. [+] (K) Problem Selecting HP-Roman8 character set from the Dialer
479. [+] (K) RETURN within SWITCH didn't work
480. [+] (K) \ffiles() counted directories when it shouldn't
481. [+] (K) Problems with REMOTE QUERY KERMIT function()
482. [-] (C) K95 Host Mode might be slow to put up Login prompt
483. [*] (K) Host mode requires ANSI or VT terminal emulator
484. [+] (K) Host-mode maximum users setting wouldn't stick
485. [+] (K) Dialer Login Script text box data lost in OS/2
486. [+] (K) Dialer Printer Type combo box could not be set
487. [+] (K) Dialer Communications page speed entry wouldn't stick
488. [*] (K) HINTS: Alphanumeric Paging
489. [*] (K) HINTS: For blind users
490. [*] (V) HINTS: Telnetting to OS/2
491. [*] (V) HINTS: How to use K95 with Netscape Communicator 4.0
492. [-] (M) TEMP or TMP environment variable definition can cause problems
493. [+] (K) The GET Command Versus Filenames with Spaces
494. [*] (K) HINT: CR and/or LF disappear!
495. [*] (K) HINT: Eliminating "Press a key to continue" after RUN Command.
496. [+] (K) Cursor positioning on double-width lines
497. [+] (K) Errors in Default Keymap for EMACS Mode
498. [+] (K) SET HOST * Port Not Freed
499. [+] (K) Unwanted Command Screen Size Change
500. [+] (K) MKDIR/RMDIR Problems with UNCs
501. [+] (K) MKDIR/RMDIR Problems when Used in Macros or Command Files
502. [+] (V) RUN, REDIRECT, PIPE Interaction with Nonstandard Shells
503. [+] (K) Compression Skipped in Text-Mode Kermit File Transfers
504. [+] (K) Slow Local Echo in Terminal Screen
505. [+] (K) Slow Echo in Terminal Screen on Serial Connections
506. [+] (K) Problems with Bidirectional Printer Configuration in Dialer
507. [+] (K) Missing Error Messages in OUTPUT and INPUT
508. [+] (K) Problems Editing Certain Commands
509. [+] (K) Redirection of Certain REMOTE Commands Didn't work
510. [+] (V) K95 did not work well with Citrix Winframe
511. [+] (K,C) Wyse 370 colors didn't work
512. [ ] (M) CJK Input Method Editors do not work in Windows 95
513. [*] (V) Conflict between mouse and screen saver
514. [+] (K) Improper bolding in VT reverse-screen mode
515. [ ] (K) Dialer does not work in OS/2 2.x
516. [ ] (M) Log files can disappear in Windows 95 if K95 killed

       ----(Version 1.1.16)----
     

517. [ ] (V) Code Page 856 isn't really a code page
518. [+] (D) SET TERMINAL IDLE-xxx command misdocumented
519. [ ] (K) New screen updating method might not be good for everybody
520. [+] (M,K) Problems invoking RLOGIN.EXE and TELNET.EXE
521. [+] (K) AIXTERM, HFT, SCOANSI, AT386 scrolling problem
522. [+] (K) Program crash during XMODEM transfer
523. [+] (K) No means to receive XMODEM transfers with CRC block checking
524. [+] (K) (Two bugs, One Number)
525. [+] (K) Invalid TMP or TEMP directory will cause K95DIAL to crash
526. [+] (K) INPUT command sets \v(instatus) to wrong value
527. [+] (K) SET TERMINAL ESCAPE-CHARACTER does not work
528. [+] (K) TCP/IP sessions do not work on OS/2 3.0
529. [+] (K) OS variables not properly set in OS/2
530. [ ] (M) Win95/98 does not randomly access pooled IP hosts
531. [ ] (M) Kerberos authentication fails with "invalid network address"
532. [+] (K) PAUSE command always reports FAILURE
533. [+] (K,M,I) Kermit 95 could not display the EURO character
534. [+] (K) TES32 for Win95 connections fail immediately
535. [+] (K) \fsplit() function parses extra words
536. [ ] (M) Cursor can disappear in command screen
537. [+] (K) '\' at end of key definition cannot be sent to host
538. [+] (K) LOOKUP command does not return failure
539. [+] (K) Function rindex fails to match first instance of string
540. [+] (K) Non-CP437 extended characters displayed improperly in NT
541. [+] (K) In NT, dead keys produce an error beep when pressed
542. [+] (K) SET BELL VISIBLE does not work reliably
543. [+] (K) SET TELNET ENCRYPTION {REFUSED, ACCEPTED, ... } broken
544. [+] (K) Max Command Length is not necessarily max length of macros
545. [+] (K) END command numeric value is inaccessible to scripts
546. [+] (K) 10-digit dialing rules forgets to dial the area code
547. [+] (K) GET/REGET with SET FILE PATTERNS ON may corrupt files
548. [+] (K) REMOTE commands may set STATUS to SUCCESS on FAILURE
549. [+] (K) RUN command interferes with screen updates in a script
550. [+] (K) \fword() fails to find the last word in a string
551. [+] (K) Partial Dialing misuses dialing rules

       ----(Version 1.1.17)----
     

552. [+] (K) The PRODUCT macro had an extraneous parameter
553. [ ] (K) SETUP from CDROM might not exit cleanly
554. [+] (K) URL hot spots vs Netscape Communicator
555. [+] (K) Missing files (not really)
556. [+] (K) DATE command does not return to command prompt
557. [+] (K) CPS display in XYZmodem transfers is incorrect
558. [ ] (K) Problems with SET FILE INCOMPLETE DISCARD
559. [+] (K) Crash during Zmodem download with SET FILE COLLISION RENAME
560. [+] (K) TAPI dial gives "invalid call state message" after Busy
561. [+] (M) Dead Keys cause K95.EXE to terminate in NT
562. [+] (K) If PDIAL is used, all subsequent calls are partially dialed
563. [+] (K) HOST.KSC vs. K95 1.1.17
564. [ ] (M) Don't tell K95 to RUN 16-bit programs
565. [+] (K) SET SERVER IDLE-TIMEOUT doesn't timeout
566. [+] (K) VT Origin mode does not apply to Next Line (ESC E) command
567. [+] (K) PCTERM support not compiled into 1.1.17
568. [*] (V) Using K95 with a NASI modem
569. [*] (K) VT Soft-character-set assignments
570. [ ] (M) Windows 95/98 DNS Caching results in Kerberos Authentication Failures
571. [+] (C) TZ environment variable necessary for Kerberos Authentication
572. [+] (K) Word Perfect Keyboard Mode does not work
573. [ ] (M) More about Caps Lock
574. [+] (K) CONNECT /TRIGGER causes memory exception in OS/2
575. [ ] (C) "NO CARRIER", SET CARRIER-WATCH, INPUT and Hayes High-Speed Modems
576. [+] (K) Install of K95 1.1.17 on Alpha does not perform registration
577. [+] (K) Televideo terminals enter infinite loop when using Block mode
578. [+] (K) SNI 97801 terminal emulation bugs
579. [ ] (M) K95 Telnet can crash if remote host crashes
580. [+] (K) K95 prints double characters when Copy Print mode is used

       ----(Version 1.1.18-CU)----
     

581. [+] (K) REMOTE {SET, ASSIGN, RENAME, COPY} do not return to CONNECT mode
582. [+] (K) Incoming TAPI calls may result in K95 crashes during file sends
583. [+] (K) Kermit/2 1.1.17 server does not return from REMOTE HOST commands
584. [+] (K) Transparent-print error if CSI received when remote character set is a code page
585. [+] (V) MIT Kerberos 2.0 K5 support disables K95 telnet authentication
586. [+] (V) SRP support fails to authenticate against SRP 1.5.0 Telnetd
587. [*] (K) K95 1.1.17 breaks Host-Mode Script
588. [*] (K) K95 and Host-Mode Script versions must agree
589. [*] (K) TAKE command arguments are persistent
590. [*] (K) Title-Bar Close box [x] doesn't work in Win9x

       ----(Version 1.1.19)----
     

591. [+] (K) VT102 emulation broken in 1.1.19
592. [*] (V) Failure to make certain Telnet connections
593. [+] (K) Faulty OS/2 Dialer Patch for K95 1.1.19
594. [+] (K) LOGIN.KSC didn't work without the Dialer
595. [+] (K) C1 Printable characters of non-ISO-2022 character sets
596. [+] (K) IBM 3151 attributes
597. [+] (K) OpenSSL requires the PRNG to be seeded.
598. [+] (V) Kerberos support not compatible with NRL SecureID support
599. [+] (K) MAIL command does not work
600. [+] (K) SEND ..\\*.c fails with "unreadable error"
601. [+] (K) LOCAL and global variable name conflicts
602. [+] (K) Kerberos password prompts versus -# 96 startup option
603. [+] (K) ANSWER 0 improperly times out
604. [+] (K) ANSWER fails to answer call with SET TAPI MODEM-DIALING ON
605. [+] (K) RLOGIN Window Size reports are not sent
606. [+] (K) Pulse dialing did not work
607. [*] (V) AUTH K5 INIT /NO-ADDRESSES may crash Kermit 95

       ----(Version 1.1.20)----
     

608. [+] (K) RLOGIN protocol (and secure variations) does not work in 1.1.20
609. [+] (V) Kerberos 5 NT Alpha 2 and previous releases do not work with 1.1.20
610. [+] (K) SET FILE DOWNLOAD-DIRECTORY leads to unexpected bahavior
611. [+] (K) HOSTMODE scripts updated
612. [+] (K) Telnet Forward-X option negotiated even when an X Server not found
613. [+] (K) Wyse 60 keyboard definitions are incorrect
614. [+] (K) \v(krb5errno) and \v(krb5errmsg) do not report all errors
615. [+] (K) The Dialer does not support %ENVVAR% expansion of file names
616. [*] (K) How to debug SET PRINTER configurations on Windows 95/98/NT/2000
617. [+] (K) RLOGIN host userid fails to send userid to host
618. [+] (K) -M command line option does not work
619. [+] (K) \v(exedir), \v(startupdir), \v(inidir) may have spaces in the name
620. [+] (K) Kermit 95 does not accept keyboard input on CJK Windows 95/98
621. [+] (K) QNX terminal emulation keypad-plus and keypad-minus keys do not transmit "+" and "-"
622. [+] (K) IBM 3151 unable to restore ASCII character set after Graphics character set is used
623. [+] (K) TYPE and TRANSLATE commands only work under specific circumstances
624. [+] (V) 1.1.20 is incompatible with Services for Unix 2.0 Telnet Server
625. [*] (K) Wheel Mouse Button Numbering
626. [+] (K) Transparent Print Bug introduced in 1.1.18
627. [+] (K) Attempts to Add/Edit in K95 Dialer produce GPF on Windows 95/98
628. [+] (K) K95 crashes on Windows 95 if SECUR32.DLL is missing
629. [+] (K) K95 Dialer 1.1.20 dialer produces non-fatal GPF on startup
630. [+] (K) Printer device not closed (if open) when K95 exits
631. [*] (V) Winmodems
632. [+] (V) SRP client security hole discovered
633. [+] (K) K95 Documentation Shortcut to bugs file is incorrect
634. [+] (K) UPDATES.HTM file has wrong version number
635. [+] (K) K95 Linux Console emulation incompatible with Red Hat 7.x AND all other new Linux distributions
636. [+] (K) Buffer overflow caused by long modem response messages
637. [+] (K) Failures when connecting through SOCKS server takes too long
638. [*] (V) Can't start K95 from a DOS Prompt or from with a DOS application
639. [+] (K) K95.EXE when started from dialer complains about invalid command line parameters (Windows 2000/XP)
640. [+] (K) K95D.EXE stops accepting new connections after several hundred or thousand incoming connections
641. [+] (K) SET FILE COLLISION BACKUP fails on some file names but not others
642. [+] (K) SET TAPI MODEM-DIALING ON can cause scripting to fail
643. [+] (K) Dialer direct-serial configurations vs. Hardware Parity
644. [+] (K) Windows XP default location causes K95.EXE to crash on startup
645. [ ] (M) Ghost Character Fragments on NT/2000/XP Console Screen
646. [*] (K) The Kermit Timesync Utility Might Not Work

       ----(Version 1.1.21)----
     

647. [+] (K) Unbalanced-Braces Error in Scripts
648. [ ] (K) Disappearing Cursor
649. [ ] (K) Escape Character Status Line Typo
650. [+] (K) Status Line Not Updated after Ctrl-] Ctrl-]
651. [+] (K) HELP REMOTE HOST text wrong
652. [+] (K) SET COMMAND SCROLLBACK in a script can cause an invalid memory access
653. [+] (K) Kerberos 5 Rlogin fails to authenticate
654. [+] (K) Dialer bugs
655. [+] (K) telnet.exe and rlogin.exe do not work
656. [+] (K) Telnet ComPort option
657. [+] (K) Russian and Hebrew keyboard modes broken
658. [+] (K) SHOW SSH does not list all forwarded ports
659. [+] (K) COMPOSE and UCS2 Kverbs when used at Command Prompt do not
660. [+] (K) SET SSH STRICT-HOST-CHECK ASK is treated as OFF
661. [+] (K) \Kpaste on serial connections only sends 5 or fewer characters
662. [+] (K) SET TERMINAL KEY { RUSSIAN, HEBREW } does not work

       ----(Version 2.0)----
     

663. [-] (?) Spurious K95G screen clearing on startup
664. [ ] (V) Everson Mono Terminal Font Side Effects
665. [*] ( ) Dimensions popup inactive during resize
666. [*] ( ) Possible Help→Manual misbehavior
667. [+] (K) Underline and Blink control
668. [+] (K) Host-Initiated Resize vs Font Scaling
669. [+] (K) SET GUI WINDOW RESIZE-MODE command missing
670. [+] (K) Trouble with COM ports
671. [+] (K) Toolbar always visible
672. [+] (K) Upgrade Registration Problem

       ----(Version 2.0.1)----
     

673. [+] (K) 673. SRP authentication attempted when not configured on incoming connections
674. [+] (K) 674. Extended argument error
675. [+] ( ) 675. Non-English Directory Names
676. [+] (K) 676. SSH-AGENT.EXE Broken
677. [+] (K) 677. Default RGB color values in Dialer off by one
678. [+] (K) 678. Bulk License update loses number of seats
679. [+] ( ) 679. SSH connections to Cisco PIX
680. [+] (V) 680. TLS CBC Cipher incompatibility with IBM Info Exchange
681. [+] (K) 681. SET TRANSFER MODE MANUAL doesn't completely work
682. [+] (K) 682. COPY command destination file can have junk at end
683. [+] (K) 683. Secure FTP authorization failure error message missing
684. [+] (K) 684. Fencepost error in FTP MGET /UPDATE
685. [+] (K) 685. In FTP MGET /RECOVER failures
686. [+] (K) 686. Redundant downloads in FTP MGET /RECOVER wildcard wildcard...
687. [+] (K) 687. Missing message for FTP MGET /EXCEPT
688. [+] (K) 688. Automatic Locus switching fails when FTP connection drops
689. [+] (K) 689. FILE INCOMPLETE setting ignored by FTP module
690. [+] (K) 690. FTP MGET sends superfluous commands to server
691. [+] (K) 691. FTP MGET pattern1 pattern2 pattern3 could stop prematurely
692. [ ] (K) 692. Interrupting FTP operations with Ctrl-C is problematic
693. [+] (K) 693. Terminal screen might have fewer columns than desired
694. [+] (K) 694. /POPUP switches in GUI version work improperly
695. [+] (K) 695. Changing GUI Resize-Mode behavior while maximized
696. [+] (K) 696. SET COMMAND CURSOR-POSITION broken
697. [+] (K) 697. SSH disables password based logins upon key change detection
698. [+] (K) 698. Scroll-mode exiting not always possible using the GUI scrollbar
699. [+] (K) 699. FTP PUT Text Xfers with Character-set Translation Broken
700. [+] (K) 700. SET TERMINAL IDLE-TIMEOUT does not stick in some circumstances
701. [ ] ( ) 701. Unable to write to various Windows directories from K95

       ----(Version 2.1.0)----
     

702. [ ] (V) 702. Everson Mono Terminal font misbehavior on Win9x/ME
703. [+] (K) 703. FTP MGET Might Fail Immediately with Invalid Temp-File Name
704. [+] (K) 704. FTP MGET fails when directory segments contain wildcards
705. [+] (V) 705. Kerberos Leash Shows Garbage for Local Domain
706. [*] (M) 706. K95 can't download files named CON or CON.anything
707. [+] (K) 707. TELNET Com Port Control vs the INPUT command
708. [ ] (K) 708. VTNT connections vs Ctrl-C
709. [+] (K) 709. Mouse print selection broken in GUI
710. [+] (K) 710. K95 Does Not Support Remote SSH Agent Proxies
711. [*] (K) 711. Maximize and Restore versus Resize Mode

       ----(Version 2.1.3)----
     

[ Top ] [ Index ] [ K95 Home ] [ Kermit Home ]

BUG DESCRIPTIONS

1. Ctrl-C Interruption in Command Screen

Once Ctrl-C fails to be delivered, it might never be delivered again. Workaround: evidently the only workaround is to restart Windows. In the meantime, you can still send Ctrl-C in the Kermit 95 Terminal screen using Ctrl-Shift-C (or any other key to which you use SET KEY to map \3).

If you use Ctrl-C to interrupt a file transfer that has not yet started, there may be a delay of several seconds before the Ctrl-C takes effect (this one is fixed in 1.1.2).

In some cases, even when Ctrl-C is ignored, however, you might still be able to use Ctrl-Break for the same purpose.

Also see: Bugs 83 and 152.

2. Video Attributes vs Terminal Screen Size in Windows 95

Note, however, that Windows 95 video drivers are optimized for 80x(25,43,50); other sizes work correctly as of K95 1.1.12, but might work slowly or exhibit annoying amounts of flicker. This is a Windows 95 feature.

3. Microsoft Telephony (TAPI)

4. Registration

In 1.1, registration was applied only to the K95.EXE file. Beginning with 1.1.1 it was extended also to the Dialer.

5. Changing Code Pages

NOTE: This item applies to Windows. In OS/2, loading code pages or "PC fonts" into a full-screen session is not only permitted, but also safe -- provided the video driver allows it; evidently, however, the trend in new video drivers is not to allow it -- thus preventing Kermit 95's Hebrew and Cyrillic support from working as widely as it used to. See Section 3.4 of OS2K95.TXT.

NOTE 2: As of version 1.1.8, this section applies only to Windows 9x. The Windows NT version of Kermit 95 now uses Unicode fonts rather than PC code pages.

As noted in the Kermit 95 manual, Windows 95/98 does not support code page switching. The idea is that if you are going to use code pages, you should use only one. But that's bad because some people really do need to work in different languages; for example, English, Icelandic, Hebrew, and Russian. Kermit 95 supports all of these very nicely as long as the underlying code page is installed. Presumably if you are running Windows 95 in Iceland, your code page is 850; in Poland it is 852; in Israel it is 862; in Russia it is 866; in Greece it is 869. So if you have the code page you need, no worries. But if you need to work in (say) both Russian and Hebrew, you need a way to switch code pages.

To change code pages, you can get a utility from Microsoft called CHANGECP. It is on the Windows 95 CDROM, in the Other\Changecp folder. It comes with lots of code pages, including 862 (Hebrew) and 866 (Russian). Its menu only lists a few of them, but you can try typing any one you want on the command line; for example:

  changecp 850

or:

  changecp 866

And then rebooting your system. You can't change code pages on the fly in Windows 95 as you can in DOS. Nor is there any way to load fonts into a DOS window of Windows 95 (such as the LOADFONT program we use with MS-DOS Kermit to provide code-page switching).

Maybe CHANGECP will work for you, maybe not. When we tried it, 850 worked, 866 did not, even though all the supporting files for CP 866 were included. The supporting files for Hebrew CP 862 are not even there, so this one didn't even have a chance.

When you run CHANGECP, it prints a scary error message warning of possible disk corruption. This means that if you use accented or special characters in filenames (or for that matter, in the files themselves), the appearance of those characters can change if you change code pages. If CHANGECP does not work for you, our best advice is to give up -- do not try editing the Registry or any other workaround, as this is almost certain to end in tears.

If a code page can be loaded, Kermit 95 can use it. But it seems that the only way you can have a "non-Latin1" code page loaded is to install the appropriate national version of Windows 95 -- such as Hebrew, Russian, Czech, Ukrainian, Polish, etc.

If you want better language support in Windows 95 console applications, express your wishes to Microsoft.

NOTE: You can use the DOS LOADFONT program together with the "PC fonts" that are distributed with MS-DOS Kermit to load Cyrillic, Hebrew, and other code pages into full-screen Windows sessions, BUT this tends to cause Windows (not Kermit, but Windows) to crash, so this practice is not recommended, encouraged, or supported. The true fix to this situation will come in the conversion of K95 to full GUI, when it will no longer have to use code pages. (As of version 1.1.8, the Windows NT console version uses a Unicode font, so it can display any characters that are in its font -- e.g. Lucida Console.)

6. Keyboard Scan Codes and Caps Lock

The Caps Lock bug is fixed in 1.1.5. For dead keys, see items 103-104.

Also see items 283 and 386.

No problems in OS/2.

7. "Kermit 95" Keyboard Verb table

As of version 1.1.14, the HELP KVERB command can be used to find out what a particular kverb does and which key it is assigned to.

8. PUSH and related commands do not work in Windows NT 3.50

9. Don't Use the Auto Font Setting in Windows 95

Starting with K95 1.1.12, the first version to support true 132-column screens in Windows 95, a font size of Auto in the Console version can cause Windows 95 (original version) to create ever-smaller screens when switching back and forth between 80- and 132-column mode, eventually resulting in alert boxes or crashes. This is a Windows 95 bug, not a Kermit one. When this happens while TAPI is in use, the modem will become unusable until Windows 95 is rebooted.

Choose a specific font size, not "Auto". See the instructions in the READ.ME file creating a shortcut. You can choose your preferred font size in the K95.PIF file that you create when following those instructions. (As noted there, the default font size for console windows is set by editing the Properties of C:\WINDOWS\SYSTEM\CONAGENT.EXE).

10. Blotchy Dialer Fields

11. Missing Features

12. Hardware / System / Drivers Configuration

Serial communication devices must have unique addresses and IRQs (Interrupt numbers). You can't have more than one device using the same IRQ. If you do, neither device is likely to work -- or worse. Unfortunately, many devices (such as network boards) are often shipped set to the same IRQ (3 or 4) that is used by a serial port.

Serial ports COM3 and COM4 (or higher) are always problematic, since these are not part of the standard PC architecture and there are no slots for them in the PC BIOS. COM3 and COM4 are generally set by their manufacturers to use IRQ 3 or 4, which conflict with COM1 or COM2. To resolve the conflict, you must either find a free IRQ and set your COM3 or COM4 device to use it (and tell Windows about it), or else disable one or more of the conflicting devices. Changing the IRQ is risky because the new one you pick is likely to conflict with something else, especially in a well-equipped PC (CDROM, sound card, network adapter, etc).

In Windows 95, a COM port is supposed to be recognized automatically when you install it. However, Windows might easily make incorrect assumptions about its address or IRQ, or whether it has a FIFO (First-In-First-Out) buffer. You can examine these, and correct them if necessary, in My Computer -> System -> Device Manager -> Ports -> Advanced. In Windows NT, Control Panel -> Ports -> Advanced.

Even when your configuration is conflict-free, you will experience data loss -- often severe -- on serial connections if your serial-port controllers are not "buffered": 16550A UARTs must be used, rather than lower-numbered models. Unfortunately, many PCs are furnished with unbuffered UARTs by their manufacturers as a cost-cutting measure. You can find out what kind of UARTs you have on which COM ports, on which addresses, using which IRQs, in the Windows dialogs mentioned above.

Steer clear of any modem that says "RPI" or "Controllerless" or "Winmodem" on the box. Read the small print carefully. These are not fully functional modems, and are very likely not to work adequately, or at all, under Windows NT or OS/2. Although they are designed for Windows 95, they might not work well there either, and even if they do, they might impose an unacceptable load on your system, since the full job of the modem is being done by the PC CPU, and/or they might interfere with your sound card. (Note: nowadays, most new PCs come with Winmodems preinstalled -- the only way to avoid them is to buy a second, external, modem and attach it to your COM1 or COM2 device.)

Another type of problem occurs whenever you use certain software that installs its own drivers (such as COMM.DRV, the Windows 95 communications port driver) over the real one. Such drivers are intended specifically for use with the software they came with, and will often fail to work with other software. Unfortunately, there is often no notification when a standard driver is replaced in this manner, and also there is often no easy way to undo the change. You can find out about your communications driver in the modem diagnostics, Driver button. The communications port driver that comes with the first release of Windows 95 is identified there as:

COMM.DRV, 5856 bytes, 7/11/1995 09:50AM

(the date and time display might vary with time zone).

Problems that are even more subtle and vexing can result from any of the drivers you have installed on your PC -- SCSI-board drivers, sound-card drivers, CD ROMs, etc. Sometimes the problems are solved by obtaining a newer version of the driver from the board vendor. Other times, the only recourse is to purchase an entirely different board and driver.

Even more ominous are problems with the PC BIOS. PC makers often have BIOS upgrades available, perhaps downloadable from their BBS's or Web sites.

Also, owners of laptop and "green" PCs should watch out for the untoward effects of power savers and suspend/resume features on internal modems, PCMCIA cards, and similar hardware.

Finally, beware of any system changes that you make. In Windows, do not use the Registry editor (REGEDIT) unless (a) you know what you are doing, and (b) you have a way to back out of any changes. A seemingly innocent change in the Registry can have unpredictable ramifications later on, causing Kermit 95 and all your other applications, and Windows itself, to misbehave or malfunction. In some cases the only recourse is to reformat your hard disk and reinstall Windows 95 from the original media.

13. Miscellaneous Dialer Peculiarities

• The Hangup button does not interrupt dialing. If you need to interrupt dialing, bring the Kermit 95 Command window to the front and type Ctrl-C.

• Other items from this entry are fixed.

14. Miscellaneous Hints and Tips

• The Terminal screen can become frozen under certain circumstances; for example, receipt of an unterminated escape sequence (perhaps caused by noise). When this happens, the Terminal screen will report OSC, APC, DCS, etc, in the status line. To unfreeze, use Alt-R (Reset) while in the terminal screen. This is not a bug -- it is how real VT 220 and higher terminals work.

• If you try to download a file directly to the printer by naming the file "PRN", this will fail unless you "set file collision overwrite". That's because Kermit's normal action when receiving a file is create a backup copy -- but it can't make a backup copy of the printer :-) Similarly for other files whose names are the same as those of DOS devices: LPT1, AUX, COM2, and so on.

• The printer driver might fail to print the last or only page. This is a traditional shortcoming of PC operating systems. Sometimes the page can be forced out by using Alt-E (verb \KprintFF) to send a formfeed to the printer, or by sending another print job, to the printer. Some printers (such as the HP4L and HP5L) have a special button that ejects the page. K95 1.1.14 and later offer additional printer controls, such as the /END-OF-JOB switch, documented in the current K95 manual.

15. Debugging Tips

You can troubleshoot connection problems by following the instructions in Chapter 3-6 of Using C-Kermit, second edition. You can obtain transcripts and logs of troublesome connections using "log session" and also with "set dial display on" and then using your mouse to copy and paste the modem dialog from the screen into a file.

You can troubleshoot terminal emulation problems by putting the terminal screen into debug mode (with Alt-D when the terminal screen is active).

You can troubleshoot file-transfer problems by following the instructions in Chapter 10 of Using C-Kermit (second edition). File-transfer packet logs are obtained with the "log packets" command.

The ultimate debugging tool is the debug log, obtained with "log debug". It tends to grow huge rather quickly.

Any or all of these logs can be sent to our tech support staff for analysis in cases where suggested remedies or workarounds are ineffective.

Version 1.1.14 and later allow the session.log and debug.log files to be activated in the Dialer entry.

16. K-95 Dialer Vertical Scrolling

17. ZMODEM Downloads

18. ZMODEM and TELNET

19. Alphabetization of Dialer Entries

20. K-95 Sometimes Thinks a Connection is Open When It Starts Up

21. Download Directory Doesn't Work

22. SET MODEM commands in K95CUSTOM.INI have no effect

23. Kermit 95 sometimes can't find its script or key mapping files

24. The Dial Prefix also becomes the Dial Suffix

25. Dialer complains unnecesarily about range of certain numbers

26. Kermit BBS entry in Dialer has wrong backspace key setting

27. Screen updates updates are slow on some PCs

Kermit 95 is necessarily less snappy than MS-DOS Kermit (under DOS) on the same type of PC because MS-DOS Kermit is in direct control of the communications and the video, whereas Kermit 95 must go through several layers of drivers and operating-system calls to do the same thing.

Video drivers vary in speed. Those in Windows NT tend to be significantly slower than those in Windows 95. Even in Windows 95, some drivers or hardware might be slower than Kermit 95 was designed for. Kermit 95's default screen-updating cycle is 100 milliseconds (1/10 second); if your video driver is slower than that, you might be able to make Kermit go faster by increasing (yes, increasing) its screen-update interval, for example:

  SET TERMINAL SCREEN-UPDATE FAST 200

Flickering can occur when the video driver is not performing a comparison between what is already on the screen and what it is being asked to write. So it paints the entire window (which takes time) even when it doesn't have to. When acceleration is on (and supported by the driver) minimal screen paints occur and screen updates should be fast. In the Control Panel either on the Display object or the System Object, there is a performance page which allows you to set the Video Acceleration properties. Make sure this is set to use full acceleration. The only flickering you should see in this case is the mouse pointer, since it is turned off and on before and after each console screen paint.

If that doesn't help, you can experiment with Kermit 95's SET TERMINAL SCREEN-UPDATE FAST and SMOOTH options to choose which algorithm is used to update the screen when new data arrives from the host. Whenever a byte arrives from the host it is processed by an incoming data thread. If it would result in a screen write, an internal screen buffer is updated and a flag is set. When using the FAST algorithm, the screen buffer is copied to the physical screen (if the flag is set) on a timer thereby allowing the maximum data throughput from the host to occur regardless of the speed of the video drivers. This is the default screen updating method.

The negative aspect of this method is that on really fast connections it is possible for some screen writes to never make it to the screen, e.g. during continuous scrolling (but the data is processed correctly, and can be viewed in the scrollback buffer). The SMOOTH option says to copy the screen buffer to the window whenever the dirty flag is set. This results in much slower data handling, and a potentially significant increase in the number of screen writes, but on the other hand it tends to make echoing snappier when you are typing. Also see item 469.

28. ZMODEM Recovery

29. ANSWER command crashed Kermit 95

30. Kermit always turned off autoanswer in the modem

31. Compose Key problems

32. SET TERM CHARACTER-SET TRANSPARENT did not show all characters

33. Various other VT emulation problems

34. Printer problems

35. \v(keyboard) variable improperly set

36. XMODEM file transfer problems

37. MOVE and MMOVE command did not work right with XYZMODEM

38. Ctrl-C interruption nonfunctional in certain cases

39. File transfer recovery after Ctrl-C

40. SET FILE DOWNLOAD-DIRECTORY didn't work with server mode

41. Filenames could not be parsed from variables

42. Choosing terminal character-set in the Dialer

43. The EMACS.INI file was not properly patched in version 1.1.1

44. The 1.1.1 patch destroyed multiple READ.ME files

45. Xon/Xoff flow control doesn't work in Windows 95

46. Server mode sometimes locks up in Windows 95

Partially fixed in version 1.1.3, by using temporary files rather than pipes.

Partially fixed even more in 1.1.5 by recoding REMOTE DIRECTORY, REMOTE DELETE, etc, not to call the Windows shell, but to do everything internally. So now, hopefully, the problem occurs only with REMOTE HOST commands, if at all.

Fixed even more in 1.1.16 by changing the handle used by K95 for accessing the console device.

47. Kermit 95 file naming conventions in conflict with Windows

Kermit initialization and key mapping files historically have a filetype (extension) of .INI, but these are different from Windows .INI files.

Kermit online plain-text documentation have historically been had the .DOC filetype, but Windows thinks these are Word documents. In Kermit 95 1.1.11, all *.DOC files were renamed to *.TXT.

Similarly, Kermit script program files have long had a filetype of .SCR, but in Windows 95, .SCR files are associated with screen savers. Thus if you double click on a Kermit .SCR file, you are likely to get an undesired result.

In Kermit 95 1.1.3, all script files distributed with Kermit 95 were renamed from *.SCR to *.KSC, and all references to them (e.g. in the many Dialer pages) were changed accordingly, and the new script files that were included with this release for host mode were also given the .KSC extension. The .INI files, however, were not renamed. Kermit has been around a lot longer than Windows!

48. The Dialer Login page does not show LOGIN.SCR in the text box

49. The K-95 icon does not show up in Windows NT 3.5x

The K-95 icon is in the Windows 95 icon format, which can't be correctly displayed in Windows NT 3.xx; it shows up as a black square. It works fine in Windows NT 4.0. (An OS/2-format icon is included with the OS/2 version.)

50. SEND and RECEIVE as-names ignored by XYZMODEM

51. Missing files

Certain files mentioned in Kermit 95 manual are missing. These include:

• P.DOC (after the manual was written, the P.EXE program for XYZMODEM protocol file transfers was fully integrated into Kermit 95, and thus has no user interface or commands of its own);

• KERMIT.KDD (the Kermit Dialing Directory) referred to on page 30 is really CKERMIT.KDD in the PHONES subdirectory;

• DOCS\FONTS.DOC does not exist. At press time we thought we had a safe way to switch fonts, but it was not to be. A forthcoming release will address this issue.

• DOCS\APC.DOC does not exist. The APC feature is fully documented in the second edition of Using C-Kermit.

52. Title bar not properly set from "kermit -j host"

53. Can't interrupt SET HOST or TELNET or RLOGIN command (M).

Restriction. The Winsock connect() function does not respond to the WSACancel call.

54. Download directory only works for Kermit transfers

55. Crash when pasting voluminous material into terminal window

56. Problem with SET FILE DOWNLOAD-DIRECTORY<Enter>

57. Terminal reset kills K95 if TERM CHARACTER-SET is TRANSPARENT

58. Cursor-type selection made in Dialer not saved

59. PBX-related Dialer entries not saved

60. No choice for location of Kermit 95's temporary files

61. The "Paste" button on the Terminal Window's Toolbar doesn't work (M).

"If I put text into the Windows Clipboard using regular Windows services, such as the Mark and Copy buttons on a console-window Toolbar, or mouse-select and Edit->Copy in a GUI Window, then I can't use the Paste button on the Kermit 95 window toolbar to paste the material into the Kermit 95 screen." Cure: Open the Properties dialog for the window; go to the Misc page and turn off "Fast Pasting".

No problem in Windows NT. In OS/2, Kermit 95 comes with K2CLIP.EXE, the Kermit/2 Clipboard Server, to take care of the clipboard.

62. EMACS.INI Alt-x = Meta-x doesn't work

63. INPUT could not be canceled from the keyboard

64. SET ALARM / IF ALARM doesn't always work

65. \v(cpu) always says "unknown"

66. Invalid escape sequence ESC [ ? 6/7 i caused problems

67. Problems with transparent printing and accented letters

68. Microcom Deskporte modem configuration wrong

69. Cursor-type selection not saved by Dialer

70. PBX material from Locations and Codes Dialer page not saved

71. SET TERM CHAR TRANSPARENT, then terminal reset, causes crash

72. Spurious "Connection might still be active on COM1..." messages

73. SET PORT<Enter> gives spurious error message

74. DIAL timeouts sometimes caused an "access violation" crash

75. Modem list in SETUP program PPI / Multitech mixup

76. Incorrect default assignment for Ctrl-Space key combination

77. "k95 filename" requires fully specified filename

78. XYZMODEM Transfers didn't work over RLOGIN connections

79. PCMCIA or Plug-and-Play Modem Problems

The Microsoft VCOMM driver used in Windows 95 versions prior to OEM SR2 for serial port services in console windows does not support Plug-n-Play. Therefore, 32-bit communication programs such as Kermit 95 can not use these modems in Windows 95 unless they are previously initialized by another program, such as Hyperterminal or Dial Up Networking.

Version 1.1.10 of Kermit comes with a new utility, K95CINIT, to initialize such modems so they can be used by Kermit 95. This program needs to be run only once each time you boot Windows 95. You can run it "by hand" at any time before starting Kermit 95, or you can put put in your StartUp Menu to make it run automatically each time you restart Windows.

Version 1.1.12 supports TAPI and so should work with any modem or other TAPI device at all; K95CINIT is not needed in K95 1.1.12 or later unless you want to use a Plug-n-Play COM-port device directly that Kermit can not normally see on its own as a COM port, rather than through TAPI.

80. RLOGIN vs FTP Software OnNet-32 (V).

You can also specify the port number (not name) in RLOGIN commands to Kermit:

  rlogin hostname:513 [ userid ]

This allows you to make RLOGIN connections without editing the SERVICES file.

81. "set host 0" vs FTP Software OnNet-32

82. Kermit 95 and Digital UNIX 3.2

1. Tell UNIX "stty rows 23" (one less than Kermit's screen length), or:
2. Tell Kermit "set term height 25".
3. Tell Kermit "set term statusline off" (1.1.5) to let UNIX use the bottom line.

It is not known whether Digital UNIX 4.0 behaves differently.

83. Extraneous characters on terminal screen in Windows 95

84. Some special keys on national keyboards don't work

85. VT220/320 Erase Character (ECH) bug

86. Intel Modems without Fax

87. LOGIN.SCR renamed to LOGIN.KSC to avoid conflicts with screen savers

88. Uploads on LAT connections tend to fail

89. XYZMODEM and Kermit screens and stats are inconsistent

90. Printing to network printers in Windows 95 or NT might not work (M).

Kermit 95 1.1.12 offers various new SET PRINTER options that should address this problem. See the current manual, or type HELP SET PRINTER at the K95 prompt, for details.

91. Messed up colors on initial Terminal screen

92. Colors behave differently than in MS-DOS Kermit

93. Printing to PostScript printers doesn't work

94. Redialing on a SET HOST/SET MODEM/DIAL connection didn't work

95. Command-file line numbers not reset

96. ASSIGN/DEFINE failed to fail if definition too long

97. Dialer temporary files called .SCR instead of .KSC

98. The MSEND command did not work with ZMODEM

99. Backspace key didn't work with "set term char finnish"

100. Kermit 95 for Windows requires long filenames

One file name in the Kermit 95 distribution, K95CUSTOM.INI, exceeds the 8.3 FAT name format. This is not a problem in Windows 95, but it is bad news in Windows NT when long filenames are disabled (by editing the registry) -- the installation procedure fails. Even if the industrious user finds a way to complete the installation, the temporary files created by the Dialer (based on the Dialer entry names, many of which are quite long) will cause runtime failures. So, at least for the present, maybe forever, this is a restriction. Kermit 95 can not be installed on file systems restricted to 8.3 notation.

101. Host-controlled status lines

Version 1.1.8 adds full support for the VT320 status line (and for user messages on the Wyse models and Televideo label lines).

102. Wyse screen-transmit functions not implemented

103. Windows 95 Dead key and Caps Lock bugs are fixed! (mostly)

The bugs noted in Entry 6 regarding dead keys and Caps Lock should be mostly fixed in version 1.1.5 by doing an end-run around the buggy Windows 95 console agent(*), and adding our own substitute keyboard handling in its place. The fix is not perfect, however, because the "raw" keyboard driver is still hidden from us, and the information we do receive is partially corrupted by Windows.

On the positive side, the Caps Lock bug is gone, and dead keys seem to work correctly on US systems when the "international" keyboard driver is selected, which uses dead keys, as well as on real German, Finnish, and other West European Windows 95 systems, where it is also reported that the special single-stroke keys (such as Umlauts on the German keyboard) work correctly. The the terminal emulation and character-sets sections of the current K95 manual for details.

On the negative side, the fix interferes with the Alt-Gr key which, on most non-USA keyboards, is used to select the "third" (or lower right, or front) character printed on the keytop. Alt-Gr is normally the right Alt key, and it is really just a shorthand for Ctrl-Alt. Thus, for example, on the German keyboard, Alt-Gr-q produces at-sign (@), and so does Ctrl-Alt-q. To work around this side effect, you can either use Ctrl-Alt instead of Alt-Gr, or you can give this command to Kermit 95:

  SET WIN95 ALT-GR ON

This tells Kermit 95 to treat the right Alt key as if it were Ctrl-Alt. If SET WIN95 ALT-GR ON produces other unwanted and unanticipated side effects, set it back OFF and use Ctrl-Alt instead.

SET WIN95 ALT-GR ON enables the use of Alt-Gr as a SHIFT key (i.e. to be held down at the same time as the key it is modifying, just like Shift, Alt, or Ctrl). Kermit 95 does not support the use of Alt-Gr as a "prefix" or "sticky shift" key (to be pressed and released prior to pressing the modified key).

Also, our workaround has moved some Control keys. For example, Ctrl-\ (ASCII 28, Field Separator) which is normally sent by Ctrl-sz (Ess-Zet) on a German keyboard (top left of 0 in digits rank), or Ctrl-] (ASCII 29), normally sent by Ctrl-9, are now sent from their original positions on the US keyboard. If you want to change these back to their expected positions, use SET KEY.

Of course, under Windows NT, dead keys, special keys, and Alt-Gr work naturally and correctly (without any workarounds in the Kermit code), except that some NT users report a beep whenever a dead key is pressed (even though the correct dead-key combinations are still produced).

All of these problems will disappear when the GUI version is released and Kermit is no longer accessing any of the bug-ridden Windows console services.

(*) Microsoft PSS ID Q140456, 12-07-1995: "Deadkeys cannot be accepted as input to a Windows 95 Console application even when the appropriate keyboard layout is selected. ReadConsoleInput() cannot read deadkeys in Windows 95".

NOTE: Alt-Gr and Dead-key handling were broken again during the translation to Unicode in 1.1.8 and was fixed and improved in 1.1.14. As of 1.1.14, K95 should properly default the SET WIN95 ALT-GR command for most keyboard layouts. 8-bit characters should now be properly translated for all locales from the ANSI code page to the OEM code page used by the Windows Console environment.

104. East European keyboard features might not work in Windows 95

NOTE: This item applies only to Windows 9x. Since the release of version 1.1.7 we have had confirmation from Poland and other East European countries that the features described below work as advertised.

Testing of version 1.1.5 on East European Windows 95 versions was limited to the Czech version. Results are unknown for Polish, Hungarian, Romanian, and other East European versions. If you have problems entering East-European (Latin2) characters, first make sure you have:

  set terminal character-set latin2 cp852
  set terminal byte 8

If SHOW terminal doesn't say your code page 852, then also:

  set win95 keyboard latin2

and, as noted in item 103:

  set win95 alt-gr on

In the Terminal Window, you can also enter East-European characters using Kermit 95's Latin-2 Compose-key feature, documented in the current manual. As of 1.1.14, SET WIN95 KEYBOARD-TRANSLATION is no longer needed. Translation from ANSI code pages to OEM code pages is performed using Win32 API calls.

105. VT emulation DCS/OSC/APC/etc bugs

106. Terminal color bugs in version 1.1.4

107. VT220/320 downloadable fonts / soft character sets don't work

108. SET TERMINAL CHARACTER-SET PORTUGUESE didn't work

109. VT emulation and SET TERMINAL CHARACTER-SET FINNISH (etc) bug

110. Autodownload versus SET TERM CHARACTER-SET

111. Keyboard doesn't work if I start K95.EXE from Netscape

112. Dialer radio buttons not lined up

113. Multiple sessions to same Dialer entry don't work

114. Can't selecte a Dialer entry from keyboard

115. Dialer crash after editing an entry entry name

116. Dialer PBX configuration problems

117. Ctrl-C doesn't work in NT when K95 started from the Dialer

118. No way to make LAT connections from the Dialer

119. Kermit 95 and Internet firewalls, SOCKS, etc

Kermit 95 for OS/2 includes a SOCKS4 interface, described in the Kermit 95 for OS/2 notes.

The Windows version does not. Firewall support needs to be built into the TCP/IP stack, or the network itself (e.g. in a router or transparent bridge), not each application. Microsoft Winsock, for example, does not support the SOCKS firewall negotiation mechanism, but Trumpet Winsock and FTP OnNet-32 do support it.

The Microsoft Catapult proxy server announced in July 1996, however, is supposed to provide transparent firewall support, both CERN and RWS (Remote WinSock) styles, to all Windows applications, and so should work with K95.

And from NEC, we have a new 32-bit version of SocksCap, which sits between Windows Sockets (WinSock) and the application (Kermit 95, Netscape, etc). Its authors have tested it successfully with 32-bit Microsoft WinSock on both Windows 95 and NT using many different applications. It should work with SOCKS4 and SOCKS5 servers. You can find SocksCap at:

  http://www.socks.nec.com/sockscap.html
  ftp://ftp.nec.com/pub/socks/sockscap/

Security concerns are addressed in K95 1.1.16 for Windows 95 and NT by addition of Kerberos IV and V authentication and encryption. CLICK HERE for further information. Kerberos authentication as well as CAST and DES encryption carry export restrictions mandated by USA law.

120. Unreasonable delays in SET HOST / TELNET to numeric IP address

121. Kermit 95 does not work with LWP 5.0 TCP/IP in Windows 95

The TCP/IP stack in LAN WorkPlace 5.0 is 16-bit. Kermit 95 only works with 32-bit Winsock stacks. Workaround: You can use MS-DOS Kermit with the LWP 16-bit stack (via its TELAPI interface); or obtain a 32-bit stack from Novell, if they have one.

122. No way to select split-speed serial communication

123. Errors in built-in modem support

124. SEND did not work with filename completion

125. OUTPUT could not send backslash characters

126. OUTPUT could not send long strings

127. Extraneous material in session log during INPUT

128. INPUT buffer too short

129. SEND foo\%a did not work

130. No way to print on A4 paper using textps

131. Invalid Page Fault after using command recall a lot

132. Alt- doesn't work

  set key \1979 \161

This works in the Terminal window and, as of version 1.1.5, also in the command window. As of K95 1.1.16, you can also use SET TERMINAL KEY /LITERAL to enter a literal definition, i.e. one that will not be translated.

133. Interruption keys are ignored during XYZMODEM transfers

134. Tone dialing changes to Pulse after first digit

When dialing out from a PBX, there is almost always a secondary dialtone. Typically you take the phone off-hook, get the PBX dialtone, dial "9" to get an outside line, and then get the phone company's dialtone. In a situation like this, you need to tell the modem to expect the secondary dialtone. On Hayes and compatible modems, this is done by putting a "W" in the dial string at the appropriate place. For example, to dial 9 for an outside line, and then 7654321, use ATDT9W7654321. In Kermit 95, this is accomplished with:

SET DIAL PBX-OUTSIDE-PREFIX 9W

(replace "9" with whatever your PBX's outside-line prefix is).

135. VT100 reverse scrolling broken

136. SET KEY commands became slow in 1.1.5

137. Terminal bell doesn't work as before, or at all.

Terminal Bell

Beeps the speaker (this is sometimes mapped by the sound drivers to the Windows Default Sound as configured in the Control Panel.

Beep Information

Windows Default Sound

Beep Warning

Windows Asterisk

Beep Error

Windows Exclamation

If these sound events do not have .WAV files associated with them in the control panel they will not generate any sound.

Also, make sure that you have speakers hooked up to your computer. Many new computers with built-in stereo sound boards do not have internal speakers.

138. SET MSKERMIT KEYCODES ON did not work with some gray keys

139. Array elements could not be used for file names

140. Keyboard modes can't be modifed

141. Control keys on national keyboards in Windows 95

  ; GERMAN keyboard 

  set win95 alt-gr on

  ; control key definitions
  ; in addition to predefined US-positions

  set key \1336 \27	; Ctrl-[ (Escape)
  set key \1499 \28	; Ctrl-\ 
  set key \1337 \29	; Ctrl-] 
  set key \1054 \30	; Ctrl-^
  set key \1334 \30	; Ctrl-^
  set key \1500 \30	; Ctrl-^
  set key \1469 \31	; Ctrl-_

142. SCOANSI and AT386 emulation vs Code Page 437

143. SCOANSI and AT386 emulation vs CSI 10/11/12 m

144. Bad characters in Registration name

145. SET MODEM commands in K95CUSTOM.INI are ignored by Dialer

146. Completion does not work with directory names

147. Command-line editing doesn't use PC editing keys

148. The DIRECTORY and TYPE commands are too slow

149. DIRECTORY command gives spurious error message

150. XYZMODEM transfer statistics are off

151. SET TERMINAL ESCAPE-CHARACTER DISABLED didn't work

152. Command screen messed up after Ctrl-C

153. Cursor disappears after Ctrl-C interruption of file transfer

154. \v(sysid) was garbage

155. SHOW KEY ALL did not show keys that had string definitions

156. Dialer File Transfer page items spuriously grayed out

157. SET TERM COLOR ERASE CURRENT-COLOR didn't work

158. Patching up from version 1.1.3 might not work

159. XYZMODEM file transfers gave incorrect status codes

160. XYZMODEM transfers made no transaction log entries

161. TELNET negotiations were sometimes skipped

162. Data loss during file transfer

163. K95 could not send a file that was already open

164. Dynamic packet timeout values were sometimes too high

165. Character attributes not shown in Televideo emulation

166. PATCH.EXE only works with FAT filenames

The patch product used for applying patches to Kermit 95 only understands DOS (FAT, 8.3) filenames on its command line. You can't give a filename to the Patch program that does not conform to FAT restrictions: directory names must not be longer than 8 characters, and must not contain spaces; filenames must have no more than 8 characters before the dot, and no more than three after it, and must not contain spaces, and there can not be more than one dot. Examples of patch commands that work:

  patch wi115-6
  patch d:\k95\download\wi115-6

Example of a patch command that doesn't work:

  patch D:\Downloads\Kermit 95 Patch\K95-Intel-from-1.1.5-to-1.1.6

167. TEXTPS.EXE was broken in version 1.1.5

168. File transfer efficiency number is misleading

169. VT220/320 DCS string cancellation didn't work

170. SCOANSI and AT386 emulation conflict with Dialer

171. Server GET fails if a SEND-LIST had previously been used

172. PUSH from Terminal screen to shell could not be returned from

173. K95DIAL window minimizes to desktop instead of task bar

174. Referring to directory names that start with digits

175. Televideo and Wyse printing didn't work right

176. Wrong default character-set for VT terminals in Dialer

177. The Dialer database can be corrupted by other applications (M).

• Kermit 95 Dialer database files (DIALER.DAT, DIALUSR.DAT, DIALINF.DAT) have an extension or filetype (the part of the filename after the period) of DAT (not unreasonable; people have been using DAT for data files for decades).

• Certain other applications, when you install them, register themselves in the Windows Registry as the application for all files having the .DAT extension. These applications include at least ACT! (from Symantec) and Wordperfect 7 (from Corel).

• The Kermit 95 Dialer database files now appear with the icon of the other application. Should you click on one of these icons, the other application will be started and fed the K95 database file, and will likely damage it. If that happens, the Dialer might be unusable from that point on.

There is nothing Kermit can do to prevent this. There is no mechanism for arbitration of conflicting file associations. If filetype XYZ is associated with application A and then you install a new application, B, it might undo application A's association and take over its files (or, conversely, it might find that its files belong to application A). This is intrinsic to the design of Windows. Only one application can be the default application for each filetype.

To defend against this effect, make a backup copy of your *.DAT files prior to installing any new application, preferably on a diskette, which you should remove immediately and put in a safe place. And then remember to avoid clicking on any of the files in your Kermit 95 directory, except of course the EXE files, no matter wh