There's very little point in doing this, as firstly, VMware products (e.g. ESX, Server or even Player) can't be hosted inside other VMware products (so you couldn't run VMware Player inside anoth...
See more...
There's very little point in doing this, as firstly, VMware products (e.g. ESX, Server or even Player) can't be hosted inside other VMware products (so you couldn't run VMware Player inside another VMware product on the host), if that makes sense. Also, doing so would involve quite a large size increase, which isn't desirable for something designed for the VMware Challenge. Even if you did, it wouldn't actually add anything valuable to your virtual machine, and also licencing is a grey area for most.
It shouldn't matter, as long as the virtual machine isn't in the "Legacy" format. I had planned to create mine with VMware Server, which should be OK, seeing as it doesn't implement Shared Folder...
See more...
It shouldn't matter, as long as the virtual machine isn't in the "Legacy" format. I had planned to create mine with VMware Server, which should be OK, seeing as it doesn't implement Shared Folders, but neither does Player, so it can be useful in some regards.
It should be OK, as long as the tool itself has no components belonging to the software it's trying to install (especially if it's proprietary). It's not a good idea to host, for example a copy o...
See more...
It should be OK, as long as the tool itself has no components belonging to the software it's trying to install (especially if it's proprietary). It's not a good idea to host, for example a copy of Microsoft DirectX (customized, or not) on a personal site, for your tool to use, for obvious reasons.
Unfortunately, you wouldn't be able to run the Xbox 360 as a VM using VMware's products, for the simple reason that the Xbox 360 is using a PowerPC CPU, as opposed to an i386 based one. Messag...
See more...
Unfortunately, you wouldn't be able to run the Xbox 360 as a VM using VMware's products, for the simple reason that the Xbox 360 is using a PowerPC CPU, as opposed to an i386 based one. Message was edited by: tysonkey Fixed a typo
Interesting idea. But if you trust it to 5-6 year-olds, they'll probably destroy it, and make it non-bootable. As I've found on at least 3 Macs that I've had, if put in the control of kids, say t...
See more...
Interesting idea. But if you trust it to 5-6 year-olds, they'll probably destroy it, and make it non-bootable. As I've found on at least 3 Macs that I've had, if put in the control of kids, say to use a Notepad-type application/a basic art package, they'll find a way of deleting critical system files. But seeing as it's Linux, you should be able to fathom something so that only 'trusted' people can use the CLI, and configuration tools, and you'll have to lock the file system down tightly (e.g. restriction of file management to just the user's home folder.
You should be able to add/remove protocol/URL filters on the fly, ideally using a HTML interface, or if you're so inclined, after the VM is offered, allow people to add their own black/whitelists...
See more...
You should be able to add/remove protocol/URL filters on the fly, ideally using a HTML interface, or if you're so inclined, after the VM is offered, allow people to add their own black/whitelists after recieving the VM, but if you were to intercept and filter in this manner, your entry would probably be denied. Just a thought...
Unfortunately, the only proprietary software that can be included, is the VMware Tools. Other than that, only open-source software is allowed. I think.
Why can't you consider making VMware Tools open-source, so then there's nothing to worry about, and it'll make supporting other operating systems much easier.