Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

10.5: Restore from unsupported Time Machine backups Install
There are several hints here on how to get Time Machine to backup to an unsupported AFP share, but I found no mention of how to restore from such an unsupported share. After spending some time on Gooogle, I found this page.

The essence of the solution is that once the installer has booted from the DVD, one has to go to the Terminal and mount the AFP share manually:
$ mkdir /Volumes/TimeMachine
$ mount -t afp afp://user:password@afpserver.local/ShareName /Volumes/TimeMachine
Quit Terminal, then enter the Time Machine Restore utility. The unsupported backup volume should then show up.
  Post a comment  •  Comments (4)  
  • Currently 2.67 / 5
  You rated: 1 / 5 (9 votes cast)
[22,050 views]  View Printable Version
Install some programs without using installers Install
You may wish that all apps used the simple "drag and drop" installation, instead of Apple's installer. As it turns out, a lot of them use installers when they don't even need to -- see this hint on installing Microsoft's Remote Desktop via drag-and-drop, for instance.

There are lots of others that use package installers, and then ask for admin privileges, when they don't really need to. If you're concerned that they could be running daemons or background processes that make your computer slower, or put files where you don't want them to go, here's a manual-install method to try instead:
  1. Control-click on the package in Finder and select Show Package Contents from the pop-up menu.
  2. Navigate into Contents, where you may see more package installers, or you may see an Archive.pax.gz file.
    • If you see the pax.gz file, double-click on it to decompress it and you'll find your .app file inside.
    • If you don't see the pax.gz file, you probably see other packages, so you'll have to repeat the first step and dig deeper.
  3. Drag and drop your app wherever you want to install it.
Of course, this process won't work for every program, but you may be surprised by how many it does work for!

