Connection Timer On Linux

Well ill explain real quick my problem...

I run mirc in WineHQ on Ubuntu Linux and if/when i disconnect from the net, my mirc will not reconnect like on windows....

I have tried to do a timer on a basis of 2-3 hours to do a ping to myself and other, but that will not work. Only thing i found is just type a period in a chatroom and itll reconnect, but thats not a real cool idea for a timer, just woundering if anyone else have tried this or have any ideas on a fix for it... ty in advance

You have the auto reconnect option ticked in the options dialog?

yea i have checked about 5 times to make sure it stays clicked and still just ignores the disconnect :/ confusing

 On *:DISCONNECT: server

would that work on every server :/

ill sure throw that in and see if it helps...

I have tried notifing, ping, and a few more but it seems that mirc doesnt notice when i disconnect

if you haven't found a fix i'll boot into ubuntu and see what i can get.. the on disconnect command may not be the best to check cause there are times when mirc doesn't seem to know you are disconnected until you try to send something like a . or other command. I have a couple ideas I can try but it will probably be sunday before i can test them.

ill be on here most all sunday, and ill sure help w/ whatever, i am tired of coming home and seeing i have been offline almost all day..lol

well come to find out Ubuntu has 'so called' features to stop hacking, blah blah and some programs including wine dont run at full potential... SO i am gonna swap to Gentoo or Fedora10 tonight or tomorrow and see if that fixes a few things... + Ubuntu will not install and build the newest ruby... i hate SELinux

can't use just start up wine with full admin rights?

in terminal... sudo wine?

wine works fine, mirc just doesnt notice when its disconnected for some reason.

hmm... from memory, vincula used noop command (basically its suppose to stand for no operation), but a server didn't have that, so it would come back with a "noop command invalid".

you could replicate this idea?

to do this, have a timer which sent "noop" to the server. when sending noop, set another timer which would be similar to a reconnect or something. and if the noop isn't responded to within say 15 seconds, you can predict you are disconnected from the server, and allow the 2nd timer to continue. if it did receive something back, then you would cancel the second timer.