mIRC 6.35 and Windows 7 are already compatible. The only thing it can't do in Windows 7 is show a correct $os reply simply because it didn't know about Windows 7 when it was released. If you have a stat script that displays the OS, you can still obtain the correct OS by using COM instead of $os. Not very hard to do. And other than that, it's fully compatible with Windows 7.

It's not like UTF-8 is new. It's been out for around 10 years. People have had all that time to update. Because they didn't already do so, it is now biting them. Procrastinating doesn't make it someone else's fault.

As for scripts, you will always have scripts that break when updating to a newer version of mIRC. You either have to ask the script author to fix it, or fix the script yourself, or find someone to do it for you, or else find a different script. In the majority of cases, there aren't many changes necessary to make a script compatible with newer versions of mIRC. And regardless, updating scripts is something that has to be done even without talking about UTF-8. If you're going to use a script that someone else wrote, then you have to understand that it may someday not work with the current version of mIRC. That's just how it goes. That has nothing at all to do with UTF-8. It's a fact of life if you use scripts. And in all honesty, updating scripts is one of the LEAST problems anyone should have when changing to UTF-8.

Keep this in mind. If you refuse to update just because it means that you have to update some scripts, then you are missing out on new features as well as bug fixes and security fixes. Not very smart. There are a lot of people still using old versions of mIRC with known exploits... exploits that can allow other users to do a wide variety of dangerous things to your computer if you didn't update. If they get hacked because they didn't update, it's their own fault for being lazy. There are updates for a reason.

Last edited by Riamus2; 16/01/12 07:34 PM.