"paul" <paul@discussions.microsoft.com> wrote in message
news:077125C0-A20F-42B6-9DEF-970F760D05F8@microsoft.com...
> This is a sp3 issue it happened imediately after the sp3 install.

It is an XP issue, but it is possible that somehow SP3 created the
conditions on your PC that cause this to happen. Oddly, someone I know who
has installed SP3 recently found to his surprise, that the same fault on his
PC has been cured by the installation of SP3.

The mystery remains.