IMGBurn and HD-DVD .ISOs

[setarip_old]

I used IMGBurn to create an .ISO image file (UDF 2.50) of a ripped HD-DVD.

I was surprised to see that IMGBurn burn created BluRay directories of "BDMV" and "Certificate" and put all of the HD-DVD files and folders into those folders.

What is the proper way to use IMGBurn to make a correct .ISO of an HD-DVD?

[Adub]

I doubt it, but I don't think IMGBurn even officially supports HD-DVD structures in the first place.

[setarip_old]

Hi!I doubt it, but I don't think IMGBurn even officially supports HD-DVD structures in the first place.Huh? The "structure" is the same UDF v.2.50 as is used by BluRay...

[laserfan]

Try un-checking "Create CERTIFICATE Folder" under Settings/Build (Blu-ray Video).

[LIGHTNING UK!]

All the code is in there for HD DVD's.

What exactly did you feed it in the 'Source' box?!

If you just add the HVDVD_TS and ADV_OBJ folders like you're supposed to, I see no reason for it to think it's Blu-ray content.

[setarip_old]

If I remember correctly, I entered the parent folder of the two sub-folders that you've named - which is the same procedure I (successfully) use when selecting BluRay folders...

BTW - I continue to use v.2.4.1, as I have (with no problems) since its initial release.

[setarip_old]

Must have been a one-off anomaly, as it's now worked properly three consecutive times...

[LIGHTNING UK!]

Well you shouldn't use 2.4.1.0, I release newer ones to fix bugs!

[setarip_old]

Well you shouldn't use 2.4.1.0, I release newer ones to fix bugs!I'm well aware of the tremendous effort you put in on both "IMGBurn" and its history making predecessor, with voluminous changes and bug fixes. However, v.2.4.1 performs perfectly for my limited needs - so I continue to apply (for my personal purposes) the "If ain't broke, don't fix it" maxim...

[blutach]

@setarip_old

If you look at the monumental changelogs, you'll know there are issues that have been fixed, some of which could include your problem.

In the future, do not ask questions where the developer has specifically requested you to update to the current version, which is the only one he and his team are supporting.

Regards

[setarip_old]

there are issues that have been fixed, some of which could include your problem.'Fraid not...

[LIGHTNING UK!]

setarip, a lot of the issues are internal ones that a user might not ever really see.

For instance, incorrect descriptor info within the file systems.

Just because you can't see that it's broken doesn't mean it isn't.

For the sake of a minute of your time, I suggest you do away with that 'if it ain't broke, don't fix it' attitude and just update already!