Possible fix for UJ-815 Superdrive problem

I found a number of posts some time ago regarding this problem. Seems my Superdrive started making coasters when either reading or writing CDs / DVDs. The problem manifests itself in a grinding noise that gets louder and louder, then the drive eventually stops spinning. When it ejects the disc a circular scratch, about 1/16" in width, is noticeable near the middle of the media. The disc is then rendered useless.
So I replaced my original Superdrive with a Matshita (Panasonic) UJ-875, a much faster and more capable drive. I got it from Powerbook Medic for $99 but there are other sources such as OWC. Powerbook Medic says this drive may be installed in any of the Powerbook G4 Aluminum or Titanium models as well as the Macbook Pro 17", the Powerbook G3, or the iBook G4.
Replacing the drive is not difficult, just delicate. You need patience, good eyes, and tiny tools to manipulate tinier screws. Powerbook Medic's guide was helpful.
After installing the new drive I disassembled the old one by removing the four Phillips screws securing the top cover. Upon opening the drive the problem was immediately evident: a metal plate installed beneath where an inserted disc would be was bowed upward. There was also clear evidence of plastic CD material deposited on the area corresponding to where my discs were damaged:
See the red circle. It's not terribly clear in the photo, but that's plastic junk. It was bent to a degree that was obvious when sighting down the edge of the metal. Reflections in it were distorted.
How the metal got to be bent is a mystery, but it stands to reason that as the drive gets warm (and they do get quite warm in use) the metal could expand and bend upward, causing the damage. I thought removing it might be instructive, but as soon as I loosened the screw near the edge of the case the metal "popped" back into a flattened shape. So I merely tightened the screw that I just loosened.
The red circle is the screw I loosened, then tightened.
Now, I haven't re-installed the drive to test this fix but it seems a pretty straightforward fix, with the metal piece flat again it shouldn't interfere with the media. Of course, it could bend upward again, but perhaps the hole this screw goes through is slotted and the screw was too tight. Perhaps the metal piece could be removed and left out entirely; who knows. The point of telling you all this is that if your drive starts exhibiting the same symptoms it might be worthwhile disassembling yours to see if this is a worthwhile fix, since the cause of the grinding noise and disk damage was obvious.
Hope this helps!

download the icloud control panel version 1.0.1 from here http://www.putlocker.com/file/0238BBABA8F91AFB

Similar Messages

Possible Fix for Disc Image Creation Problems

I've noticed a number of posts describing problems similar to the one I had: with my first session with iDVD5, I tried creating an .img disc image (thanks to Apple, btw, for building that function in -- and for the new progress bars!), but it hung up all night long on the "Burn" task, and I had to force quit, leaving me with no image at all.
I used disk image burning exclusively in iDVD4, because it allowed me to preview the result before committing it to a physical burn and prevented coaster-burning if something went wrong. I had had buffer problems when burning directly from iDVD -- but never with Disk Utility.
Of course, in iDVD4, you cannot just burn a disk image using the app. Most are aware that using "Hurz" and "Pfurz" (see posts under iDVD4) provided a great workaround, however, and that's what I used.
Well, it occurred to me that perhaps Hurz and Pfurz -- which basically interfered with iDVD4 to the user's advantage -- ought NOT to be in play with iDVD5. So I removed them from my user folder, et voila -- the very next time I tried the disk image function in iDVD5 (with the same project), it worked perfectly.
But I can only SUSPECT that this was the solution, unfortunately, because of the fact that an automated maintenance script had repaird my permissions in the meantime. The problem might have been permission troubles resulting from installation.
I do know this: removing Hurz and Pfurz and repairing the permissions worked for me. Hope it does for some others as well!

Thanks, Len. I kind of wish Apple would make a bigger deal of this. Repairing permissions fixes ALL KINDS OF THINGS! And it is a VERY good idea to do it regularly.
Like you, I do it once a week, using a wonderful freeware utililty called Onyx (search MacWorld or Google for it), which has a number of advantages over Disk Utility.
In the first place, it will execute all the maintenance scripts as well. You might know that OSX has a number of scripts it runs in the background for maintenance, some daily, some weekly, and some monthly. But they are generally set to run late at night, which means you need to leave the computer ON and AWAKE. I don't do this as much as I should, so running Onyx ensures that these scripts get run. Since using Onyx, I have NEVER had a crash.
Secondly, I can schedule it to do all this automatically, which is great - because I'm getting old . . . and I forget things. . . .

