Failed again. I followed all your instructions - even go the extent of sudo cp /usr/bin/patch to my home directory to which I have rwx permissions.
Two things.
1) I needed to modify the symbolic link found iin a number of palces on the web to a copy command (also apperainig on the web)
sudo cp /usr/src/linux-headers-3.8.2-030802-generic/include/generated/uapi/linux/version.h /usr/src/linux-headers-3.8.2-030802/include/linux/version.h
This is because the target of the symbolic link does not exist!
2) Even after vmci.tar (correctly placher in ~) was copied back to its location (usinkg sudo). reruning the inistaller still brought up the specify the header location dialog. In both locations f the .h files (-generic and plain) are greyed out ini Dolphin . This almost certainly is why the patch command s doesnt't work - but then again I''m t a kernel programmer so I can't say for sure. I can open the VM's I created ini Ubuntu Raring using kernel 3.6 to my Debian Wheezy installation where I'm leaving the kernel at 3.2 for time beinig. I can alos copy the VM's to my Windows 8 partiiton and run them as WS 9 is installed there.
To me these contortions using VMware WS 9 on kernels > 3.6 are not worth my time anymore. I'm disappointed in VMware Inc for not addresssing this. VirtualBox inistalls and runs its Virtual lMachines without a hitch - I'm running Windows 7 x64 VM right now in Rarinig host. It also has full audio which I knoiw from past experience would be problematic for WS as well.
Kernel developers are movinig right along. Kernel 3.9 is now at the rc level. VirtualBox installs but can't open VM's in Fedora Rawhide with kerrnel 3.9. I'll try 3.9-rc1-rarinig to see if that works for VB and if anybody has coded and successfuly installed WS 9 using 3.9 then I'll comment.
Congrats to those that got WS 9 working on 3.8 and I feel the pain of those could notImage may be NSFW.
Clik here to view.
