                                          ****File server usage guide**** 

Beside HTTP and FTP there's an additional way of file transfer, using mIRC (client which connects you
to the IRC server) transfer protocol - DCC. 
The location of these file servers is strictly dedicated on certain channels. Which means that if you'll
start hosting files, or even look for them on common channels, you'll be more likely auto kicked.
Some of these channels on Dalnet containing these fserv are: #animemovies #animespot #animedivx #animevivo
Once on the channel, type the following word to the command line and send to the chan: !list
In a few miliseconds (depends on the connection speed, namely ping with the server) you should start receiving
a bunch of auto messages on the channel window. These messages can be either be intended for: File server, FTP advertising or request.
[NOTES]:
FTP advertisers announces on-line FTP servers, and posts it's IP address, login, password and port number.
        Further info on connection to the FTP some other time (or ask me on IRC)
Request messages are simply automessages established by some people who requests certain anime titles and encourage 
        people to trade with them etc..

Fileserver further:
Fileserver stats can be read out of set of parameters contained in the advetising message of the fserv.
The auto message may look like this:

    ****************************************************************************************************************
    * <Rumiko> File Servers Online | Triggers:!Rumiko & !non-anime MP3s) | Snagged:(699.9Mb in 27 files) |         *
    * Record CPS:(1.5Mb/s by ^Malachite^) | Online:(0/3) | Sends:(1/1) | Queues:(1/3) | Accessed:(26 times) |      *
    * Note:(Kenshin, eps, eva, Escaflowne, Tenchi movie, sm, total of 5 gigs.) *Polaris IRC*                       *
    ****************************************************************************************************************
Legends: 
---------
Trigger(s): represents the words which triggers the connection with the server. Pretty much self explanatory. 
            In other words, you have to send the certain word to the appropriate channel (the chan hosting the fserv).
            Afterwards, you'll be contacted by the server appealing for a DCC chat. Accept. At this point, you're pretty
            much connected to the server....but the worst part has yet to come. 
            Note: in many cases the triggers begin with a ! to keep a neat review. It is not a rule however.

Snagged: total amount of megabytes transfered from the server in number of files.

Record CPS: Highest download speed reached by the stated user. In my case I had my clone downloading so the 
            record reads merely my HDD speed, not the speed of connection ^^ the common speed is about 10 - 15 kbps

Online: number of users currently logged on the fserv. Remember though, that one does not have to be logged in to
        receive a download. Nor does he have to be present on the channel, not even on IRC server (since the transfer
        wages over their IPs) unless stated otherwise by the special fserv setting which forces user to remain in the 
        channel. 

Sends: number of allowed downloads at once. The 1/1 means that one download is in progress and the other will have 
       to be placed in the queue. As soon as the send is finished, the #1 placement in the queue will be prompted 
       to confirm his download.
       Note: Due to the lack of connection speed I can only offer 1 download at a time. Cable, DSL or T1/T3 fservs 
       offer about 5 sends at once.

Queues: pretty much explained above. Either you'll immediately start downloading (which is quite rare) or be placed   
        at the respective place in the queue. In other words, if you'll find yourself placed at the #10, you'll have to wait
        till the current downloads and the #1 - #9 in the queue finishes their download. 

Accessed: Total number of times the fserv has been accessed.

Note: Additional notes from the maintainer of the fserv.

------------------------------------------------------------
Now for the real stuff:
You're connected to the fserv and just received a welcome message.
Now for some basic commands. In practise, there'll come in handy as much as 5 of them. The following:

dir  -  lists all the files and subdirectories in the current folder.
cd   -  change directory.
get  -  prompt fserv to send you the mentioned file. It's pretty much the same as clicking on the download button.
sends - lists the current file sends form the fserv.
queues - lists all the queues placed on the fserv. 

In addition, broken downloads (whetever it was you or the the fserv/maintainer that broke it) can be resumed. Just receive
the file in the same folder as the incomplete one. You'll be asked whetever to overwrite, resume, or skip. You might wanna
hit resume I suppose.


That's just about all the basics when dealin' with file servers. Have fun...and dont curse the damn queues ^^


                                                                                     
                                                                          ----------------------------------------------
                                                                              File server usage writen by Malachite
                                                                                  malachite9@bishoujosenshi.com
