Support > Remote Buddy Forum > Candelair conflicting with Kodak easyshare 5100 printer // IOSPIRIT [EN]

Support

All support resources for our products. Here you can find answers to frequently asked questions, discuss with other users, recover a lost license code or file a support request.

Forum closed

This forum was closed and turned into an archive effective April 21, 2018. It is no longer possible to create new topics or reply to existing topics.

Thanks everyone for all the great questions and contributions over the years.

Please use the Contact form to get in touch.

Remote Buddy Forum

Overview

Author

Thread

User

15.11.2009 19:01:01

Candelair conflicting with Kodak easyshare 5100 printer

View

This posting is older than 6 months and can contain outdated information.

After installing the Candelair driver to fix the remote issue with Plex, I could not use my Kodak Easyshare 5100 printer. My printer would show an error, "printer not responding" or "Can't connect to printer." I updated to the most recent software from Kodak, but no luck. After uninstalling the Candelair driver, the printer worked fine. Any solutions or why this is happening?

These entries from the FAQ may be relevant to this topic:

Driver

What is the task of the driver and what do I need it for? (FAQ015E0177)
The Setup Wizard already contains a summary on how the driver does help Remote Buddy to provide additional features and hardware support. If that summary was too short, here's some more info on each of the points:
- fix for Apple® Remote driver problems in OS X
  Since OS X 10.4.9 (that includes 10.4.10/10.4.11/10.5.x/..) many users have been experiencing that one button press on their remote does now trigger two reactions - once from any currently running application that supports the Apple® Remote, once the default system action. So, this problem is not specific to Remote Buddy. The driver provides a clean, system conform fix to this problem using only documented APIs.
- enabling of all features of built-in IR receivers
  Only with the Remote Buddy driver do you gain support for arbitrary length button presses for the Play and Menu buttons as well as minimized reaction times for all buttons. While this may sound like unimportant technical details, they actually do have a strong practical impact. If, for example, you want to map a function to the Play or Menu button, that you want to see executed for as long as you press that button, this was previously simply impossible to achieve. This limitation still applies to all other applications. It does not for Remote Buddy with the driver loaded.
- the emulation of a virtual Apple® Remote
  Control applications that have support for and listen to an Apple® Remote - with any remote control of your choice supported by Remote Buddy. And on any Mac®. This allows you to f.ex. use iAlertU side by side with Remote Buddy or accessing special functions and modes inside applications that would otherwise require these apps to have full control over the built-in IR receiver of your Mac® - and that your Mac® actually came with one.
- support for Bluetooth® remotes and external receivers
  It's not possible to reliably operate many Bluetooth® based remotes, like for example the Wii® Remote with a Mac® purely from userspace due to limitations in the operating system. The situation for many external receivers is similiar: some of their features - or the entire device - can only be supported with the help of a driver.

Hardware - Apple® Remote

After uninstalling/quitting Remote Buddy, my Mac® no longer reacts to the Apple® Remote. (FAQ015E0241)
To enable you to use all capabilities of the IR Receiver of your Mac®, Remote Buddy is using its own driver. In contrast, all other applications with integrated Apple® Remote support usually use the OS X Apple® Remote subsystem.

As long as you're running Remote Buddy, Remote Buddy and its driver are responsible for turning the received button presses into actions. As soon as you quit Remote Buddy, this task is again handled by the OS X Apple® Remote subsystem.

If other applications don't use the interface to the OS X Apple® Remote subsystem correctly, this can lead to the effect that nothing happens when you press a button on your Apple® Remote. For as long as you're running Remote Buddy, issues like this are covered by Remote Buddy and it's driver and are therefore not visible to you. However, as soon as you quit Remote Buddy, the OS X Apple® Remote subsystem is back in control and any issues caused in it by other applications become visible.

Therefore Remote Buddy is neither the cause of the issue nor is it responsible for it. Instead, the cause of the issue exists independently of Remote Buddy. It's located elsewhere and can also only be solved there.

Although our products can't cause any such issues, we're regularly contacted about such issues and asked for help. In order to make locating and fixing the cause of such issues as easy and efficient as possible, we've developed a free diagnostics tool: Remote Control Diagnostics. It can locate issues with a single click and will provide you with information about the issue as well as with instructions on how you can fix it.

User

16.11.2009 08:13:46

Re: Candelair conflicting with Kodak easyshare 5100 printer

View

This posting is older than 6 months and can contain outdated information.

Dear Scott,

thanks for asking.

I can assure you that Candelair has no chance to have this effect. Inside Candelair's bundle is an Info.plist file which precisely defines for which hardware the driver is to be used. You can find it at /System/Library/Extensions/RBIOKitHelper.kext/Contents/Info.plist.

If a device is not in that list, Candelair is not used for it. And this list of USB devices does not include any Kodak hardware.

You can also verify that Candelair is definitely not used for your printer by launching System Profiler.app, selecting "Logs" and then "ioreg_sp.txt", which is a complete representation of all device drivers and how their are used - at that very moment - on your system. You'll see that for the "IR Receiver", the Candelair driver is used and that, for your printer, the regular OS X/Kodak drivers are used, but *not* Candelair.

Since Candelair has no contact to your printer or printer software at all, it simply can't have any influence on it, either. So, sorry, but Candelair is not the cause of your issue.

I may still be able to help you. Other error sources that spring to mind and fit your description:

1) a copy of VMWare/Parallels running with their "auto-attach newly connected USB hardware" option enabled. Solution: turn of the option and detach the printer from the virtual machine.

2) your USB printer is not detected due to a common Mac USB problem. If your printer doesn't turn up in System Profiler.app > Hardware > USB despite it being connected and turned on, reset the SMC (System Management Controller) of your Mac. Search Apple's support site for instructions for your Mac model. You'll find the suggestion to reset the SMC and a list of other instructions in Apple's long support article covering solutions to Mac USB problems.

Why do these fit your description?

1) when uninstalling Candelair, you're requested to reboot. A reboot will quit any instance of VMWare/Parallels and unless you have set them to launch and start a virtual machine right after login, they will no longer "rob" access to USB devices from OS X.

2) when uninstalling Candelair, you're requested to reboot. The SMC issue affects devices that are attached during boot. If you happened to have turned off the printer during the reboot and turned it on again after boot, you worked around the SMC issue.

Best regards,
Felix Schwarz

Remote Buddy
Support
1. Overview
2. Manuals
3. FAQs
4. Forums
1. Lost license code
2. Support inquiry
IOSPIRIT
1. About us
2. Blog
3. Labs
4. Developers
1. Contact
2. Press releases
3. Imprint
4. Jobs