Make ImgBurn accept zero'd video partitions

[xDREAM]

Ive found a way to make ImgBurn accept all your isos that are without a video partion.
Open up your iso in a hexeditor of choice and put this in the first 8 bytes: COBRAMB1

Code:

Offset      0  1  2  3  4  5  6  7   8  9  A  B  C  D  E  F

00000000   43 4F 42 52 41 4D 42 31  00 00 00 00 00 00 00 00   COBRAMB1........

Oh and dont forget to set the layerbreak to: 1913760

[garyopa]

The author's of the SS merger programs, should add this feature to their programs, instead
of the program just adding a totally BLANK video part, it should add one with a DVD volume
name, like you mentioned above, so that both DVD decrypter and IMG burn does not crash
saying the ISO is invalid.

[xDREAM]

The author's of the SS merger programs, should add this feature to their programs, instead
of the program just adding a totally BLANK video part, it should add one with a DVD volume
name, like you mentioned above, so that both DVD decrypter and IMG burn does not crash
saying the ISO is invalid.

ImgBurn author said that in the next version all isos will work without modification so this is only a temp fix =)

[Helltick]

could you just add this to the first 8 bytes of blank360.iso?

[xDREAM]

could you just add this to the first 8 bytes of blank360.iso?

or the finished iso it doesnt matter

[Helltick]

Thanks for the info man! only 2 days left on my evaluation of clonecd...Think i'll just fix the blank360.iso and add it to my tool kit..then its done.
Any free programs you know of to replace the need for dvdinfopro? $27US seems a little steep.

Again, nice work...thanks for the tip.

[Redline99]

What is the significance of COBRAMB1?  It doesn't turn up much on google. Why at LBA 0 offset 00000000? This area is usually reserved for a boot image I think.  UDF 1.02 says to start at LBA 16 with the Primary Volume Descriptor structure data, would putting ".CD001." 0x01 0x43 0x44 0x30 0x30 0x31 0x01 work (at sector 16)?

I think putting in something instead of all 00's is a god idea for the video section, I'm just courious about this solution.
(I will implement an agreed upon method for my app too)

[Helltick]

What is the significance of COBRAMB1?

Dunno man, but i'll tell you ...I edited the blank360.iso that c/w xtreme pack with the "cobramb1" code.
Run the build.bat as normal, rename IMAGE.000 to IMAGE.000.iso
ImgBurn works perfect now...three successful backups so far!

Anyone tried a different 8 byte header and have it work?

This is Good stuff!
Stuff I didnt know anyway

[xDREAM]

What is the significance of COBRAMB1?

dont know what its for i just found it while debugging imgburn. this passes its check and this was the easiest to pass

[xDREAM]

Found a new way...at offset 8000h put:

0143443030310100202020202020202020202020202020202020202020202020202020202020202058424F58333630202020202020202020202020202020202020202020202020200000000000000000

Code:

Offset       0  1  2  3  4  5  6  7   8  9  A  B  C  D  E  F

000008000   01 43 44 30 30 31 01 00  20 20 20 20 20 20 20 20   .CD001..       
000008010   20 20 20 20 20 20 20 20  20 20 20 20 20 20 20 20                   
000008020   20 20 20 20 20 20 20 20  58 42 4F 58 33 36 30 20           XBOX360
000008030   20 20 20 20 20 20 20 20  20 20 20 20 20 20 20 20                   
000008040   20 20 20 20 20 20 20 20  00 00 00 00 00 00 00 00           ........

[Redline99]

That would be the the Primary Volume Descriptor structure data at LBA 16

[xDREAM]

That would be the the Primary Volume Descriptor structure data at LBA 16

Yeah.. and ur disc gets a nice XBOX360 label which is nicer =)

[Redline99]

I think this is a better solution, plus like you said it gives the dvd a volume label.

[Redline99]

I have't tested this yet, (will when I get home from work)

But in addition to the above method at LBA 16 we might want to also do this at LBA 17

Code:

Offset       0  1  2  3  4  5  6  7   8  9  A  B  C  D  E  F

000008800   FF 43 44 30 30 31 01 00  20 20 20 20 20 20 20 20   .CD001..

This means "Volume Descriptor is a Volume Descriptor Set Terminator"
Might make the data a little more compliant.

Edit: Not that it matters that much anyways.

[xDREAM]

it really doesnt matter afaik

[PS2MXBOX]

So after doing this, we could basically burn this with any program that burns .img files right?  is there any need to keep the .dvd files or .ccd files?  My interest in this is that there is no way to burn my backups on a mac at this point and this could prove to be very useful if I'm reading this right.

[bomberman]

So after doing this, we could basically burn this with any program that burns .img files right?  is there any need to keep the .dvd files or .ccd files?  My interest in this is that there is no way to burn my backups on a mac at this point and this could prove to be very useful if I'm reading this right.

The program must support to set a "custom" layerbreak. The layerbreak must be @ 1913760. If the program have this feature I see no reason that it should not work.

[PS2MXBOX]

the program can put a layer break anywhere on a +r dl but it has to be told by an outside program as there is no option in the burning program to change it manually; the image file has to have it written inside it

[Pandor]

as a linux user i'm also suffering from incompatibility with Xtreme type iso's.
It seems to confuse growisfs in a sense that it won't take to user specified layer break.

So i wanted to make the video dummy file iso9660 compliant.

to create an iso that complies to the iso spec, it would need 16 sectors of system area (LBA 0 - 15), one primary volume descriptor sector and one primary volume ending descpritor sector.

So now, i was wondering, if i modifiy the nullified dummy file to contain these sectors, would i need to insert them, or overwrite them?
As i'm guessing that now, the dummy is regarded as data. hence all zeros will be written to disc. But when you overwrite the first 18 sectors, you loose 36864bytes of data (18x2048).
So won't everything shift down by 36864bytes?

[Pandor]

aargh nevermind.
i was regarding the volume descriptor as a file header. Not actual data that is also written to the disc.
so it needs to be replaced, not inserted.

What was i thinking..