mIRC Homepage
Posted By: Masoud A possible bug in /run command - 22/10/12 05:18 PM
I'm getting this error since I upgraded my mIRC to the latest version (v7.27). It used to work just fine in the previous version.
Code:
* /run: unable to open file 'ping 4.2.2.4 -t'


Although, I'm not sure if it's a bug or what, just felt like reporting it. It's no big a deal.

P.S.: "ping 4.2.2.4 -t" works just fine when I type it in the Run itself. It just gives me this error when I'm trying to execute it using mIRC.
Posted By: KindOne Re: A possible bug in /run command - 22/10/12 05:22 PM
Seems to be related to this change? https://forums.mirc.com/ubbthreads.php/topics/239030/run#Post239030
Posted By: Masoud Re: A possible bug in /run command - 22/10/12 05:27 PM
I don't think so.
Posted By: drum Re: A possible bug in /run command - 22/10/12 05:47 PM
It might be related.

In any case, you can get around the issue by doing this:

/run ping.exe 4.2.2.4 -t
Posted By: cage Re: A possible bug in /run command - 07/11/12 01:25 AM
Originally Posted By: drum
It might be related.

In any case, you can get around the issue by doing this:

/run ping.exe 4.2.2.4 -t


I had a similar issue it seems you must provide the full filename with extension now.
Posted By: argv0 Re: A possible bug in /run command - 07/11/12 08:47 AM
Yes, it is related.
Posted By: Khaled Re: A possible bug in /run command - 07/11/12 08:57 AM
That's right, the new version requires you to either enclose the command in quotes or to use an extension, so that mIRC can clearly tell where the command and parameters begin and end. Previous versions of mIRC guessed which part was command or parameter if the command line was vague (which could lead to unpredictable results). To ensure backwards compatibility, the next version will revert to the previous method.
© mIRC Discussion Forums