Re: [Amsn-devel] New contactlist feature - filters

Sun, 29 Jan 2006 04:33:19 -0800

I've changed the line, and I don't get errors any more, but I can't connect to aMSN. Here's the log:

[12:31:31] cmsn_auth starting, stat=a
[12:31:31] cmsn_auth starting, stat=v
[12:31:31] cmsn_auth starting, stat=i
[12:31:31] cmsn_ns_handler: got a NS transfer, reconnecting to 64.4.27.142!
[12:31:31] gotNexusReply: loginurl=https://loginnet.passport.com/login2.srf
[12:31:31] gotNexusReply: finished before authentication took place
[12:31:31] cmsn_auth starting, stat=a
[12:31:31] cmsn_auth starting, stat=v
[12:31:32] cmsn_auth starting, stat=i
[12:31:32] Got unknown NS input!! --> GCF
[12:31:32] cmsn_auth starting, stat=u
[12:31:32] cmsn_auth_msnp9: Nexus has replied so we have login URL...
[12:31:32] ::DirectConnection::authenticate: Getting https://loginnet.passport.com/login2.srf
[12:31:33] ::DirectConnection::GotAuthReply 200 Ticket= t=70cZH1f31F3emj1TKYDEW92ixKkaq5rmSfWBiOfsWEPQUQHbyrGOIezSQ!vZIgONIJVw0VGkciId7NYSo7OySP18iWcllUUnS76AeiepHdbERNmv!iECN!vNzZADBFl9ym&p=76FE!QpVABuNbBg9ozslWKaRgBiwSy!JxqWYzknEjvHhZbI2KoODKQPyfGIkrmScBIxYy*ptofv6FJ1G2*IB!51NrbdIlOpqHJ58un8JvcAVRra6ZgrKzN4hHyqHQaYkqyH*JoeOL!g6CebVvM2gwcNjcztEq7pKsm
[12:31:33] Got unknown NS input!! --> 420
[12:31:33] Read EOF in ::NS::Connection1, closing
[12:31:33] ::MSN::CloseSB ::ns Called
[12:31:33] ::MSN::ClearSB ::ns called
[12:31:33] clearing sb ::ns. oldstat=us
[12:31:33] ::DirectConnectin::Write: SB ns problem when writing to the socket: can not find channel named ""...
[12:31:33] ::MSN::CloseSB ns Called
[12:31:33] ::MSN::ClearSB ns called
[12:31:33] clearing sb ns. oldstat=d
[12:31:33] ::MSN::CloseSB ns Called
[12:31:33] ::MSN::ClearSB ns called
[12:31:33] clearing sb ns. oldstat=d
[12:31:33] Loging out



On 29 Jan 2006, at 10:32, Yoda BZH wrote:

same here too, using tcldom 3.0 and tclsoap 1.6.7

I suppose that's tclsoap's fault (or we need to fallback to dom 2.x)
/usr/lib/tclsoap1.6.7/SOAP.tcl:25
   if { [catch {package require dom 2.0} ::SOAP::domVersion]} {

It seems that tclsoap WANT dom 2.0. But even if dom 3.0 is installed,
the major version don't match, so `package require' fail
then versions later than version are also acceptable as long as they
have the same major version number as version.

if they don't have the same major version, it won't works.
With
    if { [catch {package require dom 3.0} ::SOAP::domVersion]} {
I can load sucessfully tclsoap. But I haven't test if it works in amsn

(hope this helps)
On 1/29/06, Tom Hennigan <[EMAIL PROTECTED]> wrote:
I have the same error on Mac OS X. tclsoap version 1.6.7.




On 29 Jan 2006, at 01:59, Arieh Schneier wrote:

then change server in advanced prefs to muser.messenger.hotmail.com
instead of messenger.hotmail.com.

Then log in and voila, instant new contactlist (but you can't do
anything else :P)

I tried that and got the error below. It seems to crash becuase it loads on
older version of Soap from my Tcl directory (version 1.6):


require dom package greater than 1.6
    while executing
"error "require dom package greater than 1.6""
    invoked from within
"if {[catch {package require SOAP::dom 1.0} ::SOAP::domVersion]} {
    if { [catch {package require dom 2.0} ::SOAP::domVersion]} {
        if { [catch..."
    (file "C:/Program Files/Tcl/lib/tclsoap1.6.7/SOAP.tcl"
line 24)
    invoked from within
"source {C:/Program Files/Tcl/lib/tclsoap1.6.7/SOAP.tcl}"
    ("package ifneeded" script)
    invoked from within
"package require SOAP"
    (file "msnp13.tcl" line 1)
    invoked from within
"source msnp13.tcl"
    ("v" arm line 8)
    invoked from within
"switch [ns cget -stat] {

  a {
   #Send three first commands at same time, to it faster
   if { [::config::getKey protocol] == 11 } {
    ::MSN::Writ..."
    (procedure "cmsn_auth" line 7)
    invoked from within
"cmsn_auth $item"
    ("VER" arm line 2)
    invoked from within
"switch [lindex $item 0] {
   MSG {
    cmsn_ns_msg $item $message
    return 0
   }
       IPG {
       ::MSNMobile::MessageReceived "$message"
      ..."
    (procedure "cmsn_ns_handler" line 17)
    invoked from within
"cmsn_ns_handler $command $message"
    ("default" arm line 2)
    invoked from within
"switch [lindex $command 0] {
    ILN {
     if {$::msnp13} {
      $self handleILN $command
     } else {
      cmsn_ns_handler $command $message
    ..."
    (procedure "::NS::Snit_methodhandleCommand" line 27)
    invoked from within
"::NS::Snit_methodhandleCommand ::NS ::NS::Snit_inst1 ::ns ::ns {VER 1
MSNP13 CVR0}"
    ("uplevel" body line 1)
    invoked from within
"uplevel 1 $command $args"
    invoked from within
"$options(-name) handleCommand $command"
    (procedure "::Connection::Snit_methodreceivedData" line
39)
    invoked from within
"::Connection::Snit_methodreceivedData ::Connection
::Connection::Snit_inst2
::NS::Connection1 ::NS::Connection1"
    ("uplevel" body line 1)
    invoked from within
"uplevel 1 $command $args"
    invoked from within
"::NS::Connection1 receivedData"
    ("uplevel" body line 1)
    invoked from within
"uplevel 1 $command $args"
    invoked from within
"ns receivedData"



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
_______________________________________________
Amsn-devel mailing list

------------------------------------
Tom Hennigan




--
Admin HLTV-Fr : http://www.hltv-fr.com
Admin, Project leader & coder Games-Tv : http://www.games-tv.org
Admin WestArena : http://www.westarena.net


o May the Force be with you
o Do it, or not, but there's no try


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
_______________________________________________
Amsn-devel mailing list

------------------------------------
Tom Hennigan

Reply via email to