Possible Fix for Printing Problems in Leopard

I got this information from Mac OS X Leopard Edition book by David Pogue. Here's his possible fix for printing problems in Leopard...Open web browser and enter this address http://127.0.0.1:631. You'll find youself at a secret "front end" for CUPS (Common UNIX Printer System), the underlying printing technology for Mac OS X 10.5. This trick lets your Mac communicate with a huge array of older printers that dopn't yet have Mac OS X drivers. Using this administration screen, you can print a test page, stop your printer in its tracks, manage your networked printers and print jobs, and more–a very slick trick. Haven't tried it yet...anyone who does let me know how it worked!

If you literally "checked" them, meaning the checkboxes, that only affects their visibility. To remove them, select one and then click on the "minus" part of the "plus minus" at lower left.
Doug

Possible fix for errors 11503 and 50

Here's a possible fix for Error 11503 and for error 50.
It worked for me and hopefully it will work for you.
I believe this error is caused by the incomplete downloading of either an update to an app. In my case it was caused by closing the lid on my laptop when I was downloading app updates on a very slow internet connection in a hotel.
Anyway, here is what I did that fixed it completely.
Close iTunes.
Go to this folder : /iTunes/Mobile Applications/Downloads
You'll find tmp files there. Drag them out of this folder to a temporary folder on your desktop. The Downloads folder should now be empty.
Restart iTunes.
All should be fine.
If it is, delete the desktop folder with all the temp files.
If it's not, then I can't help further, but that's what worked for me.

Several possible causes from the info you gave
Battery level low - recharge it for at least 4 hours till the full charge sign displays (2 prong icon instead of lightning icon).
Time to Reset the iPod - Press the Menu and center Button for about 10 secs till the Apple logo comes ON, then let go of the buttons.
your hardisk is starting to give problems, hence the skipping and some song refuse to play. - Do a disk diagnostic - follow this post by tt2.
https://discussions.apple.com/message/17028567#17028567
If you have updated any sofware application in Windows, then follow this Apple support procedure
http://support.apple.com/kb/TS1539
Most likely you have to do all, as the iPod hardisk filesystem would have been corrupted, or else the iPod Reset would bring it to normal operation.
Good Luck!

Possible fix for OS X 10.5.7, losing connection after sleep, restart

Possible fix for OS X 10.5.7, Airport, losing connection after sleep, restart, or cold reboot.
Issue: (For OS X 10.5.7 on iMac5,1, Intel Core 2 Duo)
=============================================
- After sleep, restart, cold reboot, even though cannot connect to Internet, but the AirPort bars are still full, as if connected.
- Losing Internet connection after sleep, restart, cold reboot.
Possible Fix:
1.Open Network Preference, click on the Location drop down list > Edit Location... > click on the wheel button > Duplicate Location.
a)Select this newly setup location; Use Diagnostic button to connect to the internet. Select Network or enter WEP password if necessary.
b)Test to make sure you can connect to a web page.
c)Go to sleep & wake up.
d)This time, the Airport bar will start to show correctly. Before, it will always be full even when not connected. Now there will be no bars or grey out when not connected.
2.On the left hand side of the Network Preference Window, there is a list of services, such as Airport, build-in ethernet, built-in FireWire, bluetooth, etc.
a)Click on the wheel button on the bottom of the service list; select Set Service Order...; move Airport to the top of the list.
b)Delete any services which you are sure that you are not going to use, such as Bluetooth, etc.
3.Pick one of the locations mentioned in #1, and make it sure it is connected. If not, use Diagnostic button. If you have to select Network or enter WEP password to connect, make it so.
a)Check to make sure you can connect to a web page.
4.Go to sleep & wake up. The Airport bar should be filled up quickly. Try to connect to a web page.
5.Restart computer. Test a web page.
6.Shut down & Start computer. Test a web page.
7.When everything is working fine, you can delete the extra location that you created in step #1.
8.Click the lock on the left lower corner of the Network Preference window to safeguard the setting.

