One of the new “features” of Windows XP is that it apparently no longer supports the AppleTalk protocol. In previous “professional” versions of the Windows operating system, it was possible to install support for the protocol, but no longer. For most users this isn’t a large problem, but for certain users of Apple printers that are no longer supported, it’s a big issue indeed.
One of the main reasons I purchased an Apple LaserWriter 16/600 several years ago was because it supported a wide variety of connectivity options: AppleTalk, Windows, NetWare, and TCP/IP. Like most users, I wanted my workgroup printer to be free-standing and accessible over our internal network by Mac, Windows, and *nix clients.
For the Macs, this has never been a problem. Plug ‘em in and go. For the Windows users, it wasn’t much of a problem at all with Windows NT and 2000. Just install the AppleTalk protocol, reject the option of “capturing” the port, and go. Since we’ve only ever used *nix for server applications, printing was never an issue.
Once upon a time I do remember configuring the printer to accept connections over the Internet (3 providers and more than a few years ago). Free incoming faxes by instructing users to simply print what they were trying to fax to our remote printer. Neat.
The solution to printer access in a mixed network is clear: use the TCP/IP common denominator. Except I can’t. In order to configure the IP address, subnet mask, and gateway I have to be able to login to the printer. And to do this, I need to know the password. Clearly I set a password years ago that I forgot shortly after setting it. And get this: there’s no way to reset the password unless you know it. This, from Apple, the queen of industrial design.
Actually there should be a workaround, but it doesn’t work either. If you can believe this, Apple’s Macintosh Printer Utility includes the capability of resetting the printer’s IP address, but not the subnet mask, or the gateway. Apple must think that either a) Macintosh users are too stupid to be trusted with these configuration items or b) Macintosh network configurations would never change. Because the really puzzling thing is that Apple’s printer utility for Windows does allow the user to alter these configuration items. Except it doesn’t work either, reportedly because of a bug in the printer’s ROM.
I sent a query to Apple about this almost two weeks ago. It didn’t bounce, so I assume the .(JavaScript must be enabled to view this email address) email address is valid. No response at all. Apple does, however, have some of the best support forums I’ve ever seen. Of course they rely on the Macintosh community to support themselves, for the most part, but the community actually does a pretty good job of this. It’s to be expected; they’ve had years of practice. I got a cogent response from someone in the community within an hour of my query there.
Who’s to blame for this fiasco? Apple for it’s crappy industrial design, lack of usability, and development bugs; Microsoft for removing support for the AppleTalk protocol from its operating system; or me for being stupid enough to buy another half-assed Apple product? Clearly I’m to blame for forgetting a configuration password from years past. But should I be penalized so severely for such a relatively minor misstep? Microsoft can’t be blamed for this one, folks: How can Microsoft reasonably be expected to support something that the original manufacturer no longer supports? That leaves Apple, and this incident is just another example of the company’s unwarranted hubris and a prime reason why I’ll likely never buy another Apple product.
Oh, and just to make sure there’s no misinterpretation of me being an equal-opportunity bitch-and-moaner, I just got spam from Adobe offering a seminar on XML and the Future of Publishing. Adobe’s only been promising XML support for its FrameMaker product for, oh I don’t know, about 7 years or so. Yeah, I’m going to trust Adobe to get XML right; just as soon as they can patent it.
0 responses. Comments closed for this article.