WinDrop is the Windows version of the popular IRC bot Eggdrop. WinDrop can be run as a Windows Service using FireDaemon Pro, which lets you have the script start automatically at boot prior to login, start multiple instances of the script and more. This HOWTO will show you how to set it up. You can also use FireDaemon Fusion to manage FireDaemon and other Windows services via a web browser.
WinDrop Setup Under FireDaemon Pro
Download the latest WinDrop from here.
By default WinDrop installs to "C:\Windrop". For the purposes of this HOWTO, we will use that directory.
Download and install FireDaemon Pro into the directory of your choice, typically C:\Program Files\FireDaemon. FireDaemon can be downloaded from here.
Next start the FireDaemon Pro GUI from the desktop shortcut. Click on the "Create a new service definition" button in the toolbar (or type Ctrl+N) and enter the information into the fields as you see below. Adjust the paths to suit your installation.
- Executable: The path to your eggdrop.exe file. For the purposes of this HOWTO, the directory is C:\Windrop\eggdrop.exe.
Working Directory: The directory containing your eggdrop.exe file. For the purposes of this HOWTO, the directory is C:\Windrop.
Parameters: None. Leave this field blank.
Now click on the Settings tab. If you DON'T want to see Windrop running, uncheck the Interact with Desktop check box & select “Hidden” from the “Show Window” dropdown. You can optionally run Windrop as the user you installed it as. In the Logon Account field type your username (e.g. Administrator) and then enter the user's password twice in the Password and Confirm fields. You can also change the Process Priority to allocate more CPU time to WinDrop or specify which CPU or core WinDrop will run on (in the case of multi-processor, hyperthreaded or multi-core CPUs).
Now click on the OK button to install and start WinDrop!
Some users have reported that Windrop connects and then disconnects, following up with multiple instances of itself. This problem is caused by WinDrop detaching from the console. When this happens, FireDaemon loses all control of WinDrop, thinking WinDrop has stopped running even when it hasn't. This makes FireDaemon restart the console instead of Windrop, causing multiple instances of Windrop to run simultaneously.
To fix this, edit your Windrop service definition. In the Program section, add -n <path to Windrop config file> in the Parameters section.