Jump to content

Scrambled sector or bad sector?


Ken852

Recommended Posts

Hello!

I have a set of 3 discs here in a series of Ask Video software tutorials. One of them is giving me problems. ImgBurn cannot read it for some reason. The reason given in the error message is a bit cryptic so I figured I would make a post and ask about it. I'm sorry of this question has been asked before, but I have tried using the search and the keywords that appear in my error message and I didn't find anything relevant.

Read-of-Scrambled-Sector-Without-Authentication.png.ab03deed2cb528b3602897ba4ed3e4db.png

I'm curious about the "Read of Scrambled Sector Without Authentication". Does that mean that the said sector is scrambled or simply bad (defective)? The disc appears to be in a very good condition, it looks like brand new.

Here is the log.

I 21:50:23 Operation Started!
I 21:50:23 Source Device: [0:0:0] TSSTcorp CDDVDW SH-224DB SB00 (E:) (SATA)
I 21:50:23 Source Media Type: DVD-RW (Book Type: DVD-RW) (Disc ID: RITEKW01)
I 21:50:23 Source Media Supported Read Speeds: 4x, 6x, 8x, 12x
I 21:50:23 Source Media Supported Write Speeds: 1x, 2x
I 21:50:23 Source Media Sectors: 953,616 (Track Path: PTP)
I 21:50:23 Source Media Size: 1,953,005,568 bytes
I 21:50:23 Source Media Volume Identifier: CubaseSX3Level2
I 21:50:23 Source Media Volume Set Identifier: NOT_SET
I 21:50:23 Source Media Application Identifier: TOAST ISO 9660 BUILDER COPYRIGHT (C) 1997-2004 ROXIO, INC. - HAVE A NICE DAY
I 21:50:23 Source Media File System(s): ISO9660, Joliet
I 21:50:23 Read Speed (Data/Audio): MAX / MAX
I 21:50:23 Hardware Read Error Retries: 2
I 21:50:23 Destination File: C:\Users\Me\Desktop\Optical Discs\CubaseSX3Level2.iso
I 21:50:23 Destination Free Space: 23,721,484,288 Bytes (23,165,512.00 KiB) (22,622.57 MiB) (22.09 GiB)
I 21:50:23 Destination File System: NTFS
I 21:50:23 File Splitting: Auto
I 21:50:24 Read Speed - Effective: 5x - 12x
I 21:50:31 Reading Session 1 of 1... (1 Track, LBA: 0 - 953615)
I 21:50:31 Reading Track 1 of 1... (MODE1/2048, LBA: 0 - 953615)
W 21:50:32 Failed to Read Sectors 832 - 863 - Reason: Read of Scrambled Sector Without Authentication
W 21:50:32 Failed to Read Sector 848 - Reason: Read of Scrambled Sector Without Authentication
W 21:50:32 Sector 848 maps to File: \CubaseSX3Level2.exe
W 21:50:32 Retrying (1 of 5)...
W 21:50:32 Retry Failed - Reason: Read of Scrambled Sector Without Authentication
W 21:50:32 Retrying (2 of 5)...
W 21:50:32 Retry Failed - Reason: Read of Scrambled Sector Without Authentication
W 21:50:32 Retrying (3 of 5)...
W 21:50:32 Retry Failed - Reason: Read of Scrambled Sector Without Authentication
W 21:50:32 Retrying (4 of 5)...
W 21:50:32 Retry Failed - Reason: Read of Scrambled Sector Without Authentication
W 21:50:32 Retrying (5 of 5)...
W 21:50:32 Retry Failed - Reason: Read of Scrambled Sector Without Authentication
W 21:51:46 Retrying (6)...
W 21:51:46 Retry Failed - Reason: Read of Scrambled Sector Without Authentication
W 21:51:49 Failed to Read Sector 848 - Reason: Read of Scrambled Sector Without Authentication
W 21:51:49 Sector 848 maps to File: \CubaseSX3Level2.exe
W 21:51:50 Failed to Read Sector 850 - Reason: Read of Scrambled Sector Without Authentication
W 21:51:50 Sector 850 maps to File: \CubaseSX3Level2.exe
W 21:51:50 Retrying (1 of 5)...
W 21:51:50 Retry Failed - Reason: Read of Scrambled Sector Without Authentication
W 21:51:50 Retrying (2 of 5)...
W 21:51:50 Retry Failed - Reason: Read of Scrambled Sector Without Authentication
W 21:51:50 Retrying (3 of 5)...
W 21:51:50 Retry Failed - Reason: Read of Scrambled Sector Without Authentication
W 21:51:50 Retrying (4 of 5)...
W 21:51:50 Retry Failed - Reason: Read of Scrambled Sector Without Authentication
W 21:51:50 Retrying (5 of 5)...
W 21:51:50 Retry Failed - Reason: Read of Scrambled Sector Without Authentication
W 21:51:51 Failed to Read Sector 850 - Reason: Read of Scrambled Sector Without Authentication
W 21:51:51 Sector 850 maps to File: \CubaseSX3Level2.exe
W 21:51:51 Failed to Read Sector 852 - Reason: Read of Scrambled Sector Without Authentication
W 21:51:51 Sector 852 maps to File: \CubaseSX3Level2.exe
W 21:51:51 Retrying (1 of 5)...
W 21:51:51 Retry Failed - Reason: Read of Scrambled Sector Without Authentication
W 21:51:51 Retrying (2 of 5)...
W 21:51:51 Retry Failed - Reason: Read of Scrambled Sector Without Authentication
W 21:51:51 Retrying (3 of 5)...
W 21:51:51 Retry Failed - Reason: Read of Scrambled Sector Without Authentication
W 21:51:51 Retrying (4 of 5)...
W 21:51:52 Retry Failed - Reason: Read of Scrambled Sector Without Authentication
W 21:51:52 Retrying (5 of 5)...
W 21:51:52 Retry Failed - Reason: Read of Scrambled Sector Without Authentication
E 21:51:54 Failed to Read Sector 852 - Reason: Read of Scrambled Sector Without Authentication
E 21:51:54 Sector 852 maps to File: \CubaseSX3Level2.exe
E 21:51:54 Failed to Read Sectors!
E 21:51:55 Operation Failed! - Duration: 00:01:30
E 21:51:55 Average Read Rate: 18 KiB/s (0.0x) - Maximum Read Rate: 18 KiB/s (0.0x)

 

