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

Use Siri to find movies with two specific actors Apps

Sure, IMDb’s advanced search tools can you help find occasions when two disparate actors appeared in the same film. But navigating IMDb when you want to play offshoots of Six Degrees of Kevin Bacon is no fun. If you have a Siri-capable iOS device within reach, you can find movie star overlap using only your voice.

Give Siri an instruction like, “Show me movies with Jason Biggs and Woody Allen,” and the virtual assistant should suggest Anything Else a moment later. And in cases of overlap—“What movies have both Susan Sarandon and Tim Curry”—Siri provides a list of all the matching films. (In that case, it’s both Rugrats in Paris and The Rocky Horror Picture Show.)

Tap on a matching movie to see more information about the film.

  Post a comment  •  Comments (2)  
  • Currently 3.44 / 5
  You rated: 2 / 5 (9 votes cast)
 
[5,390 views] Email Article To a Friend View Printable Version
Adjust All My Files criteria from the Finder Apps

We’ve previously shared a Terminal-based approach for customizing the behavior of All My Files in the Finder. But in Mountain Lion, customizing All My Files’s search criteria—or the criteria of any other similar Finder sidebar entry, is deliciously simple:

Simply right-click (or Control-click, or two-finger click with a trackpad) on the sidebar entry, and choose Show Search Criteria. You’ll see the Smart Search characteristics that power the entry in question, and you can tweak and re-save the search factors you prefer.

Full disclosure: You can’t save over the existing All My Files saved search with this approach; you’re really just saving a new search instead. But it’s quick, painless, and non-destructive.

  Post a comment  •  Comments (4)  
  • Currently 2.67 / 5
  You rated: 2 / 5 (6 votes cast)
 
[10,838 views] Email Article To a Friend View Printable Version
No Hints till Monday Apps
It's the Fourth of July everywhere, and that means it's Independence Day in the U.S. We'll have new hints on Monday.

And of course, as always, we'd love your hint submissions! Send them in, and we'll make you famous. At least here at Mac OS X Hints!
  Post a comment  •  Comments (1)  
  • Currently 3.50 / 5
  You rated: 4 / 5 (6 votes cast)
 
[6,356 views] Email Article To a Friend View Printable Version
Animate still photos in the Finder Apps
Suppose you have a folder full of photos taken in rapid succession. These might be images from an MRI or ultrasound, or simply a sequence of shots snapped at a celebration of some sort. Either way, you've ended up with a series of photos that would likely look good animated—but they're all simply stills.

There's an easy way to put those photos in motion. Single-click on the first one in your folder, and then press the Spacebar to bring up the Quick Look preview of your image. Now, simply hold the down arrow. The Finder selection will cycle through all the photos in your folder, and the Quick Look preview will instantly update in real time.

If your folder contains photos that work as a flip book, you can see the animation right there in the Finder using this method.
  Post a comment  •  Comments (1)  
  • Currently 2.86 / 5
  You rated: 1 / 5 (7 votes cast)
 
[5,739 views] Email Article To a Friend View Printable Version
Checking for Mac App Store system updates from a non-Admin account System 10.8
In OS X 10.8.3 and later, Apple seems to have changed the behavior of the Mac App Store: It will no longer automatically check for System Updates if you are running from an account that does not have administrator privileges.

A simple work-around: Select the Updates tab in the Mac App Store. From the Store menu, select Reload Page (Command-R). The app will now prompt you for an administrator's credentials. Then the app will search and (in my experience) find system updates if any are available. Updates can now also be installed from your non-admin account.

Lex adds: I haven't tested this one.
  Post a comment  •  Comments (2)  
  • Currently 3.67 / 5
  You rated: 3 / 5 (6 votes cast)
 
[7,341 views] Email Article To a Friend View Printable Version
Create an unread badge for a Feedbin Fluid app Apps
Now that Google Reader is dead, it's time to find a replacement news-reading solution. If you, like me, land on Feedbin as your answer, you might not be happy with any of the current Mac apps that can connect to the service. And thus you might—again, like me—choose to set up a single-site browser for Feedbin using Fluid.

In general, Fluid and Feedbin get along fine. I tweaked settings to that I could open any URL within my Feedbin Fluid app, so that I could more easily open links to whatever sites I stumble across using the service. But I missed my "unread articles" badge, which NetNewsWire had long sported in my Dock.

