If you're having problems with your network initializing upon startup, this tip might help. This stemmed from my system not initializing my Ethernet on boot and hence not having AppleTalk working. I couldn't print to my Personal Laser Writer 320, so I was fairly motivated to solve this one.
As a test to see if this fix will work for you, log in as root, cd to /System/Library/ and delete or move the "Extensions.mkext" file. Reboot. If your system takes about 6-8 minutes to reboot, and the NetInfo application in /Utilities/ which had never worked before will now come up and give you network information, this fix might work for you.
Read the rest of the article for the steps to take to implement this fix...
If you're fed up with typing username, password and which volume to mount every time you connect to your server, here's an easier way: Using location files.
In earlier versions of Mac OS, it was much easier to create these files, by simply dragging a URL to the desktop from any text editor. In Mac OS X, the only way I've found to do this is with a little help from Internet Explorer.
In the location field in Explorer, type:
Select the text you just typed and drag it to the desktop. You now get a location file with the suffix .afploc. You can also use the IP address instead of domain name. If you want to use the location files in Mac OS 9, you cannot specify the volume to mount as far as I know (correct me if I'm wrong, anyone).
Put your location files in a folder, and put the folder in the dock for easy access.
Normally, when you mount a remote drive over AFP, you are presented with a list of available share points to mount. If you know which one you want, you can save yourself some time by adding it to the URL you give to the "connect to server" panel.
For example: If you want to mount the share point "foobar" from a server at 192.168.168.5, use this
If there are spaces in the name of the mount point, you may need to encode them using %20.
If you have ever wanted to mount volumes from your linux box on your MacIntosh without the aid of an FTP client, then Netatalk is what you have been looking for.
I just discovered that Netatalk is now on Source Forge, and is actively being updated. You can download either a CVS version or the current stable version, as well as a module to control Netatalk from webmin.
The install onto my Linux box file server was quite painless and I was instantly able to mount all my Linux volumes on my OS X desktop (works equally well on OS 9).
Among other things, Netatalk allows OS X to keep the proper file types (with the ability to define custom file types) and I do not have to deal with invisible files from other file transfers from PC's or other Macs. You have the choice of either AppleTalk or AFP over TCP/IP, the latter being quite a bit faster with file transfers and easier to setup.
The modem scripts for Nokia phones (Nokia_IR and Nokia Infrared) supplied with 10.1 don't seem to work (I'm currently on 10.1.3 and this hasn't been corrected yet). However the OS 9 scripts seem to work (I'm on 9.2.2) so I simply replaced the "Nokia Infrared" script in "Library/Modem Scripts" with the one in "System Folder/Extensions/Modem Scripts".
Even though the scripts are marked as the same version, when compared in BBEdit, there are some differences, including one to the modem initialization string.
Although the following is officially a press release, it's not a product announcement, and it's directly related to using OS X, so I've chosen to publish it as a tip. Here's the blurb that Eric Zelenka, Apple's Product Line Manager for Server Software, just mailed out.
Apple is pleased to announce the release of a new document entitled Integrating Mac OS X with Active Directory. This document describes how you can use the information stored in Microsoft's Active Directory to authenticate Macintosh users and provide file services and home directories for them on Mac OS X Server. It is available for immediate download from the Mac OS X Server web site.
Read the rest of the article for a bit more information on OS X and directory services.
After I had ripped most of our CD collection to a spare drive on my Mac, my wife asked the next logical question - "So how can I listen to this down in the living room?" I didn't have a good answer for her until recently. On the advice of a friend, I checked out the Turtle Beach Audiotron.
So what's an Audiotron, you may be asking? The Audiotron is, in a nutshell, a networked MP3 player. The device has no hard drive, no fan, and it's designed to look like a standard piece of audio gear so it will fit right into your existing rack. It includes both analog and TOSlink fiber optic digital outputs. You plug in a 10-base-T cable, a power cord, and then connect the thing to your stereo system. Just like that, your entire MP3 collection is available through your stereo.
How is this related to OS X? Event though Turtle Beach disclaims any Mac support, the Audiotron works just fine with OS X (via a Samba server). After some initial snags, some help from a key web page had our Audiotron up and running without any further difficulties.
Brief editorial aside: I truly think this is the future of home audio, at least in some respects. With the Audiotron installed, we now have a catalog of 2,300+ songs (the machine can handle 30,000+, according to the specs) available at the touch of a few buttons. No more getting up to grab another CD for the player, forgetting where you put the CD you wanted to hear right now, etc. Just thousands of songs, always available as long as my Mac is up and running! I think the Audiotron (and SonicBlue's similar device) are just the tip of the iceberg in this product category.
Read the rest of the article for a summary of the steps required to get an Audiotron working with OS X...
Should anyone want to set up an OS X box for modem routing, than the following script might be of good use. It sets up all necessary services and daemons to get a clean route to ppp0 through the built-in firewall. It is designed as a usual unix daemon loader, hence usage:
[Editor's note: I have neither looked at nor tried this script, so make sure you're comfortable with what it does before you run it. Nothing intended against the author of this particular script; it's just generally good advice!]