Troubleshooting Mac OS X 10.2.2: Konica provides PPD Workaround; Symantec speaks on NUM Problems; USB Processor Use

Troubleshooting Mac OS X 10.2.2: Konica provides PPD Workaround; Symantec speaks on NUM Problems; USB Processor Use

Konica Provides PPD Workaround Konica has provided MacFixIt a workaround for issues caused by the PPD file included with several of its printer models. A member of the company's technical staff told us:

"The information posted on MacFixIt indicates a problem with the Konica IP511 controller with v.1.1.1 firmware. I referred that matter to our software support group, and they had this work-around which enables Konica products to work properly under 10.2.2. Note that this issue affects more than Konica and is apparently due to changes made by Apple. The workaround is as follows:

"In Konica's case, if you are using a Konica PPD and select a Konica printer to print from an application, the application will crash. This problem has also been verified with some HP and Xerox printers as well. The following workaround that will take care of this issue, until Apple comes out with a patch, as this was not a problem with version 10.2.1.

"The Konica PPD file has an entry called 'DefaultInputSlot'. (See Reference Below) There is a % sign to the left of the entry that is a comment marker. If you delete the % sign to the left of the entry and also on the line below it next to the "InputSlot" entry, the ppd will function correctly. If doing this on the Macintosh, just double click on the ppd file. It will automatically open in TextEdit. Do a find for the "DefaultInputslot" entry, delete the two %-sign entries, and save the file.

*% === Tray Selection ============
*OpenUI *InputSlot: PickOne
*OrderDependency: 50 AnySetup *InputSlot
*%DefaultInputSlot: AutoSelect
*%InputSlot AutoSelect/AutoSelect: "<</MediaPosition null /TraySwitch
true>> setpagedevice" *InputSlot Tray1/Tray 1: "<</MediaPosition 0
/TraySwitch false>> setpagedevice" *InputSlot Tray2/Tray 2:
"<</MediaPosition 1 /TraySwitch false>> setpagedevice" *InputSlot
Tray3/Tray 3: "<</MediaPosition 2 /TraySwitch false>> setpagedevice"
*InputSlot Tray4/Tray 4: "<</MediaPosition 3 /TraySwitch false>>
*CloseUI: *InputSlot

Users have submitted other workarounds for the PPD issue, including Graeme McKinstry who had success with an alternative PPD file on his Xerox Docucolor printer:

"I downloaded a Fiery PPD (same printer different RIP) and copied the paper size specifications into the CSX2000.ppd file and it then worked okay. I use this new PPD when selecting paper size under Page setup and use the original PPD when Printing (in Freehand 10)."

UPDATE: Another three-step workaround has been successful for a number of printer models with PPD failure problems:

  1. Delete the "" located in ~/Library/Preferences
  2. Put your printer's PPD in root/Library/Printers/PPDs/Contents/Resources/en.lproj (or whichever language your system uses). Note that the permissions on this folder must be modified in order to move the PPD to this location.
  3. Set-up the printer using Print Center, and select the newly placed PPD.

Symantec Speaks on Norton Utilities Problem Symantec has begun offering a response to users regarding the compatibility of Norton Utilities and Norton AntiVirus, which both fail to recognize any mounted volumes under Mac OS X 10.2.2:

"We are aware of issues with drives not appearing in Norton Utilities after updating to Mac OS X 10.2.2. Symantec is currently investigating this issue and hopefully a resolution will be available soon. I apologize for any inconvenience and thank you for your patience in this matter."

NVRAM Printer Workaround Resetting the NVRAM may resolve issues for some printer models that have problems after applying the Mac OS X 10.2.2 update. Phil Geller reports success with resetting the NVRAM on his Lexmark Optra E312:

"Lexmark tech support recommended resetting the NVRAM to the factory defaults. It fixed the problem. They said it might be necessary to do this every time the printer is switched from Mac OS 9 to Mac OS X. I didn't test that to determine if it was true, but after doing the NVRAM reset the printer prints from both the Mac OS X Print Center and from Classic."

Procedure for resetting the Optra E312's NVRAM (from the printer's manual) is as follows. Other printers use a similar process, refer to you model's manual for specific instructions.

  1. Turn the printer power off.
  2. Open the top cover
  3. Turn the printer power on
  4. When the Error LED comes on solid, double-click the operator panel button
  5. Once the Error and Press Putton LEDs start blinking, close the top cover
  6. The Ready LED comes on solid and the Error and Press Button LEDs continue blinking.
  7. Double-click the operator button one time. The Data LED comes on solid while the Error and Press Burron LEDs continue blinking.
  8. Perform a long button press until all LEDs come on solid.
  9. The printer is now reset ot factory default settings.

USB Devices and Processor Use We continue to receive a bevy of reports indicating that for some systems recently upgraded to Mac OS X 10.2.2, the presence of USB devices causes the process "kernel_task" to drain processor cycles. It also appears that actually activating input USB devices worsens the slow-down.

We have seen similar issues under Mac OS X 10.2.2 using FireWire devices as well. On both our in-house Power Macintosh G4/733 and PowerBook Pismo G3/400, an external Oxford 911-powered WiebeTech hard drive routinely causes the system to slow to a crawl when connected, with the problem immediately disappearing after the device is disconnected. Occasionally, the problem persists after a restart, and prevents the system from moving past the initial Mac OS X 10.2.x splash screen until the FireWire device is detached.

Thomas Keller writes:

"The problem is directly dependant on the number of USB devices connected to the Mac. The more devices I connect, the more severely up goes the processor usage of 'kernel_task' in process manager. (starting about 10 minutes after startup). With 8 devices (including external hubs), the increase of processor usage is not yet immediately noticable, although after some time it gradually rises. With 9 devices, I am able to stop 'top' from updating the display in 'Terminal' by moving the mouse. With more than 9, I even can stop the clock in the menubar from updating, because the system is so slow when I move the mouse.

Erratic Mouse Movement We continue to receive corroborating reports of erratic mouse movement after upgrading to Mac OS X 10.2.2, especially with input devices from Logitech and Microsoft. Chris Ogle writes:

"My new MX900 optical cordless mouse has been erratic under os 10.2.2 and 10.2.1 before it. The mouse will work fine and then after a period of between 1 and 4 hours all the buttons will stop working. Tracking to continues to work fine but all button control goes. Full functionality is restored by a systm reboot. I spoke with Logitech tech support and was informed that this was a known issue for which they currently have no solution but that they are working on it. In the interim it makes the mouse – otherwise a promising product – completely useless."

Unconfirmed issues There are still some seemingly isolated incidents occurring after Mac OS X 10.2.2 installation for which we are seeking confirmation:

  • A number of readers are reporting that Palm HotSync application included with Palm Desktop 4.0 crashes while attempting to synchronize data since the update
  • Stan Goldberg reports that his Dymo Turbo Labelwriter which worked under Mac OS X 10.2.1, is no longer recognized in the Print center under the 10.2.2 upgrade.
  • Some users report that their iMac's SuperDrive is no longer able to be opened from the keyboard after applying the Mac OS X 10.2.2 update.
  • Users report cascading error messages at startup of Mac OS X 10.2.2, and state that removing USB devices alleviates the errors' appearance. .

Insight on any of these issues? Drop us a line at

  • More from Late-Breakers
  • Featured Video