What is this disc

[Tobim6]

Also I read that Princo is a low quality brand. Is it good that my CD still works from 1998?

[dbminter]

Yes, but my point was you don't have a label side.  So, I'm wondering if it's not a PRR-C74 because that supposedly has only 1 data side and a branded label on the other side.  Plus, I find it difficult to fathom anyone, especially Princo, a bottom of the barrel manufacturer, would make a CD flipper with a CD-R layer on one side and a 33.3 GB BD-R layer on the other.  I've never heard of anyone, let alone Princo, making a CD-R with a BD-R layer on the other side.

[dbminter]

33 minutes ago, Tobim6 said:

Also I read that Princo is a low quality brand. Is it good that my CD still works from 1998?

 

I can't attest to their CD-R quality as I've never used it to my memory, but I have personal experience with their DVD-R, which is junk.  Unreadable after less than a year.

[Tobim6]

How do you know it is a CD and BD flipper?

[dbminter]

Well, you said one side was a CD according to ImgBurn and that the other side was 33.3 GB in size as returned by ImgBurn.  Only BD-R 33.3 GB layers or BD-R DL/TL/XL could return a size of 33.3 GB IF ImgBurn is returning correct values.  Since you're able to get some kind of format data from both sides, it's a flipper.

[Pain]

On 4/1/2025 at 2:26 AM, Tobim6 said:

Hello what is this disc it reads only from one side and on the other side it tries really hard to find a track for like 2 minutes.

It is a CD-R that was sold in 1998. That is a recording side. Opposite side is just Silver color label side.

Manufacturer: Princo. Princo is a company that sells low-quality, cheap garbage media.

Reflection Layer: GOLD. Interestingly, GOLD layer with Cyanine dye. What the......

Dye: Cyanine with tiny amount of UV stabilizer or Cyanine without UV stabilizer(not  Phthalocyanine)

This CD-R was a failed product in terms of its composition. The product itself was practically defective. Normally, when using gold, the dye should have been phthalocyanine. But for some reason, they used cyanine instead, which made the disc extremely vulnerable to light and other environmental factors. As a result, it was a trash CD-R with an extremely short lifespan.

Conclusion.

User fault with a cheap garbage CD-R. This forum is so funny including Beta Team Members.

How could they not even tell the front from the back of a CD-R?

Edited Sunday at 10:55 PM by Pain

[dbminter]

How do you explain ImgBurn returning 33.3 GB capacity on a "label" side?    That's why I didn't recognize it as a label side.

[Pain]

1 hour ago, dbminter said:

How do you explain ImgBurn returning 33.3 GB capacity on a "label" side?    That's why I didn't recognize it as a label side.

It's a malfunction caused by reading an incorrect signal. It happens occasionally and mostly occurs when the label side is silver-colored. That silver-colored label can reflect Laser. Many beginners often confuse the recording side with the label side. That's why.

Edited yesterday at 12:31 AM by Pain

[dbminter]

I had said it could possibly be a false positive for "data."  I tried reading a data label side in my setup, but all I got was an expected unable to read anything return message.

[Pain]

18 minutes ago, dbminter said:

I had said it could possibly be a false positive for "data."  I tried reading a data label side in my setup, but all I got was an expected unable to read anything return message.

 It's not for DATA. It happens occasionally.

 

• Reflection Confuses the Optical Sensor
  DVD-RW drives use laser reflection to detect and read discs. If the label side is overly reflective, the drive might mistake it for the data side or get confused by the unusual reflection pattern.

• Disc Inserted Upside Down (Misread)
  If the drive detects the shiny label side as the readable surface, it might assume the disc was inserted incorrectly. This can lead to incorrect detection of disc type, format, or capacity, sometimes even showing random or incorrect data sizes.

• Format Recognition Error
  The drive might try to interpret the label side and fail to find any logical data structure, which could cause it to report incorrect or bizarre storage sizes (like 0MB or some huge number).

Edited yesterday at 12:58 AM by Pain