Text Wielder is a "super services" application that includes about 120 different predefined actions. As a brief example, Text Wielder services can search for song lyrics, clean up email formatting, or get a map of a particular city or zip code. And since Text Wielder runs as a service, it's available to all Cocoa apps and a few Carbon apps (hopefully more in the future!).
One of the coolest things, though, is that you can use Text Wielder to write your own services. As an example, read the rest of the article for a step-by-step guide on creating a "Search macosxhints.com" service item for Text Wielder. This guide was contributed by Eric Blenkush, the author of Text Wielder.
If you would rather not create the "search macosxhints.com" service yourself, you can simply download it. Otherwise, read the rest of the article for Eric's great step by step guide...
It is my understanding that when copying files from X to a drive formatted that doesn't have resource forks, a "._filename" file is created that holds the information. While this is apparently very important if you plan to move the file back, sometimes having that file can be in a pain.
On my Kodak MC3 digital camera/MP3 player, when copying files to it's music folder on the compactflash card via the finder, it creates "._filename" files that cause the camera to freeze for long periods of time when it encounters them. I found there was no way to delete them in X. However, after fooling around a bit in the Terminal, I found that using the 'mv' and 'cp' commands will move or copy files to the compactflash card without the ._ files.
And of course, if you don't like the terminal, an applescript studio app could be made relatively simple to copy these files with the cp or mv function, which is what I did to solve my own issue.
[Editor's note: For the newcomers to OS X, it's very important to note that if you wish to retain your resource fork information, you should NOT use this method of copying files from the Terminal! But it can be useful when transferring files to systems that don't understand resource forks.]
After experiencing a hard drive crash of my LaCie external 80 gig Firewire drive today, I can advise on how to avoid this based on what I learned from LaCie tech support:
Don't use the drive out of the box in Mac OS X. It will work and appear to be fine, BUT it is formatted with Silverlining "which is incompatible with OS X".
To prepare the drive first boot from the LaCie CD supplied with the drive and run Silverlining Pro.
Check that the ATA-Firewire bridge firmware is the latest version (currently 3.12; mine was 3.11, which puzzled the tech support as drives should be shipped with the version provided on the CD. Update firmware if needed.
Boot back into X and partition/reformat the drive using the Apple hard drive software supplied with X.
The good news is that Disk Warrior was able to rebuild the volume information on the drive with no loss of infomation and I was able to remount and backup files.
The bad news is that none of this would have occurred if LaCie had included some warnings and instructions with the drive.
The next time you are in Word or TextEdit or even the terminal, look at the close button (red). If there is a small dot in the center it means that the document contains unsaved changes. This happens in the Terminal after you use the inspector to change something, but don't change the main preferences.
[Editor's note: I can't believe this hasn't been published here before, as it's one of the more basic element of OS X. The close widget will display a black dot in any Cocoa appliation document which has unsaved changes ... as noted below, Carbon application support is on an application by application basis.]
I was experiencing a number of problems one morning. Mostly applications not responding. This included the Finder and Terminal. Oddly enough, Classic still worked fine. I became fearful that my whole system was on its way down, so I thought I would try something.
I learned that the shutdown ('sudo shutdown now') command in Mac OS X does not actually bring the system down as it does in certain Linux systems I have used. Rather, it brings the system down to "single user mode." As I understand this, most everything is stopped and the system is in essence stripped down to its bare bones. To verify this, I ran top while in this state, and counted only about four (4) processes running.
Now, I just typed "exit" and the machine exitted from single user mode and the Window Server started back up. If you try this for whatever reason, you may notice that the network and other items are started back up. It seemed to fix my troubles and my system was never taken totally down. This was evident from running uptime from the terminal to see the total running time of the system has been preserved. This is also a much faster fix than a full restart.
I am not a guru in the area of the guts of this system yet, so I can't be sure of what damage I am creating or not really fixing, but so far this seems to be a more favorable fix than a full restart.
[Editor's note: Anyone have any input on the safety of this versus a full reboot into single-user mode? I believe I read somewhere that if you use "shutdown" to get into single-user mode, you should still finish with a reboot and not just an exit back to Aqua, but I can't find the reference now.]
If you need additional USB ports or have a beige G3 or run OS X on an unsupported system using XPostFActo, you can use CompUSA's $15 no-name two-port USB card. On my PowerMac 7600 it worked right out of the box. I was able to print from it to my Epson inkjet printer.
Over in this thread on the macosxhints' forums, '3film' was having problems mounting DMG (disk image) files. Some would mount, some would not. After a bit of troubleshooting, those that would not were those that had the license agreement as part of the disk mounting operation (Mozilla and ASM, for example).
After some fruitless troubleshooting help, '3film' replaced the existing Disk Copy utility by using Pacifist, which allows you to restore portions of an OS X installation. This solved the problem -- apparently the stock version of the program had been damaged somehow, which prevented disk images with software license screens from mounting properly.