The -portable switch will work as advertised:-) It will make mIRC avoid use of the registry. However that has nothing to do with folder locations. In the next version, if you want to make mIRC avoid the registry and to use the executable folder for storage, you would specify the -portable and -r switches (I've modified the -r behaviour in the next version so that -r without a path will default to the executable folder). If you don't specify -r, then mIRC will check if mirc.ini exists in the executable folder. If it does exist, it will use it. If it doesn't exist, mIRC will use your Application Data/mIRC folder for all storage. That said, I may change -portable so that it 1) avoids the registry and 2) uses the executable folder.

I would then need to add a new command line switch -noreg to avoid use of registry separately for users who want that. #174338 - 05/04/07 10:01 PM Re: mIRC 6.21 Requires Elevated User Privileges [] Bowl of petunias Registered: 05/04/07 Posts: 2.

MIRC is a full featured Internet Relay Chat client for Windows that can be used to communicate, share, play or work with others on IRC networks around the world. MIRC 6.21 was either harmful to your computer or it was pulled from our servers for another reason. We apologize for any inconviniance this may have caused.

I just made about this subject. Cara Install Openvpn Di Windows Xp. Whoops, didn't see this thread. Anywho, Khaled and others, you don't have to force all users to separate their executables from their data files. You just have to provide the option, for those like me, who want to do that.

=) Here's a scenario: the installer prompts the user if this shall be a system-wide installation for all users, or a local installation for one user. System-wide installations will be the default, and support all the Windows standards and recommendations. A 'local' installation will be just like the current default behavior, with the data files in the same directory as the executable. The situation I just described is kind of similar to the solution Winamp found for this same problem. The winamp installer asks the user if she wants to have shared settings for all users (old default behavior) or separate settings for each user (new behavior). Anyway, glad to see that you're working on it. Just be careful with the creation of shortcuts and such.

A.lnk in the All Users profile can't be deleted by a normal user. But if there isn't a.lnk in there, users created after the installation won't have a shortcut. So you have to add a.lnk in the Default User profile. Hope this helps. --Dave Loyall Conway, Arkansas, USA #174352 - 06/04/07 06:43 AM Re: mIRC 6.21 Requires Elevated User Privileges [] Fjord artisan Registered: 06/07/03 Posts: 655. Here's a scenario: the installer prompts the user if this shall be a system-wide installation for all users, or a local installation for one user.

System-wide installations will be the default, and support all the Windows standards and recommendations. Spectrum Survey 4 22 Keygen S. A 'local' installation will be just like the current default behavior, with the data files in the same directory as the executable. Not sure i agree with your logic there, the correct installer options in such programs are more along the lines of 'for this user only', 'for all users'. Hiren`s Boot 15.1 Rebuild V2.0 Iso on this page. Where 'for this user only' uses the users application data folder, and 'for all users' uses the 'all users' application data folder. I think mirc should have a little more flexibility than that however, the options should include. - install and configure to use the users application data folder (default) - install and configure to use the all users application data folder - install and configure to use a self contained folder (all files in the mirc executable/installation folder All corresponding shortcuts (if any) that are made should reflect this with use of the -r flag when neccersary. When upgrading, mirc should not move your application data anywhere unless you specifically tell it to, have it selected by default if you want, but makes sure you are able to turn it off so that an upgrade leaves the files alone (apart from baking up to /backup/ if required of corse) I personally prefer such programs as mirc to be self contained, it is often neccersary to larger programs for shared files and application data to be seperate from the binaries, but this is not the case with small programs, therefor it should not be forced during the installation.

(i often backup mirc and other smaller utilities that are used on a daily basis, which as you can guess is partially why i prefer to use the self contained method). With multi-user mode, will you release identifiers to help script in multi-user mode, so scripts can store settings in their user specific settings. Specificlly I could use $osuser(windows user name) and $osuserhomedir(user's home dir) $osusermircdir(where their mIRC settings are) so many users can use the same script with diffrent configurations. This is a hot topic for me, because I am working on an encryption script.