Get the small (15 Kb) executable kixcrypt.exe from here.
Get the small (15 Kb) console-less executable wkixcrpt.exe from here.

18 December 2002 Version 2.14b released
Actually, it was released a few days ago, but the board has been down [Frown] It's amazing how much a part of my daily life monitoring the KiXtart BB has become!
Changes
  • A bug in memory allocation causing a failure on Windows XP has been solved. Note, I could not replicate the failure, but testing at the site where the failure occurred suggests it has been resolved. Let me know if it hasn't. Many thanks to ElegantSol for his help in resolving this.
  • The first "cannot find self" error message is no longer displayed. It wasn't particularly useful and would appear on systems which don't expand the command line to include the command extension, such as most NT+ systems.
  • In DEBUG mode non-ASCII characters present on the command line are reported, with their values.
  • Well, you asked for it, now you've got it. Oe of the most popular requests has been for a method of setting the directory that the temporary file is created in. There is now a "-t path" option when you decrypt which will create the temporary file in "path"
Additional Info
The API which retrieves the command line parameters cannot handle 8-bit characters. If you supply an 8-bit character the actual value I get is undetermined.
This restriction has been in place in all version of KiXcrypt, but I have only recently received an email on the subject.
In practice this means that you must stick to 7-bit ASCII characters on the command line. Note, non-printable characters such as the BEL (control-G) or the escape character are fine, so long as you work out a way of passing them on a command line.
7-bit ASCII characters are characters with a decimal value below 128.
The only exception is NULL (Chr(0)), which is an end-of-string terminator. You may have trouble typing CR and LF characters, and the DOS end-of-file mark (control-Z) may cause some oddities as well.