Poor man's install, with extra storage, on NTFS/Win7

[Capricorny]

My impression of VirtualBox is that it offers some rudimentary
Virtual capability, but is not a very satisfactory environment
to work around in for very long. The price is right, however.

May I suggest that your impression of VirtualBox may be somewhat influenced by you "insisting" on running it off a Windows host, with all M$ antics in effect, rather than on a host built on a more empowering philosphy? Perform the described poor man's install, add the storage, boot Knoppix natively, and then you can experiment with Knoppix Virtualbox.
I may come back with some notes on that - but virtualization in itself isn't that interesting to me. And I have never understood the people running Linux guests on Wondows hosts instead of the other way around, when they have a choice. And as I just have shown, with Knoppix you always have a choice .

[Capricorny]

Perform the described poor man's install, add the storage, boot Knoppix natively, and then you can experiment with Knoppix Virtualbox.

Sad state of affairs on my machine- Pre-installed Virtualbox won't run, and apt-get:

# apt-get install virtualbox
......
The following packages have unmet dependencies:
 virtualbox : Depends: libqtcore4 (>= 4:4.7.0~beta1) but 4:4.6.3-4+squeeze1 is to be installed
              Depends: libstdc++6 (>= 4.6) but 4.4.5-8 is to be installed
              Recommends: virtualbox-qt (= 4.0.10-dfsg-1) but it is not going to be installed
E: Broken packages

So, it seems virtualbox is going to be extremely virtual for a while.

[kl522]

# apt-get install virtualbox
......
The following packages have unmet dependencies:
 virtualbox : Depends: libqtcore4 (>= 4:4.7.0~beta1) but 4:4.6.3-4+squeeze1 is to be installed
              Depends: libstdc++6 (>= 4.6) but 4.4.5-8 is to be installed
              Recommends: virtualbox-qt (= 4.0.10-dfsg-1) but it is not going to be installed
E: Broken packages

So, it seems virtualbox is going to be extremely virtual for a while.

As you can see from here, virtualbox has many packages built with many different dependencies :-

http://www.virtualbox.org/wiki/Linux_Downloads

I always use the last entry, ie All distribution i386. Using this one, it is able to avoid the file dependency problem.

[kl522]

By the way virtualbox need to rebuild it's kernel module driver for a target kernel, and this can be done by doing once after installation :-

# /etc/init.d/vboxdrv setup

This will compile the kernel driver needed to run vb if you have the proper kernel header.