Jump to content

Search the Community: Showing results for tags 'VMware'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • InsanelyMac Lounge
    • Front Page News and Rumors
    • Reader News and Reviews
    • Forum Information and Feedback
  • OSx86 Project
    • New Releases and Updates
    • New Users Lounge
    • Developers Corner
    • Tutorials (The Genius Bar)
    • Technical FAQ
    • Installation
    • Post-Installation
    • DSDT and SSDT
    • Hardware Components and Drivers
    • Desktops
    • Notebooks
    • Netbooks
    • Tablets
    • MacMod of the Month
    • Multi-booting and Virtualisation
  • International
    • Your Language
    • Deutsch
    • Español
    • Français
    • Italiano
    • Português
    • Русский
  • Apple World
    • Mac OS X
    • Apple Computers and Hardware
    • iOS Devices
    • Mac Applications
    • Mac Programming and Development
    • iOS Programming and Development
    • Mac Gaming
    • Mac Accessories
  • Discuss and Learn
    • Windows Discussion
    • *nix
    • Apple Opinions and Discussion
    • The Great Debates
    • Internet(s), Servers, and Networks
    • Buying Thoughts, Reviews, and Recommendations
    • Mods and Overclocking
    • The Big Issues [Real Life]
  • Everything Else
    • Creativity
    • Thunderdome (Random Stuff)
    • Laughs
    • The Marketplace

