This is only a problem when you are upgrading from old scripts, so given that this is specifically a problem with legacy code, I'm not sure what the point would be to change the way this stuff works for new versions.

The general idea is that you should no longer need multiple mirc.exe installations to run different instances of scripts. If you are doing this, you are trying to use a legacy concept with a new mIRC. It's not surprising that an old convention will break down with the new version. Use the following conventions and you should be fine:

1. You SHOULD install mIRC to its default location inside your Program Files directory.
2. You should only have one mirc.exe on your system. Do NOT install mIRC to multiple places. This is no longer necessary.
3. Put each script in separate directories, and create separate shortcuts to launch your standard mIRC executable (C:\Program Files (x86)\mIRC\mirc.exe) with custom arguments for each dir.

Specifically to point 3, you can run mIRC with the -r switch. This is what the Target part of your shortcut should look like:

"C:\Program Files (x86)\mIRC\mirc.exe" "-rC:\Users\myuser\Documents\MyScript1"

Note the "-r" part before the path. Each shortcut would point to a different path.

Now you have two shortcuts that run mIRC in two different contexts without needing two executables. Each shortcut will run mIRC with separate settings and separate scripts. If an mirc.ini file is not yet created in this path, it will be created for you.

If you *REALLY* want to have two executables, you can do the same thing and just make two shortcuts to different exe files, but again, this is not necessary.


- argv[0] on EFnet #mIRC
- "Life is a pointer to an integer without a cast"