:::GUIDE:::

What is IRC?

Internet Relay Chat (IRC) is one of the most popular and most interactive services on the Internet. Sure, the Web is nice for finding info and E-mail beats snailmail hands down, but when you've been wondering 'where the others are?', then IRC is what you're looking for.
IRC is the net's equivalent of CB radio. But unlike CB, Internet Relay Chat lets people all over the world participate in real-time conversations. IRC is where the Net comes alive! Using an IRC client (program) you can exchange text messages interactively with other people all over the world. Some of the more popular chat clients are mIRC, Pirch, and Virc for Windows and Homer or Ircle for Mac's. What program you use doesn't really matter; all of them connect to the same chat networks. When logged into a chat session, you "converse" by typing messages that are instantly sent to other chat participants.

What you need?

You need an IRC client now to connect to an IRC server, and give IRC a try. There are several clients available... what program you need depends on what Operating System you use. mIRC is an IRC client developed for Windows. When you use UNIX, DOS, OS/2, or a Macintosh you will need some other client.
You can download mIRC from here:
http://www.mirc.com/get.html

Join Our Chan

Ok. You have the program, now. Install and open it. In the main window type:
/server irc.irchighway.com
and (when connected)
/join #tarzan-episodes
or simply click here.
That's all, you're now in the #tarzan-episodes channel!

Downloading the files

*fservs*
Fservs allow you to browse someone's shared files - the way that are on their disk, meaning in directories and subdirectories. The general appearance of a fserv ad is:

[Fserve Active] - Triggers:[/ctcp name_serv pippo & /ctcp name_serv pippo2 & /ctcp name_serv pippo3] - Users:[0/3] - Sends:[0/2] - Queues:[0/40] - Record CPS:[29.8kB/s by i_am_a_leecher] - Message:[Please upload to me the internet] - SysReset 2.53

This would be the fserv ad of the nick name_serv. name_serv has three triggers - triggers are what you type to get into a fserv:

/ctcp name_serv pippo
/ctcp name_serv pippo2
/ctcp name_serv pippo3

Every trigger points to some shared directory on name_serv's disk. Triggers that start with /ctcp are called silent triggers - when you use them only you and name_serv can know that.

IMPORTANT NOTE: Copying and pasting in mIRC is somewhat different from the traditional ctrl+c, ctrl+v. You copy a text by simply highlighting it in the channel - position your mouse on the first character of the text, click the mouse button, drag to the end of the text and release the mouse button. You don't need to tell it to copy - it's already copied. Then you go to the command line (the line under the channel where you type everything), and paste it with ctrl+v.

You can only use one trigger at a time. Sometimes triggers are descriptive, sometimes just plain nonsense so you'll have to check what's on them. All CTCP triggers have the form:

/ctcp {serving_nick} {some text}

Inside a fserv
When you paste the trigger correctly, then you will get into the fserv - a new window opens:

DCC Chat session
-
Client: name_serv (xxx.xxx.xxx.xxx)
Time: ***
-
Acknowledging chat request...
DCC Chat connection established
-
<name_serv> -=SysReset 2.53=- FileServer
<name_serv> NOTICE: If you leave this channel all sends, gets, and fservs will be stopped.
<name_serv> Commands: cd, clr_queue, clr_queues, dir, exit, get, help, ls, queues, quit, sends, stats, who
<name_serv> Transfer Status: Sends:[1/1] - Queues:[5/17]
<name_serv> This server will auto-close after 4mins.
<name_serv> mIRC v6.03 File Server
<name_serv> Custom Message: Welcome to my fserv, be nice to it.
<name_serv> [\]

This is a DCC chat session - a direct connection between you and name_serv. There is some information there about what commands you can use on the fserv, how many sends and queues are there, sometimes an auto-close message, and sometimes a custom message by name_serv. Different fserv scripts say different things but most of the commands are the same.

Commands
'dir' and 'ls' will give you the list of the directories and files on the fserv. dir is more common since it 1.always works and 2.gives a more legible list.

<you> dir
<name_serv> SysReset 2.53
<name_serv> [\*.*]
<name_serv> Trailer
<name_serv> VCD
<name_serv> XVID
<name_serv> End of list.

