Unfortunately, this problem is *not* fixed in SP3. I'm still seeing this issue on XP Home after successful SP3 installation.