Vmware-any-any - update 117 download

Running VMWare workstation 6. I still cannot run vmware-config. Thankfully the config routine still works under 2. Why is vmware workstation so difficult to run on upgraded Fedora? Always fiddling required — such a cumbersome method to get working on Linux. Clive Long — the reason is vmnetInt. I will have to check out the reasons. VMware Workstation 6 on Fedora Core 9 —————————————————. Need to get kernel headers to compile vmware: kernel-devel Try reinstalling VMware Workstation.

I think this is because during vmware-config. Building for Workstation 6. Do you have any idea how to get it to build for the correct VMWare version? In other words, after you extract the vmware-any-any-update It detects the VMware version correctly and builds flawlessly. I got it compiled and running correctly expcept the wireless bridge. Jul 17 zion kernel: [ This is not supported configuration, and Jul 17 zion kernel: [ The vmware installation was the original one as on OpenSuSE After the upgrade it was only needed to apply the vmware-any-any-updatevery-ALPHA patch as offered here above.

The vmware-config. So again Thanks Post a Comment. Brian's lovable online gazette. EDIT July 13th Thanks to Tony Barnard who pointed me to Cameron Seader's blog entry that has a fix for the vmware-vmblock module problem described in this blog entry. They are fairly minor, but here's some info that should get you up and running. First of all, the vmware-config. No problem, that's normal, the script will just compile one for me like always correct? Well, correct for the most part; after affirming that I wanted the script to try and build the vmmodule, I got the following message: Your kernel was built with "gcc" version "4.

This configuration is not recommended and VMware Workstation may crash if you'll continue. Please try to use exactly same compiler as one used for building your kernel.

I decided to investigate whether the script was even telling me the truth or not. After browsing the gcc manual, I found the -dumpversion option and tried it out Sure enough, line of vmware-config. So this really wasn't anything to be worried about, while it is apparently a gcc bug, it's safe to just respond "yes" to the prompt.

I didn't get very far after that, however. The vmmon module fails to build almost immediately. Coincidentally, a weak or so earlier I had been installing VMware on a Slackware machine and had learned about the vmware-any-any-update patches.

These are unsupported and apparently third-party updates for vmware. The newest update I found was vmware-any-any-update I download it and ran the 'runme. So after ignoring the inaccurate gcc version warning and running the vmware-any-any-update