mIRC Home    About    Download    Register    News    Help

Print Thread
#120208 15/05/05 08:10 AM
B
BrokenDownFlier
BrokenDownFlier
B
My problem is that mIRC doesn't keep the custom nick list color settings from the address book each time I reconnect. I thought it was an Invision problem but they told me it wasn't their's and suggest I post here.

At first I tried seeing if I could edit these settings in the ini files but don't know where to look. mirc.ini calls up addrbk.ini but that file doesn't exist and I've been told it's no longer used by mirc.

Would someone please inform me of the location of these prefence settings and how I can go about flushing or forcing mIRC to save my choices? Default settings has no options for ~ or &.
Thanks in advance.

Config:
Win98SE as updated as possible with all the MS updates
**yeah I know it's ancient but for too many reasons to list, I still need it.**
mIRC v.616
MOO 4..0.4 build 1
Invision 2.0 Build 3515
SystemInfo by C}{$ Version 1.5-r4
WindowsInfofor SystemInfo by C}{$ Version 1.5-r4
WinAmp2mIRC by Task/C}{$/Deadpool - 1.3)

Joined: Dec 2002
Posts: 206
H
Fjord artisan
Offline
Fjord artisan
H
Joined: Dec 2002
Posts: 206
The color settings (alt+b -> colors tab) seem to be in the mirc.ini under the cnicks section. Perhaps mIRC can't write to the ini file for some reason (read-only, full hdd, no permission, etc). Depending on how you run it, the settings might not even be in the mIRC folder. To find its location, you can type //echo -a $mircini. mIRC should automatically flush all settings to the ini file during a normal exit, but i believe that you can also use /saveini to update them manually. If it seems to lose those settings when you disconnect/reconnect, and not just when you reopen, it is possible that you have some odd commands in perform or in an on connect script, perhaps utilizing the /cnick command.

B
BrokenDownFlier
BrokenDownFlier
B
After reading your post I tried the /saveini and it worked once then reverted to default. nothing in the mirc directory or its subs have readonly attribs and there aren't any other accounts on this computer to deny permissions to or be denied by.

I did find out that it's an invision problem after all. their addon alters or sets a forced reset in NickListCLR in ialias2.mrc line 350. I've modified it a bit and hope that does what I need it to do.

Thanks, and I'll let you know if it works.

Joined: Oct 2004
Posts: 8,061
R
Hoopy frood
Offline
Hoopy frood
R
Joined: Oct 2004
Posts: 8,061
Lol. It isn't an Invision "problem." Set your colors for the nick list in the Main Settings > Colors dialog. Most settings that are set in Invision dialogs cannot be set from mIRC itself. And, if you don't understand that, I wouldn't go modifying the script. smile

Joined: Apr 2003
Posts: 701
K
Hoopy frood
Offline
Hoopy frood
K
Joined: Apr 2003
Posts: 701
Invision is the problem in this case, and probably many others too. If you script something that overwrites mIRC settings without asking, you're asking for bug reports...

Joined: Oct 2004
Posts: 8,061
R
Hoopy frood
Offline
Hoopy frood
R
Joined: Oct 2004
Posts: 8,061
Ask yourself this, then... if a script is a full script that allows all mIRC settings to be changed from within the script, is that wrong? It really isn't a problem, so much as it is made to do that for a reason. Now, you can always say you don't like that... but you can't really call it a problem or a bug. I've seen many full scripts overwrite mIRC settings for various things like that. It's rather common.

Joined: Dec 2002
Posts: 206
H
Fjord artisan
Offline
Fjord artisan
H
Joined: Dec 2002
Posts: 206
Whether you call it a problem or not, it is clearly due to invision. My opinion is that it is a problem, and therefore, I would call it an invision problem. It's one thing to allow settings to be changed from an extra place, but it's something else entirely to overrule settings changes made elsewhere. It should work with mirc's own internal options dialogs, not against them. Having done volunteer mIRC tech support for 7 or 8 years, I know how difficult it is to help someone when you have no idea what their script is doing behind their backs. Telling them to go here, and change this option doesn't work when their script says "no." Sometimes there is nothing that can be done other than telling them that we can't help unless they ditch the script.

Additionally, to say that something is common does not make it right. I won't bore you with examples. If you don't want to call it a bug, that's fine. Just call it a "hidden feature," and maybe we can all move on to problems that are caused by mirc.


Link Copied to Clipboard