Installing Mirc
---------------
Since Mirc 6.3 the control files of mirc are no longer installed into the
same folder as the mirc files are copied. The control files are put into 
a folder "C:\Dokuments\Application Data\Mirc" . To prevent this from happening
you have 2 options

**** option 1 : BEFORE YOU INSTALL MIRC:
     create a folder where you want to install mirc eg. C:\mirc\
     create a 0 byte file "mirc.ini" in that folder
     when installing mirc into that folder - mirc installer will ask you if
     you want to Upgrade. Select "Full Install" and install. Don't Backup. 
     DONE
**** option 2 : AFTER YOU INSTALLED MIRC:
     (close mirc before you do this)
     find the folder where your mirc.ini is installed and 
     move ALL folders and Files from that folder to your Mirc install dir
     so that mirc.ini and mirc.exe are in the same folder
     DONE

Fresh Installation
------------------
 1. Unzip *EVERYTHING* to your mIRC directory (where mirc.ini is)
    (i.e. c:\mirc\)
 2. Type in mirc status window: /load -rs ps_install.mrc
 3. Answer Yes to "Run Initialization Commands?" warning
 4. Enter your settings in the popup dialogs that appear



Updating Existing Installation
-------------------------------
 1. Unzip to your mIRC directory (i.e. c:\mirc\)
 2. Right click channel or status window and select
    Photoserve -> About -> Install / Update

 If the update fails for any reason (as it often does on Win9x),
 simply repeat both steps. Rerunning the update is always safe,
 if you think something *might* have gone wrong you don't lose
 anything by trying again.



PhotoServe server-bypass features
---------------------------------
 Photoserve requests and sends files one at a time. Typically this means
 leecher sends one !PSGET message, and sender sends one DCC SEND message
 (and often a queue message as well). Traditionally, all these messages
 are routed through the IRC servers. The amount of server-routed traffic
 is a major problem, as it easily triggers server-side flood protection.
 Channels have even had to move to other less flood-prone networks from
 time to time. Since Photoserve 4.8, it is possible to avoid all server-
 routed traffic by enabling two options in PSCC "Leech: Multi Nick" tab:

 IP:PORT !whereis format
 - Enables direct connections between two clients so they can send
   messages to each other without bothering the server. Originally this
   was used only for whereis replies, but now all leech-related traffic
   can use direct connections. Enable this, it is very imporant.

 !PSSERV leech method
 - Enables a mirc feature that makes it possible for other users to send
   files directly to your IP-address, without sending a message over the
   server first. This does not actually reduce flood protection errors on
   your system, but it will help everyone who is sending you files. So be
   nice to other people and enable !PSSERV.

 Bypassing servers also make your leeches faster and increase privacy.

 Aside from enabling these options, you also should switch to using the
 new multi-nick leeech system. The old "single nick leech" does not get
 the full benefit from these features, and it's very likely that the
 single-nick leech system will be removed in Photoserve 5.00.



Leech system details (new multinick leech)
------------------------------------------
 The new leech system works multithreaded. that means you can use all of your
 allowed leech slots for 1 collection at the same time. The leech system
 request require an open port in the dccserver range, this new way of transfers
 works from users that cannot send (with old !PSGET), resumes also works always.
 Try not to use !PSGET as !PSSERV works better and faster.

 To Start a leech type !l <trigger> in the channel where you want to leech
 To stop any leech, even automaticly started ones, type !ls <trigger>
 To only leech pictures of a collection use !lp <trigger>
 To only leech videos of a collection use !lv <trigger>


