Currently Being ModeratedFeb 5, 2013 9:07 AM (in response to baltwo)
Currently Being ModeratedFeb 5, 2013 11:31 AM (in response to Yttuty)
That's the top-level, HD/Library/Preferences/ one. You need to look at HD/Users/username/Library (the stupidly hidden one)/Preferences/. Without a Finder plist, there'd be no Desktop picture.27" i7 iMac SL, Lion, OS X Mountain Lion (10.8.2), G4 450 MP w/Leopard, 9.2.2
Currently Being ModeratedFeb 5, 2013 1:22 PM (in response to baltwo)
Currently Being ModeratedFeb 5, 2013 2:04 PM (in response to ppapple451)
If yiu believe you have the 'exact same problem, then the following may fix it as it did for the original poster. If not then you don't have the 'exact same' problem and therefore should start your own thread on this.
This solved my question by Chris Lyons on Aug 28, 2012 3:17 AM
PROBLEM SOLVED - I HOPE !!
Rather than visit a Genius Bar, I opted to buy an inexpensive (<$40) external USB-connected CD/DVD reader/burner (Samsung SE-208AB). I discovered that it too exhibited the same problem whereby DVDs and CDs burned in the Finder failed verification almost as soon as it began. Even though the burned discs appeared OK in that the files/music/movies were as they should be.
In addition to all the steps taken above, I also used the Recovery Disk to re-install a copy of Mountain Lion in case something was messed up. To no avail, the problem persisted.
After much more searching I discovered a tip that I had not tried. Someone had found that deleting the Finder preference file resolved their problem, in 2008 no less. So with nothing to loose, I deleted the Finder preference file, restarted and burned 3 discs flawlessly. Attached below is a screen shot from the Console app (in the Utilities folder) showing the most recent disc burning tasks including the intial one that failed verification. The highlighted text is my inserted note and not from the Console app. Interstingly it apperas as if iTunes does not perform a disc verify after a burn as the verify task is absent from the Console log.
The Finder preference files can be found at User/Library/Preferences/...
Of note is that none of these discs will work in the internal Superdrive and so I must assume that the internal Superdrive is offcially busted and must have failed coincidentally with my upgrading to Mountain Lion.
Currently Being ModeratedFeb 5, 2013 2:08 PM (in response to Yttuty)
Ignore the lockfile, since it's just a placeholder and shouldn't exist in ML, but may carryover from Lion. AFAIK, you can delete all such ones w/o any adverse effects.27" i7 iMac SL, Lion, OS X Mountain Lion (10.8.2), G4 450 MP w/Leopard, 9.2.2
Currently Being ModeratedFeb 11, 2013 3:57 AM (in response to ppapple451)
Hi bro, nice info
<Email Edited by Host>
Currently Being ModeratedFeb 20, 2013 12:21 AM (in response to Chris Lyons)
I have two late 2009 Mac Minis (2.26 Ghz Intel Core Duos) and a mid 2007 Macbook (2.16 Ghz Intel Core Duo), and late in 2012 I updated all three of them, mostly to make use of the iPhoto Cloud service. To my dismay all three are no longer working, yet if I boot my macbook into XP using Parallels then the drive works fine.
What makes this all the more frustrating is that I replaced one of the Superdrives under the last few months of my applecare warrantly, and I know for a fact that it worked to read and write DVDs and CDs the day before I installed Mountain Lion.
Apple is really incredibly irresponsible not to have patched this problem before now. I am really furious with them for letting this happen. One of the main reasons why I recommended macintosh computers to friends was because of the long interval of support for older machines, which meant that if one bought a fairly high-end mac, one could use it for many years without needing to replace it. This whole thing has completely shaken my confidence in macintosh computers.
Interestingly ppapple writes (on February 5th 2013) that apple has conceded that there is a bug and that they are working on a fix, but I think it's ridiculous that we should have to wait over a year for a bug fix on something basic like superdrive connectivity. I'm going to respond to ppapple and ask for the contact number or name at apple so that we can all harrass them until they fix this.
Currently Being ModeratedFeb 20, 2013 4:39 AM (in response to ppapple451)
Hi there, thank you for sharing this information. Could you please tell me how you contacted apple to report your problem directly? I'm finding it hard to do so,
Currently Being ModeratedFeb 20, 2013 8:12 AM (in response to mzadow)
I didn't contact them, they emailed me. First it was a guy named Adam, then he got pulled off my project and a guy name Rick took over. I talked to Rick for 30 min about a week after the emails, loaded some software he sent me to gather logs, and sent him the log file.
<Edited By Host>
Currently Being ModeratedFeb 20, 2013 10:29 AM (in response to mzadow)
I think it's ridiculous that we should have to wait over a year for a bug fix on something basic like superdrive connectivity. I'm going to respond to ppapple and ask for the contact number or name at apple so that we can all harrass them until they fix this.
Please inform Apple of your opinion. www.apple.com/feedback
Currently Being ModeratedFeb 20, 2013 10:47 AM (in response to Csound1)
Hi Csound1, thanks for reposting. I am fairly new to the Apple Support Communities Forum. What do you think we should do? Are we over-reacting?
FYI, I have sent a note to apple, to an email address that I received on another forum. Here it is (see below).
Thanks very much,
--Thanks,Dear xxxxx,Do you have or are you developing a patch for this software bug? What can I do to help you resolve it? A little more transparency would go a long way towards reassuring me and my fellow very loyal Apple customers,
I have a white acrylic Macbook and two late 2009 Mac minis (2.26 Ghz) that I absolutely love, but they have all three suffered Superdrive failures immediately after upgrading to Mountain Lion.
This is all the more strange, since two weeks before I upgraded to Mountain Lion I had the Superdrive in one of the Minis replaced under the last few months of the Applecare warranty, and I tested all the drives out immediately following the replacement, backing up information from my computers to DVDs, so I know for a fact that both drives on the Minis worked fine up until the upgrade. For all three to conk out at once seems rather unlikely. Now I am in the situation where I have to use an external LaCie firewire DVD drive to move the backed-up files from DVD to my computers; it is cumbersome and twitchy... and untenable.
Currently Being ModeratedFeb 20, 2013 10:45 AM (in response to mzadow)
Hi Csound, thanks for reposting. What do you think we should do? Are we over-reacting?
I think that the best way to express your opinion is to express it to Apple, we're just users, like you.
Currently Being ModeratedFeb 20, 2013 10:46 AM (in response to mzadow)
Hi Csound, thanks for reposting. What do you think we should do?
Post feedback. It can't, not help.
?Are we over-reacting?
Nope, I know the problem you are referring to and for me has resulted in many a coaster.
Currently Being ModeratedFeb 20, 2013 10:59 AM (in response to Csound1)
I did as you suggested. Here's what I sent to Apple via the feedback option at www.apple.com/feedback.
"Hi there, I have three macintosh computers. Two Mac minis late 2009, and one late 2007 macbook. In all cases the three superdrives failed immediately upon upgrading to Mountain Lion. You might call this a coincidence but I had one of the drives replaced under warranty a few weeks before upgrading, and used the superdrives on all three machines to make DVD backups of photographs, audio files, documents etc. I am certain that they all worked prior to the upgrade, and they all were bricked afterwards. What I find interesting is that the superdrive in the macbook worked in windows XP when I ran Parallels but not in Mountain Lion!
This is obviously a software issue and I wish that you would be transparent about it and inform those affected persons, and develop a software patch to fix this.
Currently Being ModeratedFeb 20, 2013 11:48 AM (in response to mzadow)
If you want to report this issue to Apple's engineering, bypassing marketing and sales (where I suspect feedback goes first), send a bug report or an enhancement request via its Bug Reporter system. To do this, register as an Apple Developer—it's free and available for all Mac users and gets you a look at some development software. Since you already have an Apple username/ID, use that. Once a member, go to Apple BugReporter and file your bug report or enhancement request. You'll get a response and a follow-up number; thus, starting a dialog with engineering and you'll be able to track its status.27" i7 iMac SL, Lion, OS X Mountain Lion (10.8.2), G4 450 MP w/Leopard, 9.2.2