Second, and final, post on this. On Fri, 2003-04-18 at 22:54, D. D. Brierton wrote: > Okay. This is my first update, of hopefully two. This is just about > VMware Workstation 4.0 on RHL9. The install (via RPM) is fine, the perl > configure script seems fine, and I have observed no problems. Unless you > really know what you are doing, you will be best off disabling RHL9's > samba and just using what comes with VMware, unless you have specialised > needs, in which case you probably don't need any help from me. I just wanted to underline this again. From my experience if you are doing a fresh install and starting from scratch there doesn't seem to be any grounds for hesitancy. > However, upgrading from a previous version of VMware is messy and > complicated, and I will give more details in my next email when (or > pessimistically if) I overcome them. It turns out that it isn't really that messy at all. Most of the complications were easily resolved at my end. > The one thing I did notice was that > the perl configure script asked me if i wanted to keep my previous > settings, to which I said yes, and yet somehow it didn't. The samba > settings seem to have been hosed, whilst the NAT settings were > preserved; and even more weirdly, it seems (although I haven't > determined this for certain) that vmnet1 and vmnet8 were swapped around > (one was supposed to be the NAT network for sharing my internet > connection and the other was supposed to be the samba network): the only > VM that had both had internet access but no samba access, and the other > VMs which were only supposed to have internet access via NAT didn't. No VMware did not swap vmnet1 and vmnet8, I just had to make them trusted devices in redhat-config-securitylevel. My original samba settings were not preserved, but simply copying back my old config had the desired effect. One complication was that I couldn't log in to samba because my UID from my old Samba smbpasswd file did not match my UID on my fresh RHL9 install. A simple edit of /etc/vmware/vmnet1/smb/private/smbpasswd did the trick. > Upgrading the VMs to the new Virtual Hardware is a complicated process, > and so far has not worked properly. I'll give more details in my next > post, whenever that may be. Actually this is not that difficult, but you really need to follow the instructions here: http://www.vmware.com/support/ws4/doc/upgrade_lin_ws.html to the letter. The first VM I tried to upgrade without paying proper attention to the instructions and I hosed it. Thankfully I had a backup of it, and so simply deleted and started again, and once I followed the instructions it was fine. QUICK REVIEW OF VMWARE WORKSTATION 4.0: Pros: * new interface is much nicer than the old * new virtual hardware makes for dramatic improvements in multimedia in guest OSs Cons: * I can't get the virtual USB interface to work: none of my VMs recognise the locally connected USB printer I hope this is a help to some of you, and not just noise on the list! Best, Darren -- ===================================================================== D. D. Brierton darren@xxxxxxxxxxx www.dzr-web.com Trying is the first step towards failure (Homer Simpson) =====================================================================
