home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
archives
/
honeywellgcosb.tar.gz
/
honeywellgcosb.tar
/
hdps8.txt
< prev
next >
Wrap
Internet Message Format
|
2000-10-11
|
3KB
From: Mark Sapiro <msapiro@value.net>
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Kermit with GCOS 8
Date: Thu, 31 Aug 2000 17:51:12 -0700
Organization: Not Very Much
Frank da Cruz wrote:
>
> In article <8olujd02gr9@enews2.newsguy.com>,
> David Copelovici <dcopelov@thinkage.com> wrote:
> : Is it possible to send text/binary files from a GCOS 8 machine (to an NT
> : machine) using the kermit protocol (I think it's called kermsend on the
> : GCOS machine)? If not, what are the problems associated with such a
> : transfer? I'm using C-Kermit 7.0.197.
> :
> Using C-Kermit 7.0.197 on what? You only mentioned GCOS 8 and NT. Do you
> mean Kermit 95 on NT? If not, that's the appropriate software for the NT
> side:
>
> http://www.columbia.edu/kermit/k95.html
>
> Anyway, maybe somebody who actually uses GCOS 8 can answer with more
> authority, but in case you don't hear anything else, everything we have for
> GCOS 8 is in the Kermit FTP archive:
>
> ftp://kermit.columbia.edu/kermit/d/
>
> The files are:
>
> -rw-rw-r-- 664 Aug 16 1988 hgann.txt
> -rw-rw-r-- 1105 Aug 16 1988 hgboot.a
> -rw-rw-r-- 3439 Aug 16 1988 hgdns.doc
> -rw-rw-r-- 64350 Aug 16 1988 hgker.b
> -rw-rw-r-- 46705 Aug 16 1988 hgker.c
> -rw-rw-r-- 9234 Aug 16 1988 hgker.doc
> -rw-rw-r-- 4620 Aug 16 1988 hgker.hlp
> -rw-rw-r-- 1323 Aug 16 1988 hgnps.doc
>
> These are all plain-text ASCII files. The actual release date was
> 5 Sep 1984. Whatever documentation exists is in the hg*.doc and hgker.hlp
> files (and the source code itself, of course).
>
> - Frank
Disclaimer---
I supported GCOS III and GCOS 8 at City College of San Francisco from
1975 through 1992. I knew a lot in those days. I may have forgotten it
all.
IMHO, the better GCOS Kermit is the package from University of Kansas.
This is found in the same ftp directory that Frank mentions, but the
files are those named "hdps8.*". In particular, the executable is
hdps8.pak which is run through the hdps8.ftn fortran program to convert
it to an actual executable (h*) file.
The one big drawback of this package is it doesn't support extended
length packets, but it does work. (I don't think any of the Kermit
implementations from Honeywell or Bull supported extended packets
either.)
Transferring text files in either direction is no problem. Transferring
to or from a GCOS binary file is accomplished differently depending on
the objective. If you wish to store a GCOS binary file on another
machine to be later sent back to GCOS and used there, you should use
text format for both transfers. This is the only method which will
preserve both the content and exact size of the GCOS file. If you wish
to transfer binary data files to/from GCOS to actually be used on GCOS
and a different machine, you use either "bitstream"
or "bytestream" format depending on whether or not you want to transfer
the 9th bit of each GCOS byte. See the hdps8.doc file for more
information.
--
Mark Sapiro <msapiro@value.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan