Khaled
I would really advise against removing the timeout completely - because then the only route out of it is either Ctrl-Break (which might or might not work) or killing mIRC process completely and restarting it. Instead I would suggest:
1. Make Ctrl-Break work to interrupt it.
2. If you can do one, set a timeout of (say) 60s. If not, make a timeout of (say) 30s. This would be the amount of time a user might realistically wait before deciding to kill the mIRC process and relaunch it - an action that should IMO be avoided if at all possible.
3. Alternatively, if you can, if you don't get a response within (say) 10s, you could display some sort of pop-up which explains what is happening and allows the user to cancel.
P
