fingerprint software rejects password-can't enroll prints

[ChugokuOtaku]

I installed Thinkvantage Fingerprint Software version 5.9.3 on Win7 32bit on my T42 laptop.
I first setup a primary admin account, launched the software, entered password, enrolled prints, no problems.
I then created a 2nd admin account for another user, but when I logged in as the new user and tried to enroll prints, ThinkVantage Fingerprint Software rejects the password. I've tried changing the 2nd account's password to something very simple, and it still won't accept it. I confirmed the passwords are correct by login back in right after changing it, but no luck trying to enroll finger prints.

help?

[RealBlackStuff]

Maybe the software can't handle 2 Admin accounts?
Have you seen this? http://www-307.ibm.com/pc/support/site. ... 59650.html

[ChugokuOtaku]

Maybe the software can't handle 2 Admin accounts?
Have you seen this? http://www-307.ibm.com/pc/support/site. ... 59650.html

So I tried following the instructions on that page:

Note: Security mode must be set to Secure Mode which enables the administrator role.
To set the security mode to Secure Mode:
Click Start, select Programs, select Access IBM, select Fingerprint Software, then click Control Center.
Click Settings.
Click Security Mode.
Click the Secure mode option.
Click Finish.
The software should be configured to support multiple user logon via fingerprint authentication.
You can use the "Create new passport and enroll fingerprints" selection under the Fingerprints section to enroll each user. At log on, the software will read the user's print and automatically authenticate the appropriate user.

I then tried recreating two accounts, one standard, one admin. The windows password for both accounts are still rejected.
It seems that Fingerprint Software will prompt me for a password regardless of whether or not a password has been set. Anything else I can try?

[ChugokuOtaku]

okay, got it all figured out

I was running into all kinds of problems with browser configs and E-mail clients spitting SSL errors at me.
turns out it all had to do with me choosing a non-Latin character username

laptop was configured for my mom, and after I changed the name back to the Romanized version, all was well!

[RealBlackStuff]

Good sleuthing, my dear Watson!