If my assessment is correct, the LIDE 200 driver is version 14.8.1 and dated 26-Sep-2008. It is possible that the driver will not work with the latest version of OSX. I would advise that you contact Canon and ask them the question.
(Removed link because of the way Flash drives the Canon site).
It is not uncommon (though irritating) that devices no longer work when an OS is upgraded. One has to ask the question if (or why) the driver was not written in such a way as to be OS version independent.
Chris
I spoke to Canon over here in Australia. Not helpful at all. In fact they were about as useful as an ashtray on on motorcycle. Having said that the tech seemed to think that there would be an update soon. But that is assuming that Canon are aware that there is a problem with that Scanner under OS X 10.5.7.
Message was edited by: 2point5

[svn:fx-trunk] 10229: Fixes for some transform effects problems.

Revision: 10229
Author:   [email protected]
Date:     2009-09-14 08:43:43 -0700 (Mon, 14 Sep 2009)
Log Message:
Fixes for some transform effects problems.
- We were not animating the postLayout properties in some cases where we should have, effectively pinning the object in place. We now animate those properties whenever applyChangesPostLayout is true.
- A copy/paste error meant that we did not animate the scaleZ property in cases where we should have.
- A problem in the transform code means that using a null transform center is not the same as a transform center which uses the transformX/Y/Z properties of the target object. We now force the creation/use of a transform center in all cases to avoid that problem.
QE notes: This breaks about a dozen tests in the transform effects area, but I believe the new results are correct and the tests/bitmaps should be changed.
Doc notes: None
Bugs: sdk-23177
Reviewer: Hans
Tests run: checkintests, Mustella transform effects
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/sdk-23177
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/AnimateTransform.as

Fix for Airport Wireless Connection Problem stating Self-Assigned IP and not wanting to connect in Lion OSX.

Fix for Airport Wireless Connection Problem stating Self-Assigned IP and not wanting to connect in Lion OSX.
Bought my girlfriend the newest Macbook Pro 13" and began experiencing problems with my wifi the moment we got home. Her Macbook would not connect to our home Wi-Fi while my old Macbook Late 2008 running Snow Leopard connected without a problem. Airport would say that it had a Self-Assigned IP address (168.x.x.x). Did not realize it was a Lion problem until after using her Macbook Pro and becoming jealous of the new OSX, I upgraded. Soon after I was unable to go online. Luckily I had my iPad 2 and I began to scoure the net for help. Ran into allot of suggestions but it was not until I tried the following all together was I able to share the good new, from my Macbook. Hope this works:
First go to Preferences > Network and click on the cog next to the + and - on the sidebar and click Set Service Order
     - Move Wi-Fi to the top and click ok.
     - Set location to Automatic
     - Click Apply
     - Click Advanced
     - Click the "-" on the selected Wi-Fi router you wish to connect to
     - Click Apply
     - Click Lock to Prevent Further Changes
Go to your Mac's harddrive, (Macintosh)
     - Go to Library > Preferences > SystemConfiguration >
     - Delete "com.apple.airport.preferences.plist" file
Turn off your computer
     - push and hold Option+Command+R+P
     - turn on computer
     - when the grey screen turns on you will hear the OS X "ON" sound (for lack of a proper term) and it will momentarily restart.
     - you will once again hear the "ON" sound, let go of all keys.
     - this resets your PRAM
Go to Preferences > Network > Advanced > + sign
     - click Choose a Network
     - Select your network and enter password
Viola!!! I tried this on my Macbook Late 2008 and my girlfriends new Macbook Pro 2010

     No you are clearly mistaken. The Self-Assigned IP address problem exists on many Macbook Pro models, including the current model, which I mentioned as being the original computer with the problem. While my 2008 Macbook is older it was working perfectly on Snow Leopard and didn't suffer issues until switching to Lion. So clearly the problem exists on the operating system and not so much the hardware.
     I called Apple Support and they had no fix for the problem and told me that this would hopefully be addressed in a subsequent update. It wasn't until I came accross the answer after trying many different methods that I got both of the Macbooks to connect to my router. Otherwise I wouldn't or could not have been surfing the internet for the last 4 months.
Cheers.

Possible fix for Adobe PDF plug ins (Safari & Print) on Snow Leopard

