[comp.os.os9] OSTERM pak, cuts ... ?!?

reisinger@col01.dec.com (tausche Diesel gegen Flugzeug...) (11/24/88)

>    >>begin 644 osterm.pak
>>
>>What exactly is a '.pak' file? Is this an archiveer I don't know about?
>To you and Kevin H, (and all that need it)
>  A pak is an archiver you don't know about.  It follows in cuts format,
>including docs.  Osterm IS a super level 2 term pkg, I totally agree!  (I'm
>using it now)
>One bug I've found--sometimes the options window stops working.  (instead
>of a menu you get a scroll-by of trash--like C's string array pointer pointed
>to a bit bucket)
>Also, the autodial menu is slow to get started dialing.
> 
>Kevin...
>	Got news for me?  Reply normal please.  Of COURSE I'm being pateint!
>:-)

    !?!?,

    I never heard of CUTS, PAK and so on, but I'm running OS9.
    Is it possible to post at least one of this famous programs as
    (Compiler-) readable source ?

    
 Josef Reisinger
 DEC Cologne

PS: I have no chance to get any source from archives other than by mail
    or via usegroups.

jonh@tekgen.BV.TEK.COM (Jon Howell) (11/25/88)

>>>
>>To you and Kevin H, (and all that need it)
>>  A pak is an archiver you don't know about.  It follows in cuts format,
>>including docs. 
>
>    I never heard of CUTS, PAK and so on, but I'm running OS9.
>    Is it possible to post at least one of this famous programs as
>    (Compiler-) readable source ?
I assume you're running CoCo os9, osterm won't work on others, I'm sure!
I can only get the pak in binary format, however, I could re-encode it
using the Level I command BINEX, so if you have Level I, you can un-
encode it with EXBIN.  How's that?  I'll also send you cuts that way
too.  Cuts is currently only available in binary, as the author is
cleaning it up and sorting it, but it should be available as source
sometime in December.  Would you like both programs in BINEX format?
OR, I could just uuencode both, but that would mean you'd have to
have a way to either 1) download binaries from your mainframe (I don't)
or 2) have a uudecode on your CoCo.  I have C sources for uudecode
and uuencode.

This all looks a bit clumsy, but all SHOULD have a uudecoder, pak and
ar, and cuts for their CoCos.  CUTS is only necessary if you get files
from the ListServer at Princeton, or if you get them from people who
do (like myself).  CUTS is made to be able to send files over almost
any sort of mail link, including BITNET's silly 80 column and EBCDIC
conversions.  (For princeton's archaic IBM)

If you need any of these routines, folx, just hollar!

		Jon Howell

-- 
...!tektronix!tekgen!jonh  (503) MAK-SEMA  Jon Howell | Q: How come they never
  //  //  //  _  __    _   .  .   . .    ___   .  _   | play that on the radio?
 //  //  //  / \(_ __ (_)  |\/|  /| |\ |  |   /| /    | A: They should.
//  //  //   \_/__)    /   |  | /"| | \| _|_ /"| \_   |             --Dave Barry