[robg adds: I wouldn't recommend this process as a general rule; some of the parts that you bypass may be required for the app to function properly.]
  Post a comment  •  Comments (3)  
  • Currently 1.75 / 5
  You rated: 1 / 5 (8 votes cast)
[16,097 views]  View Printable Version
Install Remote Desktop Connection 2 via drag-and-drop Install
If you need to install Microsoft Remote Desktop Connection 2 for the Mac, the disk image that comes from contains an mpkg installer, not an application. To use it, you have to run the installer with root privileges in order to install the simple Remote Desktop Client application, not to mention the installer also comes with Office2008_en_autoupdate, Office2008_en_errorreporting, and Office2008_en_helpviewer.

I really don't want to run the installer, I just want to install the application in the OS X way, via a simple drag and drop, and without the extra programs.

Well I found out I can Control-click on the Remote Desktop Connection.mpg, choose Show Package Contents from the pop-up menu, and navigate into the Contents » Packages folder. In that folder, Control-click on the Remote Desktop Connection.pkg file, and again choose Show Package Contents from the pop-up menu. Finally, browse into the Contents folder and copy the Archive.pax.gz file to your desktop. Double-click on that file to extract its contents, and you will get Remote Desktop Now just drag and drop that file to the folder where you'd like it to reside, and you're done.
  Post a comment  •  Comments (6)  
  • Currently 1.88 / 5
  You rated: 1 / 5 (8 votes cast)
[14,495 views]  View Printable Version
10.5: Use Apple Remote Desktop for OS X Server install Install
You can use Apple Remote Desktop to connect to a machine that is booted from the O X 10.5 server installation disk by typing the first eight characters of the computer's serial number into the password field while leaving the user name field blank.

[robg adds: I haven't tested this one, and I don't know if it works with the Client installation disk as well.]
  Post a comment  •  Comments (7)  
  • Currently 2.83 / 5
  You rated: 4 / 5 (12 votes cast)
[34,685 views]  View Printable Version
Completely uninstall PhoneView Install
The procedure outlined on Ecamm Network's website for uninstalling PhoneView is not necessarily complete. The Ecamm website indicates "to uninstall PhoneView, simply drag the PhoneView icon to the Trash icon on your dock." However, by default PhoneView will enable an option in its preferences to "launch PhoneView when iPhone is Attached." The effect of this option is to create an entry in the Login Items tab, which can be found in Accounts section of System Preferences.

If you just trash PhoneView, the entry in the Login Items tab is NOT removed. Unfortunately, that means that every time you login from now on, the will run. The best way to avoid this situation is to be sure to uncheck the box 'Launch PhoneView when iPhone is Attached' in PhoneView's preferences before trashing PhoneView

If you happen to delete PhoneView without unchecking the box, then you can cleanup in one of two ways:
  1. Re-download PhoneView from Ecamm's website, uncheck the offending preference, and then trash PhoneView
  2. Go to the Accounts section in System Preferences and manually remove PhoneViewHelper from the Login Items tab. (Note that you must remove it by using the minus button, not by simply unchecking it, which only hides it but does not remove it).
Also, to completely clean up after removing PhoneView, you might want to run the following in Terminal:
$ rm ~/Library/Preferences/com.ecamm.PhoneView.plist
$ rmdir ~/Library/Application Support/PhoneView
$ rm -rf /private/var/folders/eR/eRBksv+RGmS05uQjre+8GE+++TQ/-Caches-/com.ecamm.PhoneView
Finally, using your favorite text editor, remove the PhoneView entry from the file PreferenceSync.xml found here: ~/Library » Application Support » PreferenceSync.
  Post a comment  •  Comments (0)  
  • Currently 2.13 / 5
  You rated: 1 / 5 (8 votes cast)
[14,583 views]  View Printable Version
Remove every trace of a program by reinstalling it Install
Since almost every program installs files in many different places, it can be nearly impossible to completely remove an installed application. But with Leopard's new fsevents service, which tracks all write activity to the hard drive, a user can find out where all the miscellaneous files are, thus allowing them to be removed manually.

To do this, first install fseventer, run it, and turn it on (press the Play button). Then reinstall the program you wish to remove. You'll see the tree diagram in fseventer populated with every file that's been changed. Next, open the program you just installed (since many programs create their preference files upon first launch). Then stop (press the Pause button) fseventer. Now you can follow the paths to the files and delete each of them manually for a complete uninstall. If you need to get to files in folders which Finder hides, you can choose Go » Go to Folder in the Finder.

NOTE: Be smart about choosing which files to remove, because fseventer will record all file activity that occurs while it is recording. So if any other programs or services write to the disk during that time (which is likely), those files will also show up in the fseventer tree. You will only want to remove the files which make sense to be associated with the program you would like to uninstall.

[robg adds: fsevents was added in 10.4 to support Spotlight; I believe it was modified in 10.5 to help Time Machine do its job. fseventer will run on either 10.4 or 10.5, so this hint should work in either of those versions.]
  Post a comment  •  Comments (16)  
  • Currently 1.63 / 5
  You rated: 1 / 5 (8 votes cast)
[17,307 views]  View Printable Version
A quick uninstall tip for Quicksilver-AppZapper users Install
You can directly drag an application from the Quicksilver pane onto the AppZapper window to uninstall the program. This is easier than opening the Applications folder and then dragging and dropping over to AppZapper (or any such similar program).
  Post a comment  •  Comments (6)  
  • Currently 1.29 / 5
  You rated: 2 / 5 (7 votes cast)
[12,718 views]  View Printable Version
Install Windows XP in Boot Camp on multi-partition Macs Install
When you try to install Windows XP for Boot Camp using Boot Camp Assistant, you are required to have a single partition to start out with. For those who already have partitioned their disks manually, this is truly inconvenient.

If you already have partitioned your hard drive, you need a manual installation method. Many of the installations with only one or two Mac OS partitions (in addition to Boot Camp) can be done by simply starting up the Mac with the XP installer disc and installing into the C: drive that it recognizes. (You will have to make sure the FAT partition is less than 30G, and that you do a Quick Reformat into FAT before install into C:). However, due to XP limitations, if you have more than two Mac OS partitions in addition to the Boot Camp partition (ie more than three partitions total), XP cannot handle it, as XP can only detect up to three partitions. If you try, it will force you to reformat the entire drive (including the MacOS portion) to NTFS ... and that is not good.

The way to get around this three-partition limitation in the XP installer is to trick it into thinking that the Mac OS parititions do not exist. For this, I found that if you use iPartition v3, you can make your Mac OS partitions "vanish." Launch the program, and in the partition inspector, uncheck the 'Viewable by Windows' box for all of the Mac OS partitions. Now when you boot up using the Windows XP installer, it will only see the partitions that were formatted in FAT (under 30Gb please!), and will lump all the other Mac OS partitions together as "unrecognized disk space" and ignore them.

This way you can have four separate Mac OS partitions (I have System, Applications, User, and EFI header -- which is created for all IntelMacs) and the Boot Camp (FAT) partition, and you can still install XP manually. Once you conclude installation, one step that I didn't see in other hints that stumped me (mainly because it's the RTFM issue, and was my fault) was that you can get all the hardware drivers installed by simply inserting your Mac OS Leopard installer disc after rebooting into Windows XP. This will activate all the Ethernet ports, wireless, display, sound card, etc.
  Post a comment  •  Comments (3)  
  • Currently 2.40 / 5
  You rated: 3 / 5 (10 votes cast)
