[comp.protocols.appletalk] MacTCP problems and solutions.

veizades@apple.com (John Veizades) (03/16/90)

This is a response to several messages all dealing with problems with 
MacTCP that have been exhibited by several third party applications.  This 
is also a message announcing the availability of an updated version of 
MacTCP (MacTCP 1.0.1).  This release will be sent to all licensed users of 
MacTCP 1.0 (These are individuals and organizations who have directly 
licensed MacTCP from APDA or Apple Software licensing, these are not 
individuals or companies who have received MacTCP with a third party 
developer product, talk to your vendor).

Remember that single user evalution kits are available through APDA as 
well as a HyperCard MacTCP toolkit complete with X-CMDS and an NNTP stack.

Individuals who have had problems with mail gateways and the domain name 
system should take notice of item 6 specifically.

Questions and comments to:

John Veizades...
veizades@apple.com

--------------------------------
Release Notes

This release is intended to correct several software problems found in the 
1.0 version of this product.  The bug fixes are as follows:

1. In BootP, DNS information found in the vendor-extensions area were not
handled properly by MacTCP and caused the machine to crash.

2. A TCP MSS of 586 was advertised across DDP to IP gateways; this value 
is now 576.

3. When determining whether a packet should be sent to the broadcast 
address, all packets are sent to the broadcast address on class C 
networks.  This has been corrected. 

4. MacTCP 1.0 ignored DDP-IP gateways when the reported gateway address 
appeared to be on a foreign subnet.  Since this is a common problem with DDP-IP gateways, MacTCP 1.0.1 is less rigorous in filtering this information.

5. Various problems that arose when attempting to communicate
LocalTalk-to-LocalTalk on a network without a DDP-IP gateway have been
corrected.

6. The values entered in the Control Panel for domain name servers were 
timed out by the DNR (Domain Name Resolver) and disappeared from the cache 
after one week.  These values are now kept indefinitely.

7. On machines supporting the Slot Manager (SE/30, Mac II-class), MacTCP 
1.0 would only look for Ethernet drivers in slot space; Ethernet drivers that use the SCSI device were not found.  This has been changed so that if no slot
manager-based Ethernet drivers are found, MacTCP 1.0.1 attempts to opens the   .ENET0 driver.

8. When sending fragments on Ethernet an ARP packet was sent out for every 
fragment of the first packet.  Now an ARP packet is sent if there is no 
outstanding ARP request for the host in question.

9. When fragments are being sent off net, they were fragmented using the 
local net MTU; they are now fragmented using the off-net MTU of 576.
 
In addition to the machines supported by MacTCP 1.0, MacTCP 1.0.1 has been
tested for operation on Mac IIcx, Mac IIci and the Portable.  When using 
MacTCP on the Portable, it is important that the user not put the machine into its "sleep" mode while using a MacTCP application.  In sleep mode, the machine
loses communication with the DDP-IP gateway and must be restarted to regain
contact with the DDP-IP gateway.  Operation when a MacTCP application is 
not in use is not effected.

rickf@Apple.COM (Rick Fleischman) (03/16/90)

In article <7218@goofy.Apple.COM> veizades@apple.com (John Veizades) writes:
>This is a response to several messages all dealing with problems with 
>MacTCP that have been exhibited by several third party applications.  This 
>is also a message announcing the availability of an updated version of 
>MacTCP (MacTCP 1.0.1).  This release will be sent to all licensed users of 
>MacTCP 1.0 (These are individuals and organizations who have directly 
>licensed MacTCP from APDA or Apple Software licensing, these are not 
>individuals or companies who have received MacTCP with a third party 
>developer product, talk to your vendor).
>
>Remember that single user evalution kits are available through APDA as 
>well as a HyperCard MacTCP toolkit complete with X-CMDS and an NNTP stack.
>

The above message about MacTCP v.1.0.1 being available is a bit
premature.  At this point, we don't yet have the master disks to start
producing the product.  I would estimate that we will start shipping
MacTCP v.1.0.1 through APDA in approximately 2-3 weeks.  However, I would
estimate that we will start taking orders for MacTCP v.1.0.1 as early as next
week.

As was stated above, anyone who has a MacTCP license (through Software
Licensing) or has purchased a MacTCP Evaluation Kit (through APDA) will
automatically receive an update to the new version.  There is no need
to call to receive this update.  It will be sent out automatically.  I would
estimate that these updates will also be sent out in approximately 2-3 weeks.

Please feel free to e-mail me directly if there are any questions.

For information about APDA or to order APDA products, call:
(800) 282-2732 (in the U.S.)
(800) 637-0029 (in Canada)
(408) 562-3910 (elsewhere) 
or via e-mail at: APDA@applelink.apple.com

Sorry for any confusion this may have caused.

Rick Fleischman
Developer Channels/APDA
Apple Computer, Inc.
e-mail:  rickf@apple.com
AppleLink:  FLEISCHMAN@applelink.apple.com