![]() If you do have a machine that can still run these old clients, and if you’re lucky, it might be possible to connect them up to Escargot with a little bit of tweaking. With my own server I’ve been able to get a number of these native Mac clients working, using host files and manually installing SSH certificates, and they don’t seem to be substantially different to the Windows versions as far as the server is concerned. Running Messenger for Mac 5.x under Rosetta on Leopard might work, but I haven’t tested that, as I don’t have an Intel Mac to try it on. That only leaves you with very old (and PPC-only) versions, so unless you have an old PowerPC-based Mac with either MacOS 9.2 or MacOS X 10.2 or higher, I guess you’re out of luck for the moment. So basically 6.0.x and above are incompatible with Escargot (because they use newer protocols), Messenger for Mac 5.x might work, I haven’t tested them with Escargot. Version: 8.0.2 - Final version, recommends upgrading to Skype Protocol: MSNP16 (thanks Probably macmsgs/macmsgs like all the others? Version: 2.5.1 (About dialog says 2.5.0, but client reports 2.5.1 when connecting)ĬVR: Probably macmsgs/macmsgs like all the others? They should behave more or less like the Windows versions, although it depends which version of MacOS you’re running. app on Mac > Applications > Microsoft Messenger Pro > Move Microsoft. The native Mac versions, or at least some of them, seem to work fine connecting to an unofficial server. Microsoft Messenger for Mac (previously MSN Messenger for Mac) was. I’ve been experimenting with Mac versions on my own server, with varying levels of success.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |