Script Updated 20071228
Script now includes the wrapper for vmware player 1.0.x in the dotpet package.
Script can now create the dotpet package without rerunning the installer. See below.
Fixed location of generated dotpet package created during installation.
Changed archive from .gz to .tar.gz
Prerequisites:
Make sure you have the development and kernel-source add-ons loaded. If you are using the retro version of Puppy3 you will need to use the 216 or 217 add-ons renamed to 301 -- See herefor more info. You can get the required addons from either ftp or http sites.
For assistance installing the addons visit http://puppylinux.org/wikka/Puppy215sfsExpansionPacks
Important!!
For puppy3 (or puplets based on it) install a functioning insmod first, a copy is available here.
To install VMware Player:
0. Download VMware Player x.y.z for Linux (.tar) to a partition that has ~190M free space
1. Download the attached vminstall.tar.gzto the same location
2. Extract vminstall.tar.gz
3. Run ./vminstall.sh VMware-player-VERSION-BUILD.i386.tar.gz
4. Answer the questions presented by the vmware player installation script as desired (or you could just hit enter for every thing)
5. Answer yes/no to creating a dotpet package from the installed files. If you answer "No", you can create the dotpet later using
./vminstall.sh -p vmware-player-version". Eg ./vminstall.sh -p 2.0.2.
To get full screen in the guest OS
You have to install vmware tools in the guest OS. To obtain the tools you will need to:
1. Download a version of vmware workstation or vmware server (preferably server as it's smaller and free)
2. Extract the files and copy out the iso file for your guest OS eg windows.iso, linux.iso
3. Set the iso as (one of) your cdrom(s) and boot the guest OS
4. Once the guest OS is booted navigate to the cdrom and run the installation program
Things to note
Which version works
VMware Player 1.0.x
- works in puppy2 but not puppy3
VMware Player 2.0.x
- works in puppy2 and puppy3
- gives me a BSOD for windows guest OSes in puppy2 but works fine in puppy3
this may specific to my machine or maybe due to the version of xorg/gtk/kernel
This script was tested in puppyNOP 301r2 and puppy301.
Dotpet Package
The dotpet package created via the installer is not an unleashed package but rather more like a tgz2pet-converted slackware package. This was the quickest and least space-consuming to create. To covert it to a unleahsed dotpet use the following:
Code: Select all
pkg="VMwarePlayer-2.0.2"
pet2tgz $pkg.pet; tar xfz $pkg.tar.gz; cd $pkg; tar xvfz $pkg.tar.gz; rm $pkg.tar.gz; cd ..; dir2pet $pkg
After installing the dotpet, you must either run /etc/init.d/vmware start from the console or restart, puppy before you can run vmplayer.
Reinstalling VMware Player
Will back up installed files as /path-to-file/filename.old.x so if you re-run the installer you should delete these backed-up files to save space.
What this script does
It automates the process of:[/b]
* Patching VMware Player v 1.0.x http://www.murga-linux.com/puppy/viewto ... 321#140321
* Patching VMware Player v 2.0.x http://www.murga-linux.com/puppy/viewto ... 262#117262
* Creating the /etc/rcX.d directories
* Fixing the menu icon for vmware
* Removing unneeded precompiled modules that take up ~120M of space
* Creates wrapper/launcher script for VMware Player 1.0.x that forces it to use the VMware-packaged gtk
* Optionally creates a dotpet package from the installed files
* Creates vmkill; a script to kill vmware in a pinch if it starts to hog the cpu
Useful Links
The download link for vmware player is http://www.vmware.com/download/player/download.html
To automate creating vmx config files for your vmware player visit http://www.easyvmx.com/. You can try starting with the Super Simple
For help manually create a vmx config files for your vmware player visit http://sanbarrow.com/vmx.html
To manually convert an existing installation to a vmdk image http://www.robertpeaslee.com
For advanced users only - that's why there is no description.