Skip to main content

Performing a clean install of Mac OS X 10.6 Snow Leopard

Snow Leopard seems to be a little different to its predecessors when it comes to performing a clean installation/re-installation.  The following needs to be done:

  1. Boot off the OS X install DVD – place DVD in drive, restart Mac, hold down C when it “bongs” and keep it held until you see the Apple logo with a spinning wheel
  2. Click Continue when you see Welcome to OS X Snow Leopard
  3. Choose Utilities and then Disk Utility
  4. In Disk Utility click on your hard drive on the left, choose Erase and go with the defaults (OS X Extended (Journaled))
  5. Once the drive has been erased select Quit from the Disk Utility menu
  6. Back in the install screen click Continue
  7. Choose your newly erased hard drive, agree to the license and click Install
  8. The installation process should now run for about 30 minutes
  9. After that you’ll have to fill in your personal info, location details, network/wireless info, etc.

Hope this helps!

Comments

Post a Comment

Popular posts from this blog

Where are SCANPST.EXE and/or SCANOST.EXE?

I sometimes have to deal with customer computers whose Outlook PST or OST files have become corrupted.  Very often the fix is to run SCANPST.EXE on the offending PST/OST file.   However, every time I go to do this I forget where the two executable files are.  Here is where they are on a Vista machine running Office 2007: C:\Program Files\Microsoft Office\Office12 I hope this helps.
11 comments
Read more

Resolve WSUS Server issue that gives "Cannot save configuration because the server is still processing"

This is a pretty infuriating error and can sometimes crop up as a result of running a "wsusutil reset" command. First of all, give the server some time, and then a bit more...  but you've probably already done this. These steps may help to resolve the situation: - Install Microsoft SQL Management Studio (free download) - Run SQL Management Studio and start to connect to the WSUS database - Enter this in the "Server Name" box:  \\.\pipe\MICROSOFT##WID\tsql\query - Expand the "Databases" tree - Right-click on "SUSDB" and choose "New Query" - Paste this query in:     UPDATE tbSingletonData     SET ResetStateMachineNeeded = 0 - You should see a message like "1 row affected", which is good - Quit SQL Management Studio - Open "Services" and restart the "WSUS Service" - Now, open WSUS
Post a Comment
Read more

Unable to Extend Volume because the Windows Recovery Partition is in the way

I had to increase the space allocated to a customer's WSUS server VM that had run out of capacity and was keeling over. So I powered off the VM, added the extra capacity to the virtual hard disk, powered it back on, and went into Disk Management to extend the C: drive partition.  However, I discovered that because the Windows Recovery Partition was in between the C: partition and the new unallocated space (similar to the image below which I've copied from Woshub.com ), I was unable to do an "Extend Volume" job. The solution was to move the recovery partition.  This involves disabling it, deleting it, extending your partition as required, and then re-creating the recovery partition and enabling it. Here are the steps involved: Disable existing recovery partition: You will need to disable the existing Windows recovery partition. To do this, run this command from an admin command line/PowerShell:  reagentc /disable If you get the error message "REAGENTC.EXE: Operati...
Post a Comment
Read more