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.
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, either in multi-user group conferences or in one-to-one private discussions. It has a clean, practical interface that is highly configurable and supports features such as buddy lists, file transfers, multi-server connections, SSL encryption, proxy support, UTF-8 display, customizable sounds, spoken messages, tray notifications, message logging, and more. MIRC also has a powerful scripting language that can be used both to automate mIRC and to create applications that perform a wide range of functions from network communications to playing games. MIRC has been in development for over a decade and is constantly being improved and updated with new technologies.
MIRC's default toolbar is now customizable through a /toolbar command. You can add, move and delete buttons, add your own icons, and of course, attach your own commands to them. By popular demand also a treebar has been added. This lists network connections with channels, queries and other open windows, much like the switchbar.
It behaves like the switchbar in many ways as well. You can expand and collapse trees, just like you would expect. Right-clicking on an item pops up the usual menu for that window.
Right-clicking in an empty area of the treebar pops up a menu with various display options. The treebar width can be set by dragging the border with the mouse, and jsut as with virtually all other windows the background and text colors can be set in the colors dialog. Just like the toolbar the treebar can be repositioned to the top/bottom/left/right of the main mIRC window! In the previous version UTF-8 support was added. In this version several UTF-8 related bugs are fixed, including bugs with text wrapping and copy/pasting from UTF-8 'display' or 'encode' enabled windows, and bugs relating to the order in which SJIS/JIS and UTF-8 encodings are applied.
Much more important is that UTF-8 support has been greatly enhanced in this version of mIRC to allow people all over the world to chat in their own languages, with their own fonts, with a lot less hassle then ever before. To do so support for font substitution/font linking has been added. This allows mIRC to display all characters needed, regardless of the font you are using, assuming you have the required fonts on your system, somewhere.
End
MIRC will try to match font sizes etc. To speed up the process Khaled has implemented his own caching routines to enable fast font/character referencing. Of course all buggies and most of the other comments and remarks we received after the previous release have been addressed. Various other changes include: - better support of XP and classic themes, - faster re-wrapping of text, - fixes for various $regsubex and $regsub parsing bugs, for a flood protection bug, for some agent speech bug, and for a bug with the find dialog in desktop windows, - and mIRC now stores servers that were connected to successfully to prioritize future server connection attempts.and a lot more. For experienced users and scripting enthousiasts this new version has heaps of changes and other new thingies to play with.
We encourage you to explore the new or improved identifiers, and the new events that have been added.
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. I just made about this subject.
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).
Free download slacker usb station refresher Files at Software Informer. StationRipper is a web based program used for recording and downloading online music. Slacker USB Station Refresher (slacker.tray.exe). Flexible Resizing Re-size your player to be exactly the size you want. Keep it out of the way while you are working. Slacker USB Station Refresher is a program developed by Slacker. It adds a background controller service that is set to automatically run. Delaying the start of this. Slacker usb station refresher. 3Install the Slacker USB Station Refresher. Hardware or software to play Slacker Radio stations on. Want on your Slacker G2. •Installing the Slacker USB.
Mirc 6.21 Scripts
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. 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'. 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.
I can leave the script and DLLs in program files mIRC, but user data like keys will be owned by invidual users. Also, default settings files should be stored in program files mirc as a template for when new users are created. Just a few ideas. Edit: I've been using mIRC since 4.5, Edited by CakerX ( 13/04/07 12:48 AM) #174820 - 13/04/07 02:07 AM Re: identifiers for multi-user mode Planetary brain Registered: 03/08/04 Posts: 7252 Loc: Ontario, Canada.