Hidden settings & commands
--------------------------
 List of seldom needed settings in photoserve. As only a few people will find
 these settings useful, no PSCC user interface has been created for changing them.
 Set these using the mirc set command. To set dcc port: /set -s %ps.dccserverport 59

 %ps.dccserverport (Number 1-65535 or 'endrange', default 'endrange')
                   Set listening port for Mirc's DCC Server feature which is used by the
                   photoserve autoleech system. By default uses one of the ports defined
                   in your DCC Port Range (Options -> Connect -> Options -> Advanced).
                   The standard DCC Server port would be 59 but using 'endrange' makes
                   router configuration somewhat easier.
                   /set -s %ps.dccserverport 59
                   /set -s %ps.dccserverport endrange


 %ps.miscdepth     (Number 0-99, default 0 meaning infinity)
                   Set max recursion depth for searching files in your "misc" paths.

 %ps.dccserver     ('off' or 'on', default 'on')
                   Sending files via the DCC Server protocol has been known to cause
                   mirc crashes for some people. The root cause is a mirc bug so only
                   "fix" is to disable sending via DCC Server and force pserve to use
                   the regular DCC protocol. You should do this ONLY if your mirc is
                   crashing frequently, not "just in case". And if this setting does
                   not help with the crashes, turn it back on. To disable DCC Server
                   execute the following command: /set %ps.dccserver off
                   Recent information have shown that a tool called Netlimiter is a 
                   reason for mirc crashing. so instead of turning this setting off 
                   you should upgrade your netlimiter software to the latest available
                   version.

 %psl.defaultorder ('picfirst', 'vidfirst' or unset, default unset)
                   Tells leech to download pics/videos first. If this variable is unset
                   (unset is the defaul) videos and pics will downloaded in random order.
                   /set -s %psl.defaultorder picfirst
                   /set -s %psl.defaultorder vidfirst
                   /unset -s %psl.defaultorder
    

 %psl.constructmode  ('download' or unset, default unset)
                     Setting this to 'download' enables continous construction of parts as
                     they are received. With this setting the target files will be fully
                     pre-allocated on disk. You need this only if you want start downloading
                     a large file in pserve and later resume and finish it with Bittorrent.
                     Note that despite the pre-allocation you cannot delete the received
                     parts by hand, meaning this will more than double the amount of disk
                     space used by parts-leeching.
                     /set -s %psl.constructmode download
                     /unset -s %psl.constructmode

 %ps.speedfactor     (Number 0.1-10, default 2)
                     Control pserve/mirc CPU usage. Higher values throttle CPU usage, lower
                     values allow pserve to consume more CPU. Whatever the value, mirc will
                     still do the same amount of work, this only controls over how long period
                     the work spread out. You can increase this value if you feel that mirc is
                     freezing every two seconds or hogging too much CPU time from your other
                     applications.
                     /set -s %ps.speedfactor 4

%ps.limit.gets      Sets a hard limit for number of gets. To set your max number of gets to 3 use:
                    /set -s %ps.limit.gets 3

%psl.leechsort         Manualy setting /set -s %psl.leechsort nogang  
                       in this mode the leech picks only by priority nothing is grouped. 
                       This mode tries to fetch the rarest parts first (this does ganged mode too -
                       but only within each file group). (HEROIC MODE ;-))

%ps.TmpDir           /set -s %ps.TmpDir D:\temp\PStemp\
                     use this if you dont want to use the default TmpDir (this is where the
                     part files are stored, that are temporarly created for upload)



 !PSRequestCSV     Command to download CSVs of multiple triggers in one .rar file.
 
                   Syntax:  /ctcp <Nick> !PSRequestCSV [ip:port] <pattern>
                            The [ip:port] part is optional

                   Example: /ctcp Duud !PSRequestCSV SNCD* 
                            Downloads all Susenet CSVs from nick Duud


!PSPAR2            Command to download a par2 file for a damaged large file from a collection
  
                   Syntax:  /ctcp <Nick> !PSPAR2 [ip:port] <trigger> [crc [size]] \path\file.ext
                             The crc or size can be left away.  only 1 value will be interpreted as crc
                                 ( there is a menu for these commands )

                   Example: /ctcp Hugh !PSPAR2 CNVCD1 abcdef12 \Video of Month\v12354-123.mov     
       
 

  /set -s %ps.autoident_#<channelname> <password> <handle on bot>


  /set %ps.noinviteleechstart   to disable auto invite leech starts


  /set -s %ps.cr.noqueuesend_limit 600
                  users having more credits than this limit (default is 1000)
                  will bypass the PS Send QUEUE and the file is sent directly which 

  /set -s %ps.cr.unlimitedsend_limit 300
                  users having more credits than this limit (default is 0 which means disabled)
                  will bypass the PS send speed cap limit. If you reserve 50% bandwith you can use 
                  the reserved bandwith to send to your main leech sources

  /set %ps.noAutoTriggerUpdate  to turn fully automated Trigger Updates off


