[comp.sys.mac.comm] CommToolBox

dubuc@IRO.UMontreal.CA (Martin Dubuc) (08/09/90)

It has been more than a year that the CTB is out. I do not understand
why there is so little software that uses it. I suspect that there are
still some problems with the CTB, or it is too difficult to cope with it
unless all the major softwares (White Knight, MicroPhone, NCSA Telnet,
ZTerm, etc...) would be CTB compatible. By now the only product that I know 
which uses the CTB is VersaTerm, but I didn't see it run. I would like to
have your impressions about it. I am particularly concerned since I am myself 
hesitating to integrate the CTB in MultiXfer.

   Martin Dubuc                     Local S-242, Pavillon Principal
   dubuc@IRO.UMontreal.CA           Universite de Montreal
   Tel.: (514) 343-6111, poste 3507

"Qui a dit que rien ne pouvait arreter le progres?" -- un bureaucrate

gshapiro@wpi.wpi.edu (Gregory Neil Shapiro) (08/09/90)

Doe anyone know where to find the Tools for the Toolbox?  And has
anyone written one for Zmodem yet?

						Greg

 ____________________________________________________________________________
 Gregory Neil Shapiro                                    Gregory Neil Shapiro
 gshapiro@wpi.wpi.edu (130.215.24.1)          Worcester Polytechnic Institute
 husc6!m2c!wpi!gshapiro                          100 Institute Road, Box 1397
 America Online/GEnie: GShapiro                Worcester, Massachusetts 01609
 ____________________________________________________________________________

austing@Apple.COM (Glenn L. Austin) (08/09/90)

dubuc@IRO.UMontreal.CA (Martin Dubuc) writes:

>It has been more than a year that the CTB is out. I do not understand
>why there is so little software that uses it. I suspect that there are
>still some problems with the CTB, or it is too difficult to cope with it
>unless all the major softwares (White Knight, MicroPhone, NCSA Telnet,
>ZTerm, etc...) would be CTB compatible. By now the only product that I know 
>which uses the CTB is VersaTerm, but I didn't see it run. I would like to
>have your impressions about it. I am particularly concerned since I am myself 
>hesitating to integrate the CTB in MultiXfer.

The main problem is that it requires a MAJOR change in most of the commercial
software source code.  It's actually easier to write for (just ask Lonnie)!

As for your hesitation, CTB solves some MAJOR problems with the Mac
serial drivers, and allows your app to be more useful in more environments
rather than just over serial data lines.

-- 
-----------------------------------------------------------------------------
| Glenn L. Austin               | "Turn too soon, run out of room,          | 
| Auto Racing Enthusiast and    |   Turn too late, much better fate"        |
| Communications Toolbox Hacker |   - Jim Russell Racing School Instructors |
| Apple Computer, Inc.          | "Drive slower, race faster" - D. Waltrip  | 
| Internet:   austing@apple.com |-------------------------------------------|
| AppleLink:  AUSTIN.GLENN      | All opinions stated above are mine --     |
| Bellnet:    (408) 974-0876    |                who else would want them?  |
-----------------------------------------------------------------------------

APPLEREP@MTUS5.BITNET (08/09/90)

The Communication Toolbox has been announced for quite a while, but it did
not actually ship until (I think) this spring.  (I'd use my newly aquired
On Location to do a look-up on Press Releases saved from AppleLink, but I
read my news on a high speed dumb terminal down the hall.)  One other
package that supports the Comm Toolbox is MacTerminal 3.0.  As the number
of devices that want your serial port multiply, I am thinking about picking
up a serial port card.  I sure hope using the Comm toolbox becomes popular.

BTW, On Location is great! (Except for the funky scroll bars, but I nit-pick.)
Highly recommended for any Student Rep, or anyone who works in the information
or consulting area.  All I need now is a huge hard drive to keep all of my
information on, as I now have a tool to actually utilize it with.  Thank you
Mitch!