[48,993 views]  View Printable Version
One way to avoid keeping DMG files after installation Install
I often find my downloads directory filling with disk images I've downloaded off the internet, installed, and forgotten to delete after unmounting (and possibly rebooting). I'm not sure this qualifies as a hint, but I find the following trick effective to avoid the problem:

While you can't mount an image from the trash using the Finder, you can trash an image once it is already mounted. I won't go into the technical details of why this is true, but the system has no problem keeping track of the actual image's location. So after you open an image to mount it, you can immediately trash it. You can then install and unmount (or reboot) like normal, and forget about the image file altogether, since it's already trashed.

As an alternative, you can mount an image from the trash from the command line. For example:
open ~/.Trash/MyTrashedImage.dmg
And although the Finder will not empty the image from the trash while it is mounted, you can use the command line to remove the image file altogether after it's mounted, bypassing the trash altogether:
rm ~/Downloads/MyMountedImage.dmg
If the image is actually a sparsebundle, this technique should probably be avoided (some will probably work, some will definitely not, and some might have problems if you empty the trash). However, .dmg installers downloaded off the internet should be fine. However, as with any use of rm, be careful what you delete, and make sure you have a current backup!
  Post a comment  •  Comments (7)  
  • Currently 2.57 / 5
  You rated: 4 / 5 (7 votes cast)
[13,614 views]  View Printable Version
10.5: Install 10.5 on an unsupported PowerPC iMac Install
There are two parts to this solution; the first part covers installing Leopard on an unsupported 700mhz G4 iMac, and the second part fixes the sleep issues with the graphics drivers.

Part One: Installation using the DVD installation disk. The instructions below pretend that the iMac is an 867Mhz model. The change is temporary; after reboot the settings are lost.
  1. Insert installation DVD
  2. Reboot
  3. Hold down Command-Option-O-F to boot into open firmware
  4. At the prompt (>), type the following (note that the 0 below is a zero)
    dev /cpus/PowerPC,G4@0 
    d# 867000000 encode-int " clock-frequency" property 
    boot cd:,:tbxi 
  5. After the install disk has booted, you must load Terminal from the menu and enter the following:
    pmset -a displaysleep 0 halfdim 0 sleep 0 disksleep 0 force
    To verify your changes, type pmset -g. If this is not done, the install will freeze when the display or system tries to sleep during the install.
  6. After installation, go to the Energy Saver System Preferences panel, and set the machine to never sleep.
Read on for the sleep issue solution...
read more (126 words)   Post a comment  •  Comments (6)  
  • Currently 1.78 / 5
  You rated: 2 / 5 (9 votes cast)
[32,841 views]  View Printable Version