Confusion with Clsuatl Omega installation on Windows 7 64bit

[Bara'a Al-Hammad]

Hi

I have been trying to install Clustal Omega on my Windows 7 64bit platform for a whole week but it's not getting configured correctly , it's really driving me crazy .

I followed the instructions provided here : ( http://www.blaststation.com/freestuf...64ClustalO.php ) , but I noticed that no file named ( libcc_sjlj-1.dll ) was created ... instead I had this file ( libgcc_s_sjlj-1.dll ) !!

When I attempt to run it after installation it pops up for a second and disappears , on the other hand it's not recognizable by the cmd !!

I desperately need help with this , please if any one know what's wrong with this logfile ( https://gist.github.com/Baraa-1989/6d38f6327a5772d4d6c6 ) I will be very grateful and thankful for his/her help .

I need to know what's missing there .... is it something related to the platform characteristics that I'm not aware of ?!

Regards all ^_^

[GenoMax]

If you are working in windows why are you not using the pre-compiled binary provided here: http://www.clustal.org/omega/#Download There is no need to compile anything.

[Bara'a Al-Hammad]

If you are working in windows why are you not using the pre-compiled binary provided here: http://www.clustal.org/omega/#Download There is no need to compile anything.

Because it's not working !!

I tried to follow the installations instructions in the INSTALL.txt file , but when I came across argtable2 installation according to this reference ( http://sourceforge.net/projects/argtable/files/ ) I couldn't proceed with this command ( nmake -f Makefile.nmake ) ... it was not recognized by the cmd and I went through maze of dependencies , by which I mean installing visual studio , etc.

Do you have any idea why is that , please ?!

[GenoMax]

It is unfortunate that the INSTALL.txt file was left in the windows binary zip package. It does not appear to have any useful role in windows.

Just run included windows executable (clustalo.exe, like you did clustalw2.exe) before.

[Bara'a Al-Hammad]

It is unfortunate that the INSTALL.txt file was left in the windows binary zip package. It does not appear to have any useful role in windows.

Just run included windows executable (clustalo.exe, like you did clustalw2.exe) before.

So I'm not the only one who thought that it was weird to have (INSTALL.txt) in a windows package!!

I think such mistake could definitely consume memory as it leads to unnecessary installation's and procedures ... that's really irritating especially for those who are unfamiliar with Linux commands.

Let's hope it works as simple as running ClsutalW2 , Thanks a lot GenoMax

[Bara'a Al-Hammad]

Just run included windows executable (clustalo.exe, like you did clustalw2.exe) before.

You were absolutely right

So , the solution was just to provide the full path of the executable (clustalo.exe) to the CMD , along with the query .

This works perfectly