Invision Warning Popup

[MiNdErAsR]

Running Invision 3.2 with mIRC 7.1 on Windows 7 home premium 32 bit. Every time I start Invision I get a warning that either I'm running two instances of Invision or I didn't close mIRC down properly the last time. Neither is the case.

Anyone else seeing this? Is there a fix as it's quite annoying?

TIA

[Riamus]

If mIRC doesn't properly close, or you are running any other scripts that may conflict with Invision, or you do not have the correct permissions on the install folder and the mirc.ini file (usually if you install to a Program Files folder), then this can happen. If you installed to a Program Files folder, then you may have various other problems as well. You should never install Invision to a path that has spaces and definitely never to a Program Files folder.

You can *manually* change the "setting" that controls that message in mirc.ini be changing Shutdown to 1 instead of 0, but you'd be better off finding out why mIRC is unable to write to the mirc.ini file, which can result in other problems. In most cases, that due to where you installed Invision as mentioned above.

[MiNdErAsR]

It's installed in C:\Invision3.2

[Riamus]

So the path isn't the problem, but the permissions may still be the cause or they may be another reason why Invision can't write to mirc.ini to make the change. Try the manual change mentioned and see if you have any more trouble. If not, I'd just not worry about it. It won't be easy to find the cause of that on your system and if it's working, it isn't really worth the effort.

[MiNdErAsR]

Interesting. Shutdown was already set to 1 in mirc.ini. I changed it to 0 and still get the warning msg. Changed it back to 1 and didn't get the warning msg. However, after closing invision and reopening, shutdown was set to 0 and I got the warning msg again.

Thanks for responding.

[Riamus]

You can try a clean install of Invision and see how that works. Maybe something got messed up on your install. It's strange that it was giving the popup when it was set to 1. The script checks if Shutdown != 1, then display the warning. So if it equals 1, there shouldn't be a warning. As to why it was 0 after shutting down, it is probably related to why it showed when it equaled 1.