#50+retired on DALNet - How to... MultiTask mIRC

#50+retired onDalNet
How To..... MultiTask mIRC

Definitions:
multi-tasking: Running two copies of mIRC simultaneously, either on the same or on different networks
network: A worldwide system of internet computers linked together under one administration, such as DALNet, NEWNet, EFNet, etc.
ISP: Internet Service Provider, the people whose phone rings when your modem dials in and logs on
IP address: The number unique to your computer assigned by the ISP when you connect by modem
clones: Two or more nicknames with exactly the same IP address

Have friends on DALNet... and... friends on EFNet? Ever wish you could talk to them both simultaneously? Here is one way to do it: by running two copies of mIRC simultaneously.

With Windows 95

The 32 bit system of Windows 95 has no problem running simultaneous multiple copies of a program. If the mIRC executable (.exe) file in your mIRC directory is named mirc32.exe, then you are using the 32 bit version of mIRC. With mIRC already running, simply double click on the starting icon again and the second copy will boot up and run.

Note: It is not a good idea to modify, edit or otherwise change scripts and or mIRC settings while running two copies simultaneously. Not only is it confusing to remember which one you've changed and which one you haven't, but changes made in one do not affect the other. Furthermore, when you exit the program altogether (i.e., shut down both copies) the .ini files are updated from the last copy you exit. So, if you make all your changes in the first copy, exit it, then last of all you exit the second (unchanged) copy, all your changes will be overwritten by the unchanged second copy when it exits! Don't say we didn't warn you...

With Windows 3.1 (3.11)

The Windows 3.1(1) system is a native 16 bit system, and cannot run two copies of the same program simultaneously. If the mIRC executable (.exe) file in your mIRC directory is named mirc.exe, then you are using the 16 bit version (even if you run it in Windows 95). The mirc.exe file cannot run two copies of itself (even if you are using one of the win32s patches). However, there is another way to run two copies of mIRC simultaneously and "fool" Windows: Simply make a second copy of the mirc.exe file in the mIRC directory but change the name to mirc2.exe or mircc.exe or something similar. If you then make another startup icon for this second copy, you can double click on it with a copy of mIRC already running and the second copy will boot up.

Note: It is not a good idea to modify, edit or otherwise change scripts and or mIRC settings while running two copies simultaneously. Not only is it confusing to remember which one you've changed and which one you haven't, but changes made in one do not affect the other. Furthermore, when you exit the program altogether (i.e., shut down both copies) the .ini files are updated from the last copy you exit. So, if you make all your changes in the first copy, exit it, then last of all you exit the second (unchanged) copy, all your changes will be overwritten by the unchanged second copy when it exits! Don't say we didn't warn you...

Using Both Copies Simultaneously

Since, in either Win31(1) or Win95, the mIRC programs function independently of one another, you must connect each to a network manually. That is, connecting with the first copy leaves the second running copy of mIRC still unconnected. Since each running copy connects to an IRC network independently, it is possible to connect to two completely different networks, or even to connect twice to the same network.

Connecting to Different Networks

When you connect to two different networks, the people in one network cannot talk to the people in the other network, but you can cut and paste between networks. This fact makes possible the use of special scripts that "interconnect" networks to allow people on EFNet, for example, to chat with people in a channel on DALNet. We'll leave you to figure that one out on your own, but be aware that most IRC network administrators take a dim view of this practice.

Once connected, simply resize and rearrange each copy of mIRC and the windows open in it so that you can see them both, or so that you can go easily back and forth between them. The Win95 task bar is helpful in this regard, and with Win31(1) it is best to switch between copies using the <ALT+TAB> switch (hold down the ALT key and press TAB until the program you want is selected, then let up on ALT).

Of course, you cannot use the same nickname twice on the one network, but you can be CutiePie on both EFNet and on DALNet (if it isn't registered on one or the other). mIRC will automatically use your alternate nick when you log onto the same network twice (this is called cloning, and has some cautions to go with it... see below)

Clones Get Killed

When you appear twice on a network, with two nicknames but from a single ISP connection, then you are "cloned." Cloning is a favorite practice of IRC hackers and pranksters, and the cloning system is used to "protect" the hacker while sniffing out netsplits to take over a channel, or flooding people off one place or another. Clones are different animals than "ghosts." A "ghost" occurs when a user loses communication with the server for some reason and must reconnect. Because communication was lost, the user's original nickname remains on the server after the new connection occurs... the "ghost" of a now lost connection. Eventually a "ghost" times out and is gone; clones don't time out.

Clones are simply intentional duplicate connections to a single network from a single ISP connection, and can be used for a variety of purposes... good and bad. For example: if you want to test a new script, but don't want to disturb an already occupied channel and don't have a friend handy to test with, you might want to "chat" with your clone, or test scripts with yourself. But clones are often used by hackers to occupy dummy channels that receive "relayed" information from a channel that the hacker is raiding. Clones can also be used by remote control to flood other users without looking like you're the one doing the flooding. These are not good practices, but because they are so prevalent, most IRC Server administrators keep a close watch for clones and immediately "kill" them (kick them off the network). Repeated cloning on some networks can get you permanently banned.

We check the #50+retired channel regularly for the existence of clones and if any are found, they are investigated. Clones of unknown persons will immediately be kicked, and persistent cloning can result in our reporting the clones (with appropriate log files) to the DALNet administrators. We DO NOT RECOMMEND CLONING on DALNet, and other networks are risky as well. It is nevertheless useful at times to be on two different networks at the same time. Just use good sense and you'll be both secure and network friendly.

See you on #50+retired,

Smitty (ac5c_okla)
_Bubba (wa5nfp)

| Home Page | General Info | The OPs | How To Info | F.A.Q. | Scripts | Channel Users |

This page is maintained by Smitty, (ac5c@oklahoma.net) and was designed by _Bubba (ahbaker@theologie.uni-erlangen.de). Both can be found and/or contacted on DALNet's #50+retired channel, or through DALNet MemoServ. Absolutely nothing here is copyrighted by us, and it probably wouldn't matter even if it were. Take whatever you want, and if it will make you feel any better to take credit also for our original work we invite you to go ahead... we can always make more. If you have praise or contributions for the page, please email us right away. For all other matters please click here.