User`s guide

CPU32 Emulation 181
Chapter 11: Troubleshooting the Emulator
Problems with the Serial Interface (Emulation Probe Only)
If you have RS-232 connection problems with
the MS Windows Terminal program
❏
Remember that Windows 3.1 only allows two active RS-232 connections at
a time. To be warned when you violate this restriction, choose Always Warn
in the Device Contention group box under 386 Enhanced in the Control
Panel.
❏
Use the "Terminal" program (usually found in the Accessories windows
program group) and set up the "Communications..." settings as follows:
• Baud Rate: 9600 (or whatever you have chosen for the emulation
probe)
•Data Bits: 8
• Parity: None
• Flow Control: hardware
• Stop Bits: 1
When you are connected, hit the Enter key. You should get a prompt back.
If nothing echos back, check the switch settings on the emulation probe.
❏
If the switches are in the correct position and you still do not get a prompt
when you hit return, try turning OFF the power to the emulation probe
and turning it ON again.
❏
If you still don’t get a prompt, make sure the RS-232 cable is connected to
the correct port on your PC, and that the cable is appropriate for
connecting the PC to a DCE device.
With certain RS-232 cards, connecting to an RS-232 port where the
emulation probe is turned OFF (or is not connected) will hang the PC.
The only way to get control back is to reboot the PC. Therefore, we
recommend that you always turn ON the emulation probe before
attempting to connect via RS-232.