If, like me, you have loads of mp3's, or .sit(s) .bin(s) all downloaded into one folder, or several diferent folders, you can throw them all together in one clean move without having to find them all and drag them painstakingly one at a time.
Just open up your destination folder, open Sherlock and search for their common property (ie their name or .sit suffix). Select them all and drag them into the desitination folder. You can then, if you need to, delete all your partially downloaded mp3's by opening the folder in list view, select size to arrange and delete ...etc.
[Editor's note: Not specific to OS X, of course, but a good organization speed-up tip in general]
Over on Macintouch's Mac OS X Reader Reports (well worth reading, as there's a ton of good info collected there!), Paul Christensen posted some information he received from Apple's tech support group regarding the initial setup assistant (which configures your primary user account, among other things).
According to Apple, to re-run the assistant, you need to:
Boot into single-user mode (command-S during startup)
Once the command-line prompt appears, type the following:
mount -uw / cd /private/var/db/netinfo mv local.nidb local.old rm ../.AppleSetupDone exit
When you hit RETURN after typing exit, OS X will restart and the setup assistant will launch automatically. So if you've somehow messed up your primary OS X user, this is a good fix that may get you up and running again, even if re-running the OS X installer does not.
The Speech Recognition system in OS X seems to work MUCH more accurately when external speakers are powered down - if you are finding it somewhat frustrating to constantly repeat yourself, try turning off any external speakers you have - it made a world of difference for me.
Hopefully this is one of the bugs Mr. Jobs said were being fixed with the .1 update.
Telstra, the ex-government telecommunications monopoly down under, has 100% of the ADSL market in Australia and is the leading cable supplier.
They are exceedingly ignorant about all things MacOS especially Mac OS X. The following non-Telstra FAQ has information about connecting MacOS X to Telstra ADSL, and has links to a freeware non-classic client for Telstra Cable (a boon for Australian OS X users)
I'm an instructor at a small technical college and the only Mac user in my department. Our network is heavy on Windows, as expected, with some UNIX. Our Graphic Design department uses Macs, of course.
Anyway, our printers are HP LaserJets shared over the network. They support all types of connections, including Appletalk and TCP/IP. Under OS X, the HP PPDs are only available using LPR (TCP/IP) printing and I couldn't seem to get that working. I had to use Appletalk instead which only allowed me to print Postscript. (I try to print text, as from BBedit and get an error message.)
Just this afternoon, however, I figured out how to connect to the printers using TCP/IP so I now have full use of the HP PPDs.
From the Print Center, select Add Printer and from the connection type pulldown list choose LPR Printers using IP. Enter the IP address (or IP printer name if it's registered) and uncheck the Use Default Queue on Server box. In the queue name field, enter in the name that you want to use for that printer. (Try not to use spaces. Use underscores instead.) Select the printer type from the pick list and click on Add. The printer will appear in your printer list and be ready to go.
My problem was that I was trying to use the default queue rather than setting up my own queue name. (Ironically, this came to me while teaching a group of students how to set up LPR printing in Windows.)
This has become a major area of frustration for me. Specifically, I'm trying to get the command line version of setiathome to kick off on startup (and automatically if it goes down). In the past, I've had no problems with getting the Rhapsody version of seti@home running in a cron job, but that was before MacOS X as we know it came along. To make a long story short, I have tried every variation of users' crontabs to get this line in the cron execution pipe, and nothing seems to want to kick the process off. I have even resorted to Cronnix (excellent app) to get the job done. The line as it appears in my various crontabs:
0 * * * * cd [path to my seti dir here];[space] ./setiathome -nice 19 > /dev/console 2> /dev/console
[Editor's note: Line break inserted for readability; it's really one line, and replace '[space]' with a true space character.]
I'm on the verge of giving up, but postings on this site have given me hope (someone is making this command work).
Perhaps I'm missing something really obvious, but in any case, I need help. How do you make a cron job kick off? What am I missing -- or misunderstanding? Links to a good Cron or MacOS X (or FreeBSD) UNIX tutorial?
Apple has quietly released the OS 9.2.1 update. It's available now on the Mac OS X home page - look for the "Classic Update" link on the right-hand side of the page. It's an 82mb file, and both one-piece and multi-part downloads are available. It does not show up (yet?) on Software Update.
Important: From the online Read Me file:
"You can install this version of Mac OS 9.2 on any of the following computers: Power Mac G4, Power Macintosh G3, PowerBook G4, PowerBook G3 (except the original PowerBook G3), iMac, and iBook."
In other words, OS 9.2.1 can only be installed on machines that are capable of supporting OS X. The Read Me contains no information detailing what's been changed, other than offering "improved Classic compatability."
A few days ago I noticed a small problem with my OS X installation on my Beige G3 266 desktop... iTunes simply will not launch!
I don't know if anyone else has had a problem with their applications not launching, but I've tried a few remedies. I trashed all iTunes preferences, gotten rid of the "Music Library File" and reinstalled iTunes from scratch. All to no avail.
I have compared permissions to other OS X machines and those and everything else seems to be identical. Thus it seems to be some sort of problem besides iTunes.
Anyway, has anyone else had issues with any applications not launching? The specific symptom is that the dock icon will bounce once and then cease to do anything.