![]() |
(on Wikipedia)
https://www.vmware.com/
—
—
-
2022-03-22 – VMware-workstation-5.5.9-126128 on Windows 10
- I only installed it. I noticed that it had a bunch of shit running even though it wasn’t launched, so I uninstalled it. I’ll consider purchasing the much more recent version.
- (date not recorded) – I switched to VirtualBox.
- 2005-11-30 – 5.0 on PCLinuxOS 0.91
- I was given a free copy at a conference I went to.
- (date not recorded) – 5.0 notes for SUSE 9.3 as the host
-
(date not recorded) – 4.5.2 on (distribution not recorded)
—
- Fix VMWare Player Resolution with Solus (All Versions)
- Installing Windows for Workgroups 3.11 in VMware, by Joe P. (insmod ex)
- Honeypotting with VMware
-
How-to: VMware player modification [ 1 ] was https://web.archive.org/web/20051026010807/http://www.hackaday.com/entry/1234000153064739/
Darbo’s advice for PCLinuxOS .94 ∞
First, get the 4gig flavor of the kernel. Save’s you from needing one
patch to vmware module build script.Second, get the any_any patch. I think the current in version .94. It
patches vmware’s drivers to be compatibile with kernels newer than 2.6.11.Third, don’t use too new a kernel. I’m using:
2.6.12-oci4.mdk-i686-up-4GB
And loving it. The newer 2.6.12’s should work, too. Don’t know about
2.6.13 or .14.Live by this, and you should have no problems what so ever. I don’t.
2005-11-30 – 5.0 ∞
Seminar notes ∞
The VMware seminar: I attended a seminar and got a free license for the new version (new to me, anyway). I arrived an hour and a half before the presentation start because I overestimated the amount of time it would take me to get out that way. Good thing I brought a book. I heard there was free food, but I didn’t bother with it. Good crowd, very personable speaker and mildly interesting topics. A few items were of particular interest so it was worth it to attend for them and not just for the license. =)
Open-partition silent file destruction: Remains unsolved. Allowing free access for guest operating systems to use real partitions is still something they have a disclaimer against and is presumably still potentially destructive. Damn.
Snapshotting: It’s nice to see that snapshotting has a nice GUI frontend to it. This was a desire of mine. It’s .. um.. “instant”. Whoa.
Sound: Sound pops. But it popped under a previous version using a Windows host as well, so it could be me. It could also be issues with drive speed or the like. This is being revisited.
Full-screen: A fine border may still be painted around everything, which would force scrollbars. I think this is the fault of the window manager. Control-Alt-T should work.
Software notes ∞
-
I made another pass as I was reinstalling things. I figured out my kernel issues and apparently all that figuring out applied to this app as well. Yay!
Installation:
- I did not need to apply any of the Ocilent1 PCLinuxOS kernel VMware fixes.
-
See also VMware troubleshooting.
xhost +localhost echo "* Launching vmware" nice -n 5 nohup vmware>/dev/null&
VMware 5.0 and PCLinuxOS 0.91 ∞
-
Install a good kernel and make sure its source files are also installed. Use Synaptic.
kernel-pclos-i686-up-4GB-2.6.13.oci2.mdk#1-1texallowed VMware to install just fine, and without any installation deviations, but gave Could not open /dev/vmmon: No such file or directory. when a virtual machine was started.kernel-pclos-2.6.13.oci2.mdk#1-1texis in testing.
mcc> Lilo settings > specify the new kernel, make it default-
reboot, choosing that kernel.
- For me it was
2613-oci2
- For me it was
—
-
Install vmware
- I did an
rpm -i --force vmware*.rpm
— The--forceis for when you re-install vmware, to overwrite destination files.
— If reinstalling, you may getUnable to stop VMware Workstation's services... rebooting before doing the rpm install might be a good idea.
- I did an
su-
Edit
/usr/bin/vmware-config.plperl script:
Search for
} elsif ($first =~ /^[89ab]$/) { $first = '80000000';
Replace with
} elsif ($first =~ /^[89a]$/) { $first = '80000000'; } elsif ($first =~ /^[b]$/) { $first = 'B0000000';
-
vmware-config.pl- I used the defaults.
- I had to
rm /etc/vmware/not_installed
2005-10-10 ∞
(I don’t know where to place this note, so I’ll stick it here)
Yet another misadventure with VMware.. I rebuilt the kernel and everything.. but it all came crashing down in various ways. The entire system ended up becoming unbootable. I had to boot off of a rescue disk and do a restore from the backup I did before starting this nonsense.
(date not recorded) – 5.0 ∞
https://www.linuxquestions.org/questions/showthread.php?postid=1609871#post1609871
5.0 VMware is pretty easy to setup under 9.3 suse. You should have 2 packages a rpm and a tar.gz package. Use YaST to run the vmware-workstation-5.0.0-xxxxxx.i386.rpm which will prompt YaST to install the related packages. You will need your Suse 9.3 setup disk, if cds youll need disk 2,4,5. Follow those prompts in YaST. Then extract the vmware-workstation-5.0.0-xxxxxx.i386.tar.gz and copy the folder over to /usr/local/scr/.
Then open the vmware-distrib folder and execute ./vmware-install.pl. I think I might have had to chmod +x the file before executing. Once installed it will ask if you want to run the config say yes. Youll have to agree to the license agreement and then answer a few simple questions to complete the config. After that you should see on the Kmenu under Systems a new folder “more programs –> VMware workstation”
Click to run and then on the menu enter your license key and your done.
https://www.linuxquestions.org/questions/showthread.php?postid=1652582#post1652582
You need to have your kernel sources and devel tools installed (i.e gcc, make etc…)
cd /usr/src/linux make mrproper make cloneconfig make prepare cd <the vmware directory> ./vmware-config.pl
(date not recorded) – 4.5.2 ∞
- I was first introduced to the open-partition problem, and some of my archives were silently destroyed. Crap.
-
The VMware Workstation v4.5.2 manual made a cameo in my first picture.
Low memory patch ∞
Spoiler
Keith Moore keithmo at exmsft.com Mon Dec 27 14:28:57 EST 2004
Just in case anyone is interested…
2.6.10-ck1 with “1G Low Memory” support can be made to work under VMware
Workstation 5 Beta 2 by patching vmware-config-tools.pl before
installing VMware Tools:--- vmware-config-tools.pl.orig 2004-12-27 13:45:24.000000000 +0100 +++ vmware-config-tools.pl 2004-12-27 13:47:43.000000000 +0100 @@ -1906,8 +1906,10 @@ $first = lc(substr($fields[0], 0, 1)); if ($first =~ /^[4567]$/) { $first = '40000000'; - } elsif ($first =~ /^[89ab]$/) { + } elsif ($first =~ /^[89a]$/) { $first = '80000000'; + } elsif ($first =~ /^[b]$/) { + $first = 'B0000000'; } elsif ($first =~ /^[cd]$/) { $first = 'C0000000'; } elsif ($first =~ /^[ef]$/) {I don’t know if this is absolutely the *correct* fix, but it does enable
VMware tools to install without complaint under 2.6.10-ck1-1g. I have
not tried this with other VMware versions (including the released
4.5.2), but I suspect the fix would be similar.
Slackware 10.0 guest notes ∞
Networking ∞
Edit the rc.modules file:
nano /etc/rc.d/rc.modules # Then uncomment the `pcnet32` module: /sbin/modprobe pcnet32





VMware is being spruced up, as I got a copy of VMware Workstation 5.0
Found an old comment. While useless now, maybe it has historical value. Technically all of these old notes are for that.