Categories

  • Kexts
    • Graphics Cards
    • Audio
    • LAN and Wireless
    • Other
  • Kernels
  • Bootloaders
  • DSDTs
    • Patches
  • Pandora
  • Apps
  • Miscellaneous
  • Customization

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 18 results

  1. Hello everyone I have a problem setting the virtual OS X to display the screen's native resolution(1600x900). When the machine first boots up, it displays the right resolution then after the logging in by a few moments the screen displays a wrong resolution(800x450 HIPDI) which is a quarter of the resolution. I have macOS High Sierra (10.13.1) on VMware Workstation 14 Pro version: 14.0.0 build-6661328. My laptop has i5-4310U CPU with HD graphics 4400 which has 128mb dedicated video memory and a 1600x900 screen. I have installed VMware tools that was created on 14 September 2017 and VMware unlocker version 2.1.1 made by DrDonk. When logging in the background isn't the blurred wallpaper and the dock isn't transparent as it should be, or at least from what I saw on the internet. Here is what I have tried up until now: 1) Changing the resolution from the system preferences. 2) Using sudo /Library/Application\ Support/VMware\ Tools/vmware-resolutionSet 1600 900 Which displayed this output: Requested resolution: 1600x900 Effective resolution: 1600x900 Without any result. 3) I tried setting the screen's native resolution in the Display settings of VMware, still nothing. 4) I also tried to change virtualHW.version from 14 to 10 but it also did not do anything noticeable. The only thing that changed is that the blurred wallpaper was in the background when logging in. One thing to note is that it runs correctly up until 1366x768. I think the problem may be that the OS tries to load kexts after the logging in that interferes with the VMware tools, but I am not sure or that there is a hardware limitation, but I do not know a way to test it. Does anyone know how to fix that?
  2. Does anybody know how to use el capitan under a VMware?
  3. I was able to expand the virtual disk in VMware Workstation 12 from 50 GB to 200 GB and it's being seen by OSX 10.11.3 El Capitan (see screenshot). So when you go into Disk Utility on the OSX guest, it shows the "Capacity" as 214.75 GB, but no way to expand the Macintosh HD (42.74 GB) to capacity. Can anyone chime in here? Might be a command I have to run from the terminal window?
  4. I've built a couple Hackintoshes, but I suddenly inherited a 2012 Chronos 7 laptop. Decided to start with VMware. Installed player 7 and unlocked it. Created a VM with with plop image. I know there are various instructions of how to install os x. However, I have a vanilla bootable ML USB drive lying around so decided to try. Set the vm to os x 10.8 and booted. Presto, I have os x running and can login. However, no matter how I set the networking in vm, the Mac doesn't have a nic. I played with vmnetcfg, but no luck. I have [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] on the drive, but don't know which if any driver to install. If you tell me, go follow proven methods, I'll understand, but I'd love to know at least why it doesn't work.
  5. Hello All Has anyone had any success getting osX (10.9 or 10.10) to boot into VMWare Player 12 on a Linux host? I've gone through the site looking and I haven't found any posts about VMware Player 12.
  6. perhaps this is the right forum for this: I got SL 10.6.8 running on a PC with AMD Phenom II X6 1100T and VMware 8.0.2. SL image is boot using a DVD Room drawin_legacy.iso. The Kernel of the Mac is the latest legacy kernel i got it fromhttp://www.osx86.net...el_10.8_v2.html and i also chose the force64 option. It's running nicely with 1 Core (or 1 CPU) assigned to the Mac Guest OS. I can even connect my iphone to it via the VMware USB relay. However it is not idea as it is slow with only 1 Core. When I assign 2 Core (or even 4 Core) to the Guest OS, I can boot it and run it with no problem. However, I will get the horrible CPU(s) have been disabled by Guest message after a few hours of running. I always leave the PC and the Guest running all the time. There is no pattern on when I will get the CPU disabled message. I therefore disabled all the screensaver or energy related features within the Guest OS but i have no luck. I wonder anyone can shed some light into this and tell me how kind of log files I need to look at? I tried the /var/log/system.log but nothing happened the crashing. many thanks !
  7. Hi all, I have a VM running Mountain Lion (10.8.2) hardware ver 9, 64 bit. Everything works great with the exception of iMessage: once I try to enable it, it doesn't let me log in (it seems a server issue). Is Apple filtering us out? Is anyone aware/experiencing the issue? Regards AxeL
  8. I've just installed High Sierra as a new install under VMware Wkstn 12.5.7 and installed VM Tools but it's not mounting any USB HDDs that I plug in. USB flash drives are mounted OK. The USB HDD is recognised as a device (see External USB 3.0 in the attached screenshot) but Disk Utility doesn't see it. I've closed and re-opened DU a number of times. I've tried VMware Wkstn 14.0.0 and the latest VM tools but still doesn't mount. Has anyone had a similar issue or now what the problem may be? thanks Webby
  9. Hello I have juste installed OSX in VMware Player 7.1.2 on Windows 10. It works well and I'm very grateful to all who made it possible. The only thing which is missing is the opportunity to use the "unity mode", i.e. the ability to open OSX windows als "Windows windows". It tells me I have to install VM Tools, which I did using darwin.iso from Unlocker 2.0.7, but it still doesn't work. Does anybody know if it's possible to use "unity mode" and, if yes, how? Thanks and regards Patrick
  10. Hello! Last night I installed Yosemite in my VM on a Windows 10. I wasn't very happy with the quality so I decided to download El Capitan instead. Now this is an entirily different ball game all together. It works like a charm and after a few hours of general use it feels like a shock to then minimise the VM and boom I'm right back in Windows. Anyway everything works to my knowledge, the sound, video, wifi, etc ... The only thing is I tried to plug my Behringer Q1202USB audio interface in so I could play a video through my studio monitor speakers then the sound starts to crackle and pop. This also has an effect the video itself. Has anybody had a similar experience or know of a fix for this? (If it is even possible) My computer specs: Lenovo Y510P i7 4700MG 2.4 GHz 16G Ram 2 x Nvidia 755M SLI Thanks!
  11. For Public Beta Version I found this script from agentsim who is GitHubGist user. It Works for me on Windows 10 Workstation 12.5.7 # Generate a BaseSystem.dmg with High Sierra Beta Installer Packageshdiutil attach /Applications/Install\ macOS\ High\ Sierra\ Beta.app/Contents/SharedSupport/InstallESD.dmg -noverify -mountpoint /Volumes/highsierrahdiutil create -o /tmp/HighSierraBase.cdr -size 7316m -layout SPUD -fs HFS+Jhdiutil attach /tmp/HighSierraBase.cdr.dmg -noverify -mountpoint /Volumes/install_buildasr restore -source /Applications/Install\ macOS\ High\ Sierra\ Beta.app/Contents/SharedSupport/BaseSystem.dmg -target /Volumes/install_build -noprompt -noverify -erasecp -R /Volumes/highsierra/Packages /Volumes/OS\ X\ Base\ System/System/Installationhdiutil detach /Volumes/OS\ X\ Base\ System/hdiutil detach /Volumes/highsierra/mv /tmp/HighSierraBase.cdr.dmg /tmp/BaseSystem.dmg# Restore the High Sierra Beta Installer's BaseSystem.dmg into file system and place custom BaseSystem.dmg into the roothdiutil create -o /tmp/HighSierra.cdr -size 8965m -layout SPUD -fs HFS+Jhdiutil attach /tmp/HighSierra.cdr.dmg -noverify -mountpoint /Volumes/install_buildasr restore -source /Applications/Install\ macOS\ High\ Sierra\ Beta.app/Contents/SharedSupport/BaseSystem.dmg -target /Volumes/install_build -noprompt -noverify -erasecp /tmp/BaseSystem.dmg /Volumes/OS\ X\ Base\ Systemrm /tmp/BaseSystem.dmghdiutil detach /Volumes/OS\ X\ Base\ System/hdiutil convert /tmp/HighSierra.cdr.dmg -format UDTO -o /tmp/HighSierra.isomv /tmp/HighSierra.iso.cdr ~/Desktop/HighSierraPublicBeta.isorm /tmp/HighSierra.cdr.dmg
  12. I have scoured the internet for an answer to this, but no luck. When I try to boot into my OS X El Capitan Virtual Machine, I get an error (Pictures Below). I have tried to reinstall VMware, reinstall the Virtual Machine. I have used the unlocker provided by someone else, and installed flags to the text file. But none has worked. Processor: AMD FX 8320E @ 3.20GHz Memory: 8GB DDR3 Below is my .VMX file. El Capitan VMX.txt
  13. So I installed hackintosh (iATKOS) on a VM, and now it doesn't boot. My host is AMD, but during the installation, it crashed the first time, then went all the way through the second run. I'm guessing, "waiting for root device" means it can't see the hard drive partition? Or is this due to something missing, from the installation? Any ideas? Thanks in advance
  14. I originally wrote this "How To" in the following topic "Workstation 8/9, Player 4/5 and Fusion 4/5 Mac OS X Unlocker" started by Donk, see link below, since there are now some 500+ replies in the topic, I thought it was time to extract the post and start a new topic. http://www.insanelymac.com/forum/topic/268531-workstation-89-player-45-and-fusion-45-mac-os-x-unlocker/ Although a lot of alternative methods are available, the following "How To" based on the work by Donk, Zenith432 and others on "InsanelyMac" is a proven method for installing a "Vanilla / Retail" version of OS X 10.6 (Snow Leopard), 10.7 (Lion), 10.8 (Mountain Lion), 10.9 (Mavericks), 10.10 (Yosemite) and 10.11 (El Capitan) under VMware Workstation 10/11, Player 6/7, Workstation Pro/Player 12 and ESXi 5/6, using physical media (Snow Leopard) or an email with a content code for the Mac App Store (Lion and Mountain Lion) purchased from the Apple Store or media created from the App Store download. If you have access to an existing OS X machine physical or virtual you can download OS X 10.9 (Mavericks), 10.10 (Yosemite) or 10.11 (El Capitan) for free. It is important for the method detailed below to work, you must be running a relatively recent Intel processor with VT-x (Hardware Virtualisation) support which has been enabled in BIOS. Install the "Unlocker" following the included readme.txt, version 1.3.x for Workstation 10, Player 6 or ESXi 5 and "Unlocker" version 2.0.x for Workstation 11, Player 7, Workstation Pro/Player 12 and ESXi 6 created by Donk based on work by Donk, Zenith432 and Sam B, see the links below, to enable support for OS X. If you have access to an OS X machine, Redeem your purchase and download OS X from the Mac App Store under Purchases or use Updates to get OS X 10.9 (Mavericks), 10.10 (Yosemite) or 10.11 (El Capitan) once downloaded on your OS X machine extract the InstallESD.dmg from your App Store download of "Install OS X Lion" or "Install OS X Mountain Lion" in the Applications folder, right click the icon and select "Show Package Contents" open folder "SharedSupport" and copy the InstallESD.dmg to your desktop. Link to the "Unlocker" download to support Workstation 10.x, Player 6.x, Fusion 6.x and ESXi 5.x: http://www.insanelymac.com/forum/files/file/20-vmware-unlocker-for-os-x/ Link to the "Unlocker" download to support Workstation 11.x, Workstation Pro 12.x, Player 7.x, Workstation Player 12.x, Fusion 7.x, Fusion 8.x and ESXi 6.x: http://www.insanelymac.com/forum/files/file/339-unlocker/ Please note this media creation method will NOT work for OS X 10.9 (Mavericks), OS X 10.10 (Yosemite) or OS X 10.11 (El Capitan) an apple script is required to create a bootable DMG file from the "Install OS X Mavericks" or "Install OS X Yosemite" app downloaded from the Mac App Store, see the second post in this thread for details, link below: http://www.insanelymac.com/forum/topic/290949-how-to-install-os-x-10x-snow-leopard-lion-mountain-lion-mavericks-and-yosemite-in-vmware-workstation-10-or-player-6/?p=1937757 If you do not have access to an OS X machine, then purchase the OS X Snow Leopard DVD from the Apple Store ($19.99 US or £14.00 UK), you can use the DVD directly but it is easier to covert the DVD to an ISO. In order for you to be able to use the .dmg created for Lion or Mountain Lion as install media in Workstation 10/11 or Player 6/7 (Workstation Pro 12, Workstation Player 12, Fusion 6, 7 and 8, ESXi 5.1, 5.1 U1, 5.5, 5.5 U1, 5.5 U2, 5.5 U3, ESXi 6.0 and ESXi 6.0 U1x support .dmg files directly) the .dmg will have to be converted to an .iso, this can be done at the command line in OS X see below or in Windows using a third party product like ImgBurn ( http://www.imgburn.com/ ) or dmg2img ( http://vu1tur.eu.org/tools/ ) . In an OS X terminal session run the following: cd Desktop hdiutil convert ./InstallESD.dmg -format UDTO -o InstallESD mv InstallESD.cdr InstallESD.iso The conversion process will take some time, so apply the cup of coffee rule. The conversion process actually creates a .cdr file which we rename with the mv command to a .iso which can be mounted as installable media in Workstation 10/11 and Player 6/7. If the "Unlocker" has been installed correctly you should now be able to create a new Apple Mac OS X Guest operating system in Workstation 10/11, Workstation Pro 12, Player 6/7, Workstation Player 12 and ESXi 5/6 and select the InstallESD.iso you have created as the "Installer disc image file (iso):" and select Apple Mac OS X as the "Guest operating system" and Mac OS X Server 10.6 64-bit, Mac OS X 10.7 64-bit, Mac OS X 10.8 or Mac OS X 10.9 as the "Version". Mac OS X 10.9 can be installed from the .dmg created via the script detailed in the second post of this topic as can Mac OS X 10.10 which is only available as an option in Workstation 11, Workstation Pro 12, Player 7, Workstation Player 12 and ESXi 6, although Mac OS X 10.10 or 10.11 can be installed in Workstation 10, Player 6 or ESXi 5 using Mac OS X 10.9 as the "Version". Please note Mac OS X 10.11 is only available as an option in Workstation Pro 12, Workstation Player 12 and ESXi 6. Next choose a name and location for the virtual machine, then specify the "Maximum disk size (GB):" (I always select a minimum of 64 GB) and whether to "Store virtual disk as a single file" or "Split virtual disk into multiple files", (I select single file for ease of portability, but in theory selecting multiple files should offer better performance), however the default settings work fine. You now have the option to either Finish and create the Virtual Machine or "Customize Hardware...", I recommend adding a second core under the "Processors" section (although you may get the "Your Mac OS guest might run unreliably with more than one virtual core." warning message) and change the "Network Adapter" to "Bridged" (in theory these are optional, the default settings should will work fine, but experience would suggest using the recommended settings) select Close and Finish. It has been noted, thanks to cb4, that sometimes you get no keyboard input in the virtual machine, setting the "Enhanced virtual keyboard" from "Off" to "Use if available (recommended)" resolves the issue, and does not appear to have any issues when set on for a working OS X Virtual Machine. To disable the VMware multiple vCPU message add the following line to the VMX configuration for the guest whilst it is shutdown. isolation.tools.bug328986.disable = "TRUE" Please note this will only suppress the message, and the guest may be unstable with more than 1 vCPU, however since it is a very long time since real Mac's were not at least dual core, I always add at least two vCPU's, and have not experienced any instability. Thanks to Donk for the fix, for additional information head over to the website "Shine The Braille Toad". If you create the virtual machine using version 11 or later hardware, the default for Workstation 11, the virtual machine will not start and either hang or create a CPU core dump error message. Donk has confirmed two options to work around the issue: 1. Change the virtual machine to version 10 hardware. 2. Edit the configuration file (.vmx) and add the following line: smc.version = "0" Power on the virtual machine and the OS X installation should proceed to the Welcome screen, select your main language, and in the OS X Utilities screen select Disk Utility. In the left panel you should now see 68.72 GB VMware Virtual SATA Hard Drive Media, or similar depending on the hard drive size you set when creating the virtual machine, select the drive, and select the Partition tab. Next change the Partition Layout: from "Current" to "1 Partition", you can select more than one partition but I generally keep it simple, give the Partition a meaningful name, i.e. OS X, and click on the Apply button (the default format "Mac OS Extended (Journaled)" should be selected, and under the "Options..." button "GUID Partition Table" should be selected), you will next get an "Are you sure" warning, click on the Partition button to complete the creation of OS X formatted partition, you should see it appear below the VMware Virtual SATA Hard Drive Media. The DIsk Utility presentation has changed in El Capitan, having selected the VMware Virtual SATA Hard Drive Media as detailed above select the Erase button, the Partition button will be grayed out, and give the drive a meaningful Name: i.e. OS X and select "OS X Extended (Journaled)" as the Format: finally select "GUID Partition Map" as the Scheme and press the blue Erase button to create the drive ready for use by OS X. Now exit Disk Utility and select Reinstall or Install OS X, click Continue at the Install OS X screen and agree to the Apple EULA, at the Select the disk where you want to install OS X, you should have a nice yellow OS X disk in the middle of the screen, select the disk and click on Install, the installation should then proceed with a blue progress bar and "About 9 minutes remaining", following a re-boot OS X will continue "Installing OS X on the disk "OS X ..." again with a blue progress bar and "Time remaining: About 19 minutes", if the screen goes white with only a black mouse pointer, just click to bring back the install OS X screen. Following a further re-boot you should finally be at the Welcome screen with a map of the world and the option to select your language, followed by "Select Your Keyboard" to get the best support for a PC keyboard select the Show All and choose the relevant "Your Language - PC" version, i.e. British - PC. The next couple of screens may or may not appear depending on your network configuration, "How Do You Connect?", "Your Internet Connection" probably best to leave "TCP/IP Connection Type" Using DHCP initially. The next screen to appear is the "Transfer Information to This Mac", "Sign in with Your Apple ID" if you choose Don't sign in, you will get a splash screen with the option to "Skip", "Terms and Conditions", "Create Your Computer Account", "Select You Time Zone", "Diagnostics & Usage" followed by a "Setting up your Mac" and a thank you from Apple you should then be at the OS X desktop. This will create a vanilla install of OS X which can and should be patched via "Software Update..." as a matter of priority. It appears that like ESXi 5.5 and ESXi 6, Workstation Pro/Player 12 using Unlocker 2.0.7 or later, Install VMware Tools... under the VM tab now appears to work, if not use the method as for previous versions of Workstation and Player detailed below: To install "VMware Tools" go to the Virtual Machine Settings for the OS X VM and select CD/DVD (IDE) and under "Connection" click on "Use ISO image file:". It is quite likely your InstallESD.iso will still be selected, so just "Browse..." to the location of the darwin.iso and select "Open". The darwin.iso is not present in a standard install of either Workstation 10/11, Workstation Pro 12, Player 6/7 or Workstation Player 12, it is added as part of the "Unlocker" install and is located in the VMware Workstation folder under "Program Files (x86)\VMware" or "Program Files\VMware" for a 32-bit host in a default install, make sure the "Device status" has "Connected" ticked generally "Connect at power on" is ticked by default. You may get an error when switching mounted .iso's in the Virtual Machine Settings "The guest operating system has locked the CD-ROM door..." it is OK to answer "Yes" to the question "Disconnect anyway and override the lock?". In your OS X desktop a VMware Tools icon should appear in the upper right corner, double click and select "Install VMware Tools", it is recommended to install VMware Tools as it offers an enhanced user experience when working with the Virtual Machine. Please note VMware Tools cannot be installed from the menu in Workstation 10/11 or Player 6/7 to an OS X Virtual Machine (unlike Fusion, ESXi 5.x snd ESXi 6.x and now Workstation Pro 12 and Workstation Player 12 which support VMware Tools installation from the menu). The latest VMware Tools from Fusion 7/8 now provide the best graphics support for OS X virtual machines, and Zenith432 has stopped development of the VMsvga2 graphics drivers. The latest darwin.iso is available to download at the VMware CDS Repository, see link below: http://www.insanelymac.com/forum/user/487896-msok/ http://softwareupdate.vmware.com/cds/vmw-desktop/ Once you are up and running with your virtual OS X machine you need to do a couple of housekeeping tasks to ensure your virtual machine does not freeze. Firstly go to "System Preferences" and select "Energy Saver" and set "Computer sleep:" and "Display sleep:" to Never and also un-tick "Put hard disks to sleep when possible", "Wake for Ethernet network access" and "Allow power button to put the computer to sleep". In "Desktop & Screen Saver" set "Screen Saver" to "Start after:" Never. One final note, occasionally you can come across an unsupported CPU error, this should be rare if you have recently downloaded your OS X media from the App Store as the App Store version is updated when a new combo patch is released. Alternatively if your CPU is one of the very latest Intel processors not yet supported by OS X, Apple check CPUID's when installing OS X, and will not install on an unsupported processor platform. (A prime example was when Intel introduced the Core i3, i5 and i7 and Xeon 5600 series processors, Snow Leopard 10.6.4 was the lowest version of OS X to support the new processors, unfortunately the highest available "vanilla" media was and still is 10.6.3, without the CPUID mask it was impossible to install OS X Snow Leopard. As stated earlier in this post, Apple starting with OS X 10.7 Lion deliver the latest slipstreamed media via the App Store.) In either case add the following line to your OS X virtual machine configuration file (.vmx): cpuid.1.eax = "0000:0000:0000:0001:0000:0110:1010:0101" or cpuid.1.eax = "----:----:----:0010:----:----:1010:0111" The first was based on work by myself and Donk, the second a recommendation by jmattson of VMware, see links below: http://www.insanelymac.com/forum/topic/232183-snow-leopard-on-vmware-and-disabled-cpu-error/ http://communities.vmware.com/thread/423099?start=30&tstart=0
  15. Donk

    VMware Unlocker for OS X

    Version 1.3.0

    239,958 downloads

    Mac OS X Unlocker for VMware ============================ 1. Introduction --------------- The package is a combination of the Unlocker code written by Zenith432 plus some fixes and scripts written by myself that wrap the actual unlocker code. It has been tested against: * Workstation 8/9/10 on Windows and Linux (32 & 64-bit versions) * Player 4/5/6 on Windows and Linux (32 & 64-bit versions) * Fusion 4/5/6 on Snow Leopard, Lion, Mountain Lion and Mavericks * ESXi 5.0/5.1/5.5 The patch code carries out the following modifications dependent on the product being patched: * Fix vmware-vmx and derivatives to allow Mac OS X to boot * Fix vmwarebase .dll or .so to allow Apple to be selected during creation * Copy darwin.iso if needed to VMware folder Note that not all products recognise the darwin.iso via install tools menu item. You will have to manually mount the darwin.iso for example on Workstation. Also Player is missing vmware-vmx-debug and vmware-vmx-stats files and so an error is shown during patching as the files are not found. This can be safely ignored. OS X guests on ESXi patched hosts cannot be controlled from vCenter, only from the ESXi host itself. This means power operations have to be run directly on the server. The vmwarebase code does not need to be patched on ESXi or OS X so you will see a message on those systems telling you that it will not be patched. In all cases make sure VMware is not running, and any background guests have been shutdown. 2. Windows ---------- On Windows you will need to either run cmd.exe as Administrator or using Explorer right click on the command file and select "Run as administrator". install.cmd - patches VMware and copies darwin.iso tools image to VMware uninstall.cmd - restores VMware and removes darwin.iso tools image from VMware 3. Linux --------- On Linux you will need to be either root or use sudo to run the scripts. You may need to ensure the contents of the linux folder have execute permissions by running chmod +x against the 4 files. install.sh - patches VMware and copies darwin.iso tools image to VMware uninstall.sh - restores VMware and removes darwin.iso tools image from VMware 4. Mac OS X ----------- On Mac OS X you will need to be either root or use sudo to run the scripts. This is really only needed if you want to use client versions of Mac OS X. You may need to ensure the contents of the osx folder have execute permissions by running chmod +x against the 3 files. install.sh - patches VMware uninstall.sh - restores VMware 5. ESXi ------- You will need to transfer the zip file to the ESXi host either using vSphere client or SCP. Once uploaded you will need to either use the ESXi support console or use SSH to run the commands. Use the unzip command to extract the files. <<< WARNING: use a datastore volume to run the scripts >>> Please note that you will need to reboot the host for the patches to become active. The patcher is embbedded in a shell script local.sh which is run at boot from /etc/rc.local.d. You may need to ensure the contents of the esxi folder have execute permissions by running chmod +x against the 3 files. install.sh - patches VMware uninstall.sh - restores VMware Note: 1. System should have a persistent scratch partition - should be OK except for stateless and USB boot on drives less than 4GB http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1033696 http://www-01.ibm.com/support/docview.wss?uid=isg3T1013015 http://www.vreference.com/2011/04/28/check-for-esxi-scratch-persistence/ 2. Any changes you have made to local.sh will be lost. If you have made changes to that file, you will need to merge them into the supplied local.sh file. 3. This option runs at boot time to patch the releavant files and it now survives an upgrade or patch to ESXi as local.sh is part of the persisted local state. 6. Zenith432's Unlocker ----------------------- In all cases the unlocker can be run without the scripts but you would need to carry out additional actions which the scripts encapsulate for you especially on ESXi. If you want to run the unlocker directly the parameters are: Usage: Unlocker [-h] [-u] [target_directory] -h: print help -u: remove the patch target_directory: customize location of vmx executables On all platforms you must run it with administrator or root privileges. The source code is provided and Zenith432 makes it freely available for modification. I have modified the code and it is available as per Zenith432's original statement. Thanks to Zenith432 for building the unlocker and Mac Son of Knife for all the testing and support. History ------- 11/10/11 1.0.0 - First release 07/11/11 1.0.1 - Fixed typo in Windows command files 07/12/11 1.0.2 - Updated patcher and tools for latest release WKS 8.0.1 & FUS 4.1.1 10/05/12 1.1.0 - Changed the patching mechanism for vmwarebase .dll or .so & tested against ESXi 5.0 U1 and Tech Previews. 13/07/13 1.1.1 - Changed ESXi scripts to ensure not deleting root /bin folder - Fixed vmwarebase patching on 32-bit Linux - Some other code clean-up in Unlocker.cpp 18/09/13 1.2.0 - Updated vmwarebase pattern matching for WKS 10.0.0 & FUS 6.0.0 25/03/14 1.3.0 - New method to run patcher on ESXi - Fixes crashes when using vCenter - Tested against ESXi 5.5 - Darwin guest tools from Fusion 6.0.2 - Zip file preserves file attributes for Posix based systems © 2011-2014 Dave Parsons
  16. I'm tyring to run iATKOS S3 V2 on VMware Fusion 6(on Mavericks). I tried to set up Fusion with the iso file but when I start the VM, it says "The guest operating system is not MacOS X Server". Then I have downloaded the Fusion Unlocker v1.2.0 but I can't seem to get it to work. I have taken the execution permissions for the files install.sh, uninstall.sh and Unlocker.osx file by running the following commands, sudo chmod +x /Users/tim/Desktop/VMware/unlock-all-v120/osx/install.sh sudo chmod +x /Users/tim/Desktop/VMware/unlock-all-v120/osx/uninstall.sh sudo chmod +x /Users/tim/Desktop/VMware/unlock-all-v120/osx/unlocker.osx Then I tried to run the install.sh script using the command, sudo /Users/tim/Desktop/VMware/unlock-all-v120/osx/install.sh But I get this error message, TimBok:~ tim$ sudo /Users/tim/Desktop/VMware/unlock-all-v120/osx/install.sh Password: VMware Unlocker 1.2.0 =============================== Copyright: Dave Parsons 2011-13 Patching... /Users/tim/Desktop/VMware/unlock-all-v120/osx/install.sh: line 12: ./Unlocker.OSX: No such file or directory TimBok:~ tim$ I need to know what I can do here to get rid os this issue and run the VM.
  17. Hi, I was working with OSX 10.8.3 on my Sony VAIO VPCEH laptop using VmWare 9. It was working fine and I had been doing my projects on it, but suddenly a few days back OSX fails to load. When I power on the machine on VMWare it shows the OSX loading screen for a while and automatically shuts down. I searched in the internet and I am guessing it had something to do when I cleared off my temporary files using Windows Disk CleanUp utility. Now is there anyway I can get my OSX working again??
  18. scottryan1992

    Tried Booting to Install

    Hello Guys, I'm in need of some help, I bought a new system and wanted to dual boot with Windows 8. I thought I didn't want to jump the gun so then I decided to install Windows 8 get some software together then install apple and then finally try the dual boot. Here are my results from trying different distros: iDeneb - Put in disk, press F8, Type -V, Press enter... Oh No! Restarted. Tried different flags just keeps restarting. iPC and iAtkos - Put in disk, press F8, Type -V, Press Enter... Oh No! Kernal Panic and something about 0 hard drive problem?? I then decided to try a different method and went and installed VMware (which i could boot all 3 of the distros in - so im guessing thats a problem with my specs of bios?), the method was to make a virtual machine with access to the physical drive and the setting where it writes immediately to disk. I then try to run the virtual machine but have a problem something about the disk already being used. I think this is because i would be overwriting the disk file that VMware creates which would probably break the virtual machine and not work. Do you think I could use a USB pen for the virtual machine disk file? Then I can use my HDD as a full physical drive? All help would be greatly appreciated and im sorry if this is in the wrong place. (Mods please move if this is the case) Computer specs are in my signature.
×