wrong label and imp ID

[G0d3L]

Hi to everyone in the forum.

I have used ImgBurn since 2 years and never got any problem (except a buffer problem only on one pc with same configuration as the others but this is secondary) till yesterday when I treid to reburn an old working image (so it's not something releated to an iso problem) and came up with a not playble disc.

I ONLY use Verbatim so it's not a support problem.

When I rechecked what was gone wrong in the procedure I foud that the label and imp ID have cahnged.

Before I usually got:

 

LABEL xg2dvd_ntsc

 

imp ID Sonic Scenarist 3.1

 

File Sys ISO9660

 

UDF 1.02

 

NOW I get:

 

LABEL DVD_ROM

 

imp ID Microsoft CDIMAGE UDF

 

File Sys ISO9660

 

UDF 1.50

 

 

I googled for the problem and found several people with this problem but no aswer.

Any suggestions?

Thanks in advance

[spinningwheel]

Please....pay attention to the bit at the top and post a log.

[mmalves]

Google further and you should find out why it isn't working.

 

Hint: it's not an ImgBurn problem, the problem is in your console

[G0d3L]

Please....pay attention to the bit at the top and post a log.

 

I'm sorry spinningwheel I have read what's on top and didn't post the log 'cause it's not a failed burning instance and thought it didn't matter.

Here it is:

 

TSSTcorp CDDVDW SH-S202J SB02 (ATA)

Current Profile: DVD+R DL

 

Disc Information:

Status: Complete

Erasable: No

Sessions: 1

Sectors: 3.827.488

Size: 7.838.695.424 bytes

Time: 850:35:13 (MM:SS:FF)

 

File System Information:

Sectors: 77.472

Size: 158.662.656 bytes

Time: 17:14:72 (MM:SS:FF)

 

TOC Information:

Session 1... (LBA: 0)

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

-> LeadOut (LBA: 3827488)

 

Track Information:

Session 1...

-> Track 01 (LTSA: 0, TS: 3827488, LRA: 0)

 

Disc Control Blocks Information:

TSSTcorp SH-S202J

 

Physical Format Information (ADIP):

Disc ID: MKM-003-00

Book Type: DVD+R DL

Part Version: 1

Disc Size: 120mm

Maximum Read Rate: Not Specified

Number of Layers: 2

Track Path: Opposite Track Path (OTP)

Linear Density: 0.293 um/bit

Track Density: 0.74 um/track

First Physical Sector of Data Area: 196.608

Last Physical Sector of Data Area: 16.580.607

Last Physical Sector in Layer 0: 2.283.519

 

Physical Format Information (Last Recorded - L0):

Disc ID: MKM-003-00

Book Type: DVD-ROM

Part Version: 1

Disc Size: 120mm

Maximum Read Rate: Not Specified

Number of Layers: 2

Track Path: Opposite Track Path (OTP)

Linear Density: 0.293 um/bit

Track Density: 0.74 um/track

First Physical Sector of Data Area: 196.608

Last Physical Sector of Data Area: 16.580.575

Last Physical Sector in Layer 0: 2.110.367

 

Physical Format Information (Last Recorded - L1):

Disc ID: MKM-003-00

Book Type: DVD-ROM

Part Version: 1

Disc Size: 120mm

Maximum Read Rate: Not Specified

Number of Layers: 2

Track Path: Opposite Track Path (OTP)

Linear Density: 0.293 um/bit

Track Density: 0.74 um/track

First Physical Sector of Data Area: 196.608

Last Physical Sector of Data Area: 16.580.575

Last Physical Sector in Layer 0: 2.110.367

 

Layer Information:

Layer 0 Sectors: 1.913.760 (50%)

Layer 1 Sectors: 1.913.728 (50%)

 

I'd want only to know why for all my old WORKING isos (some are 3 years old) the LABEL, the IMP ID and UDF are changed.

Just when I open the .dvd file ImgBurn shows these different informations so it's something before the burning procedure.

All the isos passed the abgx360 checks.

Never had a DRE and the same "problematic" disc doesn't work on all working 360 I have tried.

 

EDIT:

I have checked for a new fw update of the drive and the samsung live update told me that it's already running the latest one.

 

Google further and you should find out why it isn't working.

 

Hint: it's not an ImgBurn problem, the problem is in your console

 

Maybe there are a lot of noobs screaming for help on this board and this could explain your not very kind answer.

I never said that it's an ImgBurn problem but that I'm having a problem WITH ImgBurn.

I can tell you for sure that it's not a console problem because I mod by myself the 360 and I'm having a problem with a second backup from the same image of the first, till now, working backup.

It's not a DRE problem for the reason above written and also because I have tweaked some pots of the 360 laser lens.

I haven't messed up the ImgBurn settings because I never touched them and however just in case I restored them to default with the same problem.

I hope you can help me.

Edited August 5, 2009 by G0d3L

[LIGHTNING UK!]

It's nothing to do with ImgBurn - period.

 

If you modded the box yourself then you should be up on all the latest xbox news. Things do get updated you know.

[G0d3L]

It's nothing to do with ImgBurn - period.

 

If you modded the box yourself then you should be up on all the latest xbox news. Things do get updated you know.

 

I asked kindly and I didn't point the finger against ImgBurn.

I just ask a question adding some personal informations.

I was only try to understand if MAYBE there was something related ImgBurn.

I wasn't searching for a ImgBurn's evidence of guiltiness.

Said this I'm up to all the latest xbox news and in the end I solved the problem which turned out to be 2 bad burns that ImgBurn checked as good ones.

 

Sorry to have bothered all of you, it will not eve happen again.

[Cynthia]

Those bad burns passed the verify stage?

[G0d3L]

My fault, I didn't made the verify cause I was running out of time in that occasion but ImgBurn told me that everything went ok in the burning process.

the log I posted before is from the read of one of those 2 "bad" discs that seems to have everything all right.

Edited August 5, 2009 by G0d3L

[Cynthia]

Can't see any log posted. Only a media descriptor post.

 

Edit: Very often the burn shows no errors in the burn part, but the verify part freaks out.

[G0d3L]

Can't see any log posted. Only a media descriptor post.

 

Edit: Very often the burn shows no errors in the burn part, but the verify part freaks out.

 

sorry I called a read log what in reality is a media descriptor.

I lost every log cause I uninstalled and reinstalled ImgBurn to see if in some way I corrupted something.

Never had a problem burning with ImgBurn so I stopped verifing burned discs.

Thanks for remainding me to always verify.

Edited August 5, 2009 by G0d3L

[Cynthia]

TSSTcorp CDDVDW SH-S202J SB02 (ATA)

There is a later firmware for your burner.

 

http://www.firmwarehq.com/Samsung/SH-S202J/files.html

 

Might improve the burns.

[G0d3L]

EDIT:

I looked at your link and I saw that as you said there is a new fw SB03 when I'm running SB02.

Don't know why the Live Update told me I'm on the latest one.

I'll look in to that.

Thanks for everything Cynthia, I really appreciate.

 

P.S. upgrade done manually

Edited August 6, 2009 by G0d3L