I went looking for a quick reference containing all of the known OS X startup, shutdown, and sleep command keys. I couldn't find one, so I put this together after a little research. Most of these are the same under OS 9 and earlier.
Startup Command Keys
Close Open Windows - Shift Start from CD - C Start from OS X - X (some machines) Select Start Up Disk - Option Reset PRAM - Cmd+Option+P+R Start Up in Single User Mode - Cmd+S Start Up in Verbose Mode - Cmd+V Boot into Open Firmware - Cmd+Option+O+F Eject CD at Startup - Hold down Mouse button
Shutdown, Restart and Sleep Keys
Deep Sleep - Cmd+Option+Eject Shutdown, Restart, Sleep Dialog - Control + Eject Shutdown, Restart, Sleep Dialog - Power key on keyboard
[Editor's note: Although many of these have been posted here before in various hints, I thought it might be worthwile to have them all in one article -- thanks to autohag for submitting the nice compilation. If there are any missing that you know of, add them as a comment and I'll revise the original article as necessary.]
The December Developer Tools download and mailing contains AppleScript Studio, previewed earlier this year to great reviews.
This story originally stated that the tools were available for general download by any registered developer (including free online-only developers). Unfortunately, this appears not to be the case. I had followed a link off the VersionTracker page, logged in, saw the tools, and assumed they were being generally distributed. This was an incorrect assumption on my part. At this point, it appears that only those developers who receive the Developer Tools' mailings on CD-ROM have the ability to download the December release which includes the AppleScript Studio.
Quoting Apple: "The December 2001 Mac OS X Developer Tools will be available as a free download or for purchase on CD-ROM from the ADC Member Site during the week of December 10. All ADC Online members will be notified via email when the Tools become available."
I have now found out on two separate occasions that the set user ID bit is very important, even for GUI apps where you might not expect it to be. This is because some GUI apps require to be root in order to get their work done.
I have had problems using both NetInfo Manager and Disk Utility after copying them over from another machine and thus not having their set user ID bit set. In the case of Disk Utility, the situation is worse because there are several executables in the application package, all of which need their set user ID bit to be set in order to get anything done.
The solution to this is use chmod to set the set user ID bit on the executables stored within each package. In fact, you can just to set the set user ID bit for everything in the package. This can be done as follows in the Terminal:
Why would want to clear the Printer and Spool files? If you lose the ability to print in OS X 10.1 and the Classic environments, booting to 9.X.X and printing is not a real solution. But clearing the Printer and Spool files may be a quick way to restore your printing capabilties. To clear the queue and printers:
Open "Print Center" in Applications -> Utilities
Click on the "PrintCenter" menu, then press and hold the option key and select "Quit Print Center". This will bring up a dialog box asking you if you're sure you want to delete your printer and any jobs waiting to be printed. Select "Yes".
Open Print Center again and re-add your printer. I've had this work with Apple, Epson, HP and Lexmark printers.
[Editor's note: I just used this hint to clear a stuck queue on a Brother HL-1270N as well.]
I wanted to restrict other users' access to folders that existed prior to my upgrade to OS X, like the subfolders in my home folder.
Files and folders that were on the hard disk prior to upgrading to OS X are not assigned to a user or group. They take on ownership by whatever user is logged in. Using the Finder: Show Info to change the Privileges does not work. Any user logging in is listed as the owner with rw, r, r privledges. Group is usually "unknown."
To restrict access, you can log in as the user you want to own the files and copy them. Then delete the original. A faster method can be done via Terminal using "chown". You must sudo to use this command:
sudo chown [user shortname] filename
I did this to a folder and, voila, logging in as a different user I couldn't open the folder and got the "do not enter" folder icon.
For neatness' sake, you can also change the group [Editor: chown username:group filename]. The group is usually "Staff", but check out an existing file's privileges first.
I think an option for chown will change all files below "filename" but I haven't tried it. [Editor: use the "-R" option on chown]
Based on a blurb in an email I received, I asked Software Update to check for new software. As expected (thanks to the email!), I saw that the "DVD Player Update" was available. This 15.2mb download "delivers improved performance and stability, as well as support for Blue and White Power Mac G3 and Power Mac G4 systems with PCI-based graphics." [According to the blurb in Software Update panel]
So for all of you who have been using the hacked DVD player on your Blue & White's, check your Software Update!
I won't have a chance to test this until later tonight ... anyone have any feedback on performance yet?
My brother upgraded to 10.1 today. Unfortunately, his non-OS X partitions were all hidden; still, by using GetFileInfo and SetFile, I was able to show and access all the missing partitions.
That is, all the partitions except the one named slash ('/'). While SetFile seemed to work on '/Volumes/\/', I still couldn't access it. After much headache, we found that we could access it in the Terminal or "Go To Folder" by typing '/Volumes/:'. Apparently, the pathname separator character differences between HFS+ and UNIX are to blame...thankfully, not so hard to overcome, at least on the Desktop level.
[Editor's note: Glad you got this one resolved ... I must admit, this is the first I've heard of someone naming their hard drive '/' ... I think I'll be sticking to letters and numbers for my volumes names!]
Someone asked me whether it was possible to change the short username in OS X. I knew it wasn't possible in the Login preferences panel (it's greyed out), but I thought NetInfo Manager should have a way to do this. In looking at the "Users" panel in NetInfo Manager, it seems like it would be a simple matter of changing all references from "oldshortname" to "newshortname". I did not, however wish to try this on my own machine (since it's working well!), so I went digging for some answers.
I found two interesting articles (one, two) on the MacNN forums which seem to describe the process fairly well. The essence of the solution seems to be:
Login as root
Rename the /Users/old_username folder to /Users/new_username
Open NetInfo Manager and click on the lock to allow changes (enter admin password)
Click on the "Users" column, and then edit any reference to "old_username" and replace it with "new_username"
Click on the "Groups" column, and make sure "new_username" is in any of the same groups as "old_username". Wheel, in particular, will be an important group!
Save the changes in NetInfo Manager and quit.
Logout and login as the new 'shortuser' and see if everything works.
Please note that I have not tried this myself! Make sure you have a backup of your important user files before you start, just in case! If you know of a better way to do this, or have actually tried changing your short username, please let us know about it!
Some of you may be familiar with the OS X Guidebook I wrote back in April of this year. This was a 12-page PDF file with some general advice on using OS X, and it proved quite popular -- over 20,000 downloads to date!
Since its release, I've been slowly working on a revised version with more detail and updated information relative to recent OS X updates. I used the four-day break for Thanksgiving to complete the revision. Only it was so 'revised' that I felt it merited a new name. After way too many hours in development, I am pleased to announce the release of:
The Mac OS X Solutions Guidebook - download [1.3mb PDF] **
The Guidebook is now 60+ pages long and covers a number of topics, including general advice, the Finder, the dock, Classic, System Prefs, a few key apps, and a detailed section of UNIX command-line tricks and hints. There are over 100 screenshots to help illustrate various hints, and the entire Guidebook runs over 32,000 words (spellchecking took forever!).
As a reflection of the size and scope of the new Solutions Guidebook, it is being distributed as a shareware project. I'll be using the registration fees to help fund macosxhints in the future. The shareware fee is only $10.00 ($5.00 for students), but if you've made a donation (either monetary or a submitted hint) to support macosxhints, then the Guidebook is free -- consider it my way of saying "Thank You" for the support!
For everyone else, please download the guide and put it to use. If, after you've read it thoroughly and tested the hints and found the Guidebook to be valuable, please pay the shareware fee. Not only will you be helping to support macosxhints (remember, I don't accept advertising), but you'll be getting an incredibly useful book for only $10!
As always, I welcome comments, corrections and criticisms - drop me an email with your thoughts.
** NOTE: If you have trouble with the mac.com download, the Guidebooks is also available via a direct download from macoshxints. If you can't get mac.com to work, try the direct download.
I had somehow managed to create a file which simply defied deletion. I was pretty sure I'd created the file, as it was named "testfile" and was in my Documents folder. I'm not sure what I was testing, but the file was simply locked into place. Everything I tried failed to remove this file -- I made sure it wasn't "locked" in the Finder, I tried putting it in another folder first, and I even tried 'sudo chflags nouchg,noschg testfile' in the Terminal. Still, I couldn't even put the file in the trash, and if I tried to delete it as root, I received "Operation not permitted".
I finally killed it by switching to single-user mode and then changing the flags:
% sudo shutdown now [ends Aqua and enter single-user mode] % su [become root] % chflags nouchg,noschg testfile [change the two flags I thought responsible] % rm testfile [get rid of it!] % exit [end root] % exit [restart Aqua]
This did the trick; the file is now history, and no true restart was required (dropping to single-user from Aqua and then exiting back to Aqua is much faster than two restart cycles) ... my 'uptime' even survived intact :-).
Read the rest of the article if you'd like an explanation as to why this had to be done in single-user mode (thanks to Marc D. for providing the addition insight).