aMSN Forums
August 15, 2020, 08:50:18 pm *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: New forum for aMSN !!
  Home Help Search Login Register  
  Show Posts
Pages: [1]
1  aMSN Support / Windows / Re: Problems with 0.98.9 on: June 21, 2012, 09:06:55 pm
Here is the error log:

can not find channel named ""
    while executing
"fileevent $sock writable"
    (procedure "::p2p::BaseP2PTransport::Snit_method__Send_chunk" line 25)
    invoked from within
"$self __Send_chunk $peer $peer_guid $chunk $blob"
    (procedure "::p2p::BaseP2PTransport::Snit_methodProcess_send_queue" line 32)
    invoked from within
"$self Process_send_queue"
    (procedure "::p2p::BaseP2PTransport::Snit_methodsend" line 8)
    invoked from within
"$transport send $peer $peer_guid $blob"
    (procedure "::p2p::P2PTransportManager::Snit_methodsend" line 9)
    invoked from within
"[$self transport_manager] send $options(-peer) "" $blob"
    (procedure "::p2p::P2PSession::Snit_methodSend_p2p_data" line 23)
    invoked from within
"$self Send_p2p_data $resp"
    (procedure "::p2p::P2PSession::Snit_methodRespond" line 12)
    invoked from within
"$self Respond "200""
    (procedure "::p2p::MSNObjectSession::Snit_methodaccept" line 7)
    invoked from within
"$session accept [$obj cget -data]"
    (procedure "::p2p::MSNObjectStore::Snit_methodHandle_message" line 15)
    invoked from within
"$handler Handle_message $peer "" $msg"
    (procedure "::p2p::P2PSessionManager::Snit_methodOn_blob_received" line 43)
    invoked from within
"::MSN::P2PSessionManager1 On_blob_received p2pBlobReceived2 ::p2p::BaseP2PTransport::MessageBlob21"
    ("eval" body line 1)
    invoked from within
"eval $listener [linsert $args 0 $eventName]"
    (procedure "::Event::fireEvent" line 11)
    invoked from within
"::Event::fireEvent p2pBlobReceived2 p2pTransportManager $blob"
    (procedure "::p2p::P2PTransportManager::Snit_methodOn_blob_received" line 6)
    invoked from within
"::p2p::P2PSessionManager::P2PTransportManager1 On_blob_received p2pBlobReceived ::p2p::BaseP2PTransport::MessageBlob21"
    ("eval" body line 1)
    invoked from within
"eval $listener [linsert $args 0 $eventName]"
    (procedure "::Event::fireEvent" line 11)
    invoked from within
"::Event::fireEvent p2pBlobReceived p2pBaseTransport $blob"
    (procedure "::p2p::BaseP2PTransport::Snit_methodOn_signaling_chunk_recei..." line 19)
    invoked from within
"$self On_signaling_chunk_received $chunk"
    (procedure "::p2p::BaseP2PTransport::Snit_methodOn_chunk_received" line 22)
    invoked from within
"$self On_chunk_received [$self cget -peer] [$self cget -peer_guid] $chunk"
    (procedure "::p2p::SwitchboardP2PTransport::Snit_methodOn_message_receiv..." line 31)
    invoked from within
"$transport On_message_received $msg"
    (procedure "::SB::Snit_methodhandleMSG" line 207)
    invoked from within
"$self handleMSG $command $message"
    ("MSG" arm line 2)
    invoked from within
"switch -- [lindex $command 0] {
$self handleMSG $command $message
cmsn_update_users $self $com..."
    (procedure "::SB::Snit_methodhandleCommand" line 30)
    invoked from within
"$options(-name) handleCommand $command $payload"
    (procedure "::Connection::Snit_methodreceivedData" line 111)
    invoked from within
"::MSN::SB5 receivedData"
2  aMSN Support / Windows / Re: Problems with 0.98.9 on: June 20, 2012, 10:18:03 am
Sorry for the wait.

I just reinstalled 0.98.9 and now I'm waiting until the issue reappears.
3  aMSN Support / Windows / Problems with 0.98.9 on: June 09, 2012, 10:14:23 pm

After I updated to 0.98.9 I got a few problems with aMSN (Windows 7 x64):

1. Whenever a specified contact (I know that guy for years) got online aMSN started throwing error messages. The same happens when I try to contact that him or he tries to contact me.
2. When I'm in a group conversation with other contacts and that specified contact has been invited, aMSN threw an error message again and it seems like I'm not in the group conversation anymore.
3. The update notification still appeared when I started aMSN, although I had the latest version already installed.

To solve all these problems above I deinstalled 0.98.9 and reinstalled 0.98.4 again (freshly downloaded from here). Now everything works like it used to be.

Unfortunately, I can't give the actual error message, because I didn't made a screenshot before I decided to downgrade. But I hope it may help nonetheless.
4  The Community / Plugins / Music Plugin has a trojan? on: August 19, 2008, 12:20:37 pm
Okay, just sent it to Avira.
5  The Community / Plugins / Music Plugin has a trojan? on: August 18, 2008, 09:26:30 pm
I just downloaded and unzipped it again and the message popped up again. It IS a false alarm...
6  The Community / Plugins / Music Plugin has a trojan? on: August 18, 2008, 09:13:40 pm
Well, I hope so. It would be quite odd if it's not. I should check the Avira settings...

Unfortunately I don't have a compiler to compile its sources (but I know where to find). I'll keep this in mind, thank you. Smiley

Ah... makes sense. Thanks. Smiley
7  The Community / Plugins / Music Plugin has a trojan? on: August 18, 2008, 08:26:54 pm

I'm new to this forum and I have something odd to report. Around 15 minutes ago I logged in into aMSN 0.97.2 (Windows XP), and my virus scanner (Avira AntiVir Personal) reported a trojan in the music plugin, the file MusicWA.exe to be exact (this plugin: ). The name is "TR/Spy.Gen". Immediately I deactived the plugin and told Avira to send it in quarantine, where it still resides. Another scan of this file still says the same. Before I started aMSN Avira updates its virus signatures.

I'm runnung a scan of my system right now to be sure it's still clean. But... I'm still concerned. Could it be just a false alarm? Yesterday everything was still okay with aMSN and its plugins.

The scan was successful, no viruses etc. found. My system appears to be clean.
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!