Hi all, I have installed twisted 2.2.0, pycrypto2.0.1, pyopenSSL0.6, PIL 1.1.5 
and all are for python 2.4.
I have even include libeay32.dll into windows/system32...

I'm getting the following error:

Unable to install any good reactors (kqueue, epoll, poll).
We fell back to using select. You may have scalability problems.
This reactor will not support more than 1024 connections +at a time.
You must install pycrypto and pyopenssl.
Traceback (most recent call last):
  File "pymsnt.py", line 11, in ?
    import main
  File "C:\Program Files\wildfire\Transport\pymsnt\src\main.py", line 102, in ?
    import session
  File "C:\Program Files\wildfire\Transport\pymsnt\src\session.py", line 7, in ?

    import legacy
  File "C:\Program Files\wildfire\Transport\pymsnt\src\legacy\__init__.py", line
 4, in ?
    from glue import LegacyConnection, LegacyGroupchat, translateAccount, startS
tats, updateStats, reloadConfig
  File "C:\Program Files\wildfire\Transport\pymsnt\src\legacy\glue.py", line 8,
in ?
    from tlib import msn
  File "C:\Program Files\wildfire\Transport\pymsnt\src\tlib\msn\__init__.py", li
ne 1, in ?
    from msnw import MSNConnection, MultiSwitchboardSession
  File "C:\Program Files\wildfire\Transport\pymsnt\src\tlib\msn\msnw.py", line 1
4, in ?
    from tlib.msn import msn
  File "C:\Program Files\wildfire\Transport\pymsnt\src\tlib\msn\msn.py", line 10
4, in ?
    from twisted.internet.ssl import ClientContextFactory
  File "c:\python24\lib\site-packages\twisted\internet\ssl.py", line 47, in ?
    from OpenSSL import SSL
  File "C:\Python24\Lib\site-packages\OpenSSL\__init__.py", line 11, in ?
    import rand, crypto, SSL, tsafe
ImportError: DLL load failed: The specified procedure could not be found.


I'm not sure why it still mention "i must install pycrypto and pyopenssl. I 
have double checked the site-packages folder and its there.

What version of pycrypto and pyopenssl do u guys installed?
I'm using the following:

http://webcleaner.sourceforge.net/pyOpenSSL-0.6.win32-py2.4.exe
PyOpenSSL 0.6

http://www.voidspace.org.uk/python/modules.shtml#pycrypto (binary)

Please i hope u guys could help me out with this problem. Thx.

                
---------------------------------
Brings words and photos together (easily) with
 PhotoMail  - it's free and works with Yahoo! Mail.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://modevia.com/pipermail/py-transports/attachments/20060217/0ae15f69/attachment-0001.htm
From [EMAIL PROTECTED]  Fri Feb 17 22:28:27 2006
From: [EMAIL PROTECTED] (James Bunton)
Date: Fri Feb 17 22:28:51 2006
Subject: [py-transports] Re: [jdev] PyMSNt 0.11 release
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>

On 18/02/2006, at 6:06 AM, Norman Rasmussen wrote:

> On 2/17/06, Peter Saint-Andre <[EMAIL PROTECTED]> wrote:
>> How do you complete the file transfer? In particular, I'm interested 
>> in
>> whether the JID of the MSN user is a bare JID or a full JID. I've 
>> heard
>> reports that it's a bare JID, which might cause problems because
>> JEP-0065 requires it to be a full JID. I'm willing to modify JEP-0065
>> (and proxy65) on this point if required.
>
> File transfers always used to work (with Psi) with a bare jid.  Now
> however all msn transport users are sending presence from the 'msn'
> resource.  (It would be fairly neat if it was linked to the msn client
> version or something dynamic, but I'm sure that would make coding
> harder - James: any chance that the iq:version reply could show that
> info?)
<snip>

hrmm.. Official clients send a capabilities bit that we could probably 
use to narrow it down to MSN6, MSN7, etc. Third party clients also send 
that though, but they'll often send an x-clientcaps message in chats. 
You don't get that until you start a conversation though. That means 
we'd be changing the contact version in the middle of a session. Not a 
very nice thing to do.

More importantly, the best way to distribute this version info is with 
the presence caps protocol. But having a bunch of clients that will all 
have identical disco#info responses seems a bit of a waste.

Plus it would be really messy and hard to do, I mean distinguishing 
third-party and official clients. I'd also have to update the list of 
clients periodically.

Nah, I don't think so :P
It is a fun idea though :)

---

James

Reply via email to