Link to comment
Share on other sites

Why would a software disc be released on a DVD-RW instead of a pressed disc?  Is this disc an archive you had of an original?

 

You're probably encountering an unreadable sector on an old DVD-RW that has simply lost its potency.  I would try using File/Windows Explorer to copy the contents in the root directory of this DVD-RW to some other location.  It will probably fail because I think your disc has probably gone bad.  Rewritable discs don't have longevity for archival purposes.  If it does succeed, you can create a new ISO from the contents you copied.

 

The scrambled sector message is probably the only interpretation the software could come up with for the error returned by the drive.  I doubt there really is a scrambled sector.  I've never heard of scrambled sectors, actually.  In fact, I don't see how you can scramble sectors.  You can apply copy protection on DVD Video discs, but that's not based on sector protection.

Link to comment
Share on other sites

The disc is not an original.

Luckily it just so happens I have an LG drive in another computer. One of the odd ones that works with Blue Ray as well as HD DVD discs (and DVD and CD of course). So when I insert the same disc in that drive and try to use ImgBurn to write an ISO file it's a total success!

So it would seem it's the first optical drive that does not like this particular disc? Or the other way around...

This is the offending drive:

TSSTcorp CDDVDW SH-224DB SB00

This is an abbreviation for "Toshiba Samsung Storage Technology". But it clearly says "SAMSUNG" on the front of it? A case of too many chefs? :rolleyes: Are these Samsung drives any good?... I only purchased this one because it was the only one available at a local computer store.

Is there anything I can do from software side of things to make this drive read the disc just as well as the LG drive? Any of those fancy settings that could help?

 

