Author Topic: AOchat class needs the sockets extension to work (Read 2667 times)

Jaqueme · « **on:** August 11, 2006, 12:12:18 pm »

Ok, I did a search and came across a few posts that advise the fix for this is to change ;extension=php_sockets.dll to extension=php_sockets.dll in the php.ini file. In my bot directory, however, I find 2 ini files, php.ini-dist and php.ini-recommended. Not knowing which one to edit, I edited both. I get the same error, which suggests to me neither is the correct ini file. I had unzipped both php and bebot into the same folder, so for giggles I unzipped bebot into another file as a reference. I could not find any ini files in that one.

I'm running BeBot_v0.2.2, PHP 5.1.1, and MySql 5.0.24

Where is this damn file?

Zimble · « **Reply #1 on:** August 11, 2006, 02:14:59 pm »

Try renaming the file to php.ini and move it to c:\windows\system32 (not quite sure about the exact location where php searches it's .ini on Windows)

or:

Startup php with the -c Option to tell php which ini to use

c:\mybot>php -c c:\mybot\php.ini start.php

HTH

Khalem · « **Reply #2 on:** August 11, 2006, 02:19:32 pm »

Download: http://files.shadow-realm.org/bebot/BeBot-php_v5.1.4.zip

Extract those files to the BeBot folder. It includes all the extentions you need.

Start the bot using: start.bat That will ensure that php looks for the extentions in the right place using the php.ini that came with the bot.

Jaqueme · « **Reply #3 on:** August 12, 2006, 11:02:39 am »

I already tied the v5.1.4.zip. After unzipping it into the bot file trying to start the bot with c:\bebot\php start.php gets the same error (AOchat class etc.). Trying c:\bebot\start.bat or c:\start.bat gets me a "Windows cannot find the file .bat. Trying c:\bebot\start just opens another dos command window.

Extracting those files put them in their own folder in Bebot (i.e. C:\bebot\bebot-php_v5.1.4\[New extracted stuff]). I tried moving the new extracted files into the bebot root but got no changes.

And Zimble, your first suggestion doesn't answer the question of which ini file to edit and move. Your second one doesn't say which file to edit, and while there are some ini files in windows32, there is no php.ini.

* Jaqueme sighs

Guess I'll have to back everything out and start from scratch again...

Jaqueme · « **Reply #4 on:** August 12, 2006, 11:40:40 am »

OK, I re-built the bot into another folder. This time I used bot version 0.2.6. I unzipped php5.1.1 into the file, and I unzipped bebot-php_v5.1.4. I didn't back out or re-install sql, and I flew over the config files from the last bot. I left the php_v5.1.4 files in their own folder. Starting the bot with "start.bat" now actually starts the bot (which is more than I was getting), but I get essentially the same error:

Warning: dl(): Unable to load dynamic library './php_extension/php_sockets.dll'
- The specified module could not be found.
in C:\BeBot_v0.2.6\main.php on line 58
Loading php_sockets.dll failed. Sockets extention required to run this bot
C:\BeBot_v0.2.6>pause
Press any key to continue . . .

C:\BeBot_v0.2.6>

Getting closer...

Jaqueme · « **Reply #5 on:** August 12, 2006, 11:44:45 am »

OK, I copied the php.extension folder from php_v5.1.4 into the bebot root. That cleared up the php_sockets.dll issue, but I then got a "could not find gmp.dll" error. I copied that dll from the php_v5.1.4 folder into the bebot root and sucess!

Bot seems to be running fine now. It loaded all the modules and updated the org roster.

Thanks for the help guys

Khalem · « **Reply #6 on:** August 12, 2006, 03:35:42 pm »

The php 5.1.4 package eliminates the need for the 5.1.1 package altogether as its a newer version.
Glad to hear you got it working. And yes, the files from the 5.1.4 package should go into the Bebot root directory, not its own directory.

Alreadythere · « **Reply #7 on:** August 12, 2006, 04:04:41 pm »

On a semi-related point:

There is a start command under windows, which allows to open files with the related program based on the extension.
Perhaps it would be better to rename the file to something like startbot.bat - just so there won't be any unintended mix of those two commands.