doon@sdcsma.UUCP (Harry Reed) (08/15/85)
To all netlanders: A friend of mine recently purchased a IBM PC/XT (running under PC-DOS) and the Crosstalk XVI communications/terminal package. He is also running 256K of main memory and dual 5 1/4 inch drives. However, he can't seem to get Crosstalk to work. He can save the com files ok (with the info on the type of terminal, function key settings, ...etc) but when he types this: A> XTALK <filename> (where <filename> is the com file) ...the machine seems to load in the file, then it displays a blank screen with the status line on the bottom. This is where it gets screwy. After this the machine refuses to dial the modem. He has checked and verified that Cross- talk is set up and should be talking to a Hayes 1200 baud Smartmodem (external) which is the type of modem he is using. His question, and mine too, is does Crosstalk automatically dial the modem? I am sure that this is the plan but cannot convince Crosstalk of this. However, he can dial the modem manually but not through Crosstalk. If anyone has any insight please let me know. Since I am not a IBM-PC guru I could use some help on this one. Thanx in advance. -- doon
mikem@tekcae.UUCP (Michael E. Meyer) (08/17/85)
When using a smart modem you need to type "go local" after getting the xtalk attention line. Also, when I use it I just type "xtalk" and have xxx.xtk files set up to choose from depending on which system I want to dial. Michael E. Meyer ________________________________________ USENET: ...!tektronix!tekcae!mikem ARPA: tekcae!mikem.tek@CSNET-RELAY USnail: TEKTRONIX, Inc. P.O. Box 500, MS 19-075 Beaverton, OR 97077 USA (503) 627-2628
W8SDZ@SIMTEL20.ARPA (Keith Petersen) (08/18/85)
Harry, are you SURE that this is the correct syntax? A> XTALK <filename> (where <filename> is the com file) Most modem programs should be executed with no arguement and then the correct option for dialing, terminal mode, transfer mode, etc., is selected from the program's command line. --Keith
mlsmith@NADC.ARPA (08/19/85)
We never use a file on the command line. The typical session is as follows: 1. Type "xtalk". 2. Main Title appears. 3. Clever quip is shown at bottom of screen. 4. Screen Clears and Menu of files is printed with call numbers. 5. Type "2" to call "Capture" file 6. (Here is where the Hayes should dial) Since we are connected to a Net,we get a message "... Already connected". 7. Respond to whatever you are talking to in the normal way. 8. When done call the command line to "quit". 9. Get DOS prompt.
ncahec@ecsvax.UUCP (Jim Gogan) (08/19/85)
Unfortunately, Crosstalk is one of those communications packages that
requires you to change the default settings on the configuration
switches inside the Hayes Smartmodem 1200 (external model). I love
Crosstalk and use it regularly, but that aspect is a real pain when you
need to evaluate and test out other communications packages as well.
The first thing you need to do is to pry open the black plastic cover
around the front of the modem (where the lights are). Just use a small
screwdriver or something with a small enough edge to fit under the
plastic guard on the side. The following table shows, for each switch,
the default Hayes factory setting and the proper setting for operating
Crosstalk:
FACTORY CROSSTALK
SWITCH SETTING SETTING
1 DOWN UP
2 UP UP (NOT USED BY XTALK)
3 DOWN DOWN (NOT USED BY XTALK)
4 UP DOWN
5 DOWN UP (IF YOU WANT AUTO-ANSWER)
6 DOWN UP
7 UP UP (FOR RJ-11 JACK, DOWN FOR RJ-12)
8 DOWN DOWN
After you've changed the settings, turn on the modem, start up XTALK and
you should (eventually) see the prompt "ENTER NUMBER FOR FILE TO USE:"
on the bottom line of your screen. Enter the number for the file
"NEWUSER", and answer the questions with responses appropriate for the
system to which you wish to connect. One of those questions asks you
for the phone number - Crosstalk will dial it for you.
--
Jim Gogan
N.C. AHEC Program
UNC-CH School of Medicine
Chapel Hill, NC 27514
919-966-2461
...!{decvax,akgua}!mcnc!ecsvax!ncaheclaj@wnuxb.UUCP (JOHNSON) (09/03/85)
In the few articles posted describing various problems with Crosstalk XVI I expected to see described the problem which plagues me in using the product. Since no one mentioned it, I am led to believe that there is an easy fix which I`m overlooking. I am running Crosstalk XVI 3.41 under MSDOS 2.1 on an IBM PC. I have found that when I'm connected to a UNIX host and issue a "break", I do not receive the expected UNIX prompt string. I hassled with Micro Stuff until I got determination of the problem and a patch. For reasons which are not clear to me, Crosstalk disables interrupts from the UART by resetting the interrupt enable register for the duration of the break. Perhaps, this is to allow them to time the break signal more accurately. In any event, interrupts are still disabled when the host, recognizing the break, sends the prompt string back. All characters except the last are lost. The patch for 3.41 nullified the manipulation of the interrupt enable register and Crosstalk worked just fine. I assumed that this was a bug which Micro Stuff would address in the next release. However, I just got release 3.5 and the bug persists. I hate to keep requesting a patch for this product. Has anyone else seen this symptom and found a convenient work-around ? -- Larry Johnson Western ElectricAT&T TechnologiesInformation Systems ihnp4!wnuxa!laj ihnp4!wnuxb!laj
STERNLIGHT@USC-ECL.ARPA (STERNLIGHT) (09/07/85)
I, too, have had experience with Microstuf that suggests that they are
less than customer-aware when anomalies occur in Crosstalk XVI. For the
longest time there has been a bug in their XMODEM protocol for receiving
files, which causes the system to hang in the middle of a transfer under some
(unknown) circumstances. Several phone calls to them, and several versions
have not cured the bug, which is notorious enough for someone to have
posted an XMODEM program to some bulletin boards for the specific purpose
of leaving Crosstalk, downloading, and returning to Crosstalk. Since I
find this unacceptable, I have abandoned my investment and use ACSII PRO,
an outstanding communications program written by Bill Blue for United
Software. I am particularly dissatisfied with the conversations with
Microstuf, in which they tried to blame their problems on everyone but
their inadequate code. ("Well, there's no standard XMODEM protocol."
ME:"Why do the following six communications programs have no problem?"
"Well we can't get information about the protocol." ME:"Try calling
..... (I supplied a list of several experts who have written various
programs like MEX, MODEM, etc.)"
--david--
-------W8SDZ@SIMTEL20.ARPA (Keith Petersen) (09/09/85)
Someone should give Microstuf a copy of:
Filename Type Bytes CRC
SIMTEL20 directory MICRO:<CPM.MODEM2>
XYMODEM.DOC.1 ASCII 43645 8113H
which clearly defines the protocol used by XMODEM, MODEM7, YAM, MEX,
etc.
--Keith Petersen
Arpa: W8SDZ@SIMTEL20.ARPA
uucp: ...!seismo!SIMTEL20.ARPA!W8SDZ
uucp: ...!{decvax,unc,hao,cbosgd,seismo,aplvax,uci}!brl-bmd!w8sdz
uucp: ...!{ihnp4!cbosgd,cmcl2!esquire}!brl-bmd!w8sdz