Source: mIRC
mIRC version 6.15 has been released thursday June 3rd, 2004. You are receiving this e-mail because you have subscribed to the mIRC release mailing list. The new version of mIRC is available from http://www.mirc.com/ and from all fast mirrors around the world. We have also provided a few download addresses below.With this release we hope to address the most important comments, requests and remarks we received after the release of version 6.14. The new version fixes quite a few small bugs found in the previous versions. We tried to focus on fixing things, making the mIRC 6 series more an more sturdy, and only few new features and functions have been added.- SJIS/JIS support and various multi-byte display/mark/copy issues have improved,- the 'reload' logs feature has improved to make sure it reloads the correct log files,- support for SSL has improved to make sure mIRC always uses an SSL port when reconnecting if it was using one in the prior connection, and some issues with SSL key files and SSL root certificates have been solved,- a small memory leak has been plugged, port selection for DCC and other connections works more smoothly, and issues with random port selection, the /fserve maxgets limit, and DCC Get via http proxy/socks are solved.There are heaps of changes and improvements in this new version. Please read the help file in mIRC and the whatsnew.txt on the website to learn about the complete list of changes and their impact. Some changes are obvious, some need getting used to - please take your time to play with them and see how they work. May we invite you to the Message Board on the website with all questions? The board offers great help with everything related to mIRC!
This is just a short email about the 46 hours of downtime which began around 8pm June 2nd. It originated as a hardware fault, which took impact on the system while waiting for datacenter techs to fix. That caused a secondary problem that then took quite some time to be pinpointed, which then required a delicate method to fix completely. None of us at Edge Network have physical access to our servers, that is a luxury of larger businesses with money to spend. Sadly, a simple gaming community like us is far from gaining such a thing. We are forced to rely on the technicians at the datacenter, who in their defence are spread across hundreds of servers and support requests daily, making progress extremely slow in cases like ours. Do remember that we operate our own sites here, and feel the sting of downtime like all of you. Despite the nature of both problems, no data was lost with exception of perhaps anything in serious use when the crashes were occurring (ie. data attempted to be inserted into a mySQL table may have been lost, but not data already in the table). No email is lost, all mail servers attempt outgoing mail for up to 5 days before bouncing. Everything is operational once more as of two hours ago. Thankyou for being patient, and our apologies for the lengthy downtime.
Friday, 04 June 2004