But getting the scanner to work only solved half of the issue. The other problem remained that the X560n wasn’t Leopard-compatible. Thus, the X560n was now set to receive a rating of Leopard-version of the X560n driver—hence the rating that you’ll see on the review.
Some of you might ask, “Why not just run with the rating so Lexmark learns a lesson?” Well, ripping apart Lexmark would indirectly solve the problem; it might not solve anything at all. Besides, our job as journalists is not only to inform readers, but to influence positive change. Did we inform you of the problems? Yes. Did we get Lexmark to fix them? Yes. It took a lot of time, but we got the job done—and I’d say it was worth the wait and aggravation.
. Fortunately, days before we were set to publish our review, Lexmark e-mailed us with a
In the mean time, Macworld Lab will keep a watchful eye. This isn’t the first time we’ve encountered issues with network scanning to a Mac on an MFP. (For example, the Brother MFC-9420CN‘s scanner exhibited quirky behavior when we tested it in 2007.) The X560N is just a small part of a large issue that we’re trying to address—one product at a time.