Windrop Central 

News Compiling Downloads FAQ Links

Frequently Asked Questions

by FireEgl and Kirben

Always use the latest Windrop version

Other useful Eggdrop information:
slennox's frequently asked questions about eggdrop
The index.html in the /doc/html/ directory of Windrop provides detailed information on how to use Windrop

Q: What is Windrop?
A: Windrop is a windows port of the Eggdrop IRC bot that runs on NT, 2000 and XP. There aren't any Eggdrops that run native on Windows, they all require Cygwin (cygwin1.dll, a library which provides the UNIX system calls). So Windrops should behave very much like normal Eggdrops.  There is very little difference between the code or the operation of Eggdrops and Windrops!

Q: Does Windrop support Windows 95/98/ME ?
Only Windrop 1.6.19 and earlier supported Windows 95, 98 and ME. Since Cygwin 1.7 dropped support for Windows 95/98/ME.

Q: Does Windrop support Windows NT4 ?
Only Windrop 1.6.19 and earlier supported Windows NT4. Since Cygwin 1.7.10 dropped support for Windows NT4

Q: Does Windrop support Windows 2000 ?
Only Windrop 1.6.19 and earlier supported Windows NT4. Since Cygwin 1.7.19 dropped support for Windows 2000

Q: Does Windrop support Windows XP ?
Only Windrop 1.6.21 and earlier supported Windows NT4. Since Cygwin 2.6.0 dropped support for Windows XP

Q: Does Windrop support Windows Vista/7/8/10 ?
Yes, the current version of Windrop should work on Windows Vista, 7, 8 and 10.

Q: Does Windrop include IPv6 support ?
A: Yes, in Windrop 1.8.0 and later.

Q: What types of proxies does Windrop support ?
A: Windrop only supports socks v4 and sun proxies, both without authorization or password support. 
Note: The complete version of eggdrop config file must be used when using Windrop 1.5.3 - 1.6.12 through a proxy. 

Q: How can I find out what version of Windrop I am using?
A: Open a Command Prompt or MS-DOS Prompt
    Change to the Windrop's directory
    ie if the Windrop was stored at D:\Windrop\ then type D: (Return) cd D:\Windrop\ (Return)
    and then type eggdrop -v