Getting a similar badge back isn't too tough. Launch your Feedbin-specific Fluid app. Then, go to Window -> Userscripts, and the top, default Userscript in the left pane will be for Google Reader. Underneath the Patterns pane at the top right, click on the plus (+) button, and add a new pattern: *feedbin.me*. The same JavaScript already present for figuring out the unread feed count from Google Reader (which uses a regular expression to parse the number from the title tag) will work for Feedbin as well.

Of course, to make the whole thing work, you'll need to enable putting that unread count in the page title, which is a setting available on the Feedbin website's Settings screen.
  Post a comment  •  Comments (2)  
  • Currently 2.40 / 5
  You rated: 1 / 5 (5 votes cast)
 
[6,615 views] Email Article To a Friend View Printable Version
Moving on Site News
Today is my last day running the Mac OS X Hints website. I'd like to thank all of the site's readers, and especially those who have submitted hints, for visiting the site and helping us provide neat hints and tips about OS X.

Lex Friedman of Macworld will be replacing me. I wish him all the best, and hope that Mac OS X Hints continues to be a place where you can find great ways to work more efficiently with your Mac.

If you want to keep up with what I'm doing, visit my website, Kirkville, follow me on Twitter, or check out my articles on Macworld.
  Post a comment  •  Comments (11)  
  • Currently 4.13 / 5
  You rated: 2 / 5 (8 votes cast)
 
[6,425 views] Email Article To a Friend View Printable Version
How to set up a Mac as a PXE boot server, with Debian Live Network
Here is how to set up a Mac, running OS X Client 10.5 or later, as a PXE boot server.  We will configure OS X's built-in DHCP, TFTP, and NFS servers, start the servers, and put the client boot files in place.  (The NFS server may be optional, depending on the operating system we are booting.)

You'll need the Mac, a PXE-capable PC, and an ethernet cable.  Some steps will require being logged in as an administrator on the Mac.

