back to knowledge base index PROBLEM: Second Scheduled Event or Group Playback using Modem fails.

Last reviewed: February 07, 2002
Article ID: 020207sab

The information in this article applies to:

Symptoms

Any of the following:

Cause

The default time that Pronto for Windows allows between hanging up the modem and dialling out for a second time is too short. When Pronto for Windows disconnects from a Logger it waits for one second before processing continues. If data is saved very quickly or if the event is a Playback to MDM file or a Check of Logger Status event the next dial out is started almost immediately. The default time of one second is sometimes too short for the modem or for some telephone exchanges and the dial out fails. This problem may not be noticed immediately for a scheduled event since the second event will succeed when it is retried after 10 minutes.

Resolution

A hidden configuration setting controls the time that Pronto waits after hanging up the modem.

To fix the problem for 32 bit releases 5.00 and later:

Note that 32 bit versions of Pronto for Windows may store their configuration settings on a per user basis instead of per machine.  To check if settings are on a per user basis examine the value of HKEY_LOCAL_MACHINE\Software\Ranger\Pronto for Windows\User Info\ProfilePerUser if the value is zero then settings are on a per machine basis otherwise settings are on a per user basis and the DropDTRMillisecs value must be stored under the key HKEY_CURRENT_USER instead of under HKEY_LOCAL_MACHINE.

To fix the problem for 16 bit releases 4.xx.

Back to Knowledge Base index

Last reviewed: February 07, 2002
© 2002 Outram Research Ltd. All rights reserved.