Though the option may be gone from the GUI, however, it still exists in the command line version. Rob Griffiths solution is to use the command:

softwareupdate -d

There are a couple problems with this. The first is that the command, as listed in Mr. Griffiths article, doesn’t do anything, at least not when I run it. From what I can tell the command requires the -a flag. So if you want it to actually work, it should look like:

softwareupdate -d -a

This will download everything you don’t already have to a directory that the Software Update app can see (/Library/Updates). Now we’re off to a more promising start.

The other problem with this method is that it doesn’t offer a great deal of things you normally get with the GUI. In particular, as Pierre Igot points out, you don’t get a progress indicator. Which really blows, I agree.

You also don’t get prompted to install the updates once downloading has finished. To that end, I’ve written a little Automator Service. The service, when launched from any Services menu in any app, will prompt you to continue with this confirmation box:

Once you click OK, the download will begin. When the download is complete, the service will copy the new updates to an Updates folder at the top level your home account (~/Updates) for safe keeping.

Once copying has finished, the Software Update app will launch and ask you if you want to install the updates you just downloaded. Just install as normal. Let Software Update do its business.

In the end everything will get installed and you’ll be left with copies of all the updates in your home account for later use, all with only a single download.

While I can’t really offer a progress bar, I like this better than the alternatives. It more closely approximates the old “Install and Keep” Software Update method than having to go and open the Terminal and do all that stuff as individual steps. And it’s almost as user-friendly, being activated from a drop-down menu, just like Software Update usually is.

So here it is. The Software Update Download service:
Software Update Download Service

Download it, unstuff it and put it in ~/Library/Services. You should be able to launch it from the Services menu in any application.

A minor disclaimer: this service has mostly worked well for me, but there was one instance in which it seems to have had troubles. In particular, it seemed to choke on the latest iWork ’09 updates. This may have been a fluke, or it may have had something to do with that particular update. I honestly don’t know. But if you have troubles, let me know in the comments of this article. I’ll do my best to figure out what’s wrong as I’m using this in my own workflow. But consider this a beta at best; it’s been through minimal testing.

Also, you should be able to open the workflow up in Automator and make adjustments to the behavior if you so please. Feel free to do so and let me know about it in the comments.

Enjoy!

Since this is something I do a lot — wrap command-line tools in Automator wrappers, that is — I thought I’d whip up a GUI method for doing this. So here it is.

The OGG Theora converter

It’s a Finder workflow, so download it, unstuff it and put it in:
~/Library/Workflows/Applications/Finder

Placing the workflow there will add the item to the Finder’s right-click contextual menu. To use the workflow, simply right-click a video you want to convert, navigate to More->Automator and choose “Convert To OGG” from the menu.

Ogg Converter Workflow

While this crunches you’ll see a badge in your menubar:

Progress

Wait a few minutes and you’ll see the OGG version appear right alongside your original movie.

Completed OGG File

And remember, you must first install the OGG Theora converter tool, ffmpeg2theora, for all this to work.

I’ve made a droplet-style version of this as well. Place this version anywhere — your Desktop, the Applications folder, your Dock — and when you want to convert a video, simply drag the video onto the droplet.

Enjoy!

UPDATE:
Folks, for those of you having trouble installing the workflow version, here’s a tip, as mentioned in the comments: Double-clicking the unstuffed workflow will open it in Automator. From here you can choose File->Save As Plug-in…

Installing Workflows the Easy Way

Make sure it’s a Plug-in for: Finder, and hit the Save button. It should now show up as an option in the Finder’s contextual menu.

And remember, there is a Droplet Version as well whose installation is drag-and-drop. To anywhere!

Hope that helps!

Also, in reviving the Script Sharing series, I realized that all the old scripts were missing. Seems when I switched ISPs a while back, I forgot to move over the archive. Well, never fear, they’re all back now.

Today’s script is actually an Automator workflow for the Finder. (What sort of workflow designer would I be if I didn’t create the odd Automator workflow every now and again?) This workflow will turn hidden files on and off in the Finder. To enable it, simply unzip the below-linked download and place the resultant file in your Workflows folder (~/Library/Workflows/Applications/Finder).