Edited by Ken852
Link to comment
Share on other sites

I noticed that there is a firmware update available from "Firmware HQ" at the following link:

https://www.firmwarehq.com/drive.php?inq=TSSTcorp CDDVDW SH-224DB&chk=252

I never heard of such a place. Can this site be trusted? :/

I don't really want to brick my drive. But if it would help in the long run, I might want to update from SB00 to SB01 firmware. I don't know if it would solve the current problem at hand of course. It's a gamble for sure.

Link to comment
Share on other sites

Are you able to try your Samsung drive in that other machine?

It's quite a specific error and seems weird a drive would return it when reading a normal DVD-RW disc. Maybe you've some software on your PC that's messing with the error codes?

There's nothing that can be done software wise to work around this issue. If that's really what the drive thinks the problem is, you just have to live with it.

The firmware update might fix it, but you'd have to try and find a changelog for SB01 somewhere. FirmwareHQ is fine, we helped collect all the firmware and build it.

Link to comment
Share on other sites

5 hours ago, Ken852 said:

The disc is not an original.

Luckily it just so happens I have an LG drive in another computer. One of the odd ones that works with Blue Ray as well as HD DVD discs (and DVD and CD of course). So when I insert the same disc in that drive and try to use ImgBurn to write an ISO file it's a total success!

So it would seem it's the first optical drive that does not like this particular disc? Or the other way around...

This is the offending drive:


TSSTcorp CDDVDW SH-224DB SB00

This is an abbreviation for "Toshiba Samsung Storage Technology". But it clearly says "SAMSUNG" on the front of it? A case of too many chefs? :rolleyes: Are these Samsung drives any good?... I only purchased this one because it was the only one available at a local computer store.

Is there anything I can do from software side of things to make this drive read the disc just as well as the LG drive? Any of those fancy settings that could help?

 

That's quite unusual.  Usually, it's a case of LG's being unable to read discs that other drives will read.  I've been using LG's for a long time now and I've found they're not the best readers, sometimes refusing to read discs other drives do.  My LG WH16NS60 BD burner appears to be much better in the reading aspect.

 

Very few optical products whose name is on the package were actually made by them.  Most companies farm out the production to a select few manufacturers and just slap their name on them.

Link to comment
Share on other sites

I have imaged all three discs with the LG drive. It's the GGW-H20L and it was given to me by a friend of mine. I know he praised it and said it was one of the best out there, winning many awards and whatnot. I don't know if it's true, but I can see it's valued highly by user reviews and it still has quite a price tag for something this old when I look at it online. Very few stores have in stock now. But it does do HD DVD, and it does burn not only read Blue Ray. So I can see why it would be priced accordingly. But I know nothing about LG optical drives and how reliable or unreliable they are.

But this is quite interesting! Here are the logs from both the LG and the Samsung drive, for the first disc that they both can read.

Samsung disc info
 

TSSTcorp CDDVDW SH-224DB SB00 (SATA)
Current Profile: DVD+RW

Disc Information:
Status: Complete
State of Last Session: Complete
Erasable: Yes
Formatted: No (Started)
Sessions: 1
Sectors: 2,295,104
Size: 4,700,372,992 bytes
Time: 510:03:29 (MM:SS:FF)
MID: RITEK-004-48
Supported Read Speeds: 4x, 6x, 8x
Current Read Speed: 3.3x - 8x

File System Information:
Sectors: 482,305
Size: 987,760,640 bytes
Time: 107:12:55 (MM:SS:FF)

TOC Information:
Session 1... (LBA: 0)
-> Track 01  (Mode 1, LBA: 0 - 2295103)
-> LeadOut  (LBA: 2295104)

Track Information:
Session 1...
-> Track 01 (LTSA: 0, LTS: 2295104, LRA: 0)

