I have a lot of music in my iTunes library that I have collected over the years. I also have several Apple devices such as an iPod, an iPad and two iPhones that I sync. Some people see my devices and think I have three phones. Even though it looks like a phone, one of them is an iPod. I carry the iPod for two reasons: 1) If the battery runs out on the iPod, I can still make calls. 2) I put only music on the device leaving my phone open for apps.
Though, that’s not really the problem. I also have multiple computers each running iTunes software and this is where the problems start. When I sync my iPod, it resyncs all 5000+ songs over and over again (takes far too long). Let’s explore.
iTunes and Media
Let’s understand the reason why iTunes resyncs a song to a device. The primary reason iTunes resyncs a song already on your iDevice is due to a change in song metadata. What is metadata? Metadata includes information such as play counts and last access times. It also includes other tag data such as artwork, title, artist, track number, duration, volume, etc. Basically, any changes to any portion of the IDtag associated with the song will force a resync to the device. Why is this important? It’s important because many households now have multiple computers.
For example, let’s say you purchased your brand spanking new Airport Extreme 3TB drive and you have now copied your entire iTunes library of music and movie files to to that network drive in hopes of sharing to your multiple computers. Nothing seems wrong with that, right? So, now all of the computers in your household will optimally share these same exact media files. Definitely a space saver, or so you thought. Yes, it may have solved your space issue, but now it has created an entirely new problem. That problem, last access times will change each time any of these computers sharing this folder play a song. Worse, when any single computer’s iTunes software instance updates to a new version, iTunes will scan the entire library of files. Let’s understand why this is a problem.
Shared Drives, iTunes and Last Access Times
When you have multiple computers accessing a single set of media on a shared network drive, this can lead to the multiple computers battling over which computer has last modified a specific song or movie. In some cases, as I said above, an iTunes instance might touch every file in the library. When other iTunes instances start, they will see the song last modify dates have changed from the last time it launched and mark the song to be downloaded to your device.
Let’s assume you have 3 computers in your household: one is yours, one is your spouse’s and one is your child’s. You have hooked each of these computers to a /Volumes/Music folder hooked to that brand spanking new Airport Extreme 3TB drive (where your media files now live), each of these computers will update the last file time access separately. Let’s say your spouse’s computer’s iTunes has gotten updated to a newer version. Each time an update happens, Apple ‘fixes’ the library to make it compatible with the newest version. This ‘fixing’ action touches every single file in the library and marks the last access updated.
So, you come along and plug in your iPhone to sync on your computer’s iTunes software (also sharing this same folder). Because every file has now been updated as a result of your spouse’s update to the latest iTunes version, your device will now download every song to your device. The same problem will happen when your child’s computer is updated.
How do I solve this problem?
The solutions aren’t as easy as one might hope. The easiest solution is to duplicate your entire library to a new folder and point your iTunes instance to that folder. Then do this again for your spouses computer and your child’s computer. Unfortunately, if your library is terabytes in size, this solution may not be practical. If your library is 100-200GB, that might be possible. This is really the best of all solutions. Once you separate your library into separately duplicated media folders, each iTunes instance will have exclusive access to its files only. This is the best of all worlds because the only iTunes computer that will update those files will be yours alone. This means that play counts and last access times will remain 100% accurate and are controlled exclusively by your iTunes computer. The same for your spouse and your child’s library set. The downside is that any new purchases made by your spouse will need to also be downloaded separately by you and by your child. Downloading from iTunes isn’t a problem today because they allow re-downloads from the cloud. But, it is somewhat of a hassle as what’s contained in each of the libraries will diverge.
In the case where you have a 1TB or larger sized library and this duplication solution is impractical, there is another alternative.
Home Sharing Server
Apple now offers the Home Sharing feature in iTunes. What this setup requires is a single system completely dedicated to the Home Sharing service. I might suggest, for practicality’s sake, to buy a new computer to dedicate iTunes to the Home Sharing server purpose. I might suggest a Mac mini or an iMac for this purpose, though you could just as easily use a Windows machine running iTunes. Let’s assume we’re using a Mac mini for this purpose as Mac mini’s are reasonably inexpensive and will serve this purpose perfectly. For performance reasons, I might also suggest a wired connection between the Mac mini and your shared library device (i.e., Airport Extreme 3TB). Your remote computers can access the Home Sharing library wirelessly.
This setup requires unwinding the shared drives mounted on each computer separately and abandoning that. Instead of sharing a network drive to each computer, you will now exclusively share that folder to the newly designated Home Sharing server. Then, share your iTunes library through Apple’s Home Sharing services within that Mac mini iTunes instance. This will then be the only machine that has direct access to your network drive media files. From here, you will then connect each of the other notebook computers and devices to this Home Sharing server to access playlists, music and movies.
How does this solve the problem? Because the single dedicated Home Sharing server has exclusive access to the files, only it will update metadata rather than having 3 or 4 or more computers competing to change file access times. It also means you only need to create your playlists once rather than on each computer separately. Now, a single set of playlists will reside on the Home Sharing server which can be managed centrally from that single computer.
Why is this not a perfect solution? Play counts. Because each computer accessing the Home Sharing server will update play counts for anything consumed, this can cause those songs with updated play counts to resync with your device each time your child or spouses listens to or watches a movie. On the other hand, the number of media that requires rsyncing will be substantially fewer than when each computer can potentially update every file in the library.
It is also not a perfect solution for syncing because you will need to sync your device with your Home Sharing server itself. Not the computer that’s consuming the Home Sharing library remotely. But, it will nearly eliminate the need to resync every file to your device each time you sync.
Can this be resolved by Apple?
Sure. But, it’s not something that will happen overnight. The reason this is a problem is because iTunes doesn’t fundamentally understand the concept of a multiuser environment. MacOS X does, but not iTunes. Apple has shoehorned in some pseudo multiuser features, but without fully supporting everything required for a multiuser environment. For example, to fully support multiple users on a Home Sharing library, each user would supply a set of unique credentials to identify themselves to get into the library which would then create a separate and unique profile for each user. Under that separate profile, iTunes could keep track of play counts separately for each user. In this way, what you play and what your spouse plays would be unique and different. So, if you synced your device against your user profile, your devices would only download those items that you had consumed with your device(s) only. Same for your spouse and for your child.
Implementing a full separately profiled multiuser system in iTunes is the only way to segregate devices and syncing. This is also the only way to prevent syncing extraneous songs after they have been played by someone else. Unfortunately, today this is not a reality.
Additional benefits that could come out of a multiuser system using individual profiles is parental controls. Each profile could then have a set of permissions to allow or disallow access to parts of the library. For example, if you had a playlist of R rated movies, you could set parental controls to lock out access to that playlist from children. A multiuser system offers a lot of benefits to parents for access controls in addition to solving the problem of re-syncing every song in the library to an iPhone or iPad.
If you would like to see such a feature added to iTunes in the future, I encourage you to visit Apple’s iTunes Feedback page and leave an enhancement request for a full multiuser and parental control system be added to iTunes Home Sharing feature.
I recently picked up a sixth generation iPod nano refurbished from Gamestop. When I got home and plugged it into iTunes for Windows 7, iTunes recognized it as a Macintosh formatted iPod and said that it needed to be restored. Here’s where the fun begins.. not. Several things happened after I plugged it in. First, Windows recognized it as drive O: and opened a requester wanting to format the iPod. This format panel stays open until cancelled. Second, when I tried to restore the iPod, iTunes kept showing me error 1436, which is a rather non-descript error that takes you to a mostly generic Apple help page that is only moderately helpful. I take that back, this help page wasn’t helpful at all.
Note, Macintosh formatted iPods cannot be used with Windows. However, Windows formatted iPods can be used on both Windows and Macs. So, this is simply a problem that exists because this iPod was originally formatted on a Mac. Such stupid issues that cause such time wasting problems.
How did the first restore go?
It didn’t. I realized the above mentioned Windows disk format panel had the iPod open and the 1436 error was due to this. However, that was just the beginning of the problems. When I cancelled that panel and I tried the restore again, I got a different issue. Basically, iTunes opens a progress bar that keeps moving without any progress. I wasn’t sure if this progress panel was normal or abnormal. Although, I suspected abnormal after 3 minutes without any changes. So, I began searching for how long an iPod restore should take. I found that restore should complete in only a few minutes (less actually). So, I knew something was wrong when it wasn’t making any progress.
It was clear that iTunes wasn’t going to restore this iPod through its normal means. I began searching on the net for how to recover this iPod and ran into a site that led me to Apple’s How to put an iPod in Disk Mode help page. This page is actually very useful and where the 1436 error page should have led me but didn’t.
What is Disk Mode? Disk Mode puts the iPod into a state that allows it to be formatted as a disk. Well, you don’t really want to format it. Instead, in Disk Mode, it gets rid of all that pesky Macintosh formatting garbage and actually lets you restore it properly. For the sixth gen iPod nano, to put it in Disk Mode, press and hold the power and volume down buttons until the screen turns black and the Apple logo appears. When you see the Apple logo, press and hold both volume up and down buttons until the iPod shows a white screen. This is the Disk Mode screen.
At this point, I plugged the iPod back in with iTunes running and iTunes saw that the iPod was ‘corrupted’ and asked to restore it. Well, the restoration this time went like a champ. No issues at all. However, after I restored it, I did have to close out of iTunes and restart iTunes. Until I did that, iTunes kept telling me that the iPod was in ‘Recovery Mode’ even though I knew that it wasn’t based on the screen of the iPod. After restarting iTunes, that stopped and it finally recognized the iPod as new and let me put music on it. Yay!
So, there you have it. Although, it should have been as simple as plug-in and restore. But, Apple had to make this a chore because of the PC vs Mac formatting thing. Seriously, is that even necessary?
Let me take a moment to commend Apple on this design of this iPod nano. When the first long skinny nano was first released, I thought it was kind of cool, but not worth it. Then the smaller squatty nano arrived and I liked that design so much that I bought one. I got my use out of that and eventually bought an iPod touch. However, the iPod touch isn’t useful in all circumstances and I wanted something smaller and lighter. When this nano was released, I always thought it was a great idea and well executed save for the fact that it has no application support. So, here’s where Apple dropped the ball on this one.
The size and weight is awesome. The look is great, especially if you get a watch band. It just needed a refresh to add a few more features like Bluetooth, video (although, not really necessary in my book) and apps support. I loved the square display because this is the exact image ratio of CD covers. So, it was the perfect marriage between a music player and a user interface. Some people complained that the touch display was overkill. Perhaps, but I always liked it, but I have never needed one of these. I still don’t really need one. The reason I bought one is because Apple has discontinued this model in lieu of it’s bigger screen cousin.
The new nano, however is neither nano in size nor is it really that small. This nano was the perfect size and perfect shape. It truly deserved the name nano. However, the new nano is really not deserving of that name. The screen is too big and it’s really just a dumbed down iPod touch. Yes, the new nano has video capabilities, but so what? I don’t plan on ever loading video on it. Without WiFi or streaming mechanisms, there’s no point. I realize Apple wants to enrich their ecosystem (read, sell more videos to people), but this isn’t the device to do it. In fact. this latest nano design to ship late 2012 is really not that great looking. I feel that it’s stepping too far into the same territory as the iPod touch. So, why do this? It’s also bigger, bulkier and likely heavier. The battery life is probably shorter even. It’s no longer a small portable player.
The 6th generation iPod nano (this one I just bought) is truly small and light. It can go just about anywhere and has a built-in clip even! It lacks some features, yes, but for a music player I certainly don’t miss them. If you’re thinking of buying a 6th generation iPod nano, you should do it now while the Apple outlet still has them in stock. Yes, they are refurbished, but they’re still quite spectacular little music players. However, don’t go into the purchase expecting the feature-set of an iPhone or an iPod touch. It’s not here. If you go into the purchase thinking it’s an iPod shuffle with a display, then you won’t be disappointed with the purchase.
Apple’s ever changing product line
What I don’t get about Apple is removing a product from its product lineup that clearly has no competition in the marketplace at all, let alone having no competition even within its own product lineup. Yet, here we are. Apple is dropping the 6th generation design in lieu of the 7th generation design that’s bigger and bulkier (and likely heavier). In fact, it looks a lot like a smaller dumbed-down iPod touch.
In reality, the 7th gen nano is so close to becoming a tiny iPod touch clone that it clearly competes with the Touch. This is bad. The 6th generation nano (pictured above) in no way competes with the iPod touch, other than it has a tiny touch screen. The 6th generation nano design clearly still has a place in Apple’s lineup. I just don’t get why they dump products from their lineup and replace them with designs that aren’t likely to sell better (0ther than to those people who complained you couldn’t play video on the 6th gen nano). The 6th gen nano is great for the gym or while running. However, after this newest nano is introduced, if you want a square sized small music player, you have to get a shuffle with no display. The bigger bulkier 7th gen design just won’t work for most activity use cases. Apple, your design team needs to better understand how these devices are actually being used before you put pen to paper on new designs, let alone release them for public consumption. Why is it always just one device? Why can’t you have both in the product lineup?
Of course, if they had retained an updated 6th gen model along with adding the 7th gen model, then that would make a lot more sense. Removing the older model in lieu of this one, this is not a replacement design. You can’t wear this one like a watch. So, that whole functionality is gone. What I would like to have seen is two models. A 6th gen revamped to add more features like bluetooth and perhaps a camera and, at the same time, introducing this new video capable model. The updated 6th gen doesn’t need to playback movies, the screen is too tiny for that. In fact, the screen on this new 7th gen model is too tiny for that. Even the iPod touch is too tiny for watching movies, in practicality. It’s not until you get to the iPad does watching a movie even become practical. In a pinch, yes you could watch a video or movie, but you’d be seriously straining your eyes. I’d rather do that (or rather, not strain my eyes) with a much bigger screen. No, an updated square-format touch screen iPod is still very much necessary in the lineup. I understand Apple’s need for change here, but not for the use case that’s now lost with this 7th generation iPod. Sometimes, Apple just doesn’t seem to get it. This is just one of a new series of cracks in the armor that is the new Jobs-less era Apple. Welcome to the new Apple folks.
This article is designed to show you how to mount and manage NTFS partitions in MacOS X. Note the prerequisites below as it’s not quite as straightforward as one would hope. That is, there is no native MacOS X tool to accomplish this, but it can be done. First things first:
This article discusses commands that will format, destroy or otherwise wipe data from hard drives. If you are uncomfortable working with commands like these, you shouldn’t attempt to follow this article. This information is provided as-is and all risk is incurred solely by the reader. If you wipe your data accidentally by the use of the information contained in this article, you solely accept all risk. This author accepts no liability for the use or misuse of the commands explored in this article.
Right up front I’m going to say that to accomplish this task, you must have the following prerequisites set up:
- VirtualBox installed (free)
- Windows 7 (any flavor) installed in VirtualBox (you can probably use Windows XP, but the commands may be different) (Windows is not free)
For reading / writing to NTFS formatted partitions (optional), you will need one of the following:
- For writing to NTFS partitions on MacOS X:
- Tuxera NTFS (not free) or
- ntfs-3g (free)
- For reading from NTFS, MacOS X can natively mount and read from NTFS partitions in read-only mode. This is built into Mac OS X.
If you plan on writing to NTFS partitions, I highly recommend Tuxera over ntfs-3g. Tuxera is stable and I’ve had no troubles with it corrupting NTFS volumes which would require a ‘chkdsk’ operation to fix. On the other hand, ntfs-3g regularly corrupts volumes and will require chkdsk to clean up the volume periodically. Do not override MacOS X’s native NTFS mounter and have it write to volumes (even though it is possible). The MacOS X native NTFS mounter will corrupt disks in write mode. Use Tuxera or ntfs-3g instead.
Why NTFS on Mac OS X?
If you’re like me, I have a Mac at work and Windows at home. Because Mac can mount NTFS, but Windows has no hope of mounting MacOS Journaled filesystems, I opted to use NTFS as my disk carry standard. Note, I use large 1-2TB sized hard drives and NTFS is much more efficient with space allocation than FAT32 for these sized disks. So, this is why I use NTFS as my carry around standard for both Windows and Mac.
How to format a new hard drive with NTFS on Mac OS X
Once you have Windows 7 installed in VirtualBox and working, shut it down for the moment. Note, I will assume that you know how to install Windows 7 in VirtualBox. If not, let me know and I can write a separate article on how to do this.
Now, go to Mac OS X and open a command terminal (/Applications/Utilities/Terminal.app). Connect the disk to your Mac via USB or whatever method you wish the drive to connect. Once you have it connected, you will need to determine which /dev/diskX device it is using. There are several ways of doing this. However, the easiest way is with the ‘diskutil’ command:
$ diskutil list /dev/disk0 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *500.1 GB disk0 1: EFI 209.7 MB disk0s1 2: Apple_HFS Macintosh HD 499.8 GB disk0s2 /dev/disk1 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *2.0 TB disk1 /dev/disk2 #: TYPE NAME SIZE IDENTIFIER 0: Apple_partition_scheme *119.6 MB disk2 1: Apple_partition_map 32.3 KB disk2s1 2: Apple_HFS VirtualBox 119.5 MB disk2s2
Locate the drive that appears to be the size of your new hard drive. If the hard drive is blank (a brand new drive), it shouldn’t show any additional partitions. In my case, I’ve identified that I want to use /dev/disk1. Remember this device file path because you will need it for creating the raw disk vmdk file. Note the nomenclature above: The /dev/disk1 is the device to access the entire drive from sector 0 to the very end. The /dev/diskXsX files access individual partitions created on the device. Make sure you’ve noted the correct /dev/disk here or you could overwrite the wrong drive.
Don’t create any partitions with MacOS X in Disk Utility or in diskutil as these won’t be used (or useful) in Windows. In fact, if you create any partitions with Disk Utility, you will need to ‘clean’ the drive in Windows.
Creating a raw disk vmdk for VirtualBox
This next part will create a raw connector between VirtualBox and your physical drive. This will allow Windows to directly access the entire physical /dev/disk1 drive from within VirtualBox Windows. Giving Windows access to the entire drive will let you manage the entire drive from within Windows including creating partitions and formatting them.
To create the connector, you will use the following command in Mac OS X from a terminal shell:
$ vboxmanage internalcommands createrawvmdk \ -filename "/path/to/VirtualBox VMs/Windows/disk1.vmdk" -rawdisk /dev/disk1
It’s a good idea to create the disk1.vmdk where your Windows VirtualBox VM lives. Note, if vboxmanage isn’t in your PATH, you will need to add it to your PATH to execute this command or, alternatively, specify the exact path to the vboxmanage command. In my case, this is located in /usr/bin/vboxmanage. This command will create a file named disk1.vmdk that will be used inside your Windows VirtualBox machine to access the hard drive. Note that creating the vmdk doesn’t connect the drive to your VirtualBox Windows system. That’s the next step. Make note of the path to disk1.vmdk as you will also need this for the next step.
Additional notes, if the drive already has any partitions on it (NTFS or MacOS), you will need to unmount any mounted partitions before Windows can access it and before you can createrawvmdk with vboxmanage. Check ‘df’ to see if any partitions on drive are mounted. To unmount, either drop the partition(s) on the trashcan, use umount /path/to/partition or use diskutil unmount /path/to/partition. You will need to unmount all partitions on the drive in question before Windows or vboxmanage can access it. Even one mounted partition will prevent VirtualBox from gaining access to the disk.
Note, if this is a brand new drive, it should be blank and it won’t attempt to mount anything. MacOS may ask you to format it, but just click ‘ignore’. Don’t have MacOS X format the drive. However, if you are re-using a previously used drive and wanting to format over what’s on it, I would suggest you zero the drive (see ‘Zeroing a drive’ below) as the fastest way to clear the drive of partition information.
Hooking up the raw disk vmdk to VirtualBox
Open VirtualBox. In VirtualBox, highlight your Windows virtual machine and click the ‘Settings’ cog at the top.
- Click the Storage icon.
- Click the ‘SATA Controller’
- Click on the ‘Add Hard Disk’ icon (3 disks stacked).
- When the ? panel appears, click on ‘Choose existing disk’.
- Navigate to the folder where you created ‘disk1.vmdk’, select it and click ‘Open’.
- The disk1.vmdk connector will now appear under SATA Controller
You are ready to launch VirtualBox. Note, if /dev/disk1 isn’t owned by your user account, VirtualBox may fail to open this drive and show an error panel. If you see any error panels, check to make sure no partitions are mounted and then check the permissions of /dev/disk1 with ls -l /dev/disk1 and, if necessary, chown $LOGNAME /dev/disk1. The drive must not have any partitions actively mounted and /dev/disk1 must be owned by your user account on MacOS X. Also make sure that the vmdk file you created above is owned by your user account as you may need to become root to createrawvmdk.
Click the ‘Start’ button to start your Windows VirtualBox. Once you’re at the Windows login panel, log into Windows as you normally would. Note, if the hard drive goes to sleep, you may have to wait for it to wake up for Windows to finish loading.
Once inside Windows, do the following:
- Start->All Programs->Accessories->Command Prompt
- Type in ‘diskpart’
- At the DISKPART> prompt, type ‘list disk’ and look for the drive (based on the size of the drive).
- Note, if you have more than one drive that’s the same exact size, you’ll want to be extra careful when changing things as you could overwrite the wrong drive. If this is the case, follow these next steps at your own risk!
DISKPART> list disk
Disk ### Status Size Free Dyn Gpt -------- ------------- ------- ------- --- --- Disk 0 Online 40 GB 0 B Disk 1 Online 1863 GB 0 B *
- In my case, I am using Disk 1. So, type in ‘select disk 1’. It will say ‘Disk 1 is now the selected disk.’
- From here on down, use these commands at your own risk. They are destructive commands and will wipe the drive and data from the drive. If you are uncertain about what’s on the drive or you need to keep a copy, you should stop here and backup the data before proceeding. You have been warned.
- Note, ‘Disk 1’ is coincidentally named the same as /dev/disk1 on the Mac. It may not always follow the same naming scheme on all systems.
- To ensure the drive is fully blank type in ‘clean’ and press enter.
- The clean command will wipe all partitions and volumes from the drive and make the drive ‘blank’.
- From here, you can repartition the drive as necessary.
Creating a partition, formatting and mounting the drive in Windows
- Using diskpart, here are the commands to create one partition using the whole drive, format it NTFS and mount it as G: (see commands below):
DISKPART> select disk 1
Disk 1 is now the selected disk
DiskPart succeeded in cleaning the disk.
DISKPART> create partition primary
DiskPart succeeded in creating the specified partition.
DISKPART> list partition
Partition ### Type Size Offset ------------- ---------------- ------- ------- * Partition 1 Primary 1863 GB 1024 KB
DISKPART> select partition 1
Partition 1 is now the selected partition.
DISKPART> format fs=ntfs label="Data" quick
100 percent completed
DiskPart successfully formatted the volume.
DISKPART> assign letter=g
DiskPart successfully assigned the drive letter or mount point.
- The drive is now formatted as NTFS and mounted as G:. You should see the drive in Windows Explorer.
- Note, unless you want to spend hours formatting a 1-2TB sized drive, you should format it as QUICK.
- If you want to validate the drive is good, then you may want to do a full format on the drive. New drives are generally good already, so QUICK is a much better option to get the drive formatted faster.
- If you want to review the drive in Disk Management Console, in the command shell type in diskmgmt.msc
- When the window opens, you should find your Data drive listed as ‘Disk 1’
Note, the reason to use ‘diskpart’ over Disk Management Console is that you can’t use ‘clean’ in Disk Management Console, this command is only available in the diskpart tool and it’s the only way to completely clean the drive of all partitions to make the drive blank again. This is especially handy if you happen to have previously formatted the drive with MacOS X Journaled FS and there’s an EFI partition on the drive. The only way to get rid of a Mac EFI partition is to ‘clean’ the drive as above.
Annoyances and Caveats
MacOS X always tries to mount recognizable removable (USB) partitions when they become available. So, as soon as you have formatted the drive and have shut down Windows, Mac will likely mount the NTFS drive under /Volumes/Data. You can check this with ‘df’ in Mac terminal or by opening Finder. If you find that it is mounted in Mac, you must unmount it before you can start VirtualBox to use the drive in Windows. If you try to start VirtualBox with a mounted partition in Mac OS X, you will see a red error panel in VirtualBox. Mac and Windows will not share a physical volume. So you must make sure MacOS X has unmounted the volume before you start VirtualBox with the disk1.vmdk physical drive.
Also, the raw vmdk drive is specific to that single hard drive. You will need to go through the steps of creating a new raw vmdk for each new hard drive you want to format in Windows unless you know for certain that each hard drive is truly identical. The reason is that vboxmanage discovers the geometry of the drive and writes it to the vmdk. So, each raw vmdk is tailored to each drive’s size and geometry. It is recommended that you not try to reuse an existing physical vmdk with another drive. Always create a new raw vmdk for each drive you wish to manage in Windows.
Zeroing a drive
While the clean command clears off all partition information in Windows, you can also clean off the drive in MacOS X. The way to do this is by using dd. Again, this command is destructive, so be sure you know which drive you are operating on before you press enter. Once you press enter, the drive will be wiped of data. Use this section at your own risk.
To clean the drive use the following:
$ dd if=/dev/zero of=/dev/disk1 bs=4096 count=10000
This command will write 10000 * 4096 byte blocks with all zeros. This should overwrite any partition information and clear the drive off. You may not need to do this as the diskpart ‘clean’ command may be sufficient.
If the drive has become corrupted or is acting in a way you think may be a problem, you can always go back into Windows with the data1.vmdk connector and run chkdsk on the volume. You can also use this on any NTFS or FAT32 volume you may have. You will just need to create a physical vmdk connector and attach it to your Windows SATA controller and make sure MacOS X doesn’t have it mounted. Then, launch VirtualBox and clean it up.
If you are using Tuxera to mount NTFS, once you exit out of Windows with your freshly formatted NTFS volume, Tuxera should immediately see the volume and mount it. This will show you that NTFS has been formatted properly on the drive. You can now read and write to this volume as necessary.
Note that this method to format a drive with NTFS is the safest way on Mac OS X. While there may be some native tools floating around out there, using Windows to format NTFS will ensure the volume is 100% compliant with NTFS and Windows. Using third party tools not written by Microsoft could lead to data corruption or improperly formatted volumes.
Of course, you could always connect the drive directly to a Windows system and format it that way. ;)
With this article, I’ll start by saying.. please purchase your copy of Mac OS X desktop software from Apple. It’s $29 and you get the original media (which is always good to have on hand).
To start, here are the softwares you will need:
- VMWare Player 3 (need to create login to download)
- Empire EFI 1.3.2 for VMWare
- Snow Leopard Install Media (Disk or ISO)
- 7zip (for opening Empire EFI archive)
- ImageBurn (for making ISO images from CD Media)
Installing Mac OS X on VMWare Player is a pretty simple install, but note that there are some important issues that aren’t yet resolved. I’ll explain the issues, however, after the install steps.
Inside the Empire EFI 1.3.2 archive, you will see the following files:
You will see that the extracted ‘Snowy_VM’ folder contains several files besides just the EFI media. Inside the Mac OS X Server*.vmwarevm directory, you’ll see it contains two .vmx templates for VMWare. Use the .vmx file without the underscore at the beginning. Note, you’ll need to use this template to get the install going. It’s far simpler to use their existing template than trying to figure out all the proper VMWare Player settings. So, use what’s given rather than trying to reinvent the wheel. If you absolutely feel you want to reinvent, then I’ll leave that for you to determine what’s necessary.
To begin, inside VMWare Player, select File->Open a Virtual Machine. Find the .vmx file mentioned just above and open it. Once opened, it will appear as ‘Mac OS X Server 10.6 (experimental)’ in the VMWare Player selection panel. From here, you will need to modify the settings for the CDROM device under this machine. Choose the ‘Mac OS X Server 10.6 (experimental)’ imported machine and choose ‘Edit virtual machine settings’ on the bottom right of the window. Now click the on the CDROM device and under ‘Connection’ change it to ‘Use ISO image’ and browse to and select the darwin_snow.iso image inside the Snowy_VM directory’. Click ‘OK’.
You’re now ready to boot. So, click ‘Play Virtual Machine’. Once the machine has started and the system begins searching for a CDROM (read the text on the screen), you will need to change the CDROM to the Mac OS X Snow Leopard media. I recommend using an ISO media to install. So, I will assume you are using an ISO image here. At the bottom of the active VM Window, right click the CDROM icon which may now be greyed out (disconnected) and choose ‘Settings’. Locate the Snow Leopard media on your hard drive and click ‘OK’ to accept it. Check the box next to ‘Connected’ at the top of the window and click ‘OK’ at the bottom.
The system should recognize the disk change and begin to boot the media in about 10 seconds. Once the install begins, you are now installing Mac OS X. Follow the steps to install Mac OS X. Once Mac OS X is installed, reboot. Note the hard drive given in this Snowy_VM archive is ‘ready to go’. So you don’t need to format it.
Booting issues with VMWare Player and Mac OS X
Let’s pause and explain this. When you reboot the first time, the system may or may not boot up. There are two behaviors you should watch for. The first behavior is that you get to the Apple Logo screen with the spinning lines. If it never progresses beyond this grey screen, then you will need to reboot and try again.
The second behavior is that it may get past the grey screen, but then Finder never appears and you see a forever spinning cursor. If you see this, you will need to reboot and try again.
These issues are annoying, but that’s why this is ‘experimental’. So, we live with these issues.
The third issue is that you will need to continually leave the darwin_snow.iso image in the drive all of the time to boot up Mac OS X. Hey, at least it works. Leaving it in the drive is really not a problem as it boots up so quickly. Perhaps they can create a standalone booter later, but for now this works.
Note, I recommend setting up a second CDROM drive inside your Mac OS X virtual machine’s settings. This way, you leave one CDROM always set up with darwin_snow.iso and you use the second one to load/unload other ISO images. If you like, you can set the second one up to your physical drive also so you can pop real CDs in the drives as you need. Note that if you change the darwin_snow.iso image to something else, you have to remember to set it back when you’re done. If you don’t do this, Mac OS X won’t boot. So, this is why I recommend setting up a second drive for loading ISO images.
Booting up successfully
After getting through any unsuccessful boot attempts (or not), you should get to the registration screen. After going through all of the registration screens you will be at the standard Finder desktop. At this point, you might want to change things like Sound and Display. Note that the sound and display drivers are just about as good as what’s in Virtual Box. In fact, Virtual Box’s resolution setup is a bit more complete than this. So, don’t expect a whole lot here.
Suffice it to say that you will need to follow editing of the apple.com.Boot.plist file as in the ‘Installing Mac OS X on VirtualBox‘ article on Randosity. Add in the lines related to the graphics. Once you have done this, edit the virtual machine in VMWare player and choose the Display setup. Under ‘Monitors’ change it to ‘Specify Monitor Settings’ and manually change the maximum resolution to ‘1366×768’. When you reboot, Mac OS X should go into this mode. If it doesn’t work, then you may have to fiddle with the apple.com.Boot.plist file until it works. Note that the resolutions here are limited, so don’t try to set up some odd resolution as it won’t work.
Note, this is the best resolution I could find. Note that in the above directory, you’ll see the file ‘EnsoniqAudioPCI.mpkg.tar’. This is a Mac OS X driver for audio. I have tried installing this without success. But, your mileage may go farther. The trick is in getting this into the Mac. So, you’ll need to start a browser and download the EFI file again on the Mac. Then extract it, find this file and install it.
At this point, you should be all set. You may run into the booting issues from time to time, just reboot until it boots up. Hopefully this booting issue will be fixed at some point. Good luck and happy installing.
If you’re looking for something that boots consistently for Mac OS X, has better video mode support and working sound, then I would suggest setting up Mac OS X on VirtualBox. The setup for VirtualBox is a little more complex, but it boots consistently every time, has its own standalone boot loader and offers a few more features.
If you have questions, please leave a comment below.