No response from my windrop

TruceBuildman · Post by **TruceBuildman** » Thu Jun 21, 2007 9:26 pm

Hey guys.

I got a little problem running my Windrop. I am running it on a local area network in my house and I decided to set it up on a machine I have, and keep that on forever, so I went through all of it, and everything seems fine but when I go to IRC, my bot won't respond(No such nick/channel). all the modules load and everything seems fine but I get one weird message in the start file which is :

[19:30] Identd: I don't know why you're using winident.tcl on your system, but it probably won't work on anything but Windows.
[19:30] winident.tcl v1.2 by FireEgl@EFnet <fireEgl@windrop.cbj.net> - Loaded.

Anyone? Thanks.
Truce.

Alchera · Post by **Alchera** » Thu Jun 21, 2007 9:31 pm

That is simply an information message and does nothing to stop Windrop from running.

From the Command Prompt type:

Code: Select all

eggdrop -n bot.conf

The above will enable you to see all that is happening when you run your bot and figure out what is wrong. CTRL + C will terminate.

TruceBuildman · Post by **TruceBuildman** » Thu Jun 21, 2007 9:36 pm

All I get is "USER FILE NOT FOUND"

Alchera · Post by **Alchera** » Thu Jun 21, 2007 9:38 pm

TruceBuildman wrote:All I get is "USER FILE NOT FOUND"

Then you should have read the documentation correctly and paid attention to (and read) what was actually sent to the command console about creating a user file (just before the line that says "not launched").

Code: Select all

eggdrop -m bot.conf

TruceBuildman · Post by **TruceBuildman** » Thu Jun 21, 2007 9:40 pm

I did, it said that if it was the newer version of Eggdrop that I didnt have to edit the crontab or botchk

Alchera · Post by **Alchera** » Thu Jun 21, 2007 9:43 pm

TruceBuildman wrote:I did, it said that if it was the newer version of Eggdrop that I didnt have to edit the crontab or botchk

As windows has no crontab; please explain what that has to do with actually creating a user file (pretty basic stuff) at all?

TruceBuildman · Post by **TruceBuildman** » Thu Jun 21, 2007 9:46 pm

I really don't know, I did the whole -m command, and it said it launched, but then I did -n and nothing happened.

Alchera · Post by **Alchera** » Thu Jun 21, 2007 9:54 pm

TruceBuildman wrote:I really don't know, I did the whole -m command, and it said it launched, but then I did -n and nothing happened.

You need to kill the windrop (in Task Manager) and then re-open the Command Console and type:

Code: Select all

eggdrop -n bot.conf

To see what is happening if it has not connected.

You are also required to pay attention to what is sent to the Command Console at all times; the successful launch also indicated what you do once windrop connects to an IRC Network.

TruceBuildman · Post by **TruceBuildman** » Thu Jun 21, 2007 9:58 pm

The only error I get is the one regarding the userfile even when I kill it and have created it previously. After it has connected it tells me to message my bot but I get "No such nick\channel" every time. Everything works when I make the -m command(Well, in the launch screen, the bot doesnt show up)

Alchera · Post by **Alchera** » Thu Jun 21, 2007 10:12 pm

Alchera wrote:You need to kill the windrop (in Task Manager) and then re-open the Command Console and type:
Code: Select all
eggdrop -n bot.conf
To see what is happening if it has not connected.

You are also required to pay attention to what is sent to the Command Console at all times; the successful launch also indicated what you do once windrop connects to an IRC Network.

Windrop Central FAQ

Post by **nml375** » Fri Jun 22, 2007 8:34 am

Might be useful to combine -n and -m, as it would seem your bot is unable to connect to your irc-server for some reason. Might also considder replacing -n with -nt to gain partyline access from your console.
Ie:

Code: Select all

eggdrop -n -m bot.conf

Alchera · Post by **Alchera** » Fri Jun 22, 2007 9:02 am

nml375 wrote:Might be useful to combine -n and -m, as it would seem your bot is unable to connect to your irc-server for some reason. Might also considder replacing -n with -nt to gain partyline access from your console.
Ie:
Code: Select all
eggdrop -n -m bot.conf

The user is on DALnet and contacted me there; a combination of not reading eggdrop.conf, output from the Command Console and a missing DMZ setting in his router.

PS: He did use the "eggdrop -n -m bot.conf" combo.