How to Correct Garbage/Repainting Problems with Digiboard

 Last reviewed: December 18, 1997
Article ID: Q120022
2.60 UNIX kbenv kbprb

WARNING: The information in this article has not been confirmed or tested by Microsoft. Some or all of the information in this article has been taken from unconfirmed customer reports. ANY USE BY YOU OF THE INFORMATION PROVIDED IN THIS ARTICLE IS AT YOUR OWN RISK. Microsoft provides this information "as is" without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

The information in this article applies to:

  • Microsoft FoxPro for UNIX, version 2.6

SUMMARY

Problems have been reported with garbage characters or with repainting in FoxPro for UNIX. Both situations described in this article have required tuning of the Digiboard software in some way.

MORE INFORMATION

Problem/Solution 1

A customer figured out how to stop getting garbage on the screen with a Wyse60 without running Digiboard's dscreen utility. In the gettydefs file on the 38400 line, the customer had CTSFLOW and -IXANY. The communications setup on the terminal setup (press F4 to get to communications setup) had the following settings: 

   Baud Rate=38400         DATA/STOP BITS=8/1
   RCV HNDSHAKE=XON/XOFF   XMT HNDSHAKE=XON/XOFF   XPC HNDSHAKE=OFF
The above setup worked with all applications except FoxPro for UNIX running at 38400. The customer found that by changing RCV HNDSHAKE=XON/XOFF to RCV HNDSHAKE=DTR, FoxPro would run correctly at 38400. The customer spoke to Digiboard about dscreen, but Digiboard did not know why FoxPro for UNIX would work with dscreen. The customer guessed that dscreen was slowing FoxPro for UNIX down enough to work correctly. The customer could not find any difference in the settings of the line while running dscreen and not running dscreen. Digiboard said dscreen does not do anything special concerning flow control.

Problem/Solution 2

Another customer was having a problem with screen repaints and screen colors in FoxPro for UNIX when using Digiboard's Doubleview. If the customer turned WRAPAROUND on, FoxPro for UNIX seemed to work correctly, but other applications, such as WordPerfect Office, would not work correctly with WRAPAROUND on.

In this situation, it's important to check the automargin ("am") terminfo capability. WRAPAROUND=ON is the same as "am"; WRAPAROUND=OFF is the same as "not am". To check this setting, you have to use the wpterm utility to look at WordPerfect's terminal facility as well as terminfo.

In this case, the customer looked in the wpterm program and edited the dbview and dbviewcol variables. The line "Can Automap be Disabled on this Terminal?" was set to N. This was right for WordPerfect 5.1 but it was set to Y for the WordPerfect Office setup. WordPerfect Office and WordPerfect 5.1 are supposed to use the same shared directories. WordPerfect Office mail was the program that was having problems the WRAPAROUND=ON setting in the Doubleview setup. To change the Automap setting, the customer ran the WordPerfect 5.0 wpterm program. The customer now has Doubleview set up with WRAPAROUND=ON, and the terminal now works correctly with WordPerfect Office mail and FoxPro for UNIX.

Additional reference words: FoxUnix 2.60 multiport digiboard dscreen
repaint
KBCategory: kbenv kbprb
KBSubcategory:

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: December 18, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.