Q: How do I setup the config file?
If using Windrop 1.4.x or earlier then open eggdrop.conf.dist with a text editor (Don't use notepad!)
If using Windrop 1.5.3 - 1.6.12 then open eggdrop.simple.conf, eggdrop.advanced.conf or eggdrop.complete.conf with a text editor (Don't use notepad!)
If using Windrop 1.6.13 or later then open eggdrop.conf with a text editor (Don't use notepad!)
Read the description above or below each setting and then change the setting
Line with a # in front of them are ignored
Don't use any < > : * ? " < > | characters for the userfile, chanfile, nick and notefile settings in config file 
Make sure you change #botcentral and #lamest to the name of your channel in the Channel Module section or comment out those lines with a #
Make sure you delete the two lines that start with die or the Windrop won't start.
When you save your config file make sure the text editor doesn't add an additional file extension to the file like .txt
A more detailed configuration setup guide is available at slennox's eggdrop page

Q: How do I a start Windrop?
A: First make sure you have edited your config file settings 
    If you are using Windrop 1.5.2 - 1.6.12 make sure you have also setup resolv.conf
    Then open a Command Prompt or MS-DOS Prompt
    Change to the Windrop's directory
    ie if the Windrop was stored at D:\Windrop\ then type D: (Return) cd D:\Windrop\ (Return)
    Start the Windrop with eggdrop -m configfilename

Q: Can I run Windrop as a service?
A: Yes but only under Windows NT4, 2000, XP or later.
If you are using an NTFS file system, the follow steps are required since Cygwin uses it owns file permissions:
1: Download chmod, extract to the Windrop directory and run chmod.bat. It will change file permissions to allow read/write access for all groups.
2: Edit your config file and change the line in the 'Files and Directories' section from:
    set userfile-perm 0600
    to:
    set userfile-perm 0666.

Q: AntiVir reports a TR/XBoxEmu.2 trojan in Windrop installer file
A: This is a false trojan warning and can be resolved by updating to latest virus definitions file.

Q: Norton AntiVirus reports a Bat.SillyB.gen virus in botchk.bat
A: This is a false virus warning, Nortan AntiVirus just looks for a certain command in any batch file. The use of botchk.bat is optional so if you are still worried then don't use it.

Q: How can I solve the problems with international characters when using an language other than English with Windrop?
A: The version of Tcl that Windrops are compiled with uses international characters a different way than earlier versions of Tcl. To fix this problem update to Windrop 1.6.7 or later.

Q: Why does Windrop keep opening and closing local listening ports ?
This was due to a bug in Cygwin, which was fixed in Cygwin 1.5.12-1. Update to Windrop 1.6.17 or later to solve the issue.

Q: Windrop reports "*** Shared region version mismatch"
Q: Windrop reports "You have multiple copies of cygwin1.dll on your system."
A: That error means there is another version of the Cygwin dll (cygwin1.dll) in memory, only one version can be in memory at a time. Try quitting all other Windrops and any other programs that use the Cygwin dll (cygwin1.dll), if that fails trying rebooting the system to clear memory completely. If you are running multiple Windrops on a system then they must all use the same version of the Cygwin dll (cygwin1.dll). 

Q: Windrop reports "* CONFIG FILE NOT LOADED (NOT FOUND, OR ERROR)"
A: First make sure all file extensions are been shown in Windows Explorer. To check, open Windows Explorer, go to Tools menu, choose Folder Options, select View tab and make sure the box next to Hide file extensions for known file types is empty (Not ticked).
A1: For 1.4.x or earlier:
Copy eggdrop.conf.dist and rename it to egg.config (Make sure you edit the settings in it!) and start the Windrop again
A2: For 1.5.2 - 1.6.13:
Copy either eggdrop.complete.conf, eggdrop.advanced.conf or eggdrop.simple.conf and rename it to eggdrop.conf (Make sure you edit the settings in it!) and start the Windrop again

Q:  Windrop reports "* Can't determine your hostname!" or "* Hostname self-lookup failed."
A: Edit your config file and try commenting out both the my-hostname & my-ip settings as in most cases they are not required. 
#set my-hostname "localhost"
#set my-ip "127.0.0.1"
A1: If that fails then edit your config file and just use 
set my-hostname "localhost"
#set my-ip "127.0.0.1"
A2: If that still fails then edit your config file and try using your exact hostname and ip address, for example:
set my-hostname "dialup160.windrop.net"
set my-ip "10.20.30.40"

Q: Windrop still reports "* Can't determine your hostname!" or "* Hostname self-lookup failed."
A: It may help to put an entry in your \Windows\hosts file (On Windows 95/98/ME) or \Winnt\System32\Drivers\etc\host file (On Windows 2000) or \Windows\System32\Drivers\etc\host file (On Windows XP) that matches what you set my-hostname to. See the \Windows\hosts.sam file (On Windows 95/98/ME) or \Winnt\System32\Drivers\etc\host.sam file (On Windows 2000) or \Windows\System32\Drivers\etc\lmhosts.sam file (On Windows XP) for a sample hosts file.

Q: Windrop reports random errors in the config file
A: This problem often occurs when using Windrop 1.5.x or 1.6.x earlier than 1.6.3. Just update to the current Windrop version to fix this problem

Q: Windrop reports "MSGxxx" or "LANG: No lang files found for section modulename"
A: Make sure you change to the Windrop directory before starting Windrop. If you start Windrop from a different directory the Windrop will be unable to find the language files, which causes those errors.
A1: Unfortunately on some systems the Windrop always fails to find the languages files, that exact reason it still known.

Q: Windrop reports "Couldn't grab nearby port"
A: Look for the line where you've set the port (e.g. listen 3333 all) in the config file, and try several different ports to see if it fixes the problem. Choose a port number between 1025 and 32767.
A1: If the first answer didn't solve your problem then your my-ip setting is probably incorrect. You probably don't even need my-ip set!  So try commenting out or removing that line.
A2: If neither of the above work, you can solve the problem by commenting out or removing the listen command(s) in the config file. Unfortunately, if you have to do this, the Windrop will not have a telnet port. This means you won't be able to telnet to the Windrop directly, and you won't be able to use it as a hub. (You can still have it link to other bots though)

Q: Windrop reports "* Please make sure you edit your config file completely." or "* You didn't edit your config file completely like you were told, did you?"
die "* Please make sure you edit your config file completely."
die "* You didn't edit your config file completely like you were told, did you?"

Q:  Windrop reports "* Please edit your config file." or "* You didn't edit your config file like you were told, did you?"
A: Edit your config file and remove the following lines if they are there:
die "* Please edit your config file."
die "* You didn't edit your config file like you were told, did you?"

Q: Windrop reports "Can't load modules modulename: dlopen: Win32 error xxx"
A: This errors means the Windrop was unable to find the required module (*.dll) files. Edit the config file and make sure set mod-path is set to "modules/" That will work no matter where the Windrop was installed to.
A1: If you have just updated your Windrop version, than make sure you are not attempting to load modules created for earlier or later version of Windrop.

Q: Windrop reports "Couldn't create channel file: chanfile. Dropping"
A: Edit your config file and make sure there are no  \ / : * ? " < > | in this line
set chanfile "chanfile"

Q: Windrop reports "no such channel record"
A: The line this error is reported in should be listed two lines below, make sure the #channel name mentioned in this error is correct. If the #channel name is incorrect then edit that section of the config file and either correct the name of the #channel the error occurred in or delete that line.
ie if the error was in "channel set #muchannel -shared" and your channel name was #mychannel then you would edit your config file and change that line to channel set #mychannel -shared
A1: Make sure there is channel add #channel {} entry for that #channel in the config file

Q: Windrop reports "illegal channel option"
:A: The line this error is reported in should be listed two lines below, edit that section of the config file and correct the name of the option that is causing the error or just delete that line.
ie if the error was in "channel set #mychannel -shares" then you would edit your config file and change that line to channel set #mychannel -shared

Q: Windrop reports "missing close-brace"
:A: The line this error is reported in should be listed two lines below, edit that section of the config file and add a close bracket } to the end of that section.
ie if the error was in "set servers" then you would edit your config file and change that section to include both an open and close bracket
ie if the line was set servers {irc.servername.com irc2.servername.com then you would change that line to set servers {irc.servername.com irc2.servername.com}

Q: Windrop reports "You have installed modules but have not selected an encryption module, please consult the default config file for info."
A: Edit your config file and remove the # in front of this line to enable the blowfish encryption
checkmodule blowfish (For Windrop 1.6.7 or earlier)
loadmodule blowfish (For Windrop 1.6.8 or later)

Q: Windrop reports "* USER FILE NOT FOUND! (try './eggdrop -m' to make one)"
A: Make sure you start the Windrop by typing: eggdrop -m

Q: Windrop reports "* CAN'T WRITE TO TEMP DIR"
A: Edit your config file and change the line that says:
set temp-path "/tmp"
to:
set temp-path "tmp/"
then create a directory in your Windrop directory called tmp

Q: Windrop reports "* Warning! Could not write pid.botname file!"
A: Edit your config file and make sure there are no \ / : * ? " < > | in these two lines
set nick "nickname"
set pidfile "pidfilename" (If using custom pid filename)
A1: If you are sure the Windrop isn't running already then just delete the botname.pid file in the Windrop directory and restart the Windrop

Q: Windrop doesn't show up on IRC after it is launched, what's wrong?
A: On Windows 95/98/ME press Ctrl+Alt+Delete keys and a "Close Program" menu will pop up, just select "Eggdrop" from the list and click the "End Task" button. On Windows NT4/2000 press Ctrl+Alt+Delete key, choose Task Manager, choose Processes tab, select eggdrop.exe and choose End Process. On Windows XP press Ctrl+Alt+Delete key, choose Processes tab, select eggdrop.exe and choose End Process.
Then restart the Windrop with:
eggdrop -mn if starting Windrop for first time, otherwise eggdrop -n
And your will be able to see what is happening as the bot tries to connect to the IRC server, sometimes it can take awhile for an error to appear. Check the FAQ index again for meaning of the error message.

Q: Windrop reports "DNS lookup failed" when trying to connect to IRC servers
A: If you're using Windrop 1.4.x or earlier than either the IRC server address is wrong, the IRC server no longer exists or your Internet Service Provider is having problems with their DNS servers.
A1: If you are using Windrop 1.5.2 - 1.6.12  then make sure you edit resolv.conf and change "192.168.0.1" to the IP address of your primary DNS server. If there is no resolv.conf file included then update to the current Windrop version.
To find out your DNS server IP address on Windows 95/98/ME Open Start Menu, choose Run, type in "winipcfg", click on More Info >> and use IP address listed next to DNS Servers
To find out your  DNS server IP address on Windows NT/2000/XP Open Start Menu, go to Accessories, choose Command Prompt, type "ipconfig /all" and use the first IP address listed next to DNS Servers
If you use a DNS forwarder like Winroute or Wingate, enter it's IP address instead
A2: If you're using Windrop 1.6.20 or later, then make sure the dns-servers setting in the DNS MODULE section of your config file, is enabled and set to working DNS servers. i.e.
set dns-servers "8.8.8.8 8.8.4.4"
A3: If that fails and you are using Windrop 1.5.x or 1.6.x then try disabling the dns module by editing your config file and adding # in front of the following line:
loadmodule dns
A3: If that still fails then either the IRC server address is wrong, the IRC server no longer exists or your Internet Service Provider is having problems with their DNS servers.

Q: Windrop reports "Invalid address on remove machine" when trying to connect to IRC servers
A: This is usually caused by setting my-ip incorrectly in your config file. You probably don't even need my-ip set!  So try commenting out or removing that line.

Q: Windrop reports "Ident required" when trying to connect to IRC servers
A: The best solution is to use the winident script that FireEgl made that has the ability to turn itself on and off when the bot needs it, no other script currently does that. The winident script is included with all recent versions of Windrop, to use the script edit your config file and remove the # in front of this line at end of your config file:
source scripts/winident1.2.tcl 
A1: mIRC has an ident server built-in, to use it go to File menu, choose Options, select Ident section and uncheck "Enable only when connecting". (Note: both you and your bot will have the same ident if you do this.)

Q: Windrop reports "No eggdrops allowed" when trying to connect to IRC servers
A: The problem is caused by the ident used by the Windrop been set to eggdrop.
A1: If you are using the winident script then just open the script with a text editor (Don't use notepad!) and change the *** $username in set ident(username) "***$username" to the name you want to use. Then restart the Windrop
A2: If you aren't using any Identd server then edit your config file and change lamest in set username "lamest" to the name you want to use. If that line doesn't exists in your eggdrop config file then add it anywhere at the start.

Q: Windrop reports 'dequeue_sockets(): errno = 128 (Transport endpoint is not connected)'
A: This means Windrop is been blocked from making a connection, for some reason.
A2: Make sure you are using the correct my-hostname and my-ip in the 'BASIC SETTINGS' section of your eggdrop config file. In most cases these settings aren't required.
A3: If you are using a firewall, double check your settings in the 'MORE ADVANCED SETTINGS' of your eggdrop config file.
A4: If you have a firewall, make sure the firewall isn't blocking your Windrop

Q: Windrop doesn't respond when I /msg bot hello
A: Make sure set owner "owner" in the config file is set to your exact nickname on IRC
A1: Make sure you have disabled these two lines in the config file if they are there, put # in front of each line to disable them and restart Windrop:
unbind msg - hello *msg:hello
bind msg - myword *msg:hello.
A2: If you are using the Handlen32 version of Windrop 1.5.x or 1.6.x then make sure you are using Windrop 1.6.3 or later.

Q: Windrop doesn't respond to dcc chat
A: Make sure you are using Windrop 1.6.8 or later, since earlier versions would reject users with a 0 or 255 in their IP address
A1: Make sure you have set a password on the Windrop, /msg bot pass password
A2: Make sure the Windrop still recognizes you, /msg bot ident password handle
    (Requires ident command to be enabled in your config file)
A3: Try /ctcp bot chat to make the Windrop dcc chat you instead.
A4: If you are using mIRC, go to File menu in Marc, choose Options, select Local Info section and try changing Lookup method to Normal
A5: Edit config file and try changing set dcc-sanitycheck to 0. Then restart the Windrop. If that line doesn't exists in your eggdrop config file then you don't need to change it
A6: If you are using a firewall, make sure the ports used for dcc aren't been blocked. The reserved-portrange setting in the config file can be used to set the dcc ports used by Windrop.
A7: If all else fails try to telnet to the Windrop instead (Using telnet is also a good way to find out why exactly the Windrop isn't accepting a dcc chat connection too)

Q: Windrop doesn't respond to telnet
A: Make sure you are using the correct hostname and port number. Using a hostname of either localhost or 127.0.0.1 should work in most cases if the Windrop is on the same system. Use the port number listed in either listen xxxx users or listen xxxx all line of config file (Ignore all lines with a # in front of them) 
A1: Edit config file and try changing set protect-telnet to 0. Then restart the Windrop. If that line doesn't exists in your eggdrop config file then you don't need to change it

Q: Windrop no longer responds to any commands
A: Make sure the Windrop still recognizes you, /msg bot ident password handle
    (Requires ident command to be enabled in your config file)
A1: If the ident command is disabled or fails try to telnet to the Windrop, then make sure that the Windrop recognizes your current nickname, ident and hostname.

Q: Windrop reports 'Tcl error: couldn't duplicate input handle: bad file number' error
A: This is a old problem which effected Windrop 1.5.2 - 1.6.16, when used under Windows 2000 or XP, but didn't occur on all IRC networks.
A1: Update to Windrop 1.6.17 or later to solve this problem.

Q: How do I telnet to my Windrop ?
A: First you need to find out the ip address and telnet port number of the Windrop.
A1: To find out your IP address on Windows 95/98/ME Open Start Menu, choose Run, type in "winipcfg", and use IP address listed next to IP Address
To find out your  IP address on Windows NT/2000/XP Open Start Menu, go to Accessories, choose Command Prompt, type "ipconfig /all" and use IP address listed next to IP Address
A2: To find out the telnet port number of the Windrop, look in your eggdrop config file for the listen xxxx all or listen xxxx users line (Ignore all lines with a # in front of them) and use that xxxx port number when telneting to the bot. 
A4: To telnet to the Windrop on Windows 95/98/ME Open Start Menu, choose Run, type in "telnet", choose OK, choose Connect, type in the IP address of Windrop next to Hostname and telnet port number of Windrop next to Port, choose Connect. When the Windrop responds enter your username and password, if you are running Windrop for the first time just use 'New'
A4: To telnet to the Windrop on Windows NT4/2000/XP Open Start Menu, choose Run, type in "telnet", choose OK, type in "open" followed by the ip address and telnet port number of the Windrop. For example if the Windrop was at IP address 1.2.3.4 and the telnet port number was 3333 you would use "open 1.2.3.4 3333". When the Windrop responds enter your username and password, if you are running Windrop for the first time just use 'New'

Q: How do I make my bot join a +k (key'd) channel?
A1: Use .dump join #channel key through dcc chat or telnet
A2: Or to make the change permanent, use this command through dcc chat or telnet:
.chanset #channel need-key putserv "JOIN #channel key"

Q: How can I change the name of the ident (nickname!ident@hostname) that my Windrop uses?
A: If you are using the winident script then just open the script with a text editor (Don't use notepad!) and change the *** $username in set ident(username) "***$username" to the name you want to use. Then restart the Windrop
A1: If you are using mIRC for Ident then go to File menu in Marc, choose Options, select Ident section and change the User ID. (Note: both you and your bot will have the same ident if you do this.) Then restart the Windrop
A2: If you are using another IRC client or utility for ident then read it's instructions or help file to find out how to change the name it uses.
A3: If you aren't using any Identd server then edit your config file and change lamest in set username "lamest" to the name you want to use. If that line doesn't exists in your eggdrop config file then add it anywhere at the start.

Q: How do I load the extra modules (botnetop, gseen and stats) included with Windrop ?
A: To load the botnetop module, edit the botnetop.conf file with a text editor (Don't use notepad!) and choose your settings. Then edit your eggdrop config file and add the following line to the module section
source botnetop.conf
A1: To load the gseen module, edit the gseen.conf file with a text editor (Don't use notepad!) and choose your settings. Then edit your eggdrop config file and add the following line to the module section
source gseen.conf
A2: To load the stats module, edit the stats.conf file with a text editor (Don't use notepad!) and choose your settings. Then edit your eggdrop config file and add the following line to the module section
source stats.conf

Q: Windrop reports "ERROR writing user file"
A: Edit your config file and make sure there are no  \ / : * ? " < > | in this line
set userfile "userfile"

Q: The .set and .tcl commands in Windrop don't work
A: The .set and .tcl commands must be enabled manually, edit your config file and add a # in front of these lines if they exist:
unbind dcc n tcl *dcc:tcl 
(To enable .tcl)
unbind dcc n set *dcc:set 
(To enable .set)
Then either .rehash or .restart bot via dcc chat/telnet or /msg bot rehash password
A1: To allow non-permanent owners to use the .set and .tcl commands edit your config file and change set must-be-owner to 0. Then either .rehash or .restart bot via dcc chat/telnet or /msg bot rehash password

Q: Windrop reports the incorrect time in logs and party line
A: Download an updated Windrop version from Windrop Central, as all Windrop versions were updated to resolve this issue.
A1: Make sure you use the eggdrop.complete.conf or eggdrop.advanced.conf eggdrop config file
Then edit your eggdrop config file and enable the following line by removing the # in front of it:
#set env(TZ) "$timezone $offset"
Then edit your config file and alter the following two lines to the correct time zone, an example for GMT+10:
set timezone "GMT"
set offset "-10"

Q: Why don't files moved manually into the file system directory show up in the Windrop?
A: This is a known problem with all versions of Windrop
A1: If you are using 1.4.x or 1.5.x then it would be best to update to the current Windrop version, then each time you added files manually use the optimise command the file system area of the Windrop to update the file listing.

Q: Windrop reports "(!) timer drift -- spun X minutes"
A: It basically means that your Windrop couldn't do anything at all for X amount of minutes, check the app-weird.html file in the doc\html directory of Windrop for an explanation of its causes.

Q: How can I kill the Windrop?  Or how do I see if it's running?
A: On Windows 95/98/ME press Ctrl+Alt+Delete keys and a "Close Program" menu will pop up, select Eggdrop from the list and choose End Task.  If you don't want to kill it, or don't see it on the list, just click Cancel.
A1: On Windows NT4/2000 press Ctrl+Alt+Delete key, choose Task Manager, choose Processes tab, select eggdrop.exe and choose End Process. If you don't want to kill it, or don't see it on the list, choose File Menu and Exit Task Manager.
A2: On Windows XP press Ctrl+Alt+Delete key, choose Processes tab, select eggdrop.exe and choose End Process. If you don't want to kill it, or don't see it on the list, choose File Menu and Exit Task Manager.

Q: Where can I find other language files for Windrop?
A: Additional language files for Windrop are available at slennox's eggdrop page

Q: Where can I find some extra modules for Windrop?
A: The botnetop, gseen and stats modules are included with all the Windrop final ports (1.4.3 or later) at Windrop Central

Q: Where can I find some good scripts at?
A: The best places to look for useful scripts are at slennox's eggdrop page, you can even search for scripts.
A1: Many other scripts are available on the EggHeads FTP site in the 1.* directories. The directory numbers refer to the version of Eggdrop/Windrop that the scripts were created for.

Q: How can I add scripts to my Windrop?
A: Unpack the script with a utility like 7-Zip, most scripts are compressed with gzip (They have a .gz file extension).
Open the script with a text editor (Don't use notepad!) and choose the settings you want.
Move the script(s) to the scripts directory of your Windrop and add the following line to the end of your config file
source scripts/script.tcl
Where script.tcl is the filename of the script
Then either .rehash or .restart bot via dcc chat/telnet or /msg bot rehash password

Q: Why do some scripts fail to work with Windrop?
A: Any script that uses Unix specific commands will not work with Windrops since the commands aren't available under Windows
Many older scripts no longer work with recent version(s) of Windrop due to changes made in the code. Sometimes using the built in compatibility script will help. Add the following command to the start of the scripts section of your config file if it isn't already there:
source scripts/compat.tcl

Q: How can I create Tcl scripts for Windrop?
A: The tcl-commands.doc file in the doc directory of Windrop contains basic details of the Tcl scripting commands used in Eggdrop/Windrop.
A!: A good guide to Tcl scripting for Eggdrop/Windrop from SUNiNet. 

Q: I changed the settings for my channel in the config file but my bot still does <insert whatever channel setting related thing here>, what's wrong?
A: Once your bot reads your Windrop config file for the first time it creates a channel settings file where it stores those settings.. And the channels settings file overrides any settings that are to the Windrop config file.  To change your settings, either delete the channel settings file (NOT recommended), or simply dcc chat your bot and use the .chanset command..  Type .help chanset if you need help.  Anything you change with the .chanset command will be saved to the channel settings file.

Q: Can Eggdrops and Windrops link and share files?
A: Yes Eggdrops and Windrops can link and share userfiles without any problems. Just make sure the Eggdrops and Windrops are compatible and using the same handle length.
Eggdrop/Windrop 1.1.x can only share userfiles with other 1.1.x versions.
Eggdrop/Windrop 1.7.x can only share userfiles with other 1.7.x and later versions 

Q: How do I make my bots share userfiles?
A: Check out the Setting Up a Botnet guide at slennox's eggdrop page. Just make sure the bots are compatible and using the same handle length.
Eggdrop/Windrop 1.1.x can only share userfiles with other 1.1.x versions.
Eggdrop/Windrop 1.7.x can only share userfiles with other 1.7.x and later versions 

Q: How do I make my bot op other bots?
A: If you are using Windrop 1.6.0 or later then try using the included botnetop module, edit the settings in botnetop.conf with a text editor (Don't use notepad!). Then edit your eggdrop config and add the following line anywhere in the module section:
source bonetop.conf
Then either .rehash or .restart bot via dcc chat/telnet or /msg bot rehash password
A1: Try the botnetop.tcl script at slennox's eggdrop page, open the script with a text editor (Don't use notepad!) and edit the settings. Then move the script to the scripts directory of each bot and add the following line to the end of your config file
source scripts/botnetop.tcl
Then either .rehash or .restart bot via dcc chat/telnet or /msg bot rehash password

Q: How can I make several bots linked together all do one command ?
A: Try the netbots.tcl script at slennox's eggdrop page, edit the scripts settings and add the script to each bot. That script is quite complex though so it isn't recommended for beginners