Vmware in Ubuntu Edgy Eft

[BIGEE1212]

I decided to give myself a challenge and install vmware. Well, that wasn't hard at all... I followed the instructions found here http://www.advicesource.org/ubuntu/Run_Existing_Windows_Instalation_On_Ubuntu_With_Vmware_player.html

Well, first problem, when I try to open the vmx file, I get an error message that says I can't access the file becuase I don't have full privelages or something like that. Well, I googled and tried adding my user to the disk group, but that didn't work. So I solved the problem by running the program through the terminal. I did sudo vmplayer to get into windows. Well, it opens up and as it boots up it looks good. But when i log on and after i re activate, none of my drivers are installed. I wasn't sure if i was supposed to re install drivers becuase whatever changes i make through vmware, it should make the same changes to my actual windows install. So i didnt want to risk it. I just wanted to ask you guys for confirmation if i should install drivers through vmware, i dont want to mess up my existing windows partition. Thanks. (hope my question makes sense).

[BIGEE1212]

Oh yeah, forgot to mention this. When I run the vmplayer through the terminal, it seems the program is running fine although there are some messages displayed in the terminal (doesn't seem to have an effect on the boot up) but i was just wondering what it was:

sudo vmplayer
/usr/lib/vmware-player/bin/vmplayer: /usr/lib/vmware-player/lib/libpng12.so.0/libpng12.so.0: no version information available (required by /usr/lib/libcairo.so.2)

(vmplayer:6194): libgnomevfs-WARNING **: Failed to open session DBUS connection: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Volume monitoring will not work.

[abf]

the message is just what it says, dbus and hal are the daemons responsible for hardware plug-n-play and mounting media.... so if dbus is not working with vmware it simply means that if you plug in any hardware/media after vmware has booted, it won't be recognized. you'll need to reboot vmware.