[sage-support] Re: Failure to import Sage-4.7.ova into VirtualBox under Win7

2011-06-30 Thread Volker Braun
Just to double-check, your md5sum is 3eadcc287c92c5391417b517e01edd9b? It does work for me. Do you happen to have any umlaut in the directory path? This can apparently cause this error, see http://www.virtualbox.org/ticket/6588. -- To post to this group, send email to

[sage-support] Re: Failure to import Sage-4.7.ova into VirtualBox under Win7

2011-06-30 Thread Volker Braun
I just realized that the file name is called Sage-4.7.ova but it should be sage-4.7.ova (lower case!). Virtualbox is unfortunately very picky about the file name. This is http://www.virtualbox.org/ticket/9033. Harald: can you fix the file name on the download page? -- To post to this group,

[sage-support] Re: Failure to import Sage-4.7.ova into VirtualBox under Win7

2011-06-30 Thread Harald Schilly
On Thu, Jun 30, 2011 at 13:48, Volker Braun vbraun.n...@gmail.com wrote: I just realized that the file name is called Sage-4.7.ova but it should be sage-4.7.ova (lower case!). Virtualbox is unfortunately very picky about the file name. This is http://www.virtualbox.org/ticket/9033. Harald: can

[sage-support] Re: Failure to import Sage-4.7.ova into VirtualBox under Win7

2011-06-30 Thread Volker Braun
Kart-Dieter Crisman suggested at SD31 that the virtualbox machine file name should be lower case to be consistent with the other Sage downloads. I then implemented this in the newer version of the Sage virtual appliance. So this is where the confusion comes from. But I agree of course that