| Author | Thread |
User 10.10.2007 05:35:24 |
This posting is older than 6 months and can contain outdated information. I love RM, purchased three licenses for my three machines that I'm using it on. One of the machines is a Mac Mini G4 1.25ghz that does nothing except run Matinee and Remote Buddy, streaming from a server in the basement, running 10.4.10. This computer has been running solid for a month with no problems. Tonight I got the pop-up to update the software and the kernel extension, so I did those things. Now, every time I use my Keyspan remote control to put the Mini to sleep, I get a kernel panic. This has happened three times in a row. Like someone asked a few threads down, how can I go back to the previous version? Was this tested on G4's? One of my other machines is a headless G4 iBook and I'm definitely NOT going to upgrade the software.
| These entries from the FAQ may be relevant to this topic: Driver 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.
General Please find the last version with support for Mac® with PowerPC™ processor below.
 | Filename | RemoteBuddy.dmg | Description
Remote Buddy 1.16.6 | | Filesize | 8,87 MB | | Last modified | 27.05.2011 15:59:54 | |
Hardware - Apple® Remote
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.
Hardware - iPhone™ / iPod® touch / AJAX Remote First of all, setup the AJAX Remote as described in the FAQ entry "How do I setup the AJAX Remote?".
Then follow these steps:
- In AJAX Remote on your iPod® Touch or iPhone™, tap on the "Music" symbol.
- Now tap on "Library" (upper-right corner) and navigate to the media file you want to playback on your iPod® Touch or iPhone™.
- Tap on the blue play button.
- If QuickTime® thinks that it can playback the file, you can now start playback by tapping on dark-blue playback button.
All preference settings are already set correctly by default. If you don't see any playback symbols: the remote access to files is only supported if you have set a password ("Require password" is enabled) and the option "Allow access to the files in your iTunes® library ("streaming")" is enabled as well. Both options can be found at Preferences > AJAX Remote.
| Thread-display::- Kernel Panic for me too, User, 10.10.2007 05:35:24
|
|
