I just noticed that Adaptec has released revised (beta) drivers for the 2906, 2930, 29160, and 39160 SCSI cards. If you've got one of these, head on over to Adaptec's OS X beta page to download the driver. They've also provided an email address for beta feedback: OSXSCSIfeedback@trillium.adaptec.com.
From the editor: Would you like the ability to easily access web sites you set up by name, instead of by number? If so, you'll want to use Virtual Hosts in Apache which will let you do just that. Read the rest of the article for jaccorens' instructions on how to configure it. I have not done this yet on my machine, but intend to ... someday when I get some free time!
[Editor's note: .htaccess is a means of placing password protection on web sites, and pages within sites. digidoodle had been trying to get it working for each user's individual site on Mac OS X ... here's what he discovered]
I just submitted a question that has been nagging me for days about how to get .htaccess files working, and I just figured out the very simple answer.
I had been spending all my time messing with the setting in the main httpd.conf file, and then realized that in the private/etc/httpd/users directory is a small config file for each user.
This is the file where the following change needs to be made:
AllowOverride none changes to AllowOverride AuthConfig
Every other source I found on the web talked about altering httpd.conf, but changes to this will not effect the pages within any particular user folder. Hope this helps somebody else!
[Editor's note: See the comments for a better solution, as well as a GUI-based way of doing this]
Sometimes the desktop will do something stupid - like leave some of the 'poof' effect on the screen or whatever else. The best thing to do is just restart it. Killing it will make it automatically restart. Here's a little unix script to find it's process ID & kill it:
#!/bin/sh DOCKPID=`ps aucx| grep Dock | grep -v Server | cut -d ' ' -f 4-5` kill $DOCKPID
Type this script in your favorite editor (command line or GUI), save it (as PLAINTEXT) to a file, say Desktop/dock.restart. Then, make it executable by doing this in a terminal:
chmod +x dock.restart
Then, double click it in the finder. It'll ask you to choose an application to use to run it. Select Terminal as the program to run it. You'll probably have to make it show you all applications in order for that to be selectable.
After that, just double click it whenever the dock is being stupid!!
NetInfo can occasionally get cranky, especially if you have been mucking around with it. If you have hosed your netinfo database you can force the machine to rebuild it.
In single-user mode (boot while holding down command-S, or see the tip here on how to quit into single-user mode), remove /var/db/local.nidb, which is your local netinfo database. Also remove /var/db/.AppleSetupDone, then reboot. You will see a registration page again and can create a new admin account and go from there. Be careful to remap your privileges if necessary.
Also, if you are having problems with the database, but don't want to trash the whole thing, you can just remove /var/db/.AppleSetupDone and reboot. Go through the registration and create a new account with a DIFFERENT name than any you already have. This doesn't recreate the database, it just adds a new admin user to it.
With the release of mail.app and OS X, Apple switched the mac.com email server from POP to IMAP. For most users, the change won't have a dramatic impact. However, there's a key difference between IMAP and POP. With POP, you retrieve your messages from the server, and (unless you tell it otherwise) they're deleted from the server. IMAP basically functions the other way around - when you're looking at your email in mail.app, you're actually looking at the IMAP server (those who know IMAP better than I can probably give a better description of the actual process). mail.app won't download and remove your mac.com mail unless you actually (a) delete it, or (b) move it to another mailbox. This has led some users hitting mac.com disk limits due to a large amount of email kept on the server.
If you'd like a simple method to prevent this from happening, read the rest of the article. This solution was distributed by Ron C. to the X4U mailing list.
If you don't want Classic to ever start up, Brian M. sent in an easy solution - simply move (in case you want it later) the file /System/Library/CoreServices/Classic Startup.app to a new location. From the terminal, you'd just do
[Replace [space] with an actual space character, and enter as one command].
Paul C. had another idea which may also work, and would put a dialog onscreen each time Classic tried to launch:
You should be able to do this by removing "Classic Support" and "Classic Support UI" from the 9.1 System Folder. You'll get asked when Classic is about to start whether you want to install certain items that Classic needs; I think if you answer "no", then Classic won't start up.
Either of these methods should prevent Classic from launching.
Noticed this one posted on one of the MacFixit forums tonight.
You can force the dock to only resize to non-interpolated icon sizes by simply holding down the option key while you drag on the vertical bar. You'll only see the "native" dock sizes; all interpolated icon sizes are skipped.