Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!sunybcs!sbcs!sblw!vallon
From: vallon@sblw.CS.SunySB.EDU (Justin Vallon)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Communications Toolbox questions
Message-ID: <4183@sbcs.sunysb.edu>
Date: 6 Dec 89 23:21:30 GMT
References: <4179@sbcs.sunysb.edu> <9125@hoptoad.uucp> <36869@apple.Apple.COM> <9194@hoptoad.uucp> <TIME.89Dec5172829@oxtrap.oxtrap.UUCP>
Sender: news@sbcs.sunysb.edu
Reply-To: vallon@sblw.CS.SunySB.EDU (Justin Vallon)
Lines: 21

In article <4179@sbcs.sunysb.edu>, vallon@sbcs.sunysb.edu (Justin
Vallon) writes:
> [Stuff about 'Comm' INIT files ]

> Two points:
> 
> 1)  That would mean that you would have to modify all current INIT 31's
>     before running the Comm Toolbox.
> 
> 2)  Why not use the 'Comm' file-type.  It is easy, prevents pointless
>     execution of Comm INITs without Toolbox installed, and doesn't have
>     to change anything that currently exists.

I'd like to be the first to correct myself.  I hadn't read the point that
the Comm file type had been tried, and it was (a) significantly slower,
and (b) it required that the Toolbox init be left open :-(.

Oh well.

-Justin
vallon@sbcs.sunysb.edu