4268 Views 8 Replies Latest reply: Sep 11, 2010 4:47 PM by rnbarrett
OK...definitely an operating system problem or something related to the OS such as an imcompatibility with something else.
I had an old harddrive around that I used for beta testing a commercial software. It was a bootable disk with 10.6.2 on it.
When I start my Mac with this disc and confirm I am in 10.6.2, my DVDs open normally in Finder. No "unreadable" problem. Even TrueCrypt works right.
I used my Snow Leopard disc to run Disk Utility and "repair" my main hard drive. That did not change anything.
I guess I will reinstall (without erasing) Snow Leopard from the original upgrade disc and then run all the subsequent upgrades. There goes the afternoon....
Any other ideas?
Just finished reinstalling Mac OS X 10.6 from the original Snow Leopard disc and then I did all the upgrades.
Still can't read a DVD that burned in this computer when I am in 10.6.4. Another Sunday afternoon shot...
I must have a conflict with something else on this machine. Is there an easy way to create of log of installed software by date? Even after installing 10.6??
I have answered my question now. It turned out to be a software problem.
I have a Lexar Jump Drive that comes with an encryption program called SecureII.app. It allows a secure "vault" to be created on the USB thumb drive that can be encrypted and read on either a Mac or a PC. I had to remove a file in System>Library>Extensions called LexarFileScheme.kext and now I can read DVDs and my TrueCrypt program will recognize a file that it has encrypted.
The error on Disk Utility for the DVD that couldn't be read was:
*+invalid BS_jmpBoot in boot block:66671c+*
When I googled that, I found references to the Lexar program and DVD problems.
Message was edited by: snsok
Thank you so much for posting this. I've been crawling the inTARwebs for the last few days to resolve a related problem. I could not open most dmg files. I got the "no mountable filesystems" message when opening the file, and disk utility kept reporting "invalid BS_jmpBoot in boot block:66671c" when trying to repair a dmg that I could open on another Mac just like mine (same hardware, OS level, etc.). I kept thinking I had screwed things up with TrueCrypt until I read this thread. I deleted the kext you mentioned, restarted, and my problems have gone away. Now I wonder how I am supposed to encrypt files on my memory key. Guess I'll just use TrueCrypt and see how that works.
No, no! Bad Lexar! Bad!