Sage 4.2.1 under Windows 7 not functioning with VirtualBox either?

9 views
Skip to first unread message

Timothy Paysen

unread,
Dec 15, 2009, 1:01:03 AM12/15/09
to sage-s...@googlegroups.com
The VirtuaBox incarnation doesn't seem to be able to get to a Sage notebook.  It will bring you to the Sage web sit--but nothing more.  So--can't even say whether it works well or not--it just doesn't seem to work.

Charles J. Daniels

unread,
Dec 17, 2009, 10:39:14 PM12/17/09
to sage-support

If you are running VirtualBox version 3.1.0, which appliance are you
importing? A newer one was exported fairly recently to correct a
problem that occurred during importing. The MD5 checksum of the zip
you downloaded should be b13de836ea5541ba34bca03310a5d265. The name of
the new zip file I downloaded was sage-virtualbox-4.2.1.p1.zip, and
the older one that didn't work for me lacked the p1 towards the end.
To determine the checksum of my downloaded zip I had to download a
freeware app. I winded up with the one at http://www.irnis.net/soft/xcsc/,
if that helps.

--charlie

Stefan

unread,
Dec 18, 2009, 12:17:10 PM12/18/09
to sage-support
Oh boy. I had a bunch of problems with getting the VirtualBox
appliance to work in Windows 7.

When you import the appliance, prior to starting it, go into the
configuration and look at the hard drive configuration. The
configuration should be reference the three files that comes with the
Sage package.

Hope that helps. If you're still having difficulty, let me know!

William Stein

unread,
Dec 18, 2009, 2:30:15 PM12/18/09
to sage-support
On Fri, Dec 18, 2009 at 9:17 AM, Stefan <stefan.lo...@gmail.com> wrote:
> Oh boy.  I had a bunch of problems with getting the VirtualBox
> appliance to work in Windows 7.
>
> When you import the appliance, prior to starting it, go into the
> configuration and look at the hard drive configuration.  The
> configuration should be reference the three files that  comes with the
> Sage package.
>
> Hope that helps.  If you're still having difficulty, let me know!
>

Hi,

So the main issue is that often some of the hard drives aren't
appearing after import, due to bugs in VirtualBox on various
platforms? Though inconvenient, I can probaby rebuild the
virtualmachine in a way such that there is exactly one virtual hard
drive instead of 3 (by partitioning that drive), which will hopefully
work around this problem.

William

Charles J. Daniels

unread,
Dec 18, 2009, 5:27:37 PM12/18/09
to sage-support

On Dec 18, 11:30 am, William Stein <wst...@gmail.com> wrote:
> Hi,
>
> So the main issue is that often some of the hard drives aren't
> appearing after import, due to bugs in VirtualBox on various
> platforms?
>

> [...]
>
> William

To be fair to your efforts William, I'm not sure they have the new
appliance you exported that fixed the "only 2 drives out of 3" error
-- at least fixed it in my case on WinXPPro SP3 in VirtualBox 3.1.0.
Perhaps the only 'bug' is a backward incompatability that breaks
importing certain appliances exported from pervious versions of
VirtualBox.

--charlie

Reply all
Reply to author
Forward
0 new messages