I see your point, but... well what's confusing me is exactly what's reporting to mIRC that this silcroadxxx.onion address is 192.x.x.x?It can't be Tor. Tor shouldn't have any more control than mIRC does over the system. Unless you're running it as admin in Windows? Does it require that?So mIRC makes a function call to the operating system to resolve the human-readable URL into the 123.456.789.012 numeric form. It shouldn't be trying to resolve that itself, it needs to call the OS because if two people try to do the same job they['re going to do it slightly differently and then everything gets all fucked. So if it isn't Windows that's registering this address system-wide, and reporting that to mIRC when queried... which mIRC then uses to connect to 192.x.x.x... who is?If that's the way it works, then it'll break mIRC. It'll always try to connect to a phantom 192 address that doesn't exist instead of 127.0.0.1:9150 the way it should. I just don't see how that mapaddress does anything but tell Tor to tell Windows to tell mIRC to never connect to the right place?I'm sure I'm missing something obvious, just don't see what? And the whole "timing out" thing is what I'd expect when you try to connect to a black hole at an address that no one's listening at...?