Community

Here's what I mean:

I'm running Windows 2000 Professional SP1, and I have set up two accounts called "Administrator" and "David", both members of the Administrators group.

I login as David, install TextPad v4.4, and use TextPad, Preferences to associate, say, .reg with TextPad. At this point it looks like all's well. I go to Windows Explorer, Tools, Folder Options, File Types and look at the entry for .reg, and everything looks fine.

Now I logoff, and log back in as Administrator. I go to Windows Explorer, Tools, Folder Options, File Types and look at the entry for .reg, and all the details have evaporated!! For instance, the File Type descriptor has changed from "Registration Entries" to "REG File". For instance, "Open With" has changed from "Registry Editor" to <null>.

This effect happens with every file type that was associated via TextPad, Preferences. I've reproduced this problem on two machines.

Help!!

David (mailto:Habermehl@mediaone.net)

I found that textpad does not save all settings if it is terminated by a logoff or shutdown. Have you closed textpad before you logged off or did you let the logoff do the closing of textpad?

Windows NT/2000 uses different registries for each user. So logging in as 'David' gives you a different registry (and so different file associations) from logging in as 'Administrator'.

Regards,
Frank

Andreas, yes I closed TextPad before I logged off.

Frank, I understand that 'David' gets a different registry (and associations) than 'Administrator'. The problem is that when I am logged in as one user ('David' in my example) and associate extensions with TextPad via TextPad's preferences, two things happen:

1. The expected changes get made to the 'David' registry.

2. Unexpected (and harmful) changes get made to the 'Administrator' registry.

Best Regards,

David (mailto:Habermehl@mediaone.net)

Thanks for bringing this problem to our attention David.
We hope to have out a minor release of TextPad for the end of this week which will fix this problem.

Kind Regards

Heidi-Marie

Thanks!

Problem fixed in 4.4.1. I appreciate your responsiveness.

-David