Tom Amberg
Apple Student Rep
Michigan Technological University
(way, way up in the Great White North, where gas has ALWAYS been expensive!)
Standard Disclaimers Apply (hey, I'm not even officially employed by Apple :( )

es2j+@andrew.cmu.edu (Edward John Sabol) (08/10/90)

>I am particularly concerned since I am myself hesitating to integrate the CTB
>in MultiXfer.

CTB will be built in System 7.0, so eventually *everyone* will use it. When
Microphone and White Knight go through their next upgrade, they'd be extremely
foolish not to implement CTB.

I've only used MultiXfer twice, but I think you should do it. I personally
would prefer any program that did support CTB. Hopefully, people will write
more CTB tools and put them out as either freeware or shareware. I would *die*
for a freeware CTB tool for TCP/IP implementing telnet, finger, and ftp. There
is a company that makes one, but they charge mucho bucks for it (more than I
think it is worth, IMHO). Correct me if I'm wrong, but I believe Hermes (the
BBS software) also uses CTB. MacTerminal 3.0 also supports this. But I've yet
to see anyone outside of Apple that has this program.

+-------------------------------+---------------------------------------+
| Edward J. Sabol               | Arpa:   es2j+@andrew.cmu.edu          |
| Carnegie Mellon University    | Bitnet: R746ES2J@CMCCVB               |
+-------------------------------+---------------------------------------+
| "The streets that Balboa walked were his own private ocean and Balboa |
| was drowning." - August Wilson                                        |
+-------------------------------+---------------------------------------+

macman@wpi.wpi.edu (Chris Silverberg) (08/13/90)

In article <EakOtmK00Vo94aPOdf@andrew.cmu.edu> es2j+@andrew.cmu.edu (Edward John Sabol) writes:
>CTB will be built in System 7.0, so eventually *everyone* will use it. When
>Microphone and White Knight go through their next upgrade, they'd be extremely
>foolish not to implement CTB.

I saw Microphone at the expo. Leonard was previewing a future version of
Microphone that used the Comm Toolbox. I dont think it used it completely, but
I'm certainly not the one for information regarding this.

From what some developers have told me, alot of the Comm Toolbox is redundant.
It's not worth it for developers to use the Comm Toolbox if they already have
these tools working perfectly within their app...

On a side note, with the special price to upgrade to Microphone for $99,
I'm very close to writing a check... I just don't want to bounce it just
yet :-)



 
 ._._._._._._._._._._._._._._._._._._.._._._._._._._._._._._._._._._._._._._.
   Chris Silverberg                     AOL:   Silverberg
   Worcester Polytechnic Institute      GEnie: C.Silverberg
   INTERNET: macman@wpi.wpi.edu         SYSOP: Main Street U.S.A. BBS
   FIDONET:  322/575.1                         508.832.7725  (1200/2400)

paul@taniwha.UUCP (Paul Campbell) (08/13/90)

In article <43776@apple.Apple.COM> austing@Apple.COM (Glenn L. Austin) writes:
>dubuc@IRO.UMontreal.CA (Martin Dubuc) writes:
>
>>It has been more than a year that the CTB is out. I do not understand
>>why there is so little software that uses it. I suspect that there are
>>still some problems with the CTB, or it is too difficult to cope with it
>>unless all the major softwares (White Knight, MicroPhone, NCSA Telnet,
>>ZTerm, etc...) would be CTB compatible. By now the only product that I know 
>>which uses the CTB is VersaTerm, but I didn't see it run. I would like to
>>have your impressions about it. I am particularly concerned since I am myself 
>>hesitating to integrate the CTB in MultiXfer.
>
>The main problem is that it requires a MAJOR change in most of the commercial
>software source code.  It's actually easier to write for (just ask Lonnie)!
>
>As for your hesitation, CTB solves some MAJOR problems with the Mac
>serial drivers, and allows your app to be more useful in more environments
>rather than just over serial data lines.

My impressions are that most serial applications are changing bit by bit.
Some stuff is easy to do (for example use the CRM to find extra serial
ports and support them - adding this code takes about 1/2 an hour -
but since it gives you names and icons for all the ports in the system 
(and their associated serial driver's names) you may have to change your
interface to allow scrolling lists of ports).

You can then add the other managers one by one - some people I've seen
have dropped in the File Transfer stuff first, others the Connection Manager.
However if you are doing the whole thing at once you are probably looking at a
major rewrite (Apple give away a sample application which makes a good base)
People who nave big applications, scripting languages, features that don't
fit well with CTB etc etc may take much longer.


	Paul Campbell
	Taniwha Systems

-- 
Paul Campbell    UUCP: ..!mtxinu!taniwha!paul     AppleLink: CAMPBELL.P
What most people don't realize is that those plastic cover slips that your 3
inch floppies come in are actually condoms for protecting your computer from
harmfull computer viruses - practice safe computing ..... :-)

