Quote:
|
Originally Posted by StarDestroyer
This seems to be caused by a conflict in the Additional Themes OEM for the registry entries in HKEY_CURRENT_USER\Software\Microsoft\Today. Commenting those out in additional themes seemed to fix it. Probably not anything you can do about it in OEMizer.....
|
The problem is not that it's being overwritten, it's that OEMizer uses an init reg entry for cusTSK that isn't properly being executed in WM6 .7. The reason it works when including "Additional Themes" is because that OEM includes a startup link to cusTSK which changes to the theme you have overwritten with your personal OEM on first startup.
As you noticed, the correct theme was selected in the Today settings, but cusTSK hadn't been executed to actually change it.
The init method seems to work in WM5 and WM6 .42, but not .7. I'm trying to not have to include a link or additional exe that users don't add themselves, so hopefully we can find a fix for init.