Can ImgBurn create ISOs of Mac Formatted DVDs?

[Citrus]

Can ImgBurn create ISOs of Mac Formatted DVDs? I would like to backup some Mac Software CDs to ISO images.

[mmalves]

If they don't have protection against copying, then yes, since ImgBurn's Read mode reads sector-by-sector from the CD/DVD to an ISO image, regardless of the actual filesystem/data that it contains.

[Citrus]

How can I tell if it has that kind of protection? Are there any settings that need to be changed to get it to read in that mode or are the default settings fine?

Edited September 18, 2007 by Citrus

[mmalves]

Are there any settings that need to be changed to get it to read in that mode or are the default settings fine?

The default settings are fine

[Citrus]

I created the image successfully but I don't see an ISO file.. just an MDS file and two other files with different extensions. How do I get it to burn to ISO format?

[mmalves]

I created the image successfully but I don't see an ISO file.. just an MDS file and two other files with different extensions. How do I get it to burn to ISO format?

While in Write mode, select the MDS file as the disc image you want to burn. ImgBurn will then read from the other files and burn your DVD accordingly.

[Citrus]

Thanks for the quick response It's because the drive was FAT32...

 

 

I have a couple of unrelated questions but thought I'd ask it here instead of starting a new topic. What are the Verify & Discovery modes exactly? What are they good for? How is Verify mode different than selecting Verify in the Write mode?

[LIGHTNING UK!]

It's no different, it's just a standalone version.

 

Discovery mode is used for testing drives / media and not something you'd use everyday (unless you're me / one of the beta team )

[Citrus]

Is there any tutorial on how to use it and what to look for in its output? Why does it require a blank disc?

[LIGHTNING UK!]

It just burns lots of zeroes to the media.

 

We use it for all the drive / disc tests in the 'drives and media' forum.

 

You can tell it to burn then entire disc without having the hassle of building an iso of that exact size.

 

You can then see the read/write rates on the media and follow them up with a PIPO scan in DVDInfoPro or CDSpeed.

 

This enables you to see how well your drive can burn them - and of course vary the write speeds to see if that makes a difference.

[Citrus]

Is there anyway to use the verify section to verify that an ISO image inst corrupt instead of checking if the disc burn is corrupt?

[LIGHTNING UK!]

No, not really.

 

Only the most basic of checks could be performed by actually seeing if the program will load it and finds a valid file system etc!

 

You could do that by loading it into Write mode or into Verify mode.

[Citrus]

I am not able to do that with the Mac discs since ImgBurn doesn't recognize the file system and IMP ID.

 

Another question

Does ImgBurn write information to the Labels of the ISO Images like Application Label, Author, Volume Set ID or does it just do an exact copy of the disc and whatever that has?

Edited September 18, 2007 by Citrus

[mmalves]

Does ImgBurn write information to the Labels of the ISO Images like Application Label, Author, Volume Set ID or does it just do an exact copy of the disc and whatever that has?

Everything is copied from the original disc as-is, sector-by-sector, absolutely no changes are made.

[Citrus]

So thats a nice feature for me. I don't like how Nero and UltraISO puts its name in the Application Label of the ISO images it creates. I want it to be as close to the original as possible.

[LIGHTNING UK!]

They shouldn't do that if you're taking an image rather than making a new one - otherwise it would be pointless doing it.

[Citrus]

When creating the ISOs from Mac formatted discs it says the destination file system is NTFS. Does that mean its not doing it the right way?

[LIGHTNING UK!]

That's the file system used on the hard disk you're writing the image to, nothing more.

 

If it was going to a FAT/FAT32 drive it would have to split large images into 4GB chunks as that's the biggest the file system can support.

 

NTFS has no such limitation.