site_archiver@lists.apple.com Delivered-To: bluetooth-dev@lists.apple.com Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:mime-version:content-transfer-encoding:message-id:content-type:to:from:subject:date:x-mailer; b=kQjNXvbjW8Q/ZK3t2l2/8iZM0JXOdre7Y3wPHm+1B2UYe1FT2UVcqFrBK2FMpM0sduKDkUlAmIvl+Z6k5Aa9eViq5T1Qa/Dm7x1GP026y+pd13u7ZWLzAfWPmpAMh0Wu5oT9IsrF/ONSZpSH1G4hA9KkBVKCs24nEHlx7BDG0pU= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:mime-version:content-transfer-encoding:message-id:content-type:to:from:subject:date:x-mailer; b=gZxaFEzzW/ZAC7o2yMF+AyTaoXPflwqfJBX7qc1jJZbqfgrD8RVRYoEUMPs1RDFvKMPihOMZVeR1XmeVgBaGWdwQ4mzUZw/vDV/sKtgXqL2GXPjFTmARnEa4uC9UHUGFNtISWrPh/OF1WRq3TzH6yhiQjT9vfWhiL7EdwXFZXx8= Best regards, Jere _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.a... Hi, this is a bit long winded but bear with me. It is relevant to Bluetooth after all. I have an Apple Wireless Keyboard that hasn't been able to pair since the batteries ran out (after a year). It seems that many others have had the same problem, but no successful remedy is available. Apple's first level support can only suggest removing and reinserting the batteries, which does not help. The keyboard is alive, but can't be found in BT search as a keyboard. However, when searching for all devices, it shows up, but only as "Device". The keyboard is alive, so I would feel stupid buying another Wireles Keyboard, especially if it failed the same way after the first batteries ran out. So I decided to investigate the problem, and it turns out to be quite a mess -- I'm hoping some knowledegeable BT experts would have some suggestions. Bluetooth Explorer (from Tiger developer tools) shows that the keyboard is identifying itself as: Major Class: Miscellaneous (0x00) Minor Class: Unclassified (0x00) Not a keyboard at all, so it seems to have lost its memory when the batteries went flat. My initial idea was to try and update the keyboard firmware, effectively resetting it. The only updater dates from March 2004, and it promptly crashed in OS X 10.4.9. The crash log revealed that dyld was looking for the following framework: /System/Library/PrivateFrameworks/SecurityHICocoa.framework/Versions/ A/SecurityHICocoa but the image was not found. Indeed this is so (in Tiger). I think the updater would use it to get the admin password. (?) There is one in the 10.3.9 SDK found in the dev tools, but that doesn't help -- I get an mmap() error. So my next idea was to borrow the Panther install disks from a friend, install Panther to an external FireWire disk and boot from it, then run the Wireless Keyboard Updater. This didn't work at all because my Mac mini would not boot from the Panther install disk (apparently because it shipped with Tiger). Bluetooth on the Mac mini is fine, it finds all devices and I've done file transfers etc. It's just that the keyboard doesn't report itself correctly, so it cannot be paired and used. The same happens with my MacBook, which also has a Bluetooth that's proven to work. Both machines have BT software version 1.7.14f14. How do I trick Wireless Keyboard Updater to run in Tiger, if at all? Or could Apple please release an updated version of it that does not depend on SecurityHICocoa.framework? Would it be feasible to write a utility that resets the keyboard? What would that require? This email sent to site_archiver@lists.apple.com