NB - This problem only affects SafeDial+ in PCMCIA slots (either in a laptop or via a PCI/ISA to PCMCIA converter). It does NOT affect SafeDial+s in SafePorts.

This problem only exists with Windows 2000 and XP - Windows 9x and Windows Millennium do not suffer from this problem.

The Microsoft document above provides a fix to this problem. Depending on which operating system you are using follow the instructions below:

If you are using Windows 2000 with Service Pack 1 or 2

In the article Microsoft recommends upgrading to Windows 2000 sp3. If you are prepared to do this download the service pack, install it and follow the instructions below in the section "If you are using Windows 2000 Service Pack 3 (or later) or Windows XP".
If you do not wish to update your service pack you can follow the old hotfix instructions:

1. If you have not already done so, insert your SafeDial+ and install the drivers in the usual way.

2. Run the attached "Q275042_W2K_SP3_x86_en.EXE". Do not reboot after installing the fix.

3. Click Start, click Run, type regedt32 in the Open box, and then press ENTER.

4. Locate the appropriate device parameters key in the registry, under the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Enum registry key. You can locate the appropriate key manually only.

HKEY_LOCAL_MACHINE
\SYSTEM
\CurrentControlSet
\Enum
\<device type> (e.g. "PCMCIA")
\<device identifier> (e.g. "Racal SafeDial")
\<device id number> (e.g. "1")
\Device Parameters

5. On the Edit menu, click Add Value, and then add the following registry value:
Value name: EnablePowerManagement
Data type: REG_DWORD
Radix: Hexadecimal
Value: 0x1

6. Exit Registry Editor and reboot your PC.
Once your PC has restarted you can test whether the fix has been applied correctly by going to the section at the end of this document entitled "Verifying that the fix has been applied correctly".

If you are using Windows 2000 with Service Pack 3 (or later) or Windows XP

1. If you have not already done so, insert your SafeDial+ and install the drivers in the usual way.

2. Click Start, click Run, type regedt32 in the Open box, and then press ENTER.

3. Locate the appropriate device parameters key in the registry, under the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Enum registry key. You can locate the appropriate key manually only.

HKEY_LOCAL_MACHINE
\SYSTEM
\CurrentControlSet
\Enum
\<device type> (e.g. "PCMCIA")
\<device identifier> (e.g. "Racal SafeDial")
\<device id number> (e.g. "1")
\Device Parameters

4. On the Edit menu, click Add Value, and then add the following registry value:
Value name: EnablePowerManagement
Data type: REG_DWORD
Radix: Hexadecimal
Value: 0x1
5. Exit Registry Editor and reboot your PC.
Once your PC has restarted you can test whether the fix has been applied correctly by going to the section at the end of this document entitled "Verifying that the fix has been applied correctly".

Verifying that the fix has been applied correctly

It can often be difficult to know whether the patch has been applied correctly or not - here is a simple way of testing whether the fix has been applied correctly.

1. Insert your SafeDial+ into your PCMCIA slot and connect to it via HyperTerminal (see "Phones and Modems" option in Control Panel if you do not know which COM port to use).
2. Type in your password with the command AT$UB<password> where <password> is the SafeDial password (default is RACAL). SafeDial should return OK if this is accepted.
3. Disconnect and close down HyperTerminal.
4. Open HyperTerminal again and reconnect to the SafeDial and then type AT$UC.
5. If the SafeDial returns OK then the fix has been successfully applied. If it returns You are not logged on. Password? Then the fix has not been applied.

What you are doing here is logging into the SafeDial+ and setting the mode to "encrypt". In step 2 you logon to the SafeDial+, in step 3 you disconnect from the SafeDial+ (and, if the fix is not applied, Windows powers off the SafeDial+). In step 4 you set the mode to encrypt (which can only be done if you are logged onto the SafeDial+).

Other Issues

If your PC goes into Hibernate or Standby mode then the SafeDial+ will be powered off (regardless of whether the above fix has been applied) - this is by design. This means that when the PC is brought out of standby you will need to logon to the SafeDial+ again with the client. Depending on how your PC is configured this will only happen if the PC is left unattended for a specified amount of time. If this behaviour is unacceptable then it is recommended that you turn off Power Management via the applet in control panel or set a suitably lengthy period before the PC goes into standby.