MacX25: Problem Reports and Enhancement Request

We've noted the following problems with MacX25:

1) To use MacPAD, MacTerminal needs more than 512K of RAM free.

2) If you have a session open, and have disabled the PAD command mode, typing a Control-P seems to indicate that your session is closed, yet the MacPAD status still shows you as connected. Nothing could be found that would let the session be re-used again without doing an Open Connection.

3) MacX25 apparently cannot insert a calling address. At least, we can't find any option for this setting. We had to patch our network to make this work, as we validate the calling nua before the call is directed to its destination. We need the ability to trace a call for accounting purposes and for troubleshooting problems.

Its implementation should be based on the user ID and assigning each user an nua or sub-address (i.e., unique address). The sub-address would be easier to maintain, because the administrator would have to type only two digits instead of the whole nua. When using the sub-address scheme, the server would be assigned an nua like 10498001%%, where %% is replaced by the sub-address from the user ID.

4) MacTerminal seems to hang quite frequently, at least on a Macintosh IIci, when trying to change the PAD command mode while a connection is open (actually a "stuck" connection as described in question 2).

5) The installation of MacTerminal puts an INIT in the System file that seems incompatible with other INITs, namely with INITPicker (when using override). This INIT should be a separate file from the System file, so the user can control when and if the INIT should run.
1) The minimum suggested memory size for MacPAD (MacTerminal or CommToolBox) is 1MB, though 2MB is recommended. The MultiFinder "Suggested Memory Size" is 560K for MacTerminal itself.

2) Questions 2 and 4 are related:

The "MacX25 User's Manual" (page 110) suggests you can go into the PAD command mode by entering Control-P. That means if you checked "enabled PAD command mode" (see "Connection Settings" on page 97), you can escape from data transfer (page 99), then enter any of your CCITT PAD commands from the keyboard. When you have checked "enabled MacPAD command mode", you can "escape" into MacPAD command mode by entering Control-P or by choosing Command Mode from the MacPAD menu.

However, if you have NOT checked "enable MacPAD command mode", you cannot enter a PAD command mode with the Escape key sequence or menu to escape to data transfer mode after starting a session. The host will interpret anything you enter through the keyboard as data. If you try to escape to command mode with a Control-P (Command Mode in the MacPAD menu is not available), the system may appear to hang. If you check Status in the MacPAD menu, it will show that you still have a live session. If you are patient, some hosts will time out (the ones we tested did so after 1 minute) and resume the data transfer.

During this time, the session menu gives you the option to open a connection, but doing so will hang your system. If your host never times you out, we recommend you quit MacTerminal, reboot, and restart your session.

3) We passed this enhancement request along. Thanks.

4) See the second item above.

5) We haven't had any conflicts with INITPicker 2.0 (or other INITs) and the INIT that the Communications Toolbox installs into the System file. We have used this combination on various systems including a Macintosh Portable, Macintosh IIci, Macintosh IIcx, and Macintosh IIx, running various versions of System Software including 6.0.4, 6.0.5, and 6.0.7. It is true, however, that INITPicker 2.0 cannot control the state of the INIT when it is installed in the System Folder. However, it is one less variable a user must monitor to conduct a successful communication session.
Published Date: Feb 18, 2012