Uwe Stöhr wrote:
Marcus D. Hanwell schrieb:
I don’t understand. The problem is independent of the install location. I installed 0.9.5b on two
different PCs with two different Windows versions and the result is the same. The problem is the
wrong file parsing of Avogadro so I don’t expect that it will work by moving files and directories.
How have you determined this?
Because the crash only occurs with files that have Windows line endings. With Unix line endings I
get an error message that Avogadro cannot load it, but not crash.
As I stated - I tested both ways (Unix and Windows line endings) - no
But now I tested out 0.9.5c:
The file handling situation is much better.
Concerning the crash:
- Strangely the crash only occurs, when you double click on a file in Windows file explorer.
- When I drag the file to Avogadro’s main window or use the menu File -> Open, the molecule is
Here I double clicked in explorer - no crash. Any other way I tried - no
Sorry for the confusion…I used Samba to get files into the VMWare
virtual machine I am using to do this testing. I am using Windows XP
inside a virtual machine, I am not a Windows user and do not have a
system with Windows installed outside of a virtual machine.
I’m normally a Windows-only user but to be able to help people with Unix OSes, I installed Ubuntu
parallel to my Windows. This worked fine, so maybe you could do the same the opposite way.
This is exactly what I just stated… Windows XP installed in a VMWare
virtual machine. This is how we built most of our releases for Windows
too. VMware in Linux/Mac with Windows XP.
I have tried many ways including following your recipe above. I cannot
reproduce your crash and nor can Tim.
Perhaps it helps that I found out that only the opening double-clicking crashed Avogadro.
Like I said - this does not cause a crash here. I already tested this
with both Unix and Windows line endings. No crash either way here with
0.9.3, 0.9.4 or 0.9.5 (python or not).
- if Unix line endings, then the file does not load. I do not have any
more time to look into this right now, Tim is also looking into the line
ending issue (but cannot reproduce your crash either).
OK, when nothing helps, then concentrate on fixing the line ending issue and postpone my crash.
With the latest couple of binaries the loading of files with different
line endings is now fixed. Windows or Unix file endings load fine in all
Thanks for your help and for the immediate release of new binaries.
We try to please, but like I said none of us are “real” Windows users. I
spend a lot more time than I would like testing code in a Windows XP
virtual machine though…
Hopefully we have managed to resolve some of the outstanding issues on