Physical Format Information (ADIP):
Disc ID: RITEK-004-48
Book Type: DVD+RW
Part Version: 2
Disc Size: 120 mm
Maximum Read Rate: Not Specified
Number of Layers: 1
Track Path: Parallel Track Path (PTP)
Linear Density: 0.267 um/bit
Track Density: 0.74 um/track
First Physical Sector of Data Area: 196,608
Last Physical Sector of Data Area: 2,491,711
Last Physical Sector in Layer 0: 0

Physical Format Information (Last Recorded):
Disc ID: RITEK-004-48
Book Type: DVD+RW
Part Version: 2
Disc Size: 120 mm
Maximum Read Rate: Not Specified
Number of Layers: 1
Track Path: Parallel Track Path (PTP)
Linear Density: 0.267 um/bit
Track Density: 0.74 um/track
First Physical Sector of Data Area: 196,608
Last Physical Sector of Data Area: 1,168,079
Last Physical Sector in Layer 0: 0

Samsung log

I 21:35:41 Operation Started!
I 21:35:41 Source Device: [0:0:0] TSSTcorp CDDVDW SH-224DB SB00 (E:) (SATA)
I 21:35:41 Source Media Type: DVD+RW (Book Type: DVD+RW) (Disc ID: RITEK-004-48)
I 21:35:41 Source Media Supported Read Speeds: 4x, 6x, 8x
I 21:35:41 Source Media Supported Write Speeds: 4x
I 21:35:41 Source Media Sectors: 482,305 (Track Path: PTP)
I 21:35:41 Source Media Size: 987,760,640 bytes
I 21:35:41 Source Media Volume Identifier: My Disc
I 21:35:41 Source Media Volume Set Identifier: NOT_SET
I 21:35:41 Source Media Application Identifier: TOAST ISO 9660 BUILDER COPYRIGHT (C) 1997-2004 ROXIO, INC. - HAVE A NICE DAY
I 21:35:41 Source Media File System(s): ISO9660, Joliet
I 21:35:41 Read Speed (Data/Audio): MAX / MAX
I 21:35:41 Hardware Read Error Retries: 2
I 21:35:41 Destination File: C:\Users\Me\Desktop\Optical Discs\CubaseSX3Level1 .iso
I 21:35:41 Destination Free Space: 24,684,437,504 Bytes (24,105,896.00 KiB) (23,540.91 MiB) (22.99 GiB)
I 21:35:41 Destination File System: NTFS
I 21:35:41 File Splitting: Auto
I 21:35:42 Read Speed - Effective: 3.3x - 8x
I 21:35:42 Reading Session 1 of 1... (1 Track, LBA: 0 - 2295103)
I 21:35:42 Reading Track 1 of 1... (MODE1/2048, LBA: 0 - 2295103)
I 21:35:42 Reading File System Area of Track 1... (LBA: 0 - 482304)
I 21:38:35 Operation Successfully Completed! - Duration: 00:02:53
I 21:38:36 Average Read Rate: 5,575 KiB/s (4.1x) - Maximum Read Rate: 6,585 KiB/s (4.9x)

LG disc info
 

HL-DT-ST BD-RE  GGW-H20L YL05 (SATA)
Current Profile: DVD+RW

Disc Information:
Status: Complete
State of Last Session: Complete
Erasable: Yes
Formatted: No (Started)
Sessions: 1
Sectors: 2 295 104
Size: 4 700 372 992 bytes
Time: 510:03:29 (MM:SS:FF)
MID: RITEK-004-48
Supported Read Speeds: 2,4x, 4,8x, 8x, 10x
Current Read Speed: 4,1x - 10x

File System Information:
Sectors: 482 305
Size: 987 760 640 bytes
Time: 107:12:55 (MM:SS:FF)

TOC Information:
Session 1... (LBA: 0)
-> Track 01  (Mode 1, LBA: 0 - 2295103)
-> LeadOut  (LBA: 2295104)

Track Information:
Session 1...
-> Track 01 (LTSA: 0, LTS: 2295104, LRA: 2295103)

