|
|
Writing this in the hope it helps bring more fserves to Kimi's channel #dewdrop - you've got no excuses now about not knowing how to share stuff on IRC! 
First off, this tutorial is for Sysreset 2.50 - some details might not match up with older versions of the script. This script is available at http://www.sysreset.com and is IMHO one of the best Fserve scripts in terms of functionality - only Invision has more functions, but that script has way too many... and Polaris just doesn't measure up when it comes down to it.
I'm going to assume you have some basic knowledge of IRC, if you don't read the related "How to become an IRC leech" thread.
First off, let's decide which form of a server you want to make. All 3 forms considered:
1. Fserve
The most basic sort of server, go with this one unless there are some special conditions which the other 2 would be better suited for. It's the most versatile and offers the most commands to people using it, and there's no limit to the number of files you can serve with this.
2. TDCC
TDCC offers single files only, so instead of offering people a look through your stuff you offer just a few files on TDCC. Note that it's not recommended to use any more than 3 TDCCs, the number of ads gets annoying really quickly. Most often used for serving a new release.
3. XDCC
Experienced leeches love XDCC bots, because usually the people who offer stuff on XDCC have insanely fast connections. Use this for a small number of related files, and if you're confident of your connection speed. Recommended for manga zips for example, serving anime on XDCC usually is leech bait since people expect you to have a connection that can send real fast.
Decided on the type you want? Good. But before we step into setting up the fserve, a quick reminder: It's a good idea to sort out your stuff nicely and plan the directory your Fserve will share, moving private stuff away from it is a good idea. It's a VERY VERY bad idea to start your fserve in a directory like C: or \My Documents or worse still, \Program Files. 
Oh, reminder from equus peduus: it's not polite to share your downloads folder filled with your incomplete files... neither is it a good idea as you might run into access problems involving files being used by more than one program at a time.
On to the main thing now.
1. Set up mIRC
You should know how to do this already, install and do the basic setup for mIRC.
I'll start with the setup for the individual sections first then finish with the general options since that covers all the different types of servers.
We'll start by going to the Sysreset menu and choosing Fileserver manager.
2a. Fserve Setup
This part covers the "File Server Triggers" setup - for setting up an fserve.
Simple to do, just click the "Add" button, enter a trigger text (your chance to be witty!) and click okay, choose a welcome file and click okay or just click cancel (the welcome file is a little text file that greets the users when they access the fserve - useful for telling them stuff), then choose a root directory and click okay.
Be carefull about choosing the root directory, your fserve will start in that directory for the trigger you just made. For example if you want to serve anime and you have your videos all sorted nicely in separate directories in a root directory "Anime", you would choose "Anime" to be your root directory.
Repeat as necessary. "Up" and "Down" can be used to change the order of the triggers, "Rename" to change the trigger text, "Delete" is self-explanatory. Also, once a trigger is created you can highlight it and choose the welcome file and root directory from the menus under the Triggers section.
In Sysreset 2.50 there's a few options you can set for each trigger, they're explained here (moving top to bottom, left to right):
1. Enabled
Determines if a trigger is enabled, ie whether it shows up in your ad and whether your Fserve will respond to this trigger. This makes it possible to enable and disable certain triggers.
2. /CTCP Trigger
This makes the selected trigger a /CTCP one, which sometimes is also known as a "silent" trigger. Read the rules where you serve, it's sometimes necessary. Also prevents inane triggers from interrupting people chatting.
3. Access mode
This enables you to restrict some triggers to Ops/Voices only or Ops only.
4. Assign Specific Message
Allows you to put a specific description for the selected trigger.
5. Global: Respond to !list
Leave this on, if you turn it off your Fserve will be completely silent, meaning unless you tell someone the trigger nobody can find out about it.
6. Trigger Channels
You can decide which channels your triggers appear in, and make different triggers for different channels. Leave it at "All Channels" if you don't bother about it, or uncheck that and input channel names. Note that the Fserve will appear whenever you join channels with the names in that list, regardless which network you're on.
7. Queue Pools
I'll explain this later, you can choose to assign each trigger to a separate queue pool or just leave them all in "Default".
That's done, now the TDCC and XDCC are pretty similar.
2b. TDCC Setup
This part covers the "TDCC Triggers" setup - for setting up TDCCs.
The way to set up a TDCC is identical to that for setting up Fserve, the only difference being there's no "Welcome File" and "Root Directory", instead you choose a "TDCC File" (your server will send/queue this file whenever the trigger is activated) and a description (to tell people what the file is).
Also among the TDCC options is an "Ad Delay", if your Fserve is set to "On" (explained below) you can choose a delay between the ad appearing. Otherwise the box is greyed out.
2c. XDCC Setup
This part covers the "XDCC Triggers" setup - for setting up XDCCs.
How does an XDCC work? Basically it provides people with a list of files to choose from, each with a number. They request a number and it gets sent/queued.
XDCC works a bit differently from the other two. First you choose a number of "XDCC Lists" to create, for example you could have one for volumes 1-10 of a manga, and another for volumes 1-5 of another manga. Use the "Description" button for put in one for each XDCC list you create.
For each XDCC list you can add any number of files - Use the Add button on the right of the column "File List" to add them. "XDCC File" and "Description" are as for the TDCC section. "Enabled", "Trigger Channels", "Queue Pools" and "Respond to !list" have already been explained, the remaining options are:
1. Small ad
Recommended. If this is turned off, whenever your ad displays it not only displays the trigger to get the listing for each XDCC list you created, it also displays each file you have on offer... spammy.
2. File Server Simulation
I haven't tried this one out myself, it's supposed to simulate a fileserver instead of the users having to deal with the usual XDCC CTCP text-command-based usage.
3. Line Delay
Whenever someone requests a listing from your XDCC, the script will send them a series of notices with the pack numbers and descriptions and file sizes. Set this to at least 1 second so you don't trigger those annoying antispam scripts.
Okay, the sharing part is done now - you shouldn't ever have to use the controls in the "Bans" and "Transfer Manager" tabs, but the buttons are pretty self-explanatory there.
Now on to the big part - main server config.
3. Server Setup
This part covers the main "Server Config" - the way your fserve looks, works and sends stuff. Many many options, we'll do the Basic Options first then move on to the advanced ones (starting top to bottom, left to right again).
Options labelled by section:
File Server Control
Controls the ad display of your server and how many users are allowed on it at one time.
1. Ad delay
Uncheck the tickbox to make your server silent (ie it either only responds to the !list command or does nothing at all) - it won't display ads then. Or check the box and enter a value. Be sensible with this setting, many channels demand silent fserves only, others don't allow the use of !list so you should have your ad on. However, never put the time lower than 45 minutes - nothing is more annoying than a huge ad appearing every 5 minutes.
2. Force Close
Turning this on will make the Fserve DCC Chat sessions the script opens close automatically after a certain delay. Note that this will override mIRC's "Close idle DCC Chats after x minutes" option. Be logical if you want to use this, don't set the delay too low (120 seconds is a good value).
3. Max users
The name says it all, this determines how many people your fserve can respond to at one time. Turn it down if opening too many DCC Chats lags you.
4. Slot display
You can choose where to display the queue slots for your fserve. Normal is, well, normal. In trigger displays the slots for each trigger (useful if your triggers have been assigned to different queue pools). Separate displays the queues separate from the triggers, and Off means no queues are displayed (only useful if you've set queues off too).
File Server Ad Message
Unlike many other fserve scripts, the Fserve message in Sysreset appears in another separate part. Describe your fserve - tell people what you have on it or your requests.
Advanced Queueing
The options inside explain themselves - turn them on if you want ops/voices to be able to skip ahead in queues. Turning them on will make either a queue by a voice jump to the first place behind all the voices and behind the ops overall but in front of normal users, and a queue by an op to skip ahead of all others and move to the the frontmost spot behind all other queued ops.
Queue Pools
Slightly complicated option for power users, this allows you to set up different pools of queues for different triggers. Each queue pool has its own set of the options listed below (they are the remaining options in the "Server Config" tab in Basic Options). Especially useful for creating different pools for different channels, or different pools for different things. For example you might not want to let people queue too many anime episodes, but at the same time you want to allow more mp3 sends and queues.
The remaining options, which are specific to the queue pools:
1. Send Control
Insta-Send
Tick to enable, and enter a maximum file size limit. This is only for the Fserve, any files queued which are below the maximum Insta-Send size will be sent straight away, skipping any queues. It also does not bother about sends and will temporarily add one to your maximum number of sends.
Max File Size
I've never used this, but I think this is to limit the size of things you want to send to a certain size, so no files bigger than this limit will be sent by your fserve.
Min CPS per send
The dreaded min CPS, bane of all modem users. Don't be silly and set this higher than your maximum send speed. Useful for preventing slowpokes from clogging sends.
2. Global
Checking Delay
This is the delay between checks for Min CPS, Max CPS and Send Bumping.
Max CPS
Evil twin of Min CPS, this limits your fserve to a certain maximum speed. Great if you don't want your server eating up all your bandwidth if you want to upload elsewhere.
3. Max Sends
Set the maximum number of persons each user (Each) can have and how many the queue pool can have in total (Total).
4. Max Queues
Set the maximum number of persons each user (Each) can have and how many the queue pool can have in total (Total). Unchecking the "Enabled" box disables queues, meaning your fserve can only send.
5. ReSend Control
Well, sends don't always go through perfectly. This controls what happens if a send fails.
ReSend Attempts
0 to turn resends off, otherwise as many as you like, the server will attempt to resend one time for each resend. Put differently this is how many times the server will requeue a failed send automatically.
On failure, requeue at:
Determines where the resend attempt will be placed. "Send" makes the resend instant, "Start" will requeue it in the 1st queue position and "End" will drop the requeue to the end of all queues.
6. Send Bumping
Another one of those features to prevent slowpokes from clogging the server.
Pool Min CPS
This is the threshold for Send Bumping to be activated.
Add x to Max Sends
Does what it says, you shouldn't put more than 1 here unless your connection is fast... You shouldn't set it to "Enabled" either if you don't think your connection is fast.
That's about all of the Basic Options, now pull down the menu and switch to Advanced Options, with Sysreset it's necessary to fiddle with them.
Color Configuration
For the psychedelic freak in you. Choose randomize if you're the random type.
Advanced Settings
Each of these can be enabled or disabled:
Show triggers with full queues
Unchecking this makes triggers with full queues not appear in your ad. Checking the Respond to !list if all triggers are full after unchecking the first one will make your ad not appear at all if you have no queue slots free.
Assign channels per trigger
If you disabled this the option to make triggers only appear in certain channels won't be there, they will appear in all channels.
Clone Protection Enabled
Prevents a person from using clones to get more queues. Checking the Display known clones in Channel or Display known clones in Status is optional if you want to see if someone has clones when he/she joins.
Anti-Timeout Enabled
Don't know what this does, think it tries to prevent sends from timing out.
Advanced Fileserver
Each of these can be enabled or disabled (they're specifically for the fserve only):
Sends count towards queues
When this is checked, sends a user has count towards his/her queues as set in the max queues per user variable.
Swap fileserver command enabled
Sorry, honestly no idea what this does.
Firewall Workaround
You'll need this if you're behind a firewall. Sysreset uses the port you've set your DCCServer to in your mIRC settings.
Block Detailed Sends and Block Detailed Queues
This will take the details like file sizes and ETAs out when your fserve responds to the "sends" and "queues" commands respectively in a Fserve DCC chat.
Abort sends if user leaves channel
Prevents people from just queuing and then leaving. Recommended.
Respond to /ctcp #channel !list
Up to you, this is still pretty much useless since among fserve scripts only Sysreset responds to this command.
Statistics Gathering
For advertising purposes, put on what you think is necessary to make your fserve more attractive, or just what is informative. Click the "View Statistics" button to have a look at them, you can also reset them from there.
Er, guess what? We're done. Almost. Click the "Done" button and wait while Sysreset updates its settings.
Now go to the Sysreset menu again, scroll down to the "Servers Active" part and choose either "On" (displaying ads at your set delay) or "Silent + !list" (responds to !list, no ads otherwise). Congrats, your server is up and running now hopefully.
Note: the "Sends only" mode will make your server accept no more requests and just complete the current sends, "Totally silent" makes your server not display ads at all (it will still respond to triggers) and "Off" turns it completely off.
Thanks to ep for helping check this thing. 
God knows I can't trust what I write when I write this kind of post that takes me two whole hours of typing and editing.