Hi,
That's a shame. Given that older model number, I assume you've not updated the firmware on
that W11S4 recently or anything. Some routers can hang Messenger with bad UPnP
implementations.
Your only real option is try removing the Messenger client cache.
Firstly, click Start, then Run and type the following:
%userprofile%\Contacts
and click OK. Now right-click the Passport/Windows Live ID corresponding to what account
you're trying to sign in on and choose Delete. This is a cache, you won't lose anything by
doing this.
Next, click Start again, Run again, and type the following:
%userprofile%\Local Settings\Application Data\Microsoft
Now right-click the Messenger folder, choose Rename, and call it something like Messenger_.
Assuming this works you can go into this folder and move your emoticons, winks, et al over
when you're done.
Now try signing into Messenger again.
--
Jonathan Kay
Microsoft MVP - Windows Live Messenger/MSN Messenger/Windows Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources -
http://messenger.jonathankay.com
All posts unless otherwise specified are (c) 2007 Jonathan Kay.
You *must* contact me for redistribution rights.
--
"Brandon M" <> wrote in message
news:5550A636-6FAD-4F8B-AF7A-...
> Finally had some time to do that system restore tonight. Unfortunately, its
> expired, and I can only go back to yesterday, so that option is out.
>
> Hang is still happening... 100% of the time. I should mention I have
> Messenger PLUS installed too (though that's never caused any issues before -
> even with this exact version of it installed)
>
> brandon
>
>
>
> "Brandon M" wrote:
>
>> I'll investigate system restore tonight, but in the meantime:
>> 1. Windows XP, Media Center Edition, SP2 (do you need more than that?)
>> 2. Yes, router used is, Linksys W11s4 vers. 3 (80211b wireless router)
>>
>> Brandon
>>
>>
>> "Jonathan Kay [MVP]" wrote:
>>
>> > Greetings,
>> >
>> > Since this just happened 24 hours ago, try using System Restore to restore back to see
>> > if
>> > that corrects it.
>> >
>> > Failing that, we'll need to know the Windows version and if you're using a router (more
>> > on
>> > this later).
>> >
>> >