Physical Format Information (Last Recorded):
Disc ID: RITEK-004-48
Book Type: DVD+RW
Part Version: 2
Disc Size: 120 mm
Maximum Read Rate: Not Specified
Number of Layers: 1
Track Path: Parallel Track Path (PTP)
Linear Density: 0.267 um/bit
Track Density: 0.74 um/track
First Physical Sector of Data Area: 196 608
Last Physical Sector of Data Area: 1 168 079
Last Physical Sector in Layer 0: 0

LG log

I 14:27:09 Operation Started!
I 14:27:09 Source Device: [0:0:0] HL-DT-ST BD-RE  GGW-H20L YL05 (F:) (SATA)
I 14:27:09 Source Media Type: DVD+RW (Book Type: DVD+RW) (Disc ID: RITEK-004-48)
I 14:27:09 Source Media Supported Read Speeds: 2,4x, 4,8x, 8x, 10x
I 14:27:09 Source Media Supported Write Speeds: 2,4x, 4x
I 14:27:09 Source Media Sectors: 482 305 (Track Path: PTP)
I 14:27:09 Source Media Size: 987 760 640 bytes
I 14:27:09 Source Media Volume Identifier: My Disc
I 14:27:09 Source Media Volume Set Identifier: NOT_SET
I 14:27:09 Source Media Application Identifier: TOAST ISO 9660 BUILDER COPYRIGHT (C) 1997-2004 ROXIO, INC. - HAVE A NICE DAY
I 14:27:09 Source Media File System(s): ISO9660, Joliet
I 14:27:09 Read Speed (Data/Audio): MAX / MAX
I 14:27:09 Destination File: C:\Users\Me\Desktop\Optical Discs\CubaseSX3Level1 .iso
I 14:27:09 Destination Free Space: 143 504 498 688 Bytes (140 141 112,00 KiB) (136 856,55 MiB) (133,65 GiB)
I 14:27:09 Destination File System: NTFS
I 14:27:09 File Splitting: Auto
I 14:27:10 Read Speed - Effective: 4,1x - 10x
I 14:27:10 Reading Session 1 of 1... (1 Track, LBA: 0 - 2295103)
I 14:27:10 Reading Track 1 of 1... (MODE1/2048, LBA: 0 - 2295103)
I 14:27:10 Reading File System Area of Track 1... (LBA: 0 - 482304)
I 14:29:31 Operation Successfully Completed! - Duration: 00:02:20
I 14:29:31 Average Read Rate: 6 890 KiB/s (5.1x) - Maximum Read Rate: 8 179 KiB/s (6.0x)

One thing that immediately jumps out when you compare the disc info section is this:
 

Track Information:
Session 1...
-> Track 01 (LTSA: 0, LTS: 2295104, LRA: 0)

Physical Format Information (ADIP):
Disc ID: RITEK-004-48
Book Type: DVD+RW

This is using the Samsung drive. Compare this to this from the LG drive.
 

Track Information:
Session 1...
-> Track 01 (LTSA: 0, LTS: 2295104, LRA: 2295103)

Physical Format Information (Last Recorded):
Disc ID: RITEK-004-48
Book Type: DVD+RW

What is the LRA? And why does one say "ADIP" and the other says "Last Recorded"?

It seems like LRA has something to do with sectors and Samsung got it wrong (zero) and LG got it right (2295103).

I should note that both computers are using ImgBurn 2.5.8.0 and are custom built by yours truly, running on Windows 10 and Ryzen 3600X (Asus ROG Strix B550 on both, but different variants). I guess I could pull out the Samsung drive and install it in the other computer to satisfy my curiosity, but it's not something I will do any time soon. Maybe some time later. I am also holding off upgrading the firmware till I have all the discs done.

 

Edited by Ken852
Link to comment
Share on other sites

