The following is a list of common problems encountered setting up a digitizer:
1) Problem -Error Opening Comm Port" message appears when you access the digitizer.
This message usually means that the wrong PORT (COM1, COM2 etc.) has been selected or another driver has opened the port, such as a FAX/MODEM or WINTAB. If you have selected the correct port, check that no other drivers are active (in Windows 95 you can do this by selecting Control Panel/System/Device Manager/Ports/Properties).
NOTE: Some digitizers can be used as the Windows mouse device. Terrain doesn't support digitizers configured as the mouse device. Do not install Windows drivers such as WINTAB for your digitizer. If you already have then you must uninstall it before using Terrain.
2) Problem -Strange characters (e.g. ^%!&&^) appear in the Digitizer Test Dialog.
This usually indicates that either the digitizer is transmitting in a BINARY mode or the Communications parameters (baud rate etc.) are wrong. Check the communication parameters. Make sure you have followed the setup instructions (hardware switches, menus etc) for your tablet as described in the Standard ASCII Digitizer Settings.
3) Problem -No response in Digitizer Test Dialog when a key is pressed on the tablet.
Check that the cable between the computer and the digitizer is correct. One of the most common problems is the wrong type of interface cable. Often a digitizer will require a "Null Modem" (or normal cable with a Null Modem adapter). Your computer or digitizer supplier will be able to help you determine exactly what type of cable you have.
Check that you are on the correct port. Check the cable connections. Make sure you have followed the setup instructions (hardware switches, menus etc) for your tablet described in the Standard ASCII Digitizer Settings. Try running diagnostic software supplied by the tablet manufacturer to verify that the table is operational.
4) Problem -Table works most of the time but occasionally it produces spurious lines while digitizing in track mode.
Symptoms like this are often caused by incorrect flow control. Check that the flow control (XON/XOFF or hardware) matches that specified in the Standard ASCII Digitizer Settings also check your digitizer manual.