wwg2101@venus.tamu.edu (Backlash) (02/22/91)

Could someone please tell me where I can get a copy of the Apple Communications
Toolbox. I would like to implement it in the program that I am writing and 
the people here on campus are extremely clueless.

Ackoofgagbarfandpuke. 

KJSTEELE@MTUS5.BITNET (03/21/91)

  Can anyone tell me where I can FTP a copy of the comm toolbox?  I need it
 fot the newest version of Hermes.  Thanks

Kevin J Steele
(KJSTEELE@MTUs5.bitnet)

terryn@prcrs.prc.com (Terry Neely) (05/22/91)

	I am writing a Terminal Tool with the CommToolBox under System 6.0.x>
Are there any ftp-able samples that actually work with source laying around?
I have the CTB, tools, and sample source, but I would like to make sure I 
have covered everything.  There seem to be bugs in the Surfer example source
(ie Hlocks/Hunlocks), and the sample tool source uses hgetstate/hlock then
hsetstate but not hunlock.  Is this a recommended way to handle memory?

	Thanks 

	Terry Neely										PRC Realty Systems
	..uunet!prcrs!terryn                            703-556-2056
	

aoki@husc9.harvard.edu (Edwin Aoki) (05/23/91)

In article <1983@prcrs.prc.com> terryn@prcrs.prc.com (Terry Neely) writes:
>
>	I am writing a Terminal Tool with the CommToolBox under System 6.0.x>
>Are there any ftp-able samples that actually work with source laying around?
>I have the CTB, tools, and sample source, but I would like to make sure I 
>have covered everything.  There seem to be bugs in the Surfer example source
>(ie Hlocks/Hunlocks), and the sample tool source uses hgetstate/hlock then
>hsetstate but not hunlock.  Is this a recommended way to handle memory?

As for the Hlock/Hunlock story, it goes something like this: If a block of
memory was locked by another function (say, the caller), and you lock it in
your piece of code and then subsequently unlock it, the caller's lock is
invalidated as well.  More succintly, Hlock/Hunlock is not nestable.  Your
HUnlock at the end of your tool not only unlocks your previous Hlock but any
previous Hlock that had been performed before the entrance to your tool.
Thus, when using memory that you don't have complete control over (i.e., 
writing a tool or a driver or something like that), you use HGetState to
get the previous settings of the lock bit, lock your handle, do whatever you
want, and then just use HSetState with the previous setting to restore the
state to exactly what it was before.  Because the lock bit is one of these
bits that's stored in HGetState, the HUnlock is not necessary.

I'd love to see the tool when you're done.  Good luck.

-Edwin Aoki
(aoki@husc9.harvard.edu)

glenn@gla-aux.uucp (Glenn Austin) (05/28/91)

In article <1983@prcrs.prc.com>, terryn@prcrs.prc.com (Terry Neely) writes:
> have covered everything.  There seem to be bugs in the Surfer example source
> (ie Hlocks/Hunlocks), and the sample tool source uses hgetstate/hlock then
> hsetstate but not hunlock.  Is this a recommended way to handle memory?

Yes.  The HGetState gets the current state of the handle.  You can then
do pretty much what you wish to do with the handle, then restore the handle
flags with HSetState.  This is introduced with the 128K ROMs, and is (IMHO)
a MUCH better way of dealing with handles.

===============================================================================
| Glenn L. Austin                | "Turn too soon, run out of room.           |
| Macintosh Wizard and           |    Turn too late, much better fate."       |
| Auto Racing Driver             |   -- Jim Russell Racing School Instructors |
|-----------------------------------------------------------------------------|
| Usenet:  glenn@gla-aux.uucp         | CI$:       76354,1434                 |
| GENie:   G.AUSTIN3                  | AOnline:   GAustin                    |
===============================================================================