Well, I'm stumped.
I've got a Win2K system running the Win32 client; was at 3.1.0.6, now at
3.7.2.01.
It's been running fine for months, with PASSWORDACCESS GENERATE in dsm.opt.
THe scheduler service was backing up fine daily.

Then we tried to change the password.

Now when you start TSM (dsmc or dsmc sched or GUI), it prompts for the TSM
password.
When you give the password, it works fine.  You can shut down TSM (dsmc or
dsmc sched or GUI), and it doesn't prompt for the password if you start the
TSM client again.

Until you reboot.
Then it doesn't know the password anymore.

In dsmerror log I see this:
12/04/2000 06:42:46 ReadPswdFromRegistry(): RegOpenPathEx(): Win32 RC=2

Which just tells me it can't find the password in the registry, yes?

I first upgraded the client from 3.1.0.6 to 3.7.2.01, and that didn't help.
So I uninstalled the 3.7.2.01 client and did a complete reinstall.  That
didn't help.

I have no clue how to fix this one.
What makes a client not save its password across a boot?