Unsolved

This post is more than 5 years old

3 Posts

10787

December 13th, 2006 08:00

Problem between Wave software and power management on a Latitude D420

Hello, first post here, I believe I haven't seen anybody writing about this problem yet.
 
On a client's Latitude D420, we have the following strange behaviour of the fingerprint reader: if the computer is woken up from standby mode after less than ca. 2 hours, the Wave logon window (fingerprint+password) works fine (the system is configured to ask for authentication when resuming from standby). If the standby period was longer than 2 hours, the Wave logon window never shows up and we must reboot the computer to be able to login again, loosing all unsaved data. I am not sure whether this is a fingerprint reader or Wave Embassy or Windows power management problem.
 
Now about what we did already:
- patched the Embassy software to the latest version;
- checked that the BIOS-level biometric authentication is off;
- disabled "turn off this device to save energy" in Device Manager for the fingerprint reader;
- obviously, disabling authentication on resuming after standby solves our problem, but our client precisely wants to authenticate in this scenario;
- called Dell support a few times without success;
- wrote to the Dell client advocates on 11/29 to complain (we've been asking for help for more than 3 months now) without any answer yet.
 
Anybody could help? I would be especially grateful if someone would check out whether their computers also fail to show the Wave logon window after 2+ hours of standby.
 
Thanks in advance!
 
Robert

2 Intern

 • 

12.7K Posts

December 13th, 2006 15:00

Looks like you have done everthing possible except get a response from Dell.
 
Have you updated the Bios, the latest is dated 10-31-06  v A02
 
Is this S3 standby?

3 Posts

December 14th, 2006 07:00

We haven't updated the BIOS but will do at the next occasion.
It is S3 standby indeed.

2 Intern

 • 

12.7K Posts

December 14th, 2006 12:00

You might try Hibernate instead of standby..a little slower to wake up but may solve the problem
 

2 Intern

 • 

12.7K Posts

December 14th, 2006 12:00

 "obviously, disabling authentication on resuming after standby solves our problem"
 
how do you do this?
make sure that ask for password when resuming from standby is unchecked, if answer to the question is a different method.

3 Posts

December 14th, 2006 12:00

Well, thanks a lot for doing this research!
 
I will try to force hibernation mode instead of standby. It could be that the PC goes from S3 to S4 after 2 hours (remember it's a client's PC, I don't have permanent access to it). If it fails to resume properly from S4, then I'll search around the USB reg hack suggested in your Web link.
 
About the "ask for password" feature: the client specifically wants to be asked for the password when resuming from standby for security reasons. So yes, the problem goes away when this feature is unchecked, but this doesn't answer the client's need. That was what I meant by "disabling authentication on resuming after standby".
No Events found!

Top