AppleShare PC's only limit with respect to the number of zones it can work
with involves the memory available in its memory pool when DA is run. This
only affects making network connections using DA, and has no effect once
those connections are made. Even then, the connections could still be made
using manual ANET commands, even with thousands of zones. We use default
installations of AppleShare PC here at Apple, where there are over 140
zones, and have no trouble using DA to make connections.
Problems can occur if the AppleShare PC memory pool is almost full. This is
the memory that AppleShare PC allocates at startup and is configurable by
changing the MEMPOOL setting in the NET.CFG file. If you are experiencing
the "Not Enough Memory" message, increase this number by 1 or 2K and the
problem should be eliminated. Because the NET.CFG file is read when
AppleShare PC loads, the user must edit the file and then reboot the PC
before the change can take effect.
Current versions of AppleShare PC actually require Phase 2 networks. This
is frequently a problem when people upgrade from an old version (pre 2.0)
and haven't upgraded all their services to be Phase-2-compliant. The
AppleShare PC node cannot see Phase 1 services like AppleShare File servers
running EtherTalk 1.x.