C-Kermit 6.0 - VMS Binaries

GO STRAIGHT TO FILE LIST

VMS binaries are different for VAX and Alpha. Furthermore, you can't run a binary built on VMS version X under any VMS version less than X. If you have a TCP/IP networking product installed on your VMS system, you must pick a binary that was built with the same or a compatible TCP/IP library, and its version number must not be greater than the version number of your own. So:

1. If you have a VAX, you need a VAX binary.
2. If you have an Alpha, you need an Alpha binary.
3. Pick a binary for a VMS version less than or equal to your VMS version.
4. If you want to make TCP/IP connections with C-Kermit, pick a binary that:
   • Was built with the same TCP/IP product that you have (Multinet, TCPware, etc);
   • Whose TCP/IP product version is less than or equal to the one you have;

   If you can't find one that meets these criteria, try one of the UCX versions, since most third-party TCP/IP products include UCX emulation.

Some of the binaries listed here might be from earlier C-Kermit releases. If you can replace them with up-to-date binaries, or you can make binaries that are not listed here, please contact us.

• This file might not be totally up to date or accurate, in which case you should go have a look at the FTP site directly, after reading the file naming conventions just below.

Remember:

• To transfer all binary files in binary mode.
• To also get the accompanying text files.

VMS binaries have names that look like:

  ckvaker-vmsnn-tttvv.exe

  ckv = "C-Kermit for VMS".
    a = architecture: A for Alpha, V for VAX.
   nn = VMS version, e.g. 55 for VMS 5.5, 70 for VMS 7.0.
  ttt = TCP/IP product, if any:
	CMU = CMU-OpenVMS/IP ("CMU/Tek")
	UCX = DEC TCP/IP
	TGV = Cisco (TGV) MultiNet
	TWG = Attachmate (Wollongong) WIN/TCP (PathWay)
	PST = Process Software TCPware
   vv = The version number of the TCP/IP product.

After obtaining the desired file, rename it to WERMIT.EXE and give it a quick run-through to make sure it works. Then read the CKVINS.DOC file (among the text files) and follow the installation instructions.

CPU   VMS_VER  TCP/IP       C-K_VER
VAX   VMS 4.4  NONET        6.0.192
VAX   VMS 4.4  TWG 3.2      6.0.192
VAX   VMS 5.?  CMU ?.?      5A(190)
VAX   VMS 5.?  PST ?.?      5A(190)
VAX   VMS 5.?  TWG ?.?      5A(190)
VAX   VMS 5.4  NONET        6.0.192
VAX   VMS 5.4  TGV 3.3D     6.0.192
VAX   VMS 5.5  NONET        6.0.192
VAX   VMS 5.5  CMU-IP       6.0.192
VAX   VMS 5.5  PST 5.0      6.0.192
VAX   VMS 5.5  TGV 4.0A     6.0.192
VAX   VMS 5.5  UCX 2.0      6.0.192
VAX   VMS 5.5  UCX 3.3      6.0.192
VAX   VMS 5.5  UCX 4.1      6.0.192
VAX   VMS 6.1  NONET        6.0.192
VAX   VMS 6.1  TGV 4.0A     6.0.192
VAX   VMS 6.1  UCX 4.0      6.0.192
VAX   VMS 6.2  NONET        6.0.192
VAX   VMS 6.2  TGV 4.0A     6.0.192
VAX   VMS 6.2  TWG 2.5      6.0.192
VAX   VMS 6.2  UCX 3.3      6.0.192
VAX   VMS 6.2  UCX 4.1      6.0.192
VAX   VMS 7.1  UCX 4.1      6.0.192

Alpha VMS 1.0  NONET        5A(190)
Alpha VMS 1.0  PST ?.?      5A(190)
Alpha VMS 1.0  TGV ?.?      5A(190)
Alpha VMS 1.0  UCX ?.?      5A(190)
Alpha VMS 6.1  NONET        6.0.192
Alpha VMS 6.1  TGV 3.5B     6.0.192
Alpha VMS 6.1  UCX 3.2      6.0.192
Alpha VMS 6.1  UCX 3.3      6.0.192
Alpha VMS 6.2  PST 5.1      6.0.192
Alpha VMS 6.2  NONET        6.0.192
Alpha VMS 6.2  TGV 3.5B     6.0.192
Alpha VMS 6.2  TGV 4.0A     6.0.192
Alpha VMS 6.2  TWG 2.5      6.0.192
Alpha VMS 6.2  UCX 3.3      6.0.192
Alpha VMS 6.2  UCX 4.0      6.0.192
Alpha VMS 6.2  UCX 4.1      6.0.192
Alpha VMS 7.0  NONET        6.0.192
Alpha VMS 7.0  PST 5.1      6.0.192
Alpha VMS 7.0  UCX 4.0      6.0.192
Alpha VMS 7.0  UCX 4.1      6.0.192

And the labeled-file conversion utility, for after-the-fact conversion of labeled files that were transferred in non-labeled mode:

VAX   VMS 4.4
VAX   VMS 5.4
VAX   VMS 5.5
VAX   VMS 6.2
Alpha VMS 6.1
Alpha VMS 7.0

KERMIT32.EXE