aMSN login error

[anserq]

I did that, and now, it keeps on asking... to download the TLS file, even though ive set it to DISABLE SSL and unchecked that box.. and it ekeps asking me over and over again?

[Brain1127]

to vivia

If you just change 1.1 to 1.0 in proc SecureSocket and leave all other 1.1 intact, can you connect and work OK? Please test more intensively and get back to us (within this weekend, if you can). It SHOULD be ok, because this is only used when trying to create a secure connection, not when actually transferring data. Waiting impatiently... Smile

yes.just change 1.1 to 1.0 in proc SecureSocket. And I can connect and work.(According to my dump packets of MSN Messenger.it was really unsecure connection to login.live.com and use HTTP 1.0 in all connections.It's some wierd. :?:I dont know whether there has the same example like me)

Now,Receive and Send Messeges were OK.Mail Notify was OK,too.Nudge and Smile were OK .Maybe I should try sending or receiving a very long messege. How long could it be available??
Some user defined Protrait cannot show.
I cannt test File Transfer.for there's some wrong with MSNFT.It's kind of connection timeout.And Once connection can build,the speed is ugly..below 1K/s.(it's an meaningless thing to me at least.I prefer REAL ftp trans)
WebCam is forbidden in My office..so,I cannt test for it

PS: Is there any prossible  for MS to use different login ways in different Countries according to USA laws of restricted crypt/decrypt??

[vivia]

@anserg: I thought I had removed the option to disable SSL? I'll take a look again. Anyway, after latest changes, it won't work without SSL.

@Brain: Thanx! I'll put that on CVS. Thanx a lot!

[anserq]

vivia, im having problems compiling the cvs version it asks for TCXimage or something... errrrr, im sorry if im posting the same thing over and over?lol.

[vivia]

It asks for TkCximage and right below this it gives you instructions on what to do. Why don't you follow the instructions, just for a change?

[stuart_taylor26]

Hi All,

I am a new user to aMSN, thought I would give it a go.

I have installed it and it all looks great, however i want aMSN to run as soon as windows boots up, however I keep getting an error 2 message box come up, which prevents aMSN running at the start which means I manually have to load it up.

Can anyone help me, as I have tried to find out what th error code means and I cant?

[vivia]

Why don't you search the forum?
Known error but we have no idea where it comes from

[spektr]

pibi : it's not amsn's fault or anything, it's just the way tls works, the reason is simple, tls should be installed in

Code:

/usr/lib/tls1.50/

so you have the files

Code:

/usr/lib/tls1.50/tls.tcl

and

Code:

/usr/lib/tls1.50/pkgIndex.tcl

but the .so should be in

Code:

/usr/lib/

so you have

Code:

/usr/lib/libtls1.50.so

which means that in the pkgIndex.tcl file, you need to load the file in the previous directory, so pkgIndex.tcl contains a

Code:

load [file join $dir .. libtls1.50.so]

p.s. : tls1.50 or tls1.41 it's the same concept...

Hi Kakaroto, I have a problem relating to this. I am using AMSN 0.96b (CVS), and TCL/TK8.5a4. For some reason I am getting the error that others are talking about above; when I start amsn it says I don't have TLS installed, or it can't find it. However, it most certainly is (and I recompiled it after installing the newest TCL/TK):

Code:

[ Searching for packages matching tls... ]
* Contents of dev-tcltk/tls-1.5.0:
/usr
/usr/bin
/usr/include
/usr/include/tls.h
/usr/lib
/usr/lib/libtls1.50.so
/usr/lib/tls1.50
/usr/lib/tls1.50/pkgIndex.tcl
/usr/lib/tls1.50/tls.tcl
/usr/share
/usr/share/doc
/usr/share/doc/tls-1.5.0
/usr/share/doc/tls-1.5.0/ChangeLog.gz
/usr/share/doc/tls-1.5.0/README.txt.gz
/usr/share/doc/tls-1.5.0/license.terms.gz

(This is on gentoo). I give AMSN the TLS path of /usr/lib/tls1.50, /usr/lib, etc, nothing seems to work. Neither does copying the tls files into any of the amsn directories. Now, when I revert to TCL/TK8.4.12, amsn can find TLS again. However, this is not optimal, because once you get used to amsn with antialiased fonts, you can't go back!!! Any ideas??

[kakaroto]

Hi spektr,  
I think it was already answered, for tcl/tk 8.5a4 and up, tls gets broken because tcl/tk became stricter.. you need to open the pkgIndex.tcl file in your tls install dir, change the line

Code:

package ifneeded tls 1.5 "...."

into

Code:

package ifneeded tls 1.50 "...."

[spektr]

Hi spektr,  
I think it was already answered, for tcl/tk 8.5a4 and up, tls gets broken because tcl/tk became stricter.. you need to open the pkgIndex.tcl file in your tls install dir, change the line

Code:

package ifneeded tls 1.5 "...."

into

Code:

package ifneeded tls 1.50 "...."

Thank you thank you thank you!!! Works perfectly, I am now happily in amsn 0.96b.

Keep up the good work!

[Netburn]

Hello Guys:

Well, I've just spent something like 4 hours trying to make AMSN work with the TLS and SSL thing. I read and followed all the possible available tutorials on the net, and none seemed to work. Here is my problem and how I corrected it, so it may help some people.

You download TCL and TK, compile them and install them, that should not be big deal.
Then you compile AMSN 0.96 telling it to use the TCL ant TK libraries you just installed.
Now the problem comes:

You open AMSN and it will ask you to install TSL, which you select to download and install depending on your architecture (Mine is AMD64). It is suppoused that after this step, AMSN and its SSL thing should work, BUT NO, THEY DON'T. So I tried downloading TSL and compiling it my self, and then recompiling everything, IT DIDN'T WORK either, even when I told AMSN where the TSL was.

Finally after doing some more research, I found the command "package require tsl" that you can type by "Ctrl+S" in the AMSN window. This command told me that TSL was trying to open "libssl0.9.7" but it could not find it!!!!!!!  Well, I had installed "libssl0.9.8" and that's why it did not want to work.

By the way, AMSN (this could be a bug) would not get the TSL lib from the folder you tell him to do it, it just will keep trying to access the lib from the AMSN PLUGINS folder. So, it does not matter if you compile and install TSL yourself, AMSN just won't get the library from the directory you installed it (probably /usr/local/lib/) even if you tell him to do it.

Anyway, I used Synaptics to get and install libssl.0.9.7(this is the one AMSN requires, and something should be done to tell him to ask for this one or a newer one) and after that, everything went ok.

I hope this may help some people, as none of the fixes posted on the net worked for me.

I am working on Ubuntu Edgy Eft (6.10) AMD64

Regards.

[kakaroto]

Hi Netburn,
it is very nice of you to post your experience here in order to help others.
Let me take a moment to help you understand better what happened.
First, the tls module amsn downloaded was compiled against libssl0.9.7 which was the latest release at that time if I remember correctly. You didn't have that lib on your PC which is why it didn't work (that's always the problem with linux, everyone has a different version of everything, so most linux users have to compile everything on their own).
I think you could have simply done 'apt-get install tcltls' and it should have work (it's written in the wiki).
Secondly, you say amsn doesn't care about the folder you specified for TLS. That's wrong, it's actualy how Tcl works, what we do with that directory is that we simply add it to the 'auto_path' variable of Tcl, which is a variable telling Tcl which directories to search when a 'package require' is specified (at that point, it looks in each directory for the pkgIndex.tcl file which states 'package ifneeded tls 1.5 "load libtls.so"' ). Now, you specified a directory, so that directory was added, but as any directory is added in a 'path' variable, the first paths are searched first.. if you deleted the tls directory from your plugins directory, it would have not found it there and would have searched in the next directory, which is the one is specified and it would have loaded the TLS package you compiled (which would have worked since you compiled it yourself).
Unfortunately, with Tcl we can't say 'search for a package in this directory', in the same way you can't say in Bash, to launch a command from a directory (unless you specify the whole path, but then you launch an executable, not a 'command'), so it always has to depend on that path variable.
Sorry you wasted 4 hours of your time over this, I'm sure you could have found the answer by either asking in the forums earlier, or asking on the IRC channel if someone was available to help you.
Nonetheless, I congratulate you for your perseverance and for you being able to find the solution on your own. It means you're good at figuring out things on your own, which is the basic skill needed for becoming a geek (unless you already are )
Thanks again, and I hope this answers your doubts.
Take care