To access a directory you type 'cd {directory name}'

<you> cd vcd
<name_serv> SysReset 2.53
<name_serv> [\vcd]

Now that you are in the directory, you type 'dir' again to see the files in that directory.

<you> dir
<name_serv> SysReset 2.53
<name_serv> [\vcd]
<name_serv> tz1x01.mpg 455 mb
<name_serv> tz1x02.mpg 454 mb
<name_serv> tz1x03.mpg 458 mb
<name_serv> tz1x04.mpg 459 mb
etc., etc.

There could be directories inside of directories, and for accessing each of them you type cd {directory name}. To go one level up, that is to the directory you came from, you type 'cd..'
When you have decided what files you want you highlight the filename to copy it, while you are in the directory, and use

get filename.ext (without the filesize)

A fserv might tell you at the beginning how many queues you are allowed to have, or you just queue files until it tell you that all of your queues are full.

If you paste the filename correctly, the fserv will either tell you something like 'Sending file' or 'Adding your file to queue slot X'.

The basic fserv leeching ends here - once you have requested your files you type 'exit'

<you> exit
-
DCC session closed

Other commands:
'sends' will give you information about the ongoing sends on a fserv
'queues' will list the queued files, or just tell you how many files are queued
'clr_queues' lets you remove all your queues
'clr_queue X' lets you remove one of your queues (you must type 'queues' before that to see which number it is (X)

*xddc serv*
Unlike fservs XDCC are not whole directories shared but just selected files, all of which numbered. A typical XDCC ad:

-xdcc_serv- [XDCC active] You have access to the following pools: pool1, pool2. Use: /ctcp xdcc_serv XDCC LIST <poolname> to list XDCC Files for one XDCC pool. - SysReset 2.53

XDCC triggers are not listed each by itself. If a person has more than one XDCC trigger you still use the same XDCC LIST command and then specify the 'XDDC pool'.

Generic trigger: /ctcp xdcc_serv XDCC LIST [poolname]
Trigger #1: /ctcp xdcc_serv XDCC LIST pool1
Trigger #2: /ctcp xdcc_serv XDCC LIST pool2

Once you enter this you will either get a list of files notice`d to you (means you will see them in the channel window).

In Channel Window
-trala- [XDCC Active] - Sends:[1/1] - Queues:[8/10] - Record CPS:[41.8kB/s by i_am_a_leecher] - Files Sent:[340] - Upload Speed:[32.6kB/s] - Current Bandwidth:[32.6kB/s] - SysReset 2.53
-xdcc_serv- [#1] [455.5MB] - tz1x01.mpg [1 Gets]
-xdcc_serv- [#2] [456.8MB] - tz1x02.mpg [5 Gets]
-xdcc_serv- [#3] [455.7MB] - tz1x03.mpg [1 Gets]
-xdcc_serv- [#4] [454.7MB] - tz1x04.mpg [0 Gets]
-xdcc_serv- Usage: /ctcp xdcc_serv XDCC GET pool1 #<pack number>

XDCCs usually have the instructions on how to request a file somewhere in the listing - either at the beginning or at the end. Files are not requested by the filename but by the number, i.e. you don't use

The generic XDCC commands:

/ctcp {serving_nick} xdcc list [poolname]
(sometimes there is just one pool, so there isn't the need to name it)

/msg {serving_nick} xdcc list
/ctcp {serving_nick} xdcc get #X
/msg {serving_nick} xdcc send #X

XDCCs behave in many ways depending on the script, so be sure to read the instructions it will give you.

*tdcc*
A TDCC is a trigger for just one file. You don't browse anything, you don't choose anything. You just type the trigger for that one file.

-tdcc_serv- [TDCC active]- Trigger:[/ctcp tdcc_serv !Tarzan] - Description:[tz1x02.mpg] - Size:[531.4MB] - Sends:[1/1] - Queues:[3/10] - Download Speed:[10B/s] - Requests:[5] - SysReset 2.53

The 'Description' says what file the TDCC is serving, and that is what you get queued for.