I think I just discovered a "fix" for the Adobe PDF problem, as well as for some other miscelanious problems with Snow Leopard applications. I found the fix for the plug in from PDF on Adobe's website. http://kb2.adobe.com/cps/509/cpsid_50983.html
Following these directions (changing the option from 64-bit, to 32-bit when the application loads), seems to have cured the plug-in for PDF from Adobe and loads the plug in properly.
There is a link, http://kb2.adobe.com/cps/512/cpsid_51248.html for changing the settings similarly for Automator to fix the "save as PDF" in Print.
I've also applied this "suggested fix" to Mail and Address Book, to see if it remedies some of the continued glitching and crashes on my iMac, even after the latest update (10.6.1). No problems with my PBG4, as it's not Snow Leopard nor Intel.
Hope this solution is useful.

I am having the same problem from CS4 Illustrator
cups/error_log shows:
D [10/May/2010:10:53:31 -0700] [Job 87] Opening Distiller
D [10/May/2010:10:53:31 -0700] [Job 87] Starting Distiller job
D [10/May/2010:10:53:31 -0700] [Job 87] Distiller child 26366, exited with status 0
D [10/May/2010:10:53:31 -0700] [Job 87] End of messages
D [10/May/2010:10:53:31 -0700] [Job 87] printer-state=3(idle)
D [10/May/2010:10:53:31 -0700] [Job 87] printer-state-message="/usr/libexec/cups/filter/pstops failed"
D [10/May/2010:10:53:31 -0700] [Job 87] printer-state-reasons=none

[svn] 1313: Fix for the use namespace problems we've been having with ASC ( I hope).

Revision: 1313
Author: [email protected]
Date: 2008-04-20 09:41:41 -0700 (Sun, 20 Apr 2008)
Log Message:
Fix for the use namespace problems we've been having with ASC (I hope). The problem was that the use directive was being defined after we had called finish package. The UseDirectiveNode has a pkgdef ptr, and does different things depending if that ptr is null or not. It should not be null when the UseDirective is inside the package - but since we were generating the UseDirectiveNode after we had called finishPackage the UseDirectiveNode didn't have it's pkgdef ptr set, and so things went awry as the package didn't get set up with all the correct open namespaces. I haven't tested this in authoring/flex but I am pretty sure that this will fix all the problems we're seeing.
Modified Paths:
flex/sdk/trunk/modules/asc/src/java/macromedia/asc/parser/Parser.java

Many thanks.
With those symptoms, I'd try the following document:
Apple software on Windows: May see performance issues and blank iTunes Store
(If there's a SpeedBit LSP showing up in Autoruns, it's usually best to just uninstall your SpeedBit Video Accelerator.)

Possible Fix for the 3.1.1 app crash problem

THIS IS A POSSIBLE FIX ONLY!!!
So like many of you I upgraded to 3.1.1 and after the update all of my apps would no longer work. They contiually crashed to the home screen when I tried to open them. I tried downloading random new apps, deleting all my apps and re-installing them with no luck. I tried reseting the iPod and even restoring it through iTunes. I also tried de-authorizing and re-authorizing my computer. None of these things worked for me. Today I tried to go back to the 2.2.1 update (which is the only one I could find that would download) when I tried to upload that onto my iPod I got an error #20 so I ended up restoring back to 3.1.1 the only difference was i told iTunes to start my iPod as a new one instead of loading it from a backup. This actually worked, the only downside was I lost my favourited websites and all the saved info in my apps but hey, atleast they work.
So long story short try wiping your iPod clean and restoring as a brand new one with the 3.1.1 and it might just just work.

I just purchased the 64GB iPod touch and it had the same issues from the start. While I had the same issue with the apps I also had intermittent problems with movies not working. I reset the entire iPod touch 64gb and re-synced as 'new' (described earlier) and it is working for now. I am planning on loading some new apps and movies and re-syncing to see if it stays working.
Also, I upgraded from 3.1.1 to 3.1.2 and everything stopped working again. I am staying on 3.1.1 as long as this solution keeps working until I see something from Apple addressing this issue.
Apple usually does a better job with their software. I am hoping that this is only a software issue and not a hardware issue.

Wireless Problems: Observations/Possible Fix for Some (No Guarantees)

