Prior to the release of 10.1, my G4 with an Adaptec card would not sleep at all. It was greyed out in both the Energy Saver and the Apple menu. With 10.1, though, it's now possible (although this is still not the 'deep' sleep of a non-Adaptec machine).
Sometimes though, especially if the machine has been sleeping a long time (overnight), when I return and try moving the mouse or hitting the keyboard to wake the machine up, nothing happens. The first time this happened, I thouhgt I'd crashed so I went and pressed the power button on the front of the machine. I didn't hold it in long enough, though, so I was about to press it again when I saw the screen come back to life.
So if you have an apparently dead sleeping machine, try touching (briefly) the power button and see if it awakens your machine. This has worked for me every time I've used it, and it also worked on a friend's G4 (also with an Adaptec card). It seems that sleep mode puts our USB keyboards and mice so far into sleep that they aren't even listening for activity. The power button, though, gets the machine's attention.
This fix may not work for everyone who's having wake from sleep issues, but it's at least worth a try.
The trashcan icon in the dock (but not on the desktop, if you've implemented that hack) has many different faces, depending on what's being dropped on it. I was quite familiar with the standard "trash" function, of course ... and I'd gotten used to the Eject symbol when a removable drive was dragged onto the trash. But the Burn symbol and the scissors were new to me.
You see the burn symbol when you drag a recordable disc onto the trash (I guess I use the contextual menus too much, as I'd never seen it!). A dialog then pops-up asking if you'd like to cancel, burn, or eject. The scissors were pointed out in an email on the Omnigroup's OS X Talk mailing list. You get the scissors when you drag an icon from the Finder toolbar to the trashcan, I suppose to represent you cutting the icon from the toolbar.
Any more trashcan states that haven't been identified here?
VERY IMPORTANT NOTE: I've broken this onto SEVERAL lines to keep the story narrow enough to read! Do NOT copy and paste the entire section. Replace the '[space]' words with an actual space character, and enter this on one line. There are ONLY two spaces in the entire string after "cp", as shown above.
Apple included an Open Firmware Password application on the MacOS X 10.1 CD, which allows you to prevent you Mac from being booted from another volume, so people cannot bypass the authorizations defined on your drive. If you want to use this application, you will have to read this macfixit report and also this Tech Info article from Apple.
People who are using non-US keyboards should be aware that MacOS X will use your currently active keyboard (in the keyboard menu) to set the password. However, Open Firmware does not, because keyboard mapping is loaded much later in the boot process. As a consequence, your password will probably not be recognized by Open Firmware at boot time. To work around this, you can use directly Open Firmware to set your password, or you can select the US keyboard from the keyboard menu before setting your password in the Open Firmware Password application.
NOTE:SecureMac revealed a security hole in the password protection.
I found this interesting discussion on the MacNN forums talking about a Netinfo security hole and the root account.
When you have the Terminal in the recent applications menu, and Netinfo Manager in the foreground, launch the Terminal (from the Recent Items Apple menu) and you will be logged in as the root user. The person who posted said that he didn't even have the root password enabled.
I tried this (I do have the root password enabled) in 10.1 (5G64) and the same thing happened.
[Editor's addition: The MacNN forums go on to pinpoint the cause (Netinfo Manager essentially runs as root while it's running) as well as a workaround - disable excecute permissions for those who aren't members of the Admin group. However, exactly HOW to do this is not listed. You should be able to do this in the terminal:
This removes the execute bit for "others", leaving it for "user" (root) and "group" (admin, which your normal user is a part of). I switched mine, and my admin user continues to be able to use NetInfo Manager, but I don't have a non-admin user to test with at the moment.]
A while back, I published an article titled Retaining OmniWeb as the default browser. This hack has changed a bit with the release of 10.1, and I thought I'd add information on how to make other browsers appear in the "Web" pop-up portion of the Internet preferences panel, and to set any one of them as the default.
The article might also be of interest if your "Web" setting seems to have amnesia - you change it, but then it randomly changes back to IE. I'll explain how to eliminate all choices except for your favorite, which (at least for me so far!) seems to prevent the "IE amnesia" from recurring.
So if you'd like to see more browser choices in your Web pop-up, or just prevent the Web pane from forgetting your preferred choice, read the rest of this article.
Last night I decided to upgrade my "experimental" partition from 10.0.4 to 10.1. This is where I test things on OS X before committing them to my production box. As part of the process, I decided to split the drive into a few partitions, as I had a lot of unutilized space. So I ran Disk Utility, partitioned, installed 10.0, upgraded to 10.1, configured a bunch of stuff, and then booted back to my production 10.1 environment. When I went to select my standard Classic partition, this is what I saw:
There were two problems here. The first was that everything was greyed out, the second was that my normal Classic partition didn't even show up! They grey-out problem didn't surprise me, as none of the listed volumes have OS 9 installations. But there were at least three other partitions that did, and they were nowhere to be seen.
Things I tried to fix the problem included copying a 'good' OS 9 to the missing partition (no change); specifying the OS 9 partition as the Startup Disk (as it was visible there), then checking Classic again (no change); and booting on the missing partition and then restarting in 10.1 (no change). Finally I gave up and did a clean install of OS 9.1 and 9.2.1 on the missing partition. Restarted in X and ... no change! Argh!
To save everyone else a ton of time, you may not have to do what I did. At least in my case, the problem seems to have been caused by a bug in the Classic prefs panel, not any issue with Classic itself or my partitions. If you have more than a few partitions (I have about ten total across three drives), the Classic panel in System Prefs doesn't seem to display scroll bars or arrows ... and it didn't seem to respond to the arrow keys, either. After some random clicking in the box and moving my scroll wheel and hitting the arrow keys, I managed to get the box to scroll ... and found the "missing" Classic partitions off the bottom of the display area!
So if you think you've lost a bootable Classic from the Classic prefs panel and you have a large number of partitions, make sure it's not a scrolling problem before investing time in a more complex solution! I'll try to investigate a bit more over the weekend to see if I can figure out exactly when it will and will not scroll ... and I've filed a bug report with Apple :-).
While logging in this morning after doing some work on another drive, I happened to notice that the Finder's keyboard navigation works in the login dialog box. If you have multiple users, just hit the first letter of the user's name, and that user will be highlighted. Hit enter, type the password, enter again, and you're logged in. No mouse required!
If you'd like to put your Mac to sleep while sitting at the login screen, there's a way to do it ... at least, there is if you have an eject key on your keyboard. Control-eject will bring up a "restart, sleep, or shutdown" dialog box, even while logged out. So just log out and then hit control-eject, and you can put your machine to sleep.
It also works, of course, while logged in. I'm not sure of any workarounds for non-eject-key keyboards. Anyone?