Q:  I am a new subscriber and have been trying to use the link function. I 
have a Universal Date Systems 9600 V.32 modem.
     I keep getting an abort with this modem and a message saying can't get 
a carrier.  I have tried various initialization strings and different transfer 
rates from 300 to 9600 Baud.
     Yet when I hook up my old apple Personal Modem (at 1200 Baud, I can 
get through. Can you explain why this happens.  I have been successful 
with Compuserve, Genie, and DUAT but unsuccessful with you and one 
other bulletin board. Why does the apple modem work and not my UDS?
-- Ronald J. LaVallee, Gardiner, ME, USA

Q:  I can not believe that the solution was so simple. I sent a link using my 
old Hayes 1200 and everything went well, so I knew the problem was still 
with the ZOOM V.42. As an experiment, I used Smartcom II (a 
communications package for the Mac) and the ZOOM to link with Nautlius. I 
entered the init string that ZOOM gave me into the init string box of the 
Smartcom II software. The init string box has "AT" at the beginning, so it is 
not necessary to enter "AT" - the software automatically sends the "AT" 
attention command. It hit me that the Nautilus software does the same 
thing - the "AT" command is automatically sent before whatever is typed 
into the init string box. What threw me off was a suggestion by one of your 
subscribers to enter "AT&&F\N1". This well might work, but you should 
not enter the "AT" part first - the program does this for you. The bottom 
line is:
     1) you must turn off the error checking and compression before linking 
to Nautilus and, 
     2) for the ZOOM v.42 modem, ZOOM suggests using AT\N0&K4N0 - 
which should "nuke" everything  including compression and error 
checking. Apparently this init string is a little too severe. I used a less 
severe init string mentioned in the ZOOM manual "AT\N0S37=6N0". This 
string assures a link at 2400 baud with no compression or error checking. 
The string for a 1200 baud link would be "AT\N0S37=5N0".
     Remember, do not put the "AT" part into the init string box of the 
comm. setup. You must use the proper backslash and a zero not an "O". 
     Just a couple more comments. It was not enough to just change the init 
string - after any changes, restart the Nautilus shell and turn the modem 
off and on (to clear the registers). I would suggest that you place "AT" 
before the init string box in the comm. setup window so that people will 
know not to duplicate that part.
     I hope this information will help other users. A "simple" problem can 
often take days to solve and be very frustrating, however, I know more 
than I care to about AT commands and init strings. Playing with the 
modem in terminal mode is very educational. Thanks for bearing with me.
-- Rick

P.S. It is a good idea to put "*70" at the beginning of the telephone number 
to turn off call waiting.
-- Frederick H. Leonhardt, Albuquerque, NM, USA

N:  For Ron and any other subscribers who have had difficulties Linking to 
NAUTILUS, Rick's efforts were so determined, and his comments so much 
"on the mark" that we included his entire message.  
The bottom line is: 
1)  If you have a modem that uses error checking or compression, you will 
need to turn these features off.  Check your modem's manual for 
information on the proper commands to use.
2)  If you change the default Modem Init String (using the Comm Setup 
dialog box) do NOT use the "AT" prefix.  The NAUTILUS Link will 
automatically include the AT command with whatever else you enter into 
the Modem Init String field.
3)  After making changes, turn the modem off and back on, and restart the 
Shell.
And note that Rick's postscript about call waiting is also good:  put "*70" at 
the beginning of the telephone number to turn off this feature.