- Joined
- Dec 5, 2010
- Messages
- 7
- Motherboard
- GA-EX58-UD3R
- CPU
- i7-3970x
- Graphics
- NVIDIA GTX-980 (2)
- Mac
- Classic Mac
- Mobile Phone
The "FileNVRAM-1.1.3" definitely DID NOT work for me, on a GA-EX58-UD3R MB (running on ML 10.8.5). However, once I replaced it with the FileNVRAM.dylib with the version 1.1.2 from "FileNVRAM-1.1.2.zip", that was my final successful attempt. I know I'm just re-iterating, the original post, but placing "emphasis" here on how important it is to avoid that 1.1.3 version (unless that's your last resort). I've NOT attempted Mavericks, so maybe 1.1.3 works for Mavericks (but only surmising here, as to that what that version's purpose or existence is useful for...besides a great waste of time).
Before I ran across jaymonkey's post, which was very helpful, I had spent most of my Thanksgiving Holiday on trial/error attempts via information strewn all over the web about iMessage problems and solutions. jaymonkey's posting, out of hundred's of so called "solutions", is what immediately worked. Particularly, for my hack, coming from being upgrades going all the way back to 10.6.8, I probably had a lot antiquated digital polution, hanging around the system. So following jaymonkey's "Step 3" I think was pretty important. After doing those deletions, I firing Message.app back up, it hung on login, so I killed it, and 2nd time around it had recreated all those files again, with the successful ingredients needed to get a login.
Here's big Kudo to you, jaymonkey, and also the developers who gave us FileNVRAM.dylib as well as the Chameleon support for iMessage. (and of course the pioneers doing the Clover EFI boot-loader...whom worked out initial problems with iMessage).
Before I ran across jaymonkey's post, which was very helpful, I had spent most of my Thanksgiving Holiday on trial/error attempts via information strewn all over the web about iMessage problems and solutions. jaymonkey's posting, out of hundred's of so called "solutions", is what immediately worked. Particularly, for my hack, coming from being upgrades going all the way back to 10.6.8, I probably had a lot antiquated digital polution, hanging around the system. So following jaymonkey's "Step 3" I think was pretty important. After doing those deletions, I firing Message.app back up, it hung on login, so I killed it, and 2nd time around it had recreated all those files again, with the successful ingredients needed to get a login.
Here's big Kudo to you, jaymonkey, and also the developers who gave us FileNVRAM.dylib as well as the Chameleon support for iMessage. (and of course the pioneers doing the Clover EFI boot-loader...whom worked out initial problems with iMessage).
