is there a way to get mIRC to shut up if it cant find a command or whatever...
for some reason lately, if it cant find an alias, word... it keeps saying it until i turn mIRC off
and its really annoying
and btw, im on a laptop and ctrl+break doesnt do anything*

Sounds like you've got a buggy script of some kind.

My mIRC will say an error once. It sounds more like you've got a while loop or a timer calling the bad command over and over again.

I agree to some extend.

I once had a clone kick remote, but wanted to debug, so rather than using /kick, I replaced it with /msg # /kick to output what the result will do.

Big mistake on my part.

Because the while loop for when the user goes down, it never goes down.

So I had to /part the channel.

And display to me in my status window my output to the channel.

Turning off remotes didn't help.

Deleting the code from my remotes didn't help.

Ctrl Break'ing doesn't permanently stop it.

Only disconnecting from the network, then reconnecting, helped.

Unfortunately, disconnecting from the network did something that /remote off, deleting the script, and Ctrl Break didn't do - and I would like to know how to do that individually.

Basically, there doesn't seem to be a way to cancel a while loop except rebooting mIRC and never triggering that while loop again.

i know, its a while loop, or timer but its really annoying
and it eventually shuts up after about 100000 messages
and i like to keep my stuff neat(staus clear, etc..)

..

So you know what's causing the problem..

..

Yet you decide it's easier to bitch about the bad/mistaken coding, than to actually *FIX* the code?

..

I'm sorry, I'm having a bit of trouble understanding your logic here..

I've already had this problem in the past, and recently, have it again, and now i know how to reproduce something like it
It can happen when you miss a } or { in your code, because mirc continue to run the script even if the number of { } are not the same and //alias can be executed but not as you want.I don't have time to make something to reproduce what i'm saying but i'll try later

why not just remove the while loop, or fix the problem ?

Because that would be too intelligent. It would be too logical.



As far as I know - that never happens. For as long as electricity runs into your computer...

But since my status window goes up to 10,000 lines (and I have $line($active,0) lines in my titlebar), I possibly won't know that. But I know a bad accidental while loop after a night's sleep still continues the next morning.

-Neal.