Toggle Hidden Files

To access it, right-click (or control-click) anywhere in the Finder and navigate to More->Automator in the contextual menu. Select “Toggle-HiddenFiles” and your Finder will restart. When it comes back up, you’ll notice that hidden files are no longer hidden. To reverse the effect, simply repeat the process. Rerunning the script will re-hide invisible files.

So, here’s the script:

Toggle Hidden Files Workflow

Enjoy!

And by golly, that’s just what I did. Here are a few Automator workflows that do, more or less what the afore-linked methods do. To me, the advantage of the Automator approach is that you don’t need to install anything. It’s all baked in. Which means you don’t ever need to update anything either. Nice. Simple. And, yeah, kind of the whole point of Automator.

So here you go. Maybe someone will find this useful, if for nothing other than as an exercise in creating contextual menu functionality with Automator. Or skinning a cat multiple ways. Or something. To use this, download the .zip file, unzip it and place it in:
~/Library/Workflows/Applications/Finder

NewTextFile Workflow

It should become active immediately.

Also, here are a couple variants. One will create a text file, and then open it in TextWrangler (if you have TextWrangler, and if you don’t, go get it now); the other creates a Word document, and opens it in Word. I’m far to lazy to completely duplicate the functionality of NuFile. But if you examine these workflows, you can at least see now how that would be possible (in fact, fairly easy) to accomplish.

NewTextFile Workflow Variants

I actually think it would be great if Apple made it drop dead simple to create true contextual menus for the Finder. Fortunately, Automator gets us pretty close.

Oh, yeah, and since this is technically script writing, and since I haven’t posted to that series in some time, we’re gonna go ahead and call this a Script Sharing post. Deal with it.

Right. Good night.

UPDATE: Revised March 31, 2007, 3:00 PM
Stephan Cleaves has added yet another implementation of this idea. He’s using a combination of Automator and AppleScript. I certainly think his implementation is better than mine in a few ways. Certainly more full-featured. It will prompt for a file name, for instance, and takes pains not to overwrite a preexisting file with the same name. Nice. But we’re taking very different approaches to the same idea (his version places a file in the front-most Finder window, my version places it in the right-clicked folder), and he was confused by my approach. After speaking to him via comments on his blog, I realized that some clarification as to how my workflow is actually constructed might be in order.

Basically, my workflow takes the folder selected in the Finder as input and assigns that input to the variable “$@”. That variable and the for loop in my workflow are automatically generated by Automator when you select “as arguments” from the “Pass input:” field in the “Do Shell Script” action. It’s how you get the context (the selected folder) passed to the script. Apparently Automator takes “$@” as the variable for “the folder you just selected” whenever there’s no input from a previous action. This was something I learned while fiddling around with all of this, and it’s really my favorite part. The coolest thing for me here, really, was figuring out how to pass the context — i.e. the right-clicked folder — to an Automator “Do Shell Script” action. This opens up worlds of potential.

Finally, as I said, the for loop in the action is auto-generated by Automator. The workflow will work almost as well with the simple script:
touch “$@/NewText.txt”

Using the for loop, however, allows you to create a new text file in multiple folders by selecting said folders and running the workflow.

It’s really kind of amazing how many ways there are to do this. Wow. Fun stuff.

After reading this hint I was reminded of a script I wrote a while back based on yet another MacOSXHints hint that uses ditto to create Finder-like .zip archives. So it seemed like a good time to post the script here and add it to the waning ScriptSharing series.

So here it is: my Archive script. It will both archive and expand folders or files using ditto, and it places these archives on the Desktop.

Archiver Script
See the code

This new version comes with the same disclaimers as the other one (which are now listed in the script itself), but gives you a few more options for disabling Spotlight. In particular, you can now choose to disable/enable Spotlight on either a single volume, or an all volumes. The script will also report the Spotlight status of all currently mounted volumes before asking you what you want to do.

Enjoy!

SpotlightEnableDisable Script
See the code

