PageAway Bug Fix History


Windows for Workgroups: (Client Edition)

Reported: November 2, 1996

Message "Out of Memory". This error has occurred on a few Windows for Workgroups workstations. To correct this problem download the latest update PageAway 3 Client Edition (Update). This self-Installing update will correct the problem.


Windows for Workgroups, Windows 95, and Windows NT (Client and Server)

Reported: February 27, 1997

PageAway Dials a 0 (Zero) when entering a password for some services. This has been determined to be a bug. To correct this problem download the latest update PageAway 3 Client Edition (Update) or PageAway 3 Server Edition (Update). Both self-Installing updates will correct the problem.

 

Reported: March 25, 1997

Unable to connect using a Shiva NetModem/E. The software connects to the shiva, initializes the modem, sends the phone number and follows with an error indicating that the modem could not connect, line busy etc. To correct this problem, download the latest modem list file or remove the FN0 and replace it with F0. Example: AT&FN0s37=0 to AT&F0s37=0.

 

Reported: April 22, 1997

Unable to Print Phonebook. PageAway will not print the phonebook to a Microsoft Windows network printer. The problem is embedded spaces in the computer name. Microsoft has confirmed this to be a bug and recommends the following workaround.

Rename the computer such that its name does not include an embedded space, or create a local printer that has the specified port redirected to the shared network printer. For more information on this please refer to the Microsoft Windows 95 documentation.

 

Reported: April 23, 1997

Message History does not display when re-directing to server. PageAway client was designed to track messages sent locally only. However, we have added support for the server with this upgrade. To add this feature, you will need to download both PageAway 3 Client Edition (Update) and PageAway 3 Server Edition (Update). 1.) Install the Server first 2.) Run the upgrade wizard 3.) Install the client update.

 

Reported: May 07, 1997

Message Log doesn't print Recipient Name for every Record. This problem has been reported to happen on some laser printers. This has been determined to be a bug and has been corrected.

To correct this problem download the latest update PageAway 3 Client Edition (Update)

Reported: May 14, 1997

PageAway Server 3.1 build 322: Integrity check displays the following message 'File Not Found'.

To correct this problem download the latest update PageAway 3 Server Edition (Update).

 

Reported: May 21, 1997

PageAway Server 3.1 build 323: Server unable to Remove Event due to a record locking conflict. This will happen in the event that a workstation attempts to open a Page Lock that overlaps another locked record. This update will pause for two seconds and try again, up to 5 times.

To correct this problem download the latest update PageAway 3 Server Edition (Update).

 

Reported: May 22, 1997

PageAway Server 3.1 build 325: The previous update has been reporting unexpected error messages. We believe the problem is related to a conflict with the server's locking database.

To correct this problem, you will need to download both PageAway 3 Client Edition (Update) and PageAway 3 Server Edition (Update). 1.) Install the Server first 2.) Run the server upgrade wizard 3.) Install the client update. 2.) Run the client upgrade wizard

We have also added a preference for the client "Verify the server is running" and the server "Verify Database Integrity each time the server starts".

Note: This update has not been confirmed to correct the problem. If you are not having any problems with the server, you do not have to download this update.

Reported: August 1, 1997

PageAway Client 3.1 build 348: If the search bar was visible, the statusbar text would not display properly. To correct this problem, you will need to download PageAway 3 Client Edition (Update).

 

Reported: October 1, 1997

PageAway Client 3.1 build 356: When sending a scheduled page, PageAway occasionally comes back with an error message: 'Type Mismatch 13". The problem is related to the way Windows 95 formats the system time. Windows 95 OSR-2 has been known to format Military time followed by the AM/PM symbols. This is incorrect and PageAway was unable to make the proper determination since using AM/PM with military time is invalid.

There are two ways to correct this. You can download the latest build PageAway 3 Client Edition (Update) or make the following changes:

Click on Windows 95 Start button, select Settings, Control Panel. Then select Regional Settings Select the Time tab and change the Time Style to say: h:mm:ss tt (If the date already says h:mm:ss tt, (Do not use Uppercase characters), then change one character then set it back the way it was and select apply.) Then select OK

 

Reported: February 12, 1998

PageAway Client 3.2 build 370: When sending a page to the server, when the date on the client side is not the same date on the server, and if you have the option "Send Expired pages today only (New Feature added in v3.2)", the server would ignore it. To correct this problem, you will need to download PageAway 3 Server Edition (Update).

 

Reported: February 13, 1998

PageAway Client 3.2 build 375: When sending a page locally, the following error occurs "Object variable not set". To correct this problem, you will need to download PageAway 3 Client Edition (Update).

 

Reported: February 18, 1998

PageAway Client 3.2 build 377: It has been brought to our attention that when renaming a group, the service provider name appears incorrect. If you attempt to rename a group it will re-assign the group to the wrong service. The following patch will correct this problem. This bug is only in (Version 3.2 build 377). Also, if you are not using a PageAway Server, this fix will not load the PageAway Server Console. Note: You do not have to run the upgrade wizard for this fix. Patch (Version 3.2 build 378)

To correct this problem download the latest update PageAway 3 Client Edition (Update)