LG drives are basically the best BD's out there, even though they have their problems.  However, they have the least problems of all the BD drives out there.  LG also has a very good replacement policy.  I just recently had a replacement done on my WH16NS60 because it was improperly writing 8x Imation Ritek DVD+RW discs.  I just had to pay to ship the drive to LG and they paid to ship me a refurbished drive.  They've done that for me for years.  Even when I've had refurbished drives sent to me, they have many times replaced the refurbished drives with refurbished drives.  LG drives generally will fail before the one year warranty period has expired, but most BD drives do that, too.  That's one of the LG drawbacks.  As I previously mentioned, LG DVD drives were known to be picky readers in the past.  The first LG DVD burner I had was a clunker.  It burned discs that played with skips on playback, even on quality media.

 

BTW, there may be something you can try on that drive that won't image the disc properly.  You could try changing the Interface.    Tools --> Settings --> I/O --> Page 1 --> Interface  It's probably set at SPTI - Microsoft.  Try Elby CDIO or the other Interfaces.  You may have better luck with one of those.

Link to comment
Share on other sites

3 minutes ago, Ken852 said:

Why am I getting comma separators in ImgBurn on one computer but not the other?


Size: 4,700,372,992 bytes

How do I disable this?

 

 

There may be a Windows setting that displays file sizes with commas that can be disabled.  I don't know.  Or, it may be down to the different drives.  Are you getting the same results regardless of what drive you're using on each computer?  One drive may be returning commas in its results but another isn't.

Link to comment
Share on other sites

LRA is last recorded address.
If you’ve got the track size, it isn’t overly required. Some drives don’t bother returning that info.

The addition of ADIP info might be down to the date of the firmware in the LG drive. The adip info doesn’t change, even once you’ve burnt the disc. So the book type field will show the real type of disc. The last recorded info can be changed as a result of burning, and that’s where you’d then see a disc have its book type changed to dvdrom for compatibility reasons.

As for the commas, that’s down to your regional settings. The program uses what your OS is configured for.

Link to comment
Share on other sites

10 minutes ago, dbminter said:

BTW, there may be something you can try on that drive that won't image the disc properly.  You could try changing the Interface.

I did come across that as I was searching for a way to disable the commas. :lol: I will try it, thanks!

8 minutes ago, LIGHTNING UK! said:

LRA is last recorded address.
If you’ve got the track size, it isn’t overly required. Some drives don’t bother returning that info.

The addition of ADIP info might be down to the date of the firmware in the LG drive. The adip info doesn’t change, even once you’ve burnt the disc. So the book type field will show the real type of disc. The last recorded info can be changed as a result of burning, and that’s where you’d then see a disc have its book type changed to dvdrom for compatibility reasons.

I didn't understand half of that. Are you saying my Sammy is lazy? :)

Nothing odd here then in these logs?

11 minutes ago, LIGHTNING UK! said:

As for the commas, that’s down to your regional settings. The program uses what your OS is configured for.

Thanks! I will look into that.

So this is not related to one of the fixes in 2.5.8.0?

Quote

Fixed: Cosmetic issue displaying numbers when the user's 'thousands separator' is set to nothing.

 

Link to comment
Share on other sites

Yes, they are both reporting 2.5.8.0 in the log. I like to clear the log after starting up ImgBurn so I have a clean slate, because I store the log after reading a disc along with the other files.

It's not you, it's me. I was starting to doubt myself after seeing that line in the changelog. :D

Computer with LG drive:

I 14:21:48 ImgBurn Version 2.5.8.0 started!
I 14:21:48 Microsoft Windows 8 Professional x64 Edition (6.2, Build 9200)
I 14:21:48 Total Physical Memory: 16 679 232 KiB  -  Available: 11 221 724 KiB
I 14:21:48 Initialising SPTI...
I 14:21:48 Searching for SCSI / ATAPI devices...
I 14:21:48 -> Drive 1 - Info: HL-DT-ST BD-RE  GGW-H20L YL05 (F:) (SATA)
I 14:21:48 Found 1 HD DVD-ROM/BD-RE!

Computer with Samsung drive:

