Avogadro 0.9 doesn't work on Windows

Development
1

Hello all,

On a clean WinXP machine (untouched by OB development), Avogadro 0.9
fails to start - no error message except “The system cannot execute
the specified program”. Avogadro 0.8.1 works fine. Avo 0.9 works fine
on my dev WinXP machines.

  • Noel
2

Noel O’Boyle wrote:

Hello all,

On a clean WinXP machine (untouched by OB development), Avogadro 0.9
fails to start - no error message except “The system cannot execute
the specified program”. Avogadro 0.8.1 works fine. Avo 0.9 works fine
on my dev WinXP machines.

  • Noel

Hi Noel,

Could you try http://blog.cryos.net/uploads/Avogadro-0.9.0a-win32.exe
(mentioned earlier as the CPack based Windows installer). It should
solve this issue, although currently does not have all the Python
support compiled in. This is an issue with manifests as far as I can
tell and this installer should have cured that problem.

This installer is also much more automated - nmake package will create a
new package. I would appreciate feedback on how well it works. I will
see about adding the Python support in the near future, otherwise you
can install the original if you install the MSVC C/C++ runtime
redistributable package too.

Thanks,

Marcus

3

2009/2/10 Marcus D. Hanwell marcus@cryos.org:

Noel O’Boyle wrote:

Hello all,

On a clean WinXP machine (untouched by OB development), Avogadro 0.9
fails to start - no error message except “The system cannot execute
the specified program”. Avogadro 0.8.1 works fine. Avo 0.9 works fine
on my dev WinXP machines.

  • Noel

Hi Noel,

Could you try http://blog.cryos.net/uploads/Avogadro-0.9.0a-win32.exe
(mentioned earlier as the CPack based Windows installer). It should solve
this issue, although currently does not have all the Python support compiled
in. This is an issue with manifests as far as I can tell and this installer
should have cured that problem.

This installer is also much more automated - nmake package will create a new
package. I would appreciate feedback on how well it works. I will see about
adding the Python support in the near future, otherwise you can install the
original if you install the MSVC C/C++ runtime redistributable package too.

Thanks,

Marcus

Yes - the new one works, but I prefer the Python one :slight_smile: though am
confused by the “foo” menu option. FYI, it may be lame but for OB we
bundle the vcredist with the installer and run it.

Noel

4

Noel O’Boyle wrote:

2009/2/10 Marcus D. Hanwell marcus@cryos.org:

Noel O’Boyle wrote:

Hello all,

On a clean WinXP machine (untouched by OB development), Avogadro 0.9
fails to start - no error message except “The system cannot execute
the specified program”. Avogadro 0.8.1 works fine. Avo 0.9 works fine
on my dev WinXP machines.

  • Noel

Could you try http://blog.cryos.net/uploads/Avogadro-0.9.0a-win32.exe
(mentioned earlier as the CPack based Windows installer). It should solve
this issue, although currently does not have all the Python support compiled
in. This is an issue with manifests as far as I can tell and this installer
should have cured that problem.

This installer is also much more automated - nmake package will create a new
package. I would appreciate feedback on how well it works. I will see about
adding the Python support in the near future, otherwise you can install the
original if you install the MSVC C/C++ runtime redistributable package too.

Yes - the new one works, but I prefer the Python one :slight_smile: though am
confused by the “foo” menu option. FYI, it may be lame but for OB we
bundle the vcredist with the installer and run it.

I thought you would prefer the Python one :wink: The “foo” menu option? May
be I did something wrong, but I don’t remember that. I am not a Windows
developer, Windows is rather just another target for our cross platform
application. We have quite a few other DLLs too and this seems like the
right solution to me. It seems that a lot of other apps take this
approach too.

It also has the added side benefit that with a little more work you
could run Avogadro from a USB stick without any installation (I need to
make a few more things relative in their loading). Short term I just
need to speak with Tim about what he installed to get all the Python
deps so I can make an all singing, all dancing Python installer too.

CPack is a great solution for us to make new Windows releases too - it
automates the packaging process into an nmake target. It is a shame the
last release suffered from these issues on Windows, and so I was
experimenting with a way to streamline Windows packaging.

Thanks,

Marcus

5

Hi,

On Tue, Feb 10, 2009 at 3:01 PM, Noel O’Boyle baoilleach@gmail.com wrote:

Yes - the new one works, but I prefer the Python one :slight_smile: though am
confused by the “foo” menu option. FYI, it may be lame but for OB we
bundle the vcredist with the installer and run it.

The “foo” menu option is just an example python extension. I’m working
on some better examples for 1.0:
http://avogadro.openmolecules.net/wiki/Python_Extensions

Tim