Hi All:
I have been following our wireless problem threads. To a large extent, they revolve around lost connections, weak signals, etc. On my machine, I previously noticed what appeared to be wide fluctuations in signal strength, although I could almost always pick up one distant network that has to be at least 125' away regardless of my apparent signal strength. Also, I never lost my connection. I also have noticed that my Windows notebooks pick up more networks than my MBP, even though some must be farther away than 125'.
Recently, I had to reinstall all my software. Once resolved I'll explain why and what to look out for. Anyway, before the reinstall, I had done all updates. When I reinstalled, I also did all updates. The bottom line is that I have not seen the wide fluctuations in signal strength since reinstalling. Sometimes I see more networks than I am used to seeing.
Am I suggesting that you reinstall to eliminate the types of problems mentioned above? Definitely not especially if your problem is pretty minor. However, if your problem is significant, then think about it. Perhaps a greater than expected number of partially bad factory installs accounts for some of our problems.
I finished my reinstall only about 24 hours ago. I'll continue to monitor and will post back if I begin to see the wide signal strength fluctuations again.

Nope, thanks. I certainly advocate all trying any possible fixes prior to taking the drastic step of reinstalling. Hope the update works for all. I must of installed it yesterday with a number of other updates. Thus, it wasn't what "fixed" my system. But, it looks like it didn't hurt it either. Both are good to know:) Gosh, and looking at some of the recent posts in this category, I am glad that none of the recent updates hosed anything on my machine. Then, I'd me reinstalling again and being more selective about the updates.
I have to admit I have been throwing caution to the wind on doing all the updates. I think I'd better go back to my old style of seeing if there are update rumblings before I install them.
Message was edited by: donv (The Ghost)
Message was edited by: donv (The Ghost)
Message was edited by: donv (The Ghost)

Possible fix for embed tag problems in Safari 5.1 - Quicktime 7.6.6

