
Previous config:
Power-on password set ON
HDD password set ON (same password as power-on)
Fingerprint swipe provides power-on password (and hdd password, since the same) set ON
=> Single fingerprint swipe would pass both power-on and HDD passwords, boot up (XP Pro SP3), and login
Last successful boot 7-14 days earlier
Upon removing the battery pack and all HDDs, I booted up, entered BIOS, sure enough the date and time were set to January 1998. Power-password is DISABLED. Set the date and time again, shut down, pulled battery, inserted HDD, inserted battery again, same indications (HDD passwords rejected).
I have a spare T43 (15in model) that someone at work gave me, so presumably a possibly good backup battery spare to use. My old X32 too (which is also not liking previously used power-on passwords, leading to doubts to memory and escrowed password records). Haven't removed the palm rest to test the battery, that's next, though this certainly looks like a bad battery (first power on November 2005). Any suggestions on this are welcomed!
My concern is to the volatility of the security chip and HDD password information. The laptop battery was run low earlier this summer, but for the most part it's been plugged in. It was plugged in since the last successful boot earlier this month. The fact that the T43 prompts for a fingerprint swipe with the drive in (but does not prompt with all media devices out, going into BIOS), tells me that memory of a HDD password is present, but ... is the correct value stored? can it become corrupted? is the HDD now bricked because the CMOS of the host laptop has been reset?
I'm also curious if I should re-enable power-on password, to what I'm 98% certain was the last one ... see if that matches. Typing it manually fails, and I'm mystified why.
If there's a procedure to follow for this, I've appreciate a pointer. It's been years since I was actively engaged here, so I'm a little rusty on the advanced T4x tech. ,:}
Afterward: having experienced this, I think I would not again utilize security features like this. It's given me peace of mind for many years, probably overkill in my use case of a laptop that hasn't left the house much in the last few years of use. But with this failure, though I have good, relatively recent backups, the headache isn't worth it IMHO.