msn explorer and messenger beta

pug_in_a_bed

still using msn explorer but want to upgrade msn messenger to the beta version - however when installing it says some features of msn explorer won't work with beta, anyone know what features?
thanks in advance

T4i

be careful with the new beta of msn messenger. Me and many of my freinds are having major problems with it crashing. Dont know if theres a fix/new release yet.

I dont know about your actual question though, sure someone will.

heatherw_01

MSN messenger 7 is no longer a beta. Just download as you normally would from the messenger site.

T4i

Oh cool! :j :j

GibsonSt19

For a start, I'd stop using MSN Explorer, which is slow and bloated.

For browsers, consider:

Deepnet Explorer
Opera v8 FINAL Released yesterday
Firefox
Avant Browser

...or even just Internet Explorer.

Then, download and install the FINAL build of MSN Messenger v7 - From Here

Hope that helps.

T4i

The MSN Messenger 7 final is broken as I thought...

Look at all the people with the same problem.

http://www.msghelp.net/showthread.php?tid=42324

My Messenger needs 4 attempts at starting it before it stops locking up.

GibsonSt19

T4i wrote:

The MSN Messenger 7 final is broken as I thought...

Look at all the people with the same problem.

http://www.msghelp.net/showthread.php?tid=42324

My Messenger needs 4 attempts at starting it before it stops locking up.

Broken? I've had no probs.

-TangleFoot-

I had the same problem when I installed it a few days ago; stopped responding almost as soon as it signed in.

After searching for a bit, I came across a rather useful piece of advice; prevent Messenger from signing in, check the box in options marked 'Connection Logging', then sign in again and see what happens.

This may not be the case for everyone, but it appears, according to the log, that MSN Messenger 7 was having trouble contacting a 'secondary echo server'; something to do with the voice communications facility I think.

Anyway, I searched for the phrase on Google, and this forum post caught my eye. Google's translation is a bit iffy but the gist of it is that the problem may have something to do with NAT routing; apparently upgrading the firmware on their router solved one poster's issues quite nicely.

Me? I'd already upgraded my router's firmware months ago, so I tried undoing some changes that I had made. I'd previously set-up a bogus virtual server for a little peace-of-mind; the router wouldn't drop ICMP echo requests otherwise. Deleted it, and all was well again. I think that that extra non-existent IP address was confusing it...

Not sure why I bothered though, as this new version looks almost exactly the same as the old one!