![]() If you already have a 64-bit wine config setup, look into setting up different wine environments, otherwise if you do not need your existing config, then the easiest route is to remove your entire ~/.wine configuration before proceeding. # Set wine architecture to Windows 32-bit since the dotnet35sp1 package requires 32-bit Windows. Once homebrew is installed, proceed with following commands. # Install homebrew, google this if you're not sure. Lines prefaced by # are my notes/comments Steps that I took to get it running, not sure if this is the only way. ![]() It will say that the installationįailed and will rollback the installation leaving the vsphere When the folder is copied you can now proceed:Ĭlick OK to the hcmon driver error dialog, and clickįinish on the installer dialog. When you see an error about installing the hcmon driver, STOP do not click OK.Ĭopy your ~/.vsphere directory to another location. Step through the installation dialogs accepting all defaults. The HCMON drvier error is now be fixed so the following steps are now deprecated: WINEARCH=win32 WINEPREFIX="$HOME/.vsphere" wine ~/.vsphere/drive_c/Program Files/VMware/Infrastructure/Virtual Infrastructure Client/Launcher/VpxClient.exe Wine ~/Downloads/VMware-viclient-all-$.exeLaunch the vSphere client, dismiss any warning/error dialogs: ![]() ![]() Install the vSphere Windows installer exe. Winetricks -q dotnet35sp1 msxml3 vcrun2005 vcrun2008 vcrun2010 NET 3.5 sp1 and several other components with winetricks: WINEPREFIX="$HOME/.vsphere" WINEARCH=win32 wine wineboot ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |