Microsoft KB Archive/143305

= Works 95: Script and Emulation Fail If Initial Call Is Busy =

Article ID: 143305

Article Last Modified on 11/15/2004

-

APPLIES TO


 * Microsoft Works 4.5 Standard Edition
 * Microsoft Works 4.5a
 * Microsoft Works 4.0 Standard Edition
 * Microsoft Works 4.0a

-



This article was previously published under Q143305



SYMPTOMS
A Works communications module sign-on script fails to run when a connection is made. This occurs if both of the following are true:

 The redial connect option in Phone Settings is turned on.

-and-

 The initial call was busy, but the redial attempt was successful.

When you set a terminal emulation mode (for example, TTY, ANSI, or VT100) and turn on the Redial option and your initial call is busy, the terminal emulation is not retained after the call connects.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.



MORE INFORMATION
If the initial attempt to connect to another computer is successful, the sign-on script and terminal emulation function properly for future communication sessions.

Additional query words: 4.00 4.00a 4.50 4.50a w_works communication modem login logon signon macro re-dial busied out

Keywords: kbbug kbpending KB143305

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.