This posting is older than 6 months and can contain outdated information.
Hi there,
thanks for your feedback.
Not a single line of code has changed in the kernel extension or
anything that gets into touch with it between 1.1 and 1.7. The only
change in the kernel extension in 1.7 is in the Info.plist XML file -
which contains more or less just metadata and info, on what software
is required by the kernel extension - to be compatible with Leopard.
Yet, this single change that has been made can never cause a kernel
panic.
I don't believe that Remote Buddy is causing you a kernel panic,
because the code in its kernel extension is stable by now, has not
seen any changes and also doesn't do any hacking, patching, abusing
APIs or similiar - it 100% obeys to Apple's documentation and
officially documented, legitimiate use of kernel APIs.
Plus the Remote Buddy kernel extension does absolutely nothing during
system startup. It only becomes active when you start Remote Buddy. It
ceases its activity when you quit Remote Buddy.
And, if you used AppZapper to remove Remote Buddy, you did not remove
the kernel extension from your system.
If you want, I can have a look at your kernel panic log (you find it
in /Library/Logs) and try to tell you where the problem stems from.
For this, please either post it here or send it by email to the info@-
address as seen in this website's imprint).
I can also send you a copy of version 1.1 by email if you so wish -
although it certainly doesn't make any difference.
Best regards,
Felix