Trouble Shooting Guide
----------------------
	This guide lists a number of possible questions or problems you may
encounter while using ACCESS, followed by a few lines describing possible
reasons for the observed symptom or suggestions for changes.
	This guide is provided on the disk rather than in the printed manual
so that it may be updated frequently as we receive feed-back from users.


* Can not see what is typed on keyboard.
	- May be that ACCESS is set for full duplex transmission but you
	  are not connected to any active remote system. In full duplex, you
	  see only what is received from the remote system. You see the letters
	  you type only if remote system echos them. 

* Lines appear double-spaced on screen.
	- The option to add a line-feed (LF) to all carriage-returns (CR) has
	  been set to YES on the Set Save menu and line-feeds are already
	  contained in the incoming data.

* All data received from remote system looks like garbage.
	- Most likely cause is mismatched protocol settings, particularly
	  mismatched bit rates. Could also be problem with remote system or
	  extremely noisy phone line.

* When receiving data at speeds greater than 1200, things look OK for a few
  screens, then become badly garbled.
	- Input buffer is filling faster than the program can process it and
	  either no handshaking system has been provided to slow the remote 
	  system down, or it is not working. Try increasing the size of the
	  remote input buffer and establishing either hardware or software 
	  handshaking.

* Occasional extraneous characters show up on screen.
	- There are several possible causes. When a modem (or other device
	  connected to the port) is turned on or off, some extraneous 
	  characters may be received. Static and noise on the phone line may
	  show up as extra characters received. The remote system may be
	  sending control characters for some type of terminal other than a
	  Heath/Zenith (or FOR a Heath/Zenith with while plaintext mode is on.)

* Control sequences (cursor positioning, clear screen, etc.) intended for a 
  Heath/Zenith terminal or computer are not carried out.
	- Plaintext mode is on (see page 30 in the manual).

* Every time a key is typed, it shows up twice on the display.
	- ACCESS is set for half duplex and remote system is also echoing 
	  keyboard characters.

* Received data is readable but full of errors, error count on Help Menu is
  very high.
	- Could be a mismatch in bits per character or stop bits on Protocol
	  Setup Menu or noisy phone line.

* During terminal mode, as soon as a key is hit, an avalanche of garbage data 
  is received.
	- This usually happens when both ACCESS and the remote system are
	  trying to echo at the same time. Only one end of a communication
	  link can be echoing. (See pages 28-29 in the manual.)

* During terminal mode, lines of text print over and over on top of each other.
	- The remote system is ending lines with only a carriage return rather
	  than a carriage return/line feed combination.  Turn on 'Add LF to CR'
	  on the Set Save menu.

* Approximately half the characters sent to remote are ignored or echoed as
  question marks.
	- Mismatch in parity type between ACCESS's settings and data received.

* The Characters '^S^Q' are echoed occasionally from remote -- particularly
  from bulletin board systems.
	- The ^S and ^Q codes are XOFF and XON codes sent by ACCESS. Some
	  systems, CP/M in particular, do not acknowledge XOFF/XON while in
	  command mode -- only while actually sending data.

* When sending a file in text mode, one line is sent, then no more.
	- If the SEND label on the status line does not stay in reverse video,
	  either the file contained only one line, or the option to send one
	  line at a time has been set in the Set Send menu.  I the SEND label
	  remains in reverse video, it may be that a character to wait for at
	  line ends has been set in the Set Send menu and it is not being 
	  received. If the remote system is not echoing characters back to you,
	  the character to wait for MUST be set to zero.

* When sending a file in text mode, transfer starts all right but eventually 
  becomes garbled.
	- Data is being sent to remote system faster than it can handle it.
	  Several of the options on the Set Send menu can be tried: waiting
	  for a carriage return at the end of lines to stay in synch with the
	  echo; a fixed delay can be inserted after every character or line
	  (or both). If remote system can send XON/XOFF codes to control speed,
	  ACCESS can be set to respond to it; etc. Don't be afraid to 
	  experiment with the settings on the Set Send Menu.

* While saving a file in text mode, a few characters are missed every so often.
	- When ACCESS writes a buffer full of received data to the disk drive,
	  it attempts to stop the incoming flow of data using whatever type
	  of handshaking you have specified. If the remote system continues
	  transmitting, however, ACCESS may lose a character or two during
	  disk activity.

* When the FF key is pressed, a formfeed is not sent immediately to printer.
	- Form feeds are placed in the printer buffer at the end of any
	  data already waiting to be printed -- they are not necessarily 
	  passed on to the printer immediately.

* Long pauses occur during data reception while printing.
	- ACCESS buffers data to be sent to the printer. If the printer buffer
	  nears its capacity, ACCESS will attempt to use whatever handshaking
	  method you have defined to halt the flow of incoming data until
	  the printer buffer is emptied.

* Data missing from printed copy.
	- If the printer buffer fills while data is being received, ACCESS
	  will attempt to halt the flow of incoming data to allow the printer
	  to catch up. If the remote system does not respond to the
	  handshaking signals sent by ACCESS, the data will continue to be
	  received, but not all of it will be printed.

* During Host Mode, several lines of un-wanted data are printed, then a message
  referring you to the manual is printed.
	- Host mode automatically begins echoing data received from the remote
	  system. If the remote system is also echoing data back, an unpleasant
	  chain reaction starts. Host mode will exit when it detects its own 
	  prompt being echoed back to it. (Note: many intelligent modems echo 
	  data to you while in the command state. The echo must be disabled 
	  before Host mode is entered.)

* When transferring files using block structured (XMODEM) method, remote system
  times out before you've had a chance to set ACCESS up to perform the 
  transfer.
	- Solution: set ACCESS up first, then instruct the remote system to 
	  prepare for the transfer.

* When using Submit function or when terminating ACCESS, a message appears
  asking you to insert the system disk in the default drive.
  	- The disk in the default drive should be one formatted with the '/s'
  	  option to include system files and should contain a copy of 
  	  'COMMAND.COM'
 
* On H/Z-100 versions, when connected with intelligent modem, modem seems to 
  respond to commands, but no response is received on screen.
	- DCD signal into pin 8 on J2 is low because modem has not detected
	  carrier during command setup. See section ***.

* On H/Z-100 versions, data can be received but nothing is transmitted.
	- A high signal (or no connection at all) must be present on pin
	  5 of J2 to enable the UART in the Z-100 to transmit. 

* On H/Z-100 versions, frame around menu and option screens is made up of
  letters and punctuation marks rather than a solid graphic line
	- The file ALTCHAR.SYS was not available on the disk during cold boot.
