info-mac@uw-beaver (06/01/85)
From: Moderator John Mark Agosta <INFO-MAC-REQUEST@SUMEX-AIM.ARPA>
INFO-MAC Digest Saturday, 1 Jun 1985 Volume 3 : Issue 3
Today's Topics:
C-Kermit Version 4C for Unix, VMS, and the Macintosh
Dynamic binding in C++
Re: Getting Maze Wars to Run
Maze Wars, an easier way
LaserWriter transparency printing?
LISA to Mac documents?
----------------------------------------------------------------------
Date: Thu 30 May 85 19:30:42-EDT
From: Frank da Cruz <SY.FDC@CU20B.ARPA>
Subject: C-Kermit Version 4C for Unix, VMS, and the Macintosh
This is to announce version 4C of C-Kermit for Unix, the Apple
Macintosh, and VAX/VMS. C-Kermit is a version of Kermit written
modularly in C, implementing the entire Kermit file transfer protocol
(except for attribute packets), designed for modularity and
transportability.
This version of Kermit has been in "field test" for about a month, and
is being released at this time because most of the major goals for it
have been met, namely:
. Most known bugs in release 4.2 fixed . Support for new systems added
and tested . A few new functions incorporated
At this point, C-Kermit should be considered a fairly stable base upon
which to add support for new systems -- the interface between the
system-dependent and portable modules seems to have settled down --
and to add new features.
A few highlights:
Systems Supported:
. Berkeley Unix 4.1 and 4.2 (but not yet 2.9)
. AT&T Unix System III and derivatives (Xenix/286, PC/IX, etc)
. AT&T Unix System V and derivatives
. Bell Unix Version 7
. DEC Pro-350 with Venix Version 1
. NCR Tower 1632, OS 1.02
. VAX/VMS
. Apple Macintosh
New features since version 4.2, common to all implementations:
. Many features redesigned to promote portability.
. Compile-time options to eliminate debugging and logging code to
reduce
size and boost performance.
. Packet parameters separately settable for inbound & outbound
packets.
. Protocol operation improved here & there, many bugs fixed.
New features for Unix implementation (and VMS):
. Command line continuation
. Support for additional modem-dialers
. Improved performance for Pro/Venix
. Better (but still not perfect) determination of local vs remote mode
in 'set line'
. User's preferred shell is used for "!" commands, rather than
always sh. (A complete list of Unix/VMS updates is in CKUKER.UPD.)
New Features (since 0.7) for Macintosh:
. A key redefinition package is now provided.
. I/O errors, such as disk full or write protected, now handled better.
. Separate boxes for inbound & outbound packet parameters in protocol
settings dialog. (A complete list of Macintosh updates is in CKMKER.UPD.)
The Macintosh implementation is built using the Stanford University
Medical Center's SUMACC cross development system, which runs on VAX
computers under Unix (or VMS with Eunice). MacKermit fits on a
standard 128K Mac, but just barely. The key configurator is a
separate program, because this additional functionality added to
Kermit itself would not fit into a 128K Mac. The memory restriction
is a problem only because the SUMACC system cannot produce swappable
segments. If someone wants to take the trouble to translate the
Macintosh-specific modules to one of the native Macintosh C
development systems that supports segment loading, then additional
functionality can be added without worrying about exceeding memory.
(If you want to volunteer to do this, please contact us first!)
The VAX/VMS implementation is more an exercise in portability than a
real Kermit implementation. It mostly works, but does not possess the
intimate knowledge of the VMS environment that the Stevens Institute
of Technology Bliss language implementation has. Still, it may be
useful to sites that do not have a Bliss compiler but do have the
VAX-11 C compiler.
Documentation includes a Unix Kermit manual (CKUKER.DOC, Scribe source
CKUKER.MSS), a Macintosh Kermit manual (CKMKER.DOC,.MSS), various help
files (CK*.HLP), program update histories (CK*.UPD), and "beware"
files (CK*.BWR). The Unix and Macintosh manuals are new chapters for
the Kermit User Guide, but the Guide itself has not yet been reissued
to include these chapters; a new revision of the manual will appear
after MS-DOS Kermit 2.28 is announced.
The files are in KER:CK*.*, available from host CU20B via anonymous
FTP on the Internet. Within a few days, they will also be available
from BITnet via KERMSRV at CUVMA. In addition, Macintosh Kermit
diskettes will be sent out to selected sites (Apple University
Consortium schools and a few others; our capacity to reproduce
diskettes is limited, so we can't do mass mailings). And of course,
the new files will be included henceforth on our Kermit distribution
tapes.
The files that had been in <CKERMIT> for testing purposes have been
removed. Thanks to all the folks on the network who participated in
the test and helped to work out the bugs, particularly Dave Tweten
(AMES-NAS), Marco Papa (USC), Dan Schullman (DEC), Lawrence Afrin
(Clemson U), and many others too numerous to mention.
Please report any problems to Info-Kermit@CU20B.
------------------------------
Date: 31 May 85 14:53 PDT
From: Fischer.pa@Xerox.ARPA
Subject: Dynamic binding in C++
C++ has both dynamic or static binding in its calls, depending on
whether the analysis of the code allow it to optimize into a static
binding.
Very neat.
I would like to predict the demise of Objective C if C++ is ever
released.
(ron)
------------------------------
Date: Fri, 31 May 85 12:07:01 EDT
From: Peter DiCamillo <CMSMAINT%BROWNVM.BITNET@WISCVM.ARPA>
Subject: Re: Getting Maze Wars to Run
I've been playing around a little with Maze Wars here, and my
experience suggests that your cable should work fine. Apparently,
when you boot a 128K Mac with a normal complement of fonts and desk
accessories, the AppleTalk init codes decides there is not enough
memory to load the .MPP driver. However, there actually is enough
memory to load .MPP and run Maze Wars. Here's a small Manx assembler
program I wrote to do just that. It opens the .MPP driver, then
chains to the game. I never was able to use Maze Wars with other
players on a 128K Mac until I used this:
PUBLIC _main
_main SUB #50,SP
MOVE.L SP,A0
CLR.B $1B(A0)
LEA MPPName,A1
MOVE.L A1,$12(A0)
CLR.W $16(A0)
DC.W $A000
ADD #50,SP
SUB #6,SP
MOVE.L SP,A0
LEA PGMNAME,A1
MOVE.L A1,0(A0)
CLR.W 4(A0)
DC.W $A9F3
MPPName DC.B 4,'.','M','P','P'
PGMNAME DC.B 9,'M','a','z','e',' ','W','a','r','s'
END
I apologize for the lack of comments, but this is very similar to the
open code in the assembler section of the AppleTalk chapter of Inside
Mac.
Peter
------------------------------
Date: Fri, 31 May 85 13:39:21 EDT
From: Dick Damon <DICK%BROWNVM.BITNET@WISCVM.ARPA>
Subject: Maze Wars
I was struggling with Peter to get Maze Wars to run on a 128k Mac.
After many futile attempts, we succeeded with the program Peter wrote
and included in the previous letter. However, I think it is much
simpler than that. First set up a disk with the new system (including
Imagewriter), and use the most recent AppleTalk Installer you can lay
your hands on (ours is dated 03/05/85). With your cable on the printer
port, use Choose Printer (in the Apple Menu), select Imagewriter,
select "phone" port, select Apple Talk Connected, then click on OK,
and you are home free.
------------------------------
Date: 30 May 85 23:51:15 EDT
From: Kevin.Dowling@CMU-RI-ROVER
Subject: LaserWriter printing
Has anyone tried transparencies on the LaserWriter? I've gotten
results that pretty much darken the entire transparency. The
temperature of the printing process can reach 200F (or C?) and I
suspect that this is higher than a normal thermofax machine.
If anyone has used a particular type or brand of transparency with the
LaserWriter I'd be interested to know about it.
Also In doing the manual feed it always seems to print the "Manual"
page with each copy. Is there a way to avoid this waste?
I'm very pleased with the LaserWriter's capability and the results
I've had so far.
-----
On a separate note is there an easy way to have forms of different
types and make it easy to enter values at different points. I can
easily imagine a program that would allow you to "paint" a form
outline (for a example a purchase order form) using Macpaint and then
define queries that would correspond to entries in the form and enter
them at the appropriate locations on the form.
Obviously you could have a template MacPaint file and then copy it and
go in by hand and enter values. Perhaps MacDraw would be even better
for this kind of approach.
Aka : Kevin Dowling
Bell: (412) 578-8830
Arpa: nivek@cmu-ri-rover
Mail: Robotics Institute
Schenley Park
Pgh, PA 15213
------------------------------
Date: Sat 20 Apr 85 09:06:37-PST
From: John Mark Agosta <INFO-MAC-REQUEST@SUMEX-AIM.ARPA>
Subject: [cperry@mitre (Chris Perry): LISA/Mac documents, etc.]
Return-Path: <cperry@mitre> Received: from mitre.ARPA by
SUMEX-AIM.ARPA with TCP; Fri 19 Apr 85 14:55:58-PST Received: by
mitre.ARPA (4.12/4.7)
id AA14018; Fri, 19 Apr 85 17:55:31 est Date: Fri, 19 Apr 85
17:55:31 est From: cperry@mitre (Chris Perry) Message-Id:
<8504192255.AA14018@mitre.ARPA> To: info-mac-request@sumex-aim
Subject: LISA/Mac documents, etc. Cc: e@mitre
Hello. I'm passing on a note from one of our local ARPANET-less Mac
users...
if anyone has, knows of, or is working on a utility to convert MAC documents
to LISA? Also if anyone knows about Compugraphic 8400 print driver for the
MAC? I know about APPLE'S utility to convert LISA to MAC, but that will not
help me with COMPUGRAPHIC'S typesetting program.
Thanks in advance.
Chris Perry (cperry@mitre.arpa)
------------------------------
End of INFO-MAC Digest
**********************