We'll boot Debian Live on the client PC as an example.  We'll show a regular setup with NFS, an alternate setup without NFS, and how to uninstall.
Regular setup (with NFS):
  1. Connect the Mac and the client PC with the ethernet cable.

  2. On the Mac, in System Preferences > Network, click "Ethernet" and enter the following settings:
    Configure IPv4: Manually
    IP Address: 192.168.1.1
    Subnet Mask: 255.255.255.0
    (All others can be left blank)
    
    Note the status may read "Cable Unplugged" at this point, which is ok.

  3. In Terminal, make new directories /srv and /srv/debian-live (we'll be sharing /srv/debian-live over NFS) with the following commands:
    $ sudo mkdir /srv
    $ sudo mkdir /srv/debian-live
    
  4. To create the NFS configuration file, enter the following command:
    $ sudo nano /etc/exports
    
    paste the following text into the editor:
    /srv/debian-live -ro -network 192.168.1.0 -mask 255.255.255.0
    
    and press Control-O to save and Control-X to exit nano.

    This will share /srv/debian-live to the ethernet network as read-only.

    For more information, type man nfsd and man exports in Terminal, and see this hint.

  5. Check the /etc/exports file created in step 4 (no output means ok):
    $ nfsd checkexports
    
    check the status of the NFS server (should say enabled and running):
    $ nfsd status
    
    and check the server's exports list (should show the /srv/debian-live directory):
    $ showmount -e
    
    For more information, see man nfsd and man showmount.

  6. To create the DHCP configuration file, enter the following command:
    $ sudo nano /etc/bootpd.plist
    
    paste the following text into the editor:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
    <dict>
    	<key>dhcp_enabled</key>
    	<string>en0</string>
    	<key>Subnets</key>
    	<array>
    		<dict>
    			<key>name</key>
    			<string>192.168.1</string>
    			<key>net_mask</key>
    			<string>255.255.255.0</string>
    			<key>net_address</key>
    			<string>192.168.1.0</string>
    			<key>net_range</key>
    			<array>
    				<string>192.168.1.2</string>
    				<string>192.168.1.254</string>
    			</array>
    			<key>allocate</key>
    			<true/>
    			<key>dhcp_option_66</key>
    			<string>192.168.1.1</string>
    			<key>dhcp_option_67</key>
    			<data>cHhlbGludXguMAA=</data>
    		</dict>
    	</array>
    </dict>
    </plist>
    


    and press Control-O to save and Control-X to exit nano.

    Notes:

    • If the file /etc/bootpd.plist already exists, turn off Internet Sharing in System Preferences > Sharing.  Then the file will be removed, and you can create it as in this step.

      (Make sure to move /etc/bootpd.plist to the Trash and disable the DHCP server before turning Internet Sharing back on.  See "Uninstall steps" below.)

    • If you are using an ethernet port other than en0 (see System Information or System Profiler for the port name), change the value for the dhcp_enabled key to the port you are using.

    • The data for the dhcp_option_67 key is the bootloader filename "pxelinux.0" (see step 9 below), null terminated and encoded into base64.  This can be generated with the free DHCP Option Code Utility, or by entering the following command in Terminal:
      $ printf %s00 `echo -n pxelinux.0 | xxd -p` | xxd -r -p | openssl base64
      
      (See this discussion thread.)

    • The string for the dhcp_option_66 key is the IP address of the tftp server, i.e. the address of the Mac from step 2.

    • See man bootpd and man tftpd.


  7. Enable the DHCP and TFTP servers with the following commands:
    $ sudo launchctl load -w /System/Library/LaunchDaemons/bootps.plist
    $ sudo launchctl load -w /System/Library/LaunchDaemons/tftp.plist
    
    See man launchd, man launchctl, man launchd.plist, and this article.

  8. Download a Debian Live netboot archive, gnome-desktop or another flavor, from one of the following (choose i386 or amd64 depending on the client PC's architecture):


    Place the .tar.gz file on the Desktop (or anywhere convenient), then double-click it to expand the archive.

  9. Open the folder that is created (with a name like "debian-live-6.0.7-i386-gnome-desktop-net"), open the "tftpboot" subdirectory, select all of the files, and move them to /private/tftpboot.  (This includes the pxelinux.0 file mentioned in step 6, and other boot menu and kernel files.)

    Note that files in /private/tftpboot should be readable by everyone (so they will transfer), but not writeable by everyone (so they can't be modified).  Check permissions with Get Info or ls -l if needed.

  10. Click the Back button to leave the "tftpboot" subdirectory, then open the "debian-live" subdirectory, then select the folder called "live" and move it to /srv/debian-live.  (When Debian Live is booting, it will look for the file /srv/debian-live/live/filesystem.squashfs over NFS, which contains the root filesystem.)

  11. Optionally, test the TFTP server:
    $ tftp localhost
    tftp> get pxelinux.0
    tftp> quit
    $ ls -l pxelinux.0
    
    You should see that a copy of the file pxelinux.0 has been downloaded to the current directory.

  12. Turn on the client PC, and press or hold the key to bring up the boot options (something like F2 or F12; check the documentation for your machine or look for a message onscreen).

  13. Choose to boot from the network (PXE).  The PC receives an IP address from the DHCP server, loads pxelinux from the TFTP server, and displays the Debian Live boot menu.

  14. Choose a boot option, and after the kernel is downloaded, the root filesystem is accessed over NFS, and the operating system is loaded, you'll end up at your graphical desktop or shell prompt of choice!
To uninstall, see "Uninstall steps" below.


Alternate setup (no NFS):

This is a shorter method, because NFS is not required.  Debian Live will download its root filesystem over TFTP.  (However, the largest file that can be downloaded is limited by a bug.)
  1. Follow steps 1, 2, 6, and 7 of the regular setup, and skip steps 3, 4, and 5.

  2. In step 8, choose a smaller archive, like the standard flavor from 6.0.7, or the lxde-desktop flavor from 5.0.10.  (A bug causes some of the larger versions to stall when downloading the root filesystem over TFTP.)  Place the .tar.gz file on the Desktop, then double-click it to expand the archive.

  3. Follow step 9 of the regular setup.

  4. In step 10, instead of moving the folder "live", open it and move the file "filesystem.squashfs" to /private/tftpboot.

  5. Open the file /private/tftpboot/debian-live/i386/boot-screens/live.cfg in TextEdit.  Edit the kernel parameters for the boot menu option you'll be using, replacing the two parameters
    netboot=nfs nfsroot=192.168.1.1:/srv/debian-live
    
    with a single parameter
    fetch=tftp://192.168.1.1/filesystem.squashfs
    
    then save the file and quit TextEdit.

  6. Follow the regular setup steps 11, 12, 13, and 14.  The root filesystem may take some time to download in step 14 (1 to 2 minutes over 100mbps ethernet), but when it finishes, you'll end up booted into Debian Live!
To uninstall, follow steps 1, 3, and 4 under "Uninstall steps", but ignore the /etc/exports file in step 1, and the /srv/debian-live directory in step 4.  Skip steps 2 and 5.


Uninstall steps:
  1. Move the files /etc/bootpd.plist and /etc/exports to the Trash.

  2. Restart the NFS server:
    $ sudo nfsd restart
    
    and check the status of the server (should say enabled, not running):
    $ nfsd status
    
  3. Disable the DHCP and TFTP servers:
    $ sudo launchctl unload -w /System/Library/LaunchDaemons/bootps.plist
    $ sudo launchctl unload -w /System/Library/LaunchDaemons/tftp.plist
    
  4. Move the files and folders from /private/tftpboot and /srv/debian-live to the Trash.

  5. Remove the /srv/debian-live and /srv directories:
    $ sudo rmdir /srv/debian-live
    $ sudo rmdir /srv
    
Lex adds: I haven't tested this one.
  Post a comment  •  Comments (6)  
  • Currently 2.80 / 5
  You rated: 1 / 5 (5 votes cast)
 
[15,713 views] Email Article To a Friend View Printable Version
More easily ignore unwanted calls to your iPhone Phones
You can identify unwanted calls. I still have a land line, but I am forwarding all calls to my iPhone. To identify unwanted calls (new windows, green energy, political adds...), I created a Contact named Don't Answer.

When I answer the phone and it is one of those annoying calls, if the number shows up, I can just use the 'add to existing contact' feature. Of course, this doesn't work if the number is blocked. But, in two weeks, I have a long list of calls that show up as Don't Answer and I can just not answer or choose Decline—there's no guesswork involved.

Lex adds: I do something similar for another reason. I use Google's two-factor authentication, and Google uses a variety of phone numbers to text me my passcode when I log in. So I created a Google entry in my contacts, and add each different number the company texts me from to that contact. That way, instead of ending up with lots of old entries from Google in Messages, there's just one that all their texts get grouped in.

iOS 7, of course, will provide a way to block specific unwanted callers, too. But this hint makes a nice stopgap!
  Post a comment  •  Comments (9)  
  • Currently 2.63 / 5
  You rated: 3 / 5 (8 votes cast)
 
[8,407 views] Email Article To a Friend View Printable Version
Making Juniper Network Connect use Keychain Network
Password managers are a good thing, as they encourage you to maintain strong passwords. Just the sort of thing you’d want if you were opening every port on every computer on your enterprise network. Unfortunately, Juniper doesn’t see it this way. This can be resolved with some crafty scripting.

First, we need a scripting addition called Useable Keychain Scripting. Download it and copy it to /Library/Scripting Additions. You'll need to type your password to do this.

Next, you need to be able to connect to your VPN, so do this, then disconnect. Network Connect should retain the address of your server (e.g. https://vpn.example.com).

Now create a password item for the server (https://vpn.example.com), and grant access to Usable Keychain Scripting. Or not, your call.

Now fire up the script. It will get the address of the server from Network Connect, get your username and password from Keychain Access, and log you in.

Modified from https://github.com/seanfisk/juniper-network-connect-vpn-applescript:
property appName : "Network Connect"

on main()
	tell application "Network Connect"
		if connected then
			sign out
			delay 5
			quit
		else
			tell application "System Events"
				-- Recover the name of the VPN from Network Connect.
			set myAddress to value of combo box 1 of group 2 of tool bar 1 of 
				window appName of application process appName
				set ASTID to AppleScript's text item delimiters
				set AppleScript's text item delimiters to "://"
				-- Get just the server address
				set vpnName to (text items 2 through -1 of myAddress) as text
				set AppleScript's text item delimiters to ASTID
			end tell
			tell application "Usable Keychain Scripting" to tell current keychain
			-- Recover the username and password from the login keychain
				set myPass to password of first internet password 
					whose name contains vpnName
				set myAccount to account of first internet password 
					whose name contains vpnName
			end tell
			connect to vpnName
			delay 5
			tell application "System Events"
			-- enter the account name and password in the dialog box and click 'Sign In"
			set value of text field 1 of group 7 of UI element 1 of scroll area 1 of 
				window appName of application process appName to myAccount of
			set value of text field 1 of group 10 of UI element 1 of scroll area 1
				window appName of application process appName to myPass
			click button "Sign In" of group 14 of UI element 1 of scroll area 1 of 
				window appName of application process appName
			end tell
			-- Could launch an application here if it's scriptable.
			return
		end if
	end tell
end main

main()
Lex adds: I haven't tested this one.
  Post a comment  •  Comments (4)  
  • Currently 2.00 / 5
  You rated: 4 / 5 (5 votes cast)
 
[5,947 views] Email Article To a Friend View Printable Version