T
Tom Barclay
I installed a trial version of WallMaster Pro wallpaper management program.
When the trial expired, I decided it wasn't something that I really wanted,
and uninstalled it using the program's own uninstall. It has since become
the program from hell that won't go away. Upon reboot, my system still tries
to load WallMaster's wallpaper, which results in a blank screen since the
program no longer exists. I have tried manually deleting all remnants of the
program that I can find from my drive, searching all files containing
"wallmast" and "wallmaster" including hidden and system directories. I also
did a search of the registry using regedit and deleted all references to the
program. Doing all of the above removes the wallmaster menu entry from the
desktop Display Properties/Desktop menu. However, when I reboot the system,
the menu entry is back, the desktop defaults to the missing wallpaper, and
all of the registry entries have been restored. I tried looking in
msconfig's .INI files, but there's no reference to the program there. I'm
assuming XP stores the information causing this in some other place that I'm
missing. Any help would be appreciated.
When the trial expired, I decided it wasn't something that I really wanted,
and uninstalled it using the program's own uninstall. It has since become
the program from hell that won't go away. Upon reboot, my system still tries
to load WallMaster's wallpaper, which results in a blank screen since the
program no longer exists. I have tried manually deleting all remnants of the
program that I can find from my drive, searching all files containing
"wallmast" and "wallmaster" including hidden and system directories. I also
did a search of the registry using regedit and deleted all references to the
program. Doing all of the above removes the wallmaster menu entry from the
desktop Display Properties/Desktop menu. However, when I reboot the system,
the menu entry is back, the desktop defaults to the missing wallpaper, and
all of the registry entries have been restored. I tried looking in
msconfig's .INI files, but there's no reference to the program there. I'm
assuming XP stores the information causing this in some other place that I'm
missing. Any help would be appreciated.