[Veltliner]

Now who's the culprit here?

I had this incident already twice on my old G5 2.1 Ghz iMac.

You insert a DVD (correct region), and you get the message "this disc cannot be read by this computer"

Only options: "Ignore" and "Eject" (just as I like it).

Archive & Install brings everything back to normal.

This time it had definitely been caused by the failed partitioning at GUID using disc utility.

Why do I think that? That's the only thing I have done (except backing up the whole drive to an external disc using SuperDuper) that was not everyday's routine. And where something went wrong (After this failed GUID partitioning the iMac didn't shut down, I had to switch him off with the off button)

I just wonder if anyone of you has heard of this thing happen. As I said, I'm just curious, as I know the solution (actually, when it happened the first time, Apple exchanged Logic board and Superdrive to no avail, but the archive & install fixed it).

So, what now, detective? Who's the culprit? Doesn't look like hardware induced. Always goes away after archive & install (done twice so far). Which piece of software would you arrest? (other suspects are: gimp printer driver, hewlett-packard jetdirect 300X on ethernet, a song by Diana Ross, the housing bubble...)

[Cadaver]

A malfunctioning optical drive can produce these symptoms. One type of disc can work (i.e., CD) while the other doesn't (i.e., DVD).

Not saying that this is definitely your diagnosis, but its one possibility.

[AKcrab]

Originally Posted by Cadaver 

A malfunctioning optical drive can produce these symptoms. One type of disc can work (i.e., CD) while the other doesn't (i.e., DVD).

Not saying that this is definitely your diagnosis, but its one possibility.

This is a different issue. We just had one of these show up in the shop. Booted from an external drive running 10.4.10 or even 10.5, all discs worked fine. Booted from the internal drive running 10.4.10, DVD's failed *every* time.

Just like the original poster, an archive and install fixed it right up. We attempted the 10.4.10 combo update as a first try, but that didn't do it.

No idea what might have caused it. The client didn't have much software installed.

[Veltliner]

In my case they exchanged the Superdrive and the logic board.

No change.

Archive and Install fixed it.

So it must be software related.