Works very nicely on my installation of Lucid Puppy 511 (and a fresh, empty installation of 511, too), with no apparent problems at all. Thanks.

In fact, it works nicely enough that I packaged it into a PET, modifying the linked script very slightly to work as a pinstall.sh script. (Hope you don't mind.)

The package is around 23 MB, and expanded and installed it's maybe 60 MB.

EDIT: I'm deleting my dot-pets for VBox 3.2.4. They seem redundant with the packages I've made for 3.2.8 and for 4.0.0.
If you need any further information, or if you need a copy and no mirrors are working, then please send me a PM.

The original binary included the guest additions CD image and the user manual as a PDF, but I've removed them from the package to try to save some space. If you need them, they can still be found on Oracle's site for VBox version 3.2.4, here, right near the top.

Anyway, thanks again for the binary. I've tried not a few times to get VBox running in Lucid Puppy, with spotty or no success, but your binary worked without fuss.Last edited by TheAsterisk! on Fri 07 Jan 2011, 06:16; edited 5 times in total

Thanks for testing
To Sc0ttman
Please test the package I'd posted in first post of this subjet (the tar package). May be these works. (I don't suggest to use the sfs packages because I'd packed Virtual Box with tar and I don't know how to convert it to sfs).
Thanks to all

Thanks for testing
To Sc0ttman
Please test the package I'd posted in first post of this subjet (the tar package). May be these works. (I don't suggest to use the sfs packages because I'd packed Virtual Box with tar and I don't know how to convert it to sfs).
Thanks to all

If you're using the SFS with your save file, the same kind of thing used to happen to me with an older SFS of VBox under Puppy 431. As I remember it, it had something to do with the priority of SFS loading- VBox wouldn't 'write' into some of the directories the kernel source SFS or the devx SFS used as they showed up in the whole file system. (I eventually got around it by combining the kernel source and devx files into one SFS, but that's another matter.) Basically, nothing in /lib/modules/2.6.33.2/misc/ was loaded from the VBox SFS, and that's pretty important since that's where the drivers for VBox sit.

You could try seeing if the following files are under /lib/modules/2.6.33.2/misc/ in your Puppy installation if only to eliminate one more possibility: vboxdrv.ko, vboxnetadp.ko, and vboxnetflt.ko.

@sc0ttman:
...
You could try seeing if the following files are under /lib/modules/2.6.33.2/misc/ in your Puppy installation if only to eliminate one more possibility: vboxdrv.ko, vboxnetadp.ko, and vboxnetflt.ko.

Thanks very much for the info Asterix, the file you mention are indeed present.

Still can't get it working though...

I'll keep checking it out and hopefully I'll get it working...

I'm sure there's nothing wrong with the packages, as they work when I don't use a save file, so it must be something in my setup.

Could it be that I'm using a frugal install on and ext3 partition - the save file seems to be loaded before the main filesystem...

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum