Reply to thread

Message

<blockquote data-quote="MacInWin" data-source="post: 1843050" data-attributes="member: 396914">@krs, normally the burner software does the initialization as part of the burn. Then once the data is burned to the drive, the closing process puts the directory information in place so that the disk is readable and files can be found on the disk. If that closing doesn't work properly, or isn't done at all, the disk is unreadable and sometimes the report is that it is &quot;uninitialized&quot; when it should be reported as &quot;unreadable.&quot; Pressed CDs don't have that issue. But in this case I am very suspicious that this disk has 32 bit software on it, which won't run, so when it tries to mount and the autorun kicks in to try to execute the un-runnable software the failure is interpreted as a disk failure instead of the software failure. Or the disk is in upside down. Good call on that one. Been there, done that, seem to be able to do it again like I had never done it before.</blockquote>

[QUOTE="MacInWin, post: 1843050, member: 396914"] @krs, normally the burner software does the initialization as part of the burn. Then once the data is burned to the drive, the closing process puts the directory information in place so that the disk is readable and files can be found on the disk. If that closing doesn't work properly, or isn't done at all, the disk is unreadable and sometimes the report is that it is "uninitialized" when it should be reported as "unreadable." Pressed CDs don't have that issue. But in this case I am very suspicious that this disk has 32 bit software on it, which won't run, so when it tries to mount and the autorun kicks in to try to execute the un-runnable software the failure is interpreted as a disk failure instead of the software failure. Or the disk is in upside down. Good call on that one. Been there, done that, seem to be able to do it again like I had never done it before. [/QUOTE]

Verification

Name this item 🌈