Track 1 is smaller on the disc than it is in the image file

[nelsonhf]

Hi LIGHTNING UK!,

 

I have a TSST SH-S203B SB04 and yesterday I faced the "Track 1 is smaller on the disc than it is in the image file" problem with the latest ImgBurn (2.5.1.0). Searching the forum, I found this topic that explains the root cause of the problem (a bug in MediaTek/Samsung/LiteOn firmware) and as I couldn't post a reply to that topic (forum restriction?), I created this one.

 

Both of my Samsung drives, the SH-S203B SB04 (DVD-RW/RAM) and the SH-M522C TS08 (Combo DVD-ROM/CD-RW) have this problem as you can see below:

Image Info:

Session         Track   Type    Index     Start         Length          LBA	
Session 1	Track 1	Mode 1	Index 1	  00:02:00	338:20:25	0 - 1522524	
		Total             338:20:25                     0 - 1522524	

               LeadOut                   338:22:25                     1522525	

Disc info of this image burned with ImgBurn 2.5.1.0 in the SH-S203B SB04:

TSSTcorp CDDVDW SH-S203B SB04 (ATA)
Current Profile: DVD-R

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

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

Same disc now read by the SH-M522C TS08:

TSSTcorp CDW/DVD SH-M522C TS08 (ATA)
Current Profile: DVD-ROM

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

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

Now, the same image burned by Nero 7 on the SH-S203B SB04:

TSSTcorp CDDVDW SH-S203B SB04 (ATA)
Current Profile: DVD-R

TOC Information:
Session 1... (LBA: 0)
-> Track 01  (Mode 1, LBA: 0 - 1522527)
-> LeadOut  (LBA: 1522528)  <<--- Nero padded the image to the next multiple of 16

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

 

This is clearly a firmware bug of MediaTek/Samsung/LiteOn drives and in the other topic, LiteOn admits it and send a test firmware that correct this bug. As I doubt that Samsung will do the same (especially with older drives) and using a program that pads the image (as Nero does) is worst (it breaks UDF standards as stated in the other topic, what can I do? Stay with ImgBurn 2.5.0.0 (as it uses TOC instead of Track info)?

 

I don't know if is possible, but for these buggy drives, in the next version of ImgBurn, can you maybe add an option or condition to use the TOC instead of Track information as in the previous ImgBurn versions?

 

Thanks for yours efforts, patience and ImgBurn of course

[LIGHTNING UK!]

I'm sure if you read that thread properly it says I've implemented a workaround for the problem samsung/liteon drives.

 

You just have to wait for 2.5.2.0

 

Where possibly, build your images with ImgBurn and you won't run into the problem in the first place. ImgBurn's images are always created so their size is a multiple of 16.

[nelsonhf]

Yes, I read in the other thread about your fix for the LTS = LRA problem. Will the next version handle the rounding down problem too?

 

TSSTcorp CDDVDW SH-S203B SB04 (ATA)

Current Profile: DVD-R

 

TOC Information:

Session 1... (LBA: 0)

-> Track 01 (Mode 1, LBA: 0 - 1522524)

-> LeadOut (LBA: 1522525)

 

Track Information:

Session 1...

-> Track 01 (LTSA: 0, LTS: 1522496, LRA: 1522511) LRA and LTS wrong?

TSSTcorp CDDVDW SH-S203B SB04 (ATA)

Current Profile: DVD-R

 

TOC Information:

Session 1... (LBA: 0)

-> Track 01 (Mode 1, LBA: 0 - 1522527)

-> LeadOut (LBA: 1522528) <<--- Nero padded the image to the next multiple of 16

 

Track Information:

Session 1...

-> Track 01 (LTSA: 0, LTS: 1522512, LRA: 1522527) LTS wrongly rounded down. Shouldn't be 1522528?

I forgot to say that the image used is a Windows 7 MSDN image which was created by Microsoft's own CDIMAGE 2.54 utility.

I'm not trying to pressure you. I understand that you are just strictly following the standards, which is a good thing.

 

Thanks for you answer and sorry for any inconvenience.

Edited May 23, 2010 by nelsonhf

[LIGHTNING UK!]

Hmm I must apologise, the two tweaks I've put in place to get around these issues won't actually do anything for this burn and the values your drive is reporting, they're all over the place!

 

I will test with my own S203B and a discovery mode burn of the exact same number of sectors and see what I can do.

 

Nero probably just burnt using the incremental write type, that always seems to pad to 16 anyway.

 

btw, it would have been useful to see the other disc info (i.e. the 'Sectors' info at the top - that's what the 'get capacity' command reports)

[LIGHTNING UK!]

I just tried a DVD-RW in mine with an image exactly the same size as yours and the disc info seems fine.

 

TSSTcorp CDDVDW SH-S203B SB04 (RAID)
Current Profile: DVD-RW

Disc Information:
Status: Complete
State of Last Session: Complete
Erasable: Yes
Sessions: 1
Sectors: 1,522,525
Size: 3,118,131,200 bytes
Time: 338:22:25 (MM:SS:FF)

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

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

Pre-recorded Information:
Manufacturer ID: MKM 01RW6X01

Physical Format Information (Last Recorded):
Book Type: DVD-RW
Part Version: 3
Disc Size: 120mm
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,719,132
Last Physical Sector in Layer 0: 0