Currently, /Sockwrite using the <text> parameter will result in the <text> encoded in utf8, there is no way around this (using a binvar is not a "solution"), this implies mIRC cannot reliably be used to "send what was received", if you receive $chr(233) using /sockread name1 %a and you send it back somewhere else using /sockwrite name2 %a, $chr(233) is sent as the two bytes 195 169.
I suggest adding a -u switch to /sockwrite, which has the same effect as /raw -n, prevents bytes 0-255 from being encoded in utf8.
