Posted: October 19, 2013 Filed under: Software | Tags: Finder, Utilities
The other day I was using my Titanium PowerBook G4 and I needed to perform a series of checks on a couple of folders containing a bunch of old digital photos. I remembered that a few years back I had stumbled on a series of very cool third-party Contextual Menu add-ons but I couldn’t locate them right away or recall their precise names. I turned to the trusty iBook G3/466 and after a bit of digging I was able to find some information, and to find these Contextual Menu add-ons again on the Web. They were all developed by Pixture Studio and the company has made them available on this page.
They are all very useful, and also very light on the system, which is perfect if you still use a vintage iBook or PowerBook. My favourites (and those I needed for the task at hand) are PhotoToolCM and QuickImageCM. Installing these little extensions is quite easy: you download the compressed archive, it extracts into a DMG file, you mount the disk image and there’s a handy AppleScript application that will install the software in the right place for you. Just follow the prompts and you’re good to go in a few seconds. Once the add-ons are installed, and you relaunch the Finder, they’ll appear at the bottom of the contextual menu in the Finder when you right-click or Ctrl-click on an item.
PhotoToolCM adds two entries to the contextual menu, Photo Exif Info and Photo Tool:
As you can see, Photo Exif Info is quite handy: you select the photo you want information about, Ctrl-click on its icon, choose Photo Exif Info and the EXIF data appears right there in a submenu. As far as I know, this is, to this day, still the quickest way to have that amount of EXIF data on the fly. It was incredibly useful for what I needed to do — quickly parse a folder full of photos I didn’t remember much about, either the camera I used to shoot them with, or the date/time. (The information you see in the screenshots is just to show you how the tool works, it’s not related to what I was doing.)
And the Photo Tool menu gives you a series of powerful features you can take advantage of without leaving the Finder. Same goes for QuickImage — take a look:
You can quickly convert an image in a bunch of different formats by selecting Convert to:
(The JPEG command has yet another submenu where you can choose the quality for the JPEG conversion).
In the QuickImage submenu, if you choose View… you’ll get a mini image editor directly in the Finder:
It’s not a full-blown editor, but for basic retouching is surely enough. And you’re still inside the Finder! And did I say the impact on CPU resources is minimal? This window in Activity Monitor on my PowerBook G4 17″ showed 0.2% CPU usage.
These Contextual Menu add-ons only work on PowerPC Macs. On the Pixture website you’ll notice Jaguar, Panther under System Compatibility, but they also work under Tiger and Leopard. (In Leopard, the additional contextual menus are added to the More command at the bottom of the standard Finder contextual menu — you can see that in the screenshots above). These tools do not work on Intel Macs. I hope you’ll find them as useful as I did, and if someone from Pixture Studio is reading this, thank you for creating these great add-ons.
Posted: June 2, 2013 Filed under: Software
The other day I was setting up my blueberry clamshell iBook G3/300 to be a Mac OS 9-only machine, and as I was installing a minimal but complete set of applications and utilities, I thought I could very well add to the mix the last iTunes version compatible with Mac OS 9, iTunes 2.0.4.
Since the version of Mac OS 9.2.2 installed on the iBook is in English, and the copy of the iTunes 2 installer I had at the ready was in Italian, the software wouldn’t install (ah, the not-good old times of non-multilingual system software applications!) — So I figured I could do a quick web search to download the English installer.
Of course, one of the first hits was Apple’s own website, the Support page called iTunes 2.0.4 for Mac OS 9: Information and Download. The problem is that the download link is broken and you land on a blank page. So I searched my archives more thoroughly and found it inside a backup of the old hard drive of my late iMac G3.
I thought it would be nice to make it available for download for other vintage Mac enthusiasts. I know you can probably find it elsewhere on the Web, but at least I’m a trustworthy source, and you know that what you’re downloading is genuine. (This is the same installer I’ve used to install iTunes 2 on my iBook.)
The file is a BIN archive. Once you’ve downloaded it, StuffIt Expander (which you’ll surely have installed on your Mac) will decode the file and extract the Self-Mounting disk Image (iTunes_2.0.4_Installer.smi). Double-click on it and inside you’ll find the VISE iTunes installer. Double-click it and follow the on-screen instructions.
For detailed System Requirements, refer to the aforementioned Apple Support page, but in short, if your Mac has built-in USB and runs Mac OS 9.0.4 at the very least, you’re good to go.
Download iTunes 2.0.4 for Mac OS 9
Posted: May 25, 2013 Filed under: Link, System, Welcome to Macintosh | Tags: Tips
Last week I needed to force my Macintosh Colour Classic to boot from an external SCSI hard drive, and I couldn’t remember the correct keyboard shortcut to hold down at boot. After some research on the Web, I found this useful resource by Charles Poynton. Since many websites with vintage-Mac-related contents in my bookmarks are increasingly suffering from link rot, I decided to ‘reprint’ the table of keyboard shortcuts made available by Poynton. (His page also links to an even more complete shortcut list collected by Dave Polascheck: Magical Macintosh Key Sequences, where you can download a handy PDF.)
The document written by Poynton begins after the line break. I hope you’ll find these resources as useful as I did. Feel free to point out any mistakes in the comment section.
When a Macintosh is powered-up or Restarted (“booted”), various pieces of Mac ROM and System software examine the keyboard, and take special actions if certain keys are held down. This page summarizes the actions.
Booting involves several phases; startup keys take effect at different times depending upon the phase. Sometimes the same key has a different effect depending upon which phase it is sensed. Generally, you should hold the indicated keys down until the desired action takes place.
||Zap PRAM (double boot)
||Force PowerBook to reset the screen
||Reset AppleVision Display (1.5.2 or later)
||Force Quadra AV (only) to use TV as a monitor
||Force Mac Classic (only) to Boot from ROM
||Eject Floppy, then boot from SCSI
||Bypass the device that is selected in the Startup Disk control panel; boot from the first bootable device other than that.
||Boot from a specific SCSI ID, where # is 0
||Boot from internal CD-ROM
(Most late model Macs)
||Boot from network (iMac and later models)
||Boot from the internal hard disk if the default boot device has been set to something else
||Boot from an internal Zip drive
||Access Open Firmware (on G3 and later models)
||Boot into FireWire Target Disk mode (on certain
Upon appearance of the happy face, let go of any boot keys you may have needed, then immediately press any keys you need to control…
Mac OS System startup
||Invoke MacsBug upon startup.
||In Mac OS 9.x, on a startup disk having multiple system folders, invoke dialog to choose System Folder.
||Boot with Virtual Memory off
||Disable all Extensions and Control Panels. Release Shift when the message “Extensions disabled” appears in the welcome box.
||Open extension manager before loading Extensions or Control Panels. Release the Space bar when the Extensions Manager displays its screen.
Holding the Shift key early in the boot sequence disables all Extensions and Control Panels. Individual Extensions and Control Panels may disable themselves upon seeing the Shift key later in the boot sequence, but the timing for this is difficult to achieve! Upon loading, an Extension or Control Panel is supposed to display its icon in the “icon parade.” If the icon is displayed at boot time, but the Extension or Control Panel disables itself because the Shift key is held or some error condition is detected, it is conventional for a red X to be drawn over its icon.
Immediately upon the appearance of the (blank) menu bar, press any keys you need to control …
||Don’t open Finder windows
||Disable “Startup Items”
Lots of Finder shortcuts are documented in the online Finder Help. (p.s. Don’t delete that file: Certain Apple installers refuse to function unless that file is in its proper place.)
|Command-Shift-1 (or 2, or 0)
||Eject a Floppy Disk [FKEYs]
||Force current app to quit.
||Invoke the debugger (if MacsBug is installed)
- G to return to interrupted code
Restart, Sleep, Shutdown
If you have a Power key, it is at the top of your keyboard, at the center or on the right hand side; it carries an incused triangle symbol.
||Present Restart, Sleep, Shutdown dialog – key
R for Restart, S for Sleep, ESC for cancel, or
Return for Shutdown.
||Put late model PowerBooks & Desktops to
||Unconditional, forced reboot (the “three-finger salute”)
This document may be freely distributed for noncommercial purposes, provided that it is distributed unmodified and in its entirety, and that this copyright notice remains intact.
Charles Poynton – Mac
Copyright © 2001-07-15
Posted: May 5, 2013 Filed under: Hardware, System | Tags: Troubleshooting
The least pleasant aspect of collecting a few vintage machines is their maintenance. One of the bits of advice I often give to new vintage Mac enthusiasts is Don’t leave these Macs unused for extended periods of time; try to use them as often as you can. Usually the part that suffers most in a vintage Mac left unused for a long time is the hard drive. Over the years I’ve witnessed my good share of Macs whose hard drives didn’t come out of the long sleep (I call this phenomenon Dead On Reboot). With vintage PowerBooks another source of problems after long periods of neglect is of course the battery — this is especially the case with the Macintosh Portable and the PowerBook 100.
Another rather common problem with vintage compact Macs (from the 128K to the Classic II) are their capacitors on the logic board. With time (and neglect) these components fail and leak on the logic board itself, causing a few issues. I tried to follow my own advice, but since I own a fair number of vintage Macs and there isn’t much space for them where I live, it’s hard to keep them all in their best shape, despite my very good intentions. Having only a small desk devoted to my vintage hardware, I’ve had to resort to some kind of rotation system where, say, I use my Macintosh SE for three weeks, then I put it away and replace it with the Macintosh Classic for another three weeks, then the Colour Classic, etc. As I said, despite my best efforts, two of the compact Macs in my little collection — first the SE/30, now the Macintosh Classic as well — have started presenting the telltale symptoms of capacitor trouble.
Earlier today, after booting my Macintosh Classic, I noticed something weird: the system clock wouldn’t advance. After a bit of Web research, I found this page, Macintosh Classic Logic Board Repair with a few decent images of where the failing capacitors are located. It also has a good summary of the revealing signs of a Mac whose capacitors are starting to fail:
The Mac Classic range of computers often show a variety of symptoms but which have a common cause of failure, for example:
- Low volume or no sound.
- Real time clock not advancing.
- Power up problems with checkers and stripes etc.
- No serial or LocalTalk functionality.
My Mac Classic suffers from the first two symptoms, while the SE/30 is curiously mute only on boot (and sometimes it presents a chequered/striped screen, but restarting the machine usually makes the problem go away, at least for now). In the next days I’ll open up my compact Macs and take a look at their logic boards. The most frustrating thing for me is my lack of skills (and tools) when it comes to soldering/desoldering components. I’ll do my best to clean the logic boards and to perform some damage control. If you find yourself in a similar situation, probably a good place to ask for help/advice are the 68k Macintosh Liberation Army forums. And if you have some logic board cleaning tips to share, you’re welcome to chime in by leaving a comment. Thanks.
Posted: April 22, 2013 Filed under: Hardware, Link, Newton | Tags: Interview
This morning I read on TUAW that “Mike Culbert, a longtime Apple hardware engineer, has passed away after battling cancer. […] His contributions include numerous patents for many iPhone and iPad innovations, we now take for granted. […] He was also a key player on the Newton development team.”
I want to pay my respects by unearthing a 1997 interview that originally appeared in Portable Design Magazine and was published at this link, which now appears to be dead. A few years ago I saved the article after it was briefly discussed on the NewtonTalk list.
Here’s the article, called PDAs: a study in contrasts.
From: Portable Design Magazine
Original link: http://pd.pennnet.com/Articles/Article_Display.cfm?Section=Archives&Subsection=Display&ARTICLE_ID=52439
PDAs: a study in contrasts
Portable Design interviews David Austin, director of engineering, Mike Culbert, systems architect, and Don Porter, mechanical engineer, at the Newton Systems Group (Cupertino, Calif.).
Alex Mendelsohn, Editor-in-Chief
* * *
PD: How did the MessagePad 2000 rise from the ashes of the original Newton?
Culbert: The idea was to design a PDA for the mobile business professional. The 2000 wasn’t envisioned to compete with an organizer, but rather to replace some of the common functions people do with a laptop – and do a better job at it. We looked at the forerunner Newton 110/121/ 130 Series and learned from its mistakes, taking a rototiller to the hardware and software and re-implementing the pieces which weren’t well done the first time around.
PD: How did you come to use the Cirrus Logic (Fremont, Calif.) Voyager chipset instead of the custom silicon used in the original Newton?
Culbert: We wanted a new chipset to expand the level of integration and eliminate jelly-bean parts.
PD: Did it let you make the unit physically smaller?
Culbert: No. But we knew users complained about the lack of PCMCIA slots on the original Newton. Without two slots, they couldn’t use storage and communications PC Cards at the same time.
We were already heading for a larger form factor to accommodate an additional slot. Our concern was how to reduce cost and power while boosting performance. Cirrus was looking for a partner to help it get into the PDA market. Since we needed a chipset, we decided to offer our PDA experience to Cirrus.
PD: Did Cirrus know you were going to use the Digital Semiconductor (Austin, Texas) StrongARM SA-110 processor?
Culbert: None of us knew we were going to use it when we started out. It didn’t exist. We were instrumental in its creation. We had this great architecture from Advanced RISC Machines (ARM – Los Gatos, Calif.), which was suited for Digital’s low-power process. Digital agreed, and we went from there.
That was totally independent of the Voyager chipset. The MessagePad 2000 design was already under way using an ARM710 microprocessor. However, once we had StrongARM silicon in hand, it became clear it was a viable alternative.
Very late in the StrongARM development game we did find a serious bug in the chip’s memory-management unit when handling permission violations. It took us and Digital’s engineers about a week to nail it down. What was astounding was that Digital delivered new silicon in less than four weeks.
PD: You were developing two microprocessor architectures for one end product?
Culbert: Yes, and it was difficult. We had to manage two logic designs in parallel to keep the MessagePad on schedule and to bring the StrongArm into the design without adding risk. At the engineering validation phase, one logic board ran a 25-MHz ARM710 and the other a 162-MHz StrongArm.
PD: That must’ve really complicated software development.
Culbert: It sure did. We had to support concurrent development and ended up building a lot of prototypes. It was an administrative headache to keep these platforms running in parallel and to make sure people had all their development needs met. But, our strategy was to stay on our time-to-market schedule and retain the opportunity to move to what we felt was the appropriate processor. If we couldn’t make it work with the StrongARM, we wouldn’t lose delivering the MessagePad on schedule. But, things did work. The Newton v2.1 operating-system software ran well.
PD: Were there technical aspirins to lessen the headaches?
Culbert: Sure. We were very careful to make all the code dynamic. For the most part, the software engineers on the team didn’t have to know what processor they were writing code for. Low-level software was implemented so that either one of the existing prototypes would function with it.
PD: Did you build in any special hooks to do that?
Culbert: Yes. We made sure the StrongARM and the Voyager included hardwired software-readable version registers. These were incremented on each version of the silicon to dynamically track low-level bug fixes and work-arounds.
For complex bugs it’s handy to observe what’s happening with a logic analyzer. We have a Hewlett-Packard (Loveland, Colo.) Model 16500B for state and timing analysis, but almost never use it during hardware development. I wrote an ARM disassembler for the H-P so we could look at traces of assembly code as it’s fetched. But I often felt that if I couldn’t debug my hardware with my trusty four-channel digital storage ’scope, it couldn’t be debugged!
We also used Geoport – an Apple protocol – for our internal debugging environment. It’s a high-speed protocol that uses SDLC framing at the low level but with a synchronous serial clock. It uses what would normally be hardware handshaking pins for the clock. Geoport let us use production-level system hardware and debug our ROM code using a Mac-hosted debugger.
PD: How did you hammer out the Voyager chipset specs?
Culbert: We spent about a year working with Cirrus on that. We created a common document and Cirrus implemented its chipset to that spec.
PD: Does the Voyager CL-PS7010 standard-cell ASIC handle SDLC and Geoport?
Culbert: Yes. It’s all in hardware.
PD: Why didn’t you use off-the-shelf SDLC/HDLC chips such as the industry-standard Zilog Z8530 serial communications controller?
Culbert: We used the 8530 SCC in the original Newton. But our goal now was to integrate as much as possible – for cost reasons. The chip we now have is bigger than we’d hoped for, but it offers significant cost savings over our previous architecture using separate ICs.
PD: Is Cirrus offering these chips to the merchant market?
Culbert: No. The Voyager is available only to Newton licensees.
PD: Does it make the MessagePad 2000 unique?
Austin: It gives us a high degree of differentiation by providing a lot of capability in a small space and with low power.
Culbert: The CL-PS7010 also has a proprietary low-pin-count bus and protocol that talks to the companion CL-PS7030 PCMCIA controller. We wanted to give users the ability to hot-insert and hot-remove PC Cards while the MessagPad 2000 was running. To do this we needed a completely isolated bus, so we came up with this scheme. Thanks to the cascadable CL-PS7030, the product can have as many as four Type II PCMCIA slots using one device per slot, all talking with a multiplexed frame format to the main controller. The bus offers voltage and signal isolation from the main system.
The unit’s DRAM and flash is the main system memory. It’s placed on the protected (memory) side of the bus, not on the PCMCIA side. Flash is where we store user information that’s not dependent on the unit’s batteries. We laid out the logic circuit board to use as little as 1 Mbyte of DRAM and 2 Mbytes of flash. Should there be customer demand, we may go to other configurations. We’re shipping 4 Mbytes of flash.
PD: How do you manage the flash array?
Culbert: There’s a flash file system, but not a Microsoft-type FFS. We use a transaction-based object database. It’s very effective for random access to large amounts of data.
Austin: If you put in a flash data card, you want the device to locate that as well as what’s stored in internal flash. The system automatically takes care of things stored in multiple areas – it provides a unified view. The transaction-based object store prevents data loss due to things such as a crash. Housekeeping is handled by the system controller.
PD: How did you engineer the analog interface to the unit’s loudspeaker, microphone, and touchpad?
Culbert: We spent months working with Cirrus-subsidiary Crystal Semiconductor (Austin, Texas) on the analog CL-PS7020 chip. We took a large discrete implementation and reduced board area, cost, and power by integrating it. Crystal brings a lot of patents in the area of sigma-delta modulation to the party. The ’7020 uses a linear single-bit A/D converter that operates in bit-serial fashion.
One of the problems inherent with sigma-delta is its slowness. It’s excellent for audio, but not very good for digitizing tablet signals where there’s electrical noise in the background and you want to detect and remove that noise from your measurement. Cirrus ended up filing four patents on the technique used in the ’7020. We got an A/D that’s speed-comparable to a successive approximation converter using a sample-and-hold, but on a very small piece of silicon – and with no external hold capacitor. It has a 19 micros sampling time.
PD: The unit has a unique subminiature connector. What is it and what does it do?
Culbert: It’s called the Newton interconnect. Originally we tried to fit an 8-pin DIN in there, but weren’t happy with the impact it had on our low-profile enclosure. Don Porter, our mechanical engineer, chose a 16-pin JAE Electronics (Irvine, Calif.) connector that was more suitable.
We added enough pins to it so a user would be able to use a communications device and a keyboard simultaneously, as well as providing charging power-in and peripheral power-out. That way, customers vertically integrating the unit could add meaningful backpack electronics. We ended up with 26 pins. JAE customized it for us.
PD: Did you work similarly with other suppliers for customized parts?
Culbert: We worked closely with Maxim Integrated Products (Sunnyvale, Calif.) to enhance its standard products. The Maxim variable-frequency and pulse-width switcher offers efficiency as high as 98%. It helps let the MessagePad work for up to six weeks from four AA cells.
PD: I can audibly hear the electroluminescent backlight switcher oscillating. Isn’t that irritating to users?
Porter: It’s one of our petty annoyances, too. It runs at a fairly low frequency between about 300 Hz and 1 kHz, and any mechanical resonance amplifies that noise. We tried freeing the toroids from the glue that holds them down, but we didn’t have enough room in the enclosure to make them float. We’ve had no customer complaints about the noise, but we’re working to solve it. At least it’s quieter than a hard disk.
PD: What makes the user interface unique?
Austin: You can rotate the screen for vertical or horizontal views. Horizontal’s good for a Web page, but vertical’s better for filling out a form. Software takes care of that. The software also gives two horizontal and two vertical presentations. That was done so extended PC Cards that might have antennas or dongles hanging out of them wouldn’t get in the way of the screen.
Porter: We also put key controls to the left and right so the MessagePad accommodates left- or right-handed users. We took the button bar that was silk-screened on the original Newton and put it in software. Users can now change what they want on it. That’s also good for licensees that want a customized user interface for vertical applications.
We also designed-in a full-size pen. Most PDAs have very thin styli or telescoping pens – people tend to play with them. We wanted a full-size stylus, but we had to fight for space for it.
We also put a real loudspeaker in, not a piezo speaker. A lot of work went into the 16-bit audio subsystem behind it. It actually runs GSM cellphone compression routines. Several compression engines permit high-quality voice at a low bit rate. That’s handled in realtime using only about 2% of the StrongARM’s processing resources.
Culbert: A big challenge was electrostatic discharge. The mixed-voltage design, where the lowest voltage is 1.6 V, didn’t leave much margin for ESD. So we routed a lot of external signals – including Reset – into general-purpose inputs on the controller to de-bounce them. We actually look for ESD events in software.
We also had to carefully control ground loops from ever seeing the ESD energy. A lot of PC Cards violate the PCMCIA’s specs. Card makers connect the metal structure of a card’s case to ground pins on the connector. That gives a chassis-to-digital-ground short with virtually zero impedance. As you can imagine, in this system, where the end of the card is exposed to the user, that presented a hazard.
We put a copper-foil shield on the PCMCIA slots under the connectors to provide a plane to absorb the energy coming in on a PC Card. We wanted to get the energy off the card before it got to the connector. We went through several iterations of the logic board design as well as the copper foil.
Inside the MessagePad 2000
The MessagePad 2000 uses a 162-MHz StrongARM SA-110 microprocessor coupled with a Cirrus Logic Voyager chipset. The SA-110 dissipates less than 500 mW, delivering 925 Mips/W. DRAM, used for temporary storage during program and system code execution, also provides the heap for a NewtonScript interpreted environment and a C heap, as well as stack and temporary buffer space for serial communications.
The CL-PS7010 packs systems-level glue functions, memory and single-/dual-scan LCD controllers, and serial ports for async and SDLC AppleTalk communications. It can support an external synchronous clock to run Geoport. The CS8130 is an IR transceiver. The CL-PS7020 provides a pen digitizer and touchpad interface, a battery and temperature monitor, audio record and playback, and a clock generator. The CL-PS7030 meets PCMCIA 2.01 specs, supporting hot insertion of 3.3-V and 5-V PC Cards. A 480 x 320-pixel indium-tin-oxide-coated glass touchscreen is used. The LTC1323 is a Linear Technology (Milpitas, Calif.) single-voltage RS-422 line driver.
Although the MessagePad was designed for 100% coverage boundary scan testing, 150 test points were requested by manufacturing. These were added late in the design cycle by carefully going around the Newton’s circuit board – by hand – turning vias into test points.
[Fig. 1] The interior of the Newton MessagePad 2000 reveals conductive-coated EMI/RFI shielding on the unit’s plastic case, relatively uncrowded circuit boards, dual PC Card controller ICs, and a mezzanine board for flash memory.
[Fig. 2] Apple’s Newton Systems Group engineering director David Austin (left), confers with systems architect Mike Culbert (standing, rear), hardware designer David Drummond (seated), and engineering manager David Turnbull.
Portable Design – July, 1997
Posted: March 18, 2013 Filed under: Software, System, Welcome to Macintosh | Tags: UI
A few days back, I read with interest an article by Stephen Hackett called The Brushed Metal Diaries: An Introduction, a Trojan Horse and a History of Abuse. While many people believe that brushed metal appeared in the Macintosh’s interface with Mac OS X 10.3 Panther, Hackett tracks its arrival back to 1999 and QuickTime 4.0:
1999 was a very interesting time to be an Apple fan. The Five Flavors were the machines of choice for many, and the Newton had been dead for little over a year. Mac OS 8.6 has just shipped, with OS 9 still several months away.
In these days, Apple released Brushed Metal in to the world. While eventually the UI would take over just about everything, its beginnings were quite humble: QuickTime 4.0.
It’s true, brushed metal started to replace the ‘platinum theme’ as the chrome of an application with QuickTime 4.0, but that got the long-time Mac user in me thinking. Somehow I wasn’t completely sure that was the first time I had seen brushed metal elements in a Mac application. As you can easily see by the awfully slow pace at which I’m keeping this site updated, lately I haven’t had much time to spend with my vintage Macs. Yesterday I finally found a moment to investigate a hunch I had, and I was right: brushed metal appeared in a Mac application as early as System 7.5.x (1994-1996), in Apple CD Audio Player’s UI:
This image in particular is taken from this page at guidebookgallery.org and it shows the Apple CD Audio Player application as it appears under System 7.5.3. (I verified by booting my Quadra 950 running that same System version, but this was an easier way to obtain a very similar screenshot). As you can see, the application UI emulates the interface of a CD player, and while the ‘Normal’, ‘Shuffle’, ‘Prog’ and ‘→’ buttons are simply faux-metal, the group of buttons on the right (Stop, Play, Eject, and so on) all present a more brushed-metal look. Apple CD Audio Player was also probably the first Mac system application to support customised skins.