I would be grateful if anyone can confirm the following problem and fix:
A user of my website reported that embedded audio (mp3) files ceased playing after installing Safari 5.1 on OS X 10.6.8. I updated my test machine's Safari from 5.0 to 5.1 and confirmed the issue. Some audio would play, some wouldn't. Wierder, a random selection of Javascript-triggered embedded audio would report, "Error calling method on NPObject".
I had a very similar issue with 64-bit Mac Firefox 5 and Quicktime Plug-in 7.6.6. In the case of Firefox 5, the fix was to open Get Info... on Firefox and select 32-bit mode (this also stopped an annoying Quicktime dialog).
The Safari problem with embedded mp3's didn't occur under a fresh user account, so I came up with a possible fix:
In Safari, choose "Empty Cache...", followed by "Reset Safari", checking only "Remove all website data" (if you don't want to lose your auto-fill, passwords and history).
My system seems to have recovered its senses... I'm just wondering if the fix above was what did the trick.
Cheers,
Chris

I followed these steps and it did not fix my problem. I still click on an mp3 link and it downloads, rather than opening in the browser.
It gives me the option of choosing, and works both ways (download/open) in Firefox.
sample link: AccNoir+Fest+2011+PRA+mp3.mp3
Curiously, if I click "Open With" on the dowloaded file and tell it to open in Safari, it opens fine like I want. So it's not that Safari can't, it just isn't being told properly.

Possible fix for CPU temp problem found.

Well, one day I decided to take the heatsink off of the nForce3 chip and put some good ol' Arctic Silver thermal compound on there. I figured it might help with overclocking and whatnot. When I took it off, look what I found(!):
Imagine my surprise! Why did they even bother? Ridiculous. After removing their mistake, I put some Arctic Silver on there and re-attached the MSI heatsink (someday I'll probably buy a much better one for it). I've noticed after a couple of days (it takes a little while for the thermal compound to set in) that the CPU temp doesn't appear to fluctuate wildly anymore. Before I was getting crazy jumps from 45C to 65C, but now it hovers around 45C-47C idle and a little over 50C stressed. I've also noticed that my overclocks are a bit more stable now too. For those of you wondering, I'm using BIOS v1.1 at the moment (haven't tried v1.42 yet).
Can anyone confirm these findings? Maybe something else I did fixed my CPU temp issue (I do fiddle with the BIOS quite a bit). My guess is that the nForce3 has a part in determining/reporting the CPU temperature.
I hope this actually is a fix for some of you out there, but don't get your hopes up too high until at least one other person can confirm my theory.

It's very easy to remove the MSI plate. Using a pair of needle-nose pliers pinch the fins on the heat sink on one side together (one at the top, one at the bottom). You don't have to do it too much and be careful. This provides enough slack for the plate to drop out with some slight assistance. Well, that's how I did mine.
I then attached a 40mm fan by screwing into the gaps between the two fins. Only on the one side mind (so 2 screws in total). It holds the fan fine, no rattling.
I have some Artic Silver adhesive and I did consider leaving the MSI plate in place and fixing the fan to it. But I wasn't sure how secure it would be. Plus the plate rattles already, imagine how it would behave with a fan stuck to it.
Unfortunately, I forgot to make a note of the NB temperature before I did it. And I can't for the life of me remember what it was. So I can't say, for sure, how it has effected the temperature. I'm sure it has though.
I suppose it's easy enough to disconnect the fan to find out. I might try that later...
Running at 230x10 (stock = 200x10), MBM reports:
Case = 37C
CPU = 35C
Sensor 3 = 49C
The sensors are labelled by MBM, so I am assuming they respond to the correct items, ie the CPU temp is actually the CPU temp.
This is after a hour or so with Azureus running, mIRC open, a couple of IE windows and SETI running at ~97% CPU
When I take the side off to disconnect the fan again, I will take a picture.

Possible temporary fix for mouse scroll wheel problem in Lion

This is a potential temporary fix for those users of Lion who are unable to fix the reversed mouse scroll wheel issue. I myself have a Microsoft Arc Mouse (not the touch version but the original version) and when I went into the mouse system preferences there was no checkmark box option to return the scroll wheel to its original configuration. When I called Apple about it I was told it's an issue with Lion not recognizing the mouse as being able to reverse the scroll wheel and that Microsoft will need to update the firmware to allow for this change. On a whim, I tried out my wife's Logitech mouse (can't remember the model but it's a fairly recent one) and checked the system preferences. This time there was the checkmark box to allow the scroll wheel to be returned to its original configuration and I could use the scroll wheel as normal. When I plugged my Arc Mouse back in, the scroll wheel had reverted to its original configuration of rotate the wheel down for down scroll and up for up scroll.
So, for those of you who are unable to correct your scroll wheel through preferences, you might want to try plugging in another mouse, making the correction in system preferences, and then plug your original mouse back in.

I mean it. Apple makes major changes in the way things have worked for years, then makes that change the default, causing 1m people to struggle. Bad Bad App le.
There other changes like this in Lion as well, which are arbitrary and are "App le" policy now, which even App le themselves do not follow! (e.g. Cmd-Delete for "Don't Save" in a few App le applications, where 900 million people have used Cmd-<first letter of button> already, for years)
And yes, I did have to go next door and borrow a mouse. "Why?" they said... "I have a Mac" I said. "<laughter> get a real computer" they said. App le does itself no favors by pulling this stuff.
Many of us cannot buy new equipment when arbitrary changes are made, and "get a new driver" is a slap in the face, especially when such changes as Reversing scroll for many-millions could easily be done by making the "new way" an Option, not a default.
Don't get me wrong, Mac and iPhone etc are way ahead of MS and all, but the rabid arrogance inside App le is App aulling.

Possible fix for unable to eject ipod, files are in use by another program

If you get the above message and are using itunes 7, this may be a possible fix. Open itunes and connect your ipod. When you get the main screen, uncheck the box "open itunes when this ipod is connected" and then click apply in the lower right of the screen. After your ipod has finished updating (top of itunes says update complete) you must eject the ipod using the safely remove hardware from your tray in the taskbar. Unplug you ipod, close itunes. Now, open itunes and connect your ipod. After it updates, you should safely remove the ipod. Good luck.
pc Windows XP Pro

Easy way. Reset the iPod, then disconnect when you see the Apple logo.
Another way. Hold ctr-alt-del to bring up the Windows Task Manager. Go to the Processes tab and look for iTunesHelper.exe and iPodService.exe. Select them and hit the End Process button. Close the Windows Task Manager Window and try ejecting the iPod via the safely remove hardware method.
  If you are still having problems you can try one more thing. Right click on the My Computer icon and select Manage from the list of actions. Go to the Services and Applications item and from there the services item. Double click on the services item to bring up the list of services currently installed on your computer. Look for the iPod Service and double click on it. From the new window select Stop. Now try again to eject using the safely remove hardware option.
  If all else fails shut down the computer and disconnect the iPod.

Possible fix for UJ-815 Superdrive problem

Similar Messages

Maybe you are looking for