I find the recent upswing in cloning utilities strange. Apple’s bundled Disk Utility application has actually harbored the ability to clone a system disk for some time now (I believe as far back as Panther). And yet, it seems the easier cloning gets, the more apps there are with which to do it. And charge you for it.

Today’s script uses a handy command-line utility that’s actually been around since the Classic Mac OS days (though not, obviously, in command-line form): asr, which stands for Apple Software Restore. The asr command is essentially a command for cloning disks. In fact, that’s exactly what it is. When Mac OS X first came out, asr was not bundled. But in recent incarnations of the OS it’s hung around in the command-line, and it’s actually gotten quite refined and easy to use. Want to clone your boot drive? Here’s the command:

sudo asr -source [source_volume ] -target [target_volume ]

That’s it. I can’t imagine an easier command structure. In a way, it’s almost easier to use than GUI apps that do the same thing. Of course you can get into some very complicated uses of asr, but for basic disk-to-disk cloning it’s drop-dead simple.

Now there is one little, tiny bump in this road. Tiger, you see, has a brand spanking new way of making certain files on your boot drive invisible. You know, files like var and etc and private. And Tiger’s version of asr (as well as Tiger’s Disk Utility program) are none the wiser. So, if you want things set up properly, you need to explicitly set the visibility of these files. There are a few ways to do this. Today’s script will use a utility called SetHidden, which comes on the Tiger install disc (a la this Apple KB article). Just so you know.

So here it is. A very simple script for making an exact clone of a volume to another volume. Please keep in mind, because of the file visibility issue, this script MUST be run from the disc image, or it will not work properly. Also keep in mind that cloning will overwrite, replace or even erase the target drive. I am in no way responsible for any damage you incur to your system with this script. If you don’t feel comfortable using it, please don’t.

That said, here’s your free cloning utility.

Download ASRClone

The linked disc image contains the delayedACK Startup Item, and also includes an installer and an uninstaller for the Startup Item.

Enjoy, you lucky Intel Mac owners (of which, alas, I am not one… Yet…)

UPDATE:
A reader called Nubo recently left this comment:

…turning off delayed_ack is not necessarily something that should be left in the startup items forever. Having it on is normally beneficial or at least not severely degrading in normal environments. So this should be reviewed whenever Apple fixes the underlying problem in its implementation, or the actual root cause is found.

Nubo is absolutely right. This startup item should be removed — either by running the included uninstaller or by simply dragging the startup item to the trash — once the problem has been resolved by Apple.

Thanks, Nubo, for pointing this out.

Download the Delayed ACK Startup Item

Essentially, this script is made to take large files and cut them into smaller (theoretically CD or DVD sized) pieces. The same script can then be used to rejoin these chunks. For splitting, the script uses the split command, and to rejoin files, it uses the cat command.

So here it is in all its glory.

SplitAndRejoinFiles Script
See the code

So here’s another popular favorite: The .DS_Store Remover utility. There seem to be billions upon billions of little apps that do nothing but remove the .DS_Store files that the Mac OS puts in every folder on your system. Maybe there are so many of these little apps because it’s actually such an easy thing to script. The nice thing about the script is, you can see and modify the code very simply and easily, whereas with one of these GUI wrappers, God knows what it’s actually doing.

For those who don’t know, the .DS_Store file holds information about how a given folder should display when it’s opened. It remembers the position, size and view style (i.e. column, list or icon) of the window. Why remove them, you may ask? Some people don’t like them showing up on their windows boxes, apparently. Too messy. Ahh, if only I could write a script to delete Windows boxes. That seems like the better approach.

Anyway, here’s my script version. I call it “DSStoreRemover,” which frankly I think is possibly the most ingenious and creative name for anything ever in the history of humans on planet Earth.

It’s a really, really, drop-dead stupid simple script that takes a folder path as a variable which is used in a find command that then, in turn, executes rm on anything named “.DS_Store.”

See, you don’t need a GUI for this. Hell, you almost don’t need a script.

.DS_StoreRemover Script
See the code