<?xml version="1.0" encoding="iso-8859-1"?>

<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title>macosxhints.com install tips</title>
<link>http://hints.macworld.com/index.php?topic=install</link>
<description>Tips and tricks dealing with installing OS X (and other software), from macosxhints.com</description>
<managingEditor>webteam@macosxhints.com</managingEditor>
<webMaster>webteam@macosxhints.com</webMaster>
<copyright>Copyright 2013 Mac OS X Hints</copyright>
<generator>Geeklog</generator>
<pubDate>Tue, 16 Apr 2013 07:30:01 -0700</pubDate>
<language>en-gb</language>
<atom:link href="http://hints.macworld.com/backend/hintsinstall.rss" rel="self" type="application/rss+xml" />
<item>
<title>Cancel a Mac Store app update while it's downloading</title>
<link>http://hints.macworld.com/article.php?story=20130413220340684</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20130413220340684</guid>
<pubDate>Tue, 16 Apr 2013 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20130413220340684#comments</comments>
<dc:subject>Install</dc:subject>
<description>In the Updates section of the Mac App Store, if the user chooses to update an app or apps, the interface offers the ability to pause the download of the update, but seemingly not to cancel it. Canceling the download is possible by holding down the option key. The &quot;Pause&quot; buttons change to &quot;Cancel&quot; buttons.&lt;br&gt;&lt;br&gt; [&lt;b&gt;kirkmc adds&lt;/b&gt;: I don't have any current updates to be able to test this. I don't think this stops the update from generating a notification after you cancel the download, but I'm curious as to what happens. Post your experiences in the comments.] 
</description>
</item>
<item>
<title>Install Windows 7 on external drive using Boot Camp (Lion)</title>
<link>http://hints.macworld.com/article.php?story=20130205013401393</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20130205013401393</guid>
<pubDate>Thu, 14 Feb 2013 07:30:00 -0800</pubDate>
<comments>http://hints.macworld.com/article.php?story=20130205013401393#comments</comments>
<dc:subject>Install</dc:subject>
<description>Having purchased a Segate GoFlex Desktop Thunderbolt Adapter made me wonder if it's possible to install a Bootcamp-Partition on an external Drive. Well it works; sort of.&lt;br&gt;&lt;ol&gt;&lt;li&gt; Launch Boot Camp Assistant. &lt;/li&gt;&lt;li&gt; Select the local Drive for installation (not the external Drive) it will take about 20 GB of disk space.&lt;/li&gt;&lt;li&gt; Boot Camp Assistant will now repartition your local drive. &lt;/li&gt;&lt;li&gt; Wait a while for Boot Camp Assistant to finish preparing the drive.&lt;/li&gt;&lt;li&gt; When the Windows 7 Installer comes up simply choose the external drive as target, not the local one. &lt;/li&gt;&lt;li&gt; Proceed with the installation.&lt;/li&gt;&lt;/ol&gt;When booting your Mac (holding the Option key) you'll now see that there is a local Windows 7 boot volume. Unfortunately, you will have wasted 20 GB creating a partition on your main drive.&lt;br&gt;&lt;br&gt;[&lt;b&gt;kirkmc adds&lt;/b&gt;: I haven't tested this. I don't know if Disk Utility can delete that partition; live partitioning is possible, but in some cases cert ...</description>
</item>
<item>
<title>How to reset Lion back to the Setup Assistant</title>
<link>http://hints.macworld.com/article.php?story=20121202080339900</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20121202080339900</guid>
<pubDate>Wed, 05 Dec 2012 07:30:00 -0800</pubDate>
<comments>http://hints.macworld.com/article.php?story=20121202080339900#comments</comments>
<dc:subject>Install</dc:subject>
<description>There have been &lt;a href=&quot;http://hints.macworld.com/article.php?story=20010827120222505&quot;&gt;previous&lt;/a&gt; &lt;a href=&quot;http://hints.macworld.com/article.php?story=2007110800450816&quot;&gt;hints&lt;/a&gt; on how to reset earlier versions of Mac OS X to delete users so that it boots to the Setup Assistant again. This can be useful if you are passing on or selling your computer to someone else. The most recent hint was posted in 2007 for Mac OS X 10.5 and there were significant corrections included in the comments. There is also a command that changed in 10.7 (also in the older hint’s comments) and even with the modifications suggested in the comments, the hint is still incomplete. &lt;br&gt;&lt;br&gt; So instead of adding yet another modification in the comments of a hint related to 10.5, I thought I would submit a new hint brining everything together from the old hint, its comments, changes needed for 10.7, and the missing items I have found. This provides a current version of the hint for 10.7 and presumably 10.8 ...</description>
</item>
<item>
<title>Display a list of files in package while in Installer </title>
<link>http://hints.macworld.com/article.php?story=20120406092946908</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20120406092946908</guid>
<pubDate>Tue, 10 Apr 2012 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20120406092946908#comments</comments>
<dc:subject>Install</dc:subject>
<description>If you press Command+I while in the OS X Installer, a small window displays, showing the contents of the package about to be installed.&lt;br&gt;&lt;br&gt; [&lt;b&gt;kirkmc adds&lt;/b&gt;: This is great; I don't know why we haven't had this submitted before. I tried this with a number of installer packages. In most cases, the window shows the contents of the .pkg from the very first window. However, when checking on the Mac OS X 10.7.3 Combo Updater, clicking the disclosure triangle next to the name of the update in the file list window displayed &quot;The file listing isn't yet available,&quot; but the file list then showed up a few seconds later. Note that all you can do is view the file list; you can't copy it.] 
</description>
</item>
<item>
<title>Install Windows XP on a Sandy Bridge Mac</title>
<link>http://hints.macworld.com/article.php?story=20120223191944234</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20120223191944234</guid>
<pubDate>Fri, 24 Feb 2012 07:30:00 -0800</pubDate>
<comments>http://hints.macworld.com/article.php?story=20120223191944234#comments</comments>
<dc:subject>Install</dc:subject>
<description>Installing Windows XP through Bootcamp on a Sandy Bridge Mac is not easy. Apple decided to limit the Sandy Bridge version of Bootcamp to Windows 7, so no XP drivers are available. There are ways of tricking Bootcamp into installing XP, but they all fail for the lack of a decent video driver. The default video driver is flakey, and crashes on boot up.&lt;br&gt;&lt;br&gt;There is a way to have XP on a Sandy Bridge machine. Get a copy of VMWare's Fusion 4 and install it. Fusion can do a clean install of XP or work from your Bootcamp partition. I used the Bootcamp option which took about 10 minutes to set up. XP boots and runs flawlessly. There are no missing drivers in device manager. Windows boots faster in Fusion than it did from the Bootcamp partition, probably because it's not searching for drivers.&lt;br&gt;&lt;br&gt;I know, I know, XP is ancient and over a decade old, but some of us need it to run old software. If you have a new Mac and need XP this is the way to go.&lt;br&gt;&lt;br&gt;[&lt;b&gt;crarko adds:&lt;/b&gt; I ...</description>
</item>
<item>
<title>Install recent versions of Adobe Creative Suite on case-sensitive volumes</title>
<link>http://hints.macworld.com/article.php?story=20120118103118881</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20120118103118881</guid>
<pubDate>Fri, 20 Jan 2012 07:30:00 -0800</pubDate>
<comments>http://hints.macworld.com/article.php?story=20120118103118881#comments</comments>
<dc:subject>Install</dc:subject>
<description>Anyone who has ever tried to install parts of Adobe Creative Suite on a case-sensitive partition will know that Adobe doesn't support case-sensitive disks. Back when I first encountered this problem, I simply assumed that case sensitivity was a new thing and Adobe would fix this in a version or two, since it's a relatively trivial thing to do.&lt;br&gt;&lt;br&gt;Unfortunately, Adobe's solution to this was to simply make it so the installer refuses to install on case-sensitive partitions. It also insists that you install on your boot partition. So if you happen to have formatted your primary partition as case sensitive, you're basically out of luck.&lt;br&gt;&lt;br&gt;I spent some time coming up with &lt;a href=&quot;http://arcticmac.home.comcast.net/tutorials/cs5instructions.html&quot;&gt;a solution&lt;/a&gt; that uses gdb (the gnu debugger) to trick the installer into thinking that your disks are case insensitive so it will let you install the software. The next step would then be to go through and rename all the files th ...</description>
</item>
<item>
<title>A script to keep Flash Player up to date</title>
<link>http://hints.macworld.com/article.php?story=20110503171510369</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20110503171510369</guid>
<pubDate>Wed, 04 May 2011 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20110503171510369#comments</comments>
<dc:subject>Install</dc:subject>
<description>Frequent security updates to Flash prompted me to write this script to keep Flash current on Intel Macs that I manage. While more recent versions of Flash can be configured to notify end users of available updates, this script will silently check and upgrade to a newer version if one is available.&lt;br&gt;&lt;br&gt;It works by checking the installed version of Flash (if any) against the version number available for Mac Safari/Firefox/Opera on Adobe's About Flash page. If the two are different, it downloads the DMG of the latest Flash installer to the same folder where the script resides, silently mounts the DMG, and executes the installer package buried in the 'Install Flash' application. It runs completely silently and will log all of its activities to a file for later review. If Flash is not present, it will be installed on the system. In its current form it will not advise users to quit their browsers, because it was written to be run during off hours on machines sitting at the login win ...</description>
</item>
<item>
<title>10.6: A workaround for a Boot Camp x64 installation issue</title>
<link>http://hints.macworld.com/article.php?story=20100314110323777</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20100314110323777</guid>
<pubDate>Wed, 17 Mar 2010 07:30:00 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20100314110323777#comments</comments>
<dc:subject>Install</dc:subject>
<description>&lt;img src=&quot;http://www.macosxhints.com/images/106only.png&quot; alt=&quot;Snow Leopard only hint&quot; align=&quot;left&quot; style=&quot;margin-right: 10px&quot;&gt;Today I installed Windows 7 Ultimate x64 via Boot Camp on my 2007 MacBook Pro 2.4GHz machine. I was stumped when I couldn’t install the Boot Camp drivers from the 10.6 DVD in Windows.&lt;br&gt;&lt;br&gt;I tried several different approaches, but every single try ended with the message &lt;em&gt;Boot Camp x64 is unsupported on this computer model&lt;/em&gt; when launching the Boot Camp setup app. I could also not install the 3.1 update. The only visual indication was Nvidia drivers installing, and afterwards, it would simply quit while all the time there was no reference that I was actually about to install Boot Camp.&lt;br&gt;&lt;br&gt;Knowing that I didn’t do anything wrong, I didn’t want to give up and finally found a solution. Here's a step by step guide:&lt;ol&gt;&lt;li&gt;Boot into Windows 7 and insert your 10.6 DVD&lt;/li&gt;&lt;li&gt;Right-click on Start &amp;raquo; Programs &amp;raquo; Accessories &amp;raquo; Comma ...&lt;/li&gt;&lt;/ol&gt;</description>
</item>
<item>
<title>Install Windows in Boot Camp despite a defective SuperDrive</title>
<link>http://hints.macworld.com/article.php?story=20100227081910443</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20100227081910443</guid>
<pubDate>Tue, 02 Mar 2010 07:30:00 -0800</pubDate>
<comments>http://hints.macworld.com/article.php?story=20100227081910443#comments</comments>
<dc:subject>Install</dc:subject>
<description>My 2007 DC MacBook (running 10.6.2) has an internal SuperDrive that is defective, which hampered my Boot Camp installation.2brI set up the MacBook up for dual boot with the Boot Camp assistant, and I wanted to install Windows using a bare internal drive (Samsung) connected to USB thru a USB2.0 to SATA/IDE cable. The process failed after restart -- it stuck on the boot screen, displaying an Apple icon with (sometimes) a flashing question mark. &lt;br&gt;&lt;br&gt;Looking for a solution I came a across &lt;a href=&quot;http://refit.sourceforge.net/&quot;&gt;rEfit&lt;/a&gt;, which is a kind of boot manager for EFI-equipped (Intel) Macs.  &lt;br&gt;&lt;br&gt;Install the program and restart the MacBook twice. After the second restart, the rEfit boot menu should be visible. When I connected an external CD/DVD drive that contained a bootable Windows CD, that disk showed up as bootable. You selected the Windows installation disk and it continued with the installation process.&lt;br&gt;&lt;br&gt;For me it saved the day; I was able to insta ...</description>
</item>
<item>
<title>Run full OS X installer for another drive without rebooting</title>
<link>http://hints.macworld.com/article.php?story=20100122081044636</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20100122081044636</guid>
<pubDate>Wed, 27 Jan 2010 07:30:00 -0800</pubDate>
<comments>http://hints.macworld.com/article.php?story=20100122081044636#comments</comments>
<dc:subject>Install</dc:subject>
<description>If you ever need to install (or reinstall) OS X on a drive other than your current boot drive, you can do it without rebooting. (Normally, when you launch the OS X installer, it reboots your machine before starting the installation.) With this hint, you can do the whole install process while booted normally from your current drive -- so you can keep working while the install is going on. &lt;br&gt;&lt;br&gt;To do that, just launch the Unix executable for the installer application on the DVD, by running the following command in Terminal:&lt;div style=&quot;margin-left: 20px; margin-top:10px; margin-bottom:10px; padding: 5px; border:1px solid; width:520px; height:60px; overflow:scroll;white-space:nowrap;resize:both&quot;&gt;&lt;pre&gt;sudo /Volumes/Snow&amp;#092; leopard&amp;#092; Install&amp;#092; DVD/System/Installation/CDIS/Mac&amp;#092; OS&amp;#092; X&amp;#092; Installer.app/Contents/MacOS/Mac&amp;#092; OS&amp;#092; X&amp;#092; Installer&lt;/pre&gt;&lt;/div&gt;To make it work even faster, you can clone the install DVD to a small partition on one of your  ...</description>
</item>
<item>
<title>Uninstall applications installed from packages</title>
<link>http://hints.macworld.com/article.php?story=20100107090139622</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20100107090139622</guid>
<pubDate>Mon, 11 Jan 2010 07:30:00 -0800</pubDate>
<comments>http://hints.macworld.com/article.php?story=20100107090139622#comments</comments>
<dc:subject>Install</dc:subject>
<description>If you've installed an application from a &lt;tt&gt;.pkg&lt;/tt&gt;-type installer, Mac OS X keeps a listing of what was installed in the Library/Receipts folder -- either the top-level Library, or your user's Library. The &lt;tt&gt;lsbom&lt;/tt&gt; command can be used to see this list, and to uninstall the application.&lt;br&gt;&lt;br&gt;First, find the receipt. It will be in either &lt;tt&gt;~/Library/Receipts&lt;/tt&gt; or &lt;tt&gt;/Library/Receipts&lt;/tt&gt;, as the name of the package. The actual bom (&quot;bill of materials&quot;) file is located at, for example,&lt;pre&gt;/Library/Receipts/some_app.pkg/Contents/Archive.bom&lt;/pre&gt;Use the &lt;tt&gt;lsbom&lt;/tt&gt; command to see what was installed:&lt;code&gt;lsbom -fls /Library/Receipts/some_app.pkg/Contents/Archive.bom&lt;/code&gt;You can use this list to manually delete the items installed, or you can feed the list to &lt;tt&gt;rm&lt;/tt&gt; to delete the installed files. Be sure to examine the list of files before trying to remove them -- this command will only work if the paths are relative to the root directory (&quot;/&quot;),  ...</description>
</item>
<item>
<title>Find files created or modified by an installer</title>
<link>http://hints.macworld.com/article.php?story=20091223115101622</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20091223115101622</guid>
<pubDate>Tue, 05 Jan 2010 07:30:00 -0800</pubDate>
<comments>http://hints.macworld.com/article.php?story=20091223115101622#comments</comments>
<dc:subject>Install</dc:subject>
<description>Do you like to know which files and folders get created or modified when you install a new application? I can suggest two different solutions: Either use a tool to track all file system changes, or use a tool that searches the disk by creation/modification dates.&lt;br&gt;&lt;br&gt;[&lt;b&gt;robg adds:&lt;/b&gt; This hint includes information about using a free program, &lt;a href=&quot;http://apps.tempel.org/FindAnyFile/&quot;&gt;Find Any File&lt;/a&gt;, as one way to track file system changes. The author of this hint (Thomas Tempelmann) is the author of that application. However, because there's good information here in the hint, and because the app itself is free and seems to work well, I felt it was worth sharing. Read on for the discussion...]
&lt;b&gt;Logging tools&lt;/b&gt;&lt;br&gt;&lt;br&gt;First the &quot;pro&quot; method: Use a file system logging tool to trace all file operations during a period of time. The problem with these tools, though, is that you might see much more information than you want. Sorting out what's relevant may need some exp ...</description>
</item>
<item>
<title>One fix installations stuck at 'Preparing...'</title>
<link>http://hints.macworld.com/article.php?story=20091210073435254</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20091210073435254</guid>
<pubDate>Fri, 18 Dec 2009 07:30:00 -0800</pubDate>
<comments>http://hints.macworld.com/article.php?story=20091210073435254#comments</comments>
<dc:subject>Install</dc:subject>
<description>Since moving to Snow Leopard, I've noticed an innumerable number of times where software installations would get stalled at the &quot;Preparing...&quot; stage. If you've noticed it too, chances are you're an iPhone developer, too...&lt;br&gt;&lt;br&gt;It turns out the simple fix for this problem is to quit the iPhone Simulator, and then try the installation again.
</description>
</item>
<item>
<title>Fix Boot Camp Assistant's 'too many large files' problem</title>
<link>http://hints.macworld.com/article.php?story=20091202084645639</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20091202084645639</guid>
<pubDate>Mon, 14 Dec 2009 07:30:00 -0800</pubDate>
<comments>http://hints.macworld.com/article.php?story=20091202084645639#comments</comments>
<dc:subject>Install</dc:subject>
<description>If you've been using your Mac for months before deciding you need a Boot Camp partition, you may find it's too late. When you run the Boot Camp Assistant, it may tell you that you have too many 'large files' on the system for Boot Camp to create a partition.&lt;br&gt;&lt;br&gt;One solution found on the interwebs is to use &lt;a href=&quot;http://www.coriolis-systems.com/iDefrag.php&quot;&gt;iDefrag&lt;/a&gt; to defrag your computer. I am not a fan of this, as I am on a budget :). As an alternative, try these steps:&lt;ol&gt;&lt;li&gt;Open up Disk Utility.&lt;/li&gt;&lt;li&gt;Navigate to the Partitions tab.&lt;/li&gt;&lt;li&gt;Shrink your primary partition by the amount of space you want your Boot Camp partition to take up. NOTE: You may need to do this in two or three tries, as Disk Utility may throw an error if you try to resize by too large an amount. I had to do it in three small increments.&lt;/li&gt;&lt;li&gt;Now that the partition has shrunk, expand the partition so it covers the rest of the disk, or as much space as you would like.&lt;/li&gt;&lt;li&gt;Run Boo ...&lt;/li&gt;&lt;/ol&gt;</description>
</item>
<item>
<title>Install Windows98 in VirtualPC 7 on an OS X 10.5 PowerPC </title>
<link>http://hints.macworld.com/article.php?story=20091121162658600</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20091121162658600</guid>
<pubDate>Fri, 04 Dec 2009 07:30:00 -0800</pubDate>
<comments>http://hints.macworld.com/article.php?story=20091121162658600#comments</comments>
<dc:subject>Install</dc:subject>
<description>I still have my good ol' trusty Imac G4, and still love it and use it every day (you know I can't afford a new one). I had the need to install a few apps that are not available for Mac OS X, so I reinstalled VirtualPC 7 (VPC7) and shook the dust off my old Windows 98 disk.&lt;br&gt;&lt;br&gt;However, I found out that although I could install VPC7 under Leopard,  I couldn't use CDs, DVDs, or even disk images to install Windows98. So then I tried &lt;a href=&quot;http://www.kju-app.org/&quot;&gt;Q-[kju:]&lt;/a&gt;, but it was impossible to use -- it kept crashing, there was no network, no file sharing, and it was impossibly slow.&lt;br&gt;&lt;br&gt;There was no apparent way to fix the installing issues with Windows98, so then I thought to copy the contents of the Windows98 CD into a VirtualPC image. However, I then couldn't find a way to mount the .vhdp image. After struggling for two days, I was about to quit until I found out that .vhdp images are basically a bundle with an alias and a standard .vhd image inside. With that ...</description>
</item>
<item>
<title>Restore default bootloader without harming partitions</title>
<link>http://hints.macworld.com/article.php?story=20091111185717745</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20091111185717745</guid>
<pubDate>Fri, 20 Nov 2009 07:30:01 -0800</pubDate>
<comments>http://hints.macworld.com/article.php?story=20091111185717745#comments</comments>
<dc:subject>Install</dc:subject>
<description>If your bootloader gets changed or corrupted, this fix will restore it without damage to your disk partitions.&lt;br&gt;&lt;br&gt;This hint may be a bit esoteric, but I thought I was up for a long night of reinstallation pain before stumbling upon this fix. I made the mistake of trying to use an Ubuntu 9.04 boot CD to install Ubuntu to an external (USB) drive on my Mac.&lt;br&gt;&lt;br&gt;&lt;b&gt;Don't do this, unless you know the following:&lt;/b&gt; Regardless of the fact that you chose the external drive upon which to install Ubuntu, you won't be able to boot back into your Mac without changing the bootloader. I ended up with the dreaded question mark folder when I tried to reboot my Mac, and nothing worked to boot into my OS X partition.&lt;br&gt;&lt;br&gt;Luckily, I have a bootable external drive with OS X on it, and I was able to boot into it by holding down the Option key (the primary partition still did not show up).
I started searching online for the fix, and it seems that Ubuntu changes the Darwin (default) boot ...</description>
</item>
<item>
<title>10.6: How to install Win XP Pro Service Pack 3 in Boot Camp 3</title>
<link>http://hints.macworld.com/article.php?story=20091031132634361</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20091031132634361</guid>
<pubDate>Mon, 02 Nov 2009 07:30:03 -0800</pubDate>
<comments>http://hints.macworld.com/article.php?story=20091031132634361#comments</comments>
<dc:subject>Install</dc:subject>
<description>&lt;img src=&quot;http://www.macosxhints.com/images/106only.png&quot; alt=&quot;Snow Leopard only hint&quot; align=&quot;left&quot; style=&quot;margin-right: 10px&quot;&gt;Over the weekend, in preparation for an upcoming review of the newest versions of Fusion and VirtualBox, I needed to set up a new Boot Camp partition on my MacBook Pro. Because Windows 7 isn't yet officially supported by Apple, and Vista isn't widely used, I chose to install XP Pro. My XP Pro disc is a Service Pack 2 release, so after booting into Windows, the system found and downloaded a bunch of updates to apply, chief among them Service Pack 3 (SP3).&lt;br&gt;&lt;br&gt;The update process went smoothly, until the system tried to install SP3. The update process started, then died with this error:&lt;blockquote&gt;An error occured while copying file osloader.ntd.  Cannot copy file to destination directory.  Click Retry to retry the operation or click Cancel.&lt;/blockquote&gt;At that point, the only solution was to bail on the update, and have Windows back out the changes it ...</description>
</item>
<item>
<title>10.6: Resolve a non-usable disk during 10.6 upgrade</title>
<link>http://hints.macworld.com/article.php?story=2009091612142212</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=2009091612142212</guid>
<pubDate>Tue, 06 Oct 2009 07:30:03 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=2009091612142212#comments</comments>
<dc:subject>Install</dc:subject>
<description>&lt;img src=&quot;http://www.macosxhints.com/images/106only.png&quot; align=&quot;left&quot; style=&quot;margin-right: 10px&quot;&gt;While attempting to upgrade my MacBook Pro to 10.6, I received the error message &quot;this disk cannot be used to start up your computer.&quot; I only have one disk and one volume, so that disk was my only choice.
&lt;br&gt;&lt;br&gt;
I tried running Disk Utility to repair the drive, but that didn't help. I searched the web and came up with a solution that works. Using Disk Utility from the installer, slightly reduce the partition size on the boot disk. The act of changing and rewriting the partition seems to fix whatever is causing the issue.
</description>
</item>
<item>
<title>10.6: No way to save updates from Software Update</title>
<link>http://hints.macworld.com/article.php?story=20090910162236620</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20090910162236620</guid>
<pubDate>Wed, 30 Sep 2009 07:30:04 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20090910162236620#comments</comments>
<dc:subject>Install</dc:subject>
<description>&lt;img src=&quot;http://www.macosxhints.com/images/106only.png&quot; align=&quot;left&quot; style=&quot;margin-right: 10px&quot;&gt;In Leopard, Software Update gave you the choice of either downloading or installing an update. Under Snow Leopard, though, the download option is gone; it's install or nothing.
&lt;br&gt;&lt;br&gt;
[&lt;b&gt;robg adds:&lt;/b&gt; There's a new Update &amp;raquo; Go to Apple Download Page menu item in Software Update; every update should be available there for download. While this change simplifies the Software Update app, it does add a step for those who prefer to download updates (for updating multiple Macs, for instance).]
</description>
</item>
<item>
<title>10.6: How to install the Logitech Control Center software</title>
<link>http://hints.macworld.com/article.php?story=20090902043559141</link>
<guid isPermaLink="true">http://hints.macworld.com/article.php?story=20090902043559141</guid>
<pubDate>Tue, 15 Sep 2009 07:30:02 -0700</pubDate>
<comments>http://hints.macworld.com/article.php?story=20090902043559141#comments</comments>
<dc:subject>Install</dc:subject>
<description>&lt;img src=&quot;http://www.macosxhints.com/images/106only.png&quot; align=&quot;left&quot; style=&quot;margin-right: 10px&quot;&gt;My Logitech mouse stopped being recognized in Snow Leopard. Logitech, in their infinite wisdom, has their Logitech Control Center 3.0 installer recognize and defeat any attempt at installing on any system other than 10.5. 
&lt;br&gt;&lt;br&gt;
The simple solution is to view the contents of the installer .pkg file (Control-click on it an select Show Package Contents), then navigate to Resources &amp;raquo; Logitech Control Center.mpkg and double click. This launches the installer with no system version test, and re-installs the components in the correct locations. Restart and voilÃ¡ -- mouse recognized!
&lt;br&gt;&lt;br&gt;
[&lt;b&gt;robg adds:&lt;/b&gt; I don't have a Logitech mouse to test this one with.]
</description>
</item>
</channel>
</rss>