Manual Construction of already downloaded Part Files
----------------------------------------------------

The command you will need is :  /FindAndPutAllParts <dir> <filename>

To use it copy all the part files you have to a dir without any spaces or commas, like C:\test 
Lets say your file is abc.avi and you have a lot of abc.avi###partxxx files
then run in mirc

/FindAndPutAllParts  C:\test abc.avi

you will find your file abc.avi in $mircdir in the end.


The Leech Linker System
-----------------------

This is useful for people that are in more than 2 networks. 
PhotoServe Leech (the !L one) is able to run a leech for the same collection in different networks
but only one channel per network. You have to start the leeches manualy, there is no way to tell the
checker or PhotoServe to start such a leech other than typing !L in all of the channels. 
This is where the Leech Linker will help you.

Please read the notes before you set it up:

The Leech Linker works like this - and exactly like this and not different :
If there is a leech started, that means it has to start, which means IT HAS TO FIND TARGETS 
in some channel (the default channel of the Checker that started the leech).
When it starts an auto leech in the first channel, it searches the LinkedLeech Config file 
see below) for a matching config in all OTHER connected networks. If and when it
matches one it will start a leech there like if you started it yourself with !L in that #channel. 

The leech will run forever from that moment no matter if there are files to leech - unless the csv
is changed, that will make it requeue and stop in all channels. But other than this the leech 
will be a "manual" leech, thus blocking other leeches. So you must select very wise what you
wish to split leech. You can of course stop the leech with one !LS <trigger> anytime. 
But it wont stop just because it finds no targets. This is a feature and for 
triggers that are known to have very new csvs and new files come in bit by bit.

Just be careful with the triggers you setup for this. It can go really  bad for your leech performance.

 Things you have to remember:
     1) works only for leeches started by the Checkers (PSPV or PSC)
     2) no search in multiple channels or multiple networks for files BEFORE it is started in them
        (the first channel has to have files)
     3) it is important (because of 2) ) what the "main leech channel" is in the Checker.. Chose the 
        main channel where the new files are first, or at least enough people to start a leech..


The file PSLeech_LinkedLeechConfig.ini in PhotoServe\Settings with the following format
(examples for patterns: ABCD*  or FOO*DVD*  or BAR?CD*  or FOO*BAR?? )

[NetworkName]
pattern=#Channel

[NetworkName2]
pattern=#Channel

you can use the following command to create/alter the file out of mirc too :
//writeini PhotoServe\Settings\PSLeech_LinkedLeechConfig.ini $network pattern #channel


Generating Pserve compatible reports with The!Checker (aka PicCheck)
--------------------------------------------------------------------
 The!Checker users:

 OPTIONS, COLLECTION DEFAULTS
 change your OUTPUT SORTING to "Pathname (ECSV ONLY)"

 Miscellaneous (tab)

 SAVE REGISTRY [check the box] "automatically save registry to file when exiting program"

 select OK
 exit The!Checker
 run The!Checker
 exit The!Checker again

 now in notepad edit PICCHECK#.REG where # is the highest numbered .reg file in The!checker program directory.
	
   search for "SortType"="
   for each instance you will need to change it to "SortType"="3"
   You can use EDIT, REPLACE and replace "SortType"="1" with "SortType"="3".
   repeat the REPLACE function for "SortType"="1" "SortType"="2" and "SortType"="4"
   SAVE the edited .REG file

 double click on the PICCHECK#.REG file you just edited and select YES and OK

 run The!Checker
 select any trigger
 select CHECK ALL

 NOW YOU ARE CORRECTLY SET TO LEECH WITH THE NEW PHOTOSERVE LEECH PSERVE.DLL



---
EOF