You seem very eager to be outraged about this.
Well, I think that's the right of a customer if there is such a problem with the product which can only be noticed after buying the product.
Who says there's no interest in the issue?
The number of people responding to your post is completely irrelevant here seeing as there's only one person on these boards who has the ability to effect changes in mIRC - in which case it's entirely possible he hasn't even read this thread yet seeing as it's been less than five days since your original post. There's no need to get wound up over it.
Yes, probably I am expecting too much from a commercial product. Additionally it's not really clear to me who in this board can give "authoritative" answers. There is an answer from argv0 which proposes some workarounds. Some might find that acceptable - some might not. I don't know if the answer of argv0 is somehow official and the final decision of mIRC development "team".
And for the record the only other IRC client I've tried in the last few years is XChat (on Linux). It was an unpleasant experience to say the least; I guess it's designed with a very different userbase in mind than mIRC.
Thanks - seems to be identical to my experience. I don't consider XChat to be very user-friendly (except for geeks) ;-). I am fine with it but mainly non-it-expert users might not.
So let's see what happens, probably there are some more proposals or I am lucky and this single person who has the ability to effect changes will give at least a statement if this is going to be enhanced/fixed. I think it's absolutely fine if I look for alternatives meanwhile.
More than 100 reads within these five days also show some "public" interest in this topic. I assume it's not only affecting roaming profiles but also all users transferring their settings manually or automatically to another machine.
Thanks again for all your input.