I 11:42:13 ImgBurn Version 2.5.8.0 started!
I 11:42:13 Microsoft Windows 8 Professional x64 Edition (6.2, Build 9200)
I 11:42:13 Total Physical Memory: 16,688,180 KiB  -  Available: 12,222,308 KiB
I 11:42:13 Initialising SPTI...
I 11:42:13 Searching for SCSI / ATAPI devices...
I 11:42:13 -> Drive 1 - Info: ELBY CLONEDRIVE 1.4 (D:) (SCSI)
I 11:42:13 -> Drive 2 - Info: TSSTcorp CDDVDW SH-224DB SB00 (E:) (SATA)
I 11:42:13 Found 1 DVD±RW/RAM and 1 BD-ROM/HD DVD-ROM!

But it all checks out. The one that has the commas is the computer with the Samsung drive and this is what the Customize Format box looks like here.

Customize-Format.png.c569c29a4823b1c891862c1e8a3180b3.png

So the theory appears to be solid. I use the US settings whenever possible. I must have forgotten to change that on the other computer.

With that said, Windows is a mess when it comes to localisation, and with Windows 10 they have so many things going on with their Store or "modern" apps it's a real challenge keeping track of what to change where. But as for ImgBurn, it is doing the right thing by respecting the system settings rather than overriding them.

For the record, the dialog box above can be located by going to Control Panel, Clock and Region, Region, and then clicking on "additional settings".

 

Edited by Ken852
Added location for the dialog box.
Link to comment
Share on other sites

If I may just add that the first disc in the series displays the label "My Disc" on both the problem drive and the good drive.

Here it is on the good drive (LG):

imgburn-label-my-disc-lg.png.9a03933137e5c78812cfb6d63d3cb037.png

Here it is on the bad drive (Samsung):

imgburn-label-my-disc-samsung.png.f56254d8f3024b517f53478766191704.png

However when I image the disc on the good drive or the bad drive, or just view the disc in File Explorer on either drive, I can see the label "CubaseSX3Level1" which is quite different from what I'm seeing in ImgBurn.

file-explorer-label-CubaseSX3Level1-samsung.png.6a9b786fb3b10ff05bbf880bda770af6.png

This is not the case with the other two discs as they properly display "CubaseSX3Level2" and "CubaseSX3Level3" respectively, in File Explorer as well as ImgBurn.

Will someone please offer an explanation for this? It does not necessarily mean that something is wrong with the first disc (in addition to the second disc), as both drives can read this disc. I just have never encountered this kind of thing where ImgBurn and File Explorer tell different stories, so I'm curious why that is.

Link to comment
Share on other sites

It might be getting the 'CubaseSX3Level1' name from an autorun file. It's correctly showing 'My Disc' when you look at the properties (matching what ImgBurn shows).

ImgBurn displays the volume label from the (best) file system. It doesn't look at the autorun file.

You can hover your mouse over where it says the volume label and it'll show you info from some other fields in the file system descriptors too.

Link to comment
Share on other sites

Yeah, you were right, it's getting the name from the Autorun file.

[autorun]
label=CubaseSX3Level3
open=CubaseSX3Level3.exe
icon=ask.ico

When I hover over the label in ImgBurn I see the same details for both discs, except for Volume Identifier which differs.

Volume Identifier: CubaseSX3Level3
Volume Set Identifier: NOT_SET
Application Identifier: TOAST ISO 9660 BUILDER COPYRIGHT (C) 1997-2004 ROXIO, ING. - HAVE A NICE DAY
Data Preparer Identifier: Unknown
Implementation Identifier: Unknown
Publisher Identifier: Unknown
System Identifier: APPLE COMPUTER,
File System(s): ISO9660, Joliet

I may have left the label as "My Disc" when I made the copy. But I definitely did not use an Apple computer.

On 3/31/2021 at 12:44 AM, LIGHTNING UK! said:

ImgBurn displays the volume label from the (best) file system. It doesn't look at the autorun file.

What file system is that?

Link to comment
Share on other sites

I think it depends on whatever file systems are present on the disc.  I would guess UDF is preferred over ISO9660 since ImgBurn seems to display the label from UDF, if it's present, whereas Windows will display the ISO9960?  I don't know that for sure, though.

 

Link to comment
Share on other sites

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.