LIGHTNING UK!

The padding value comes from burning a file that doesn't have a 'number of sectors' that's divisible (exactly) by 16. When you burn to DVD+R media the drive will always pad the image (disc) so the size is divisible by 16 - so if you read the disc back you'll get the MD5 shown in the 'padded' line and not the other one.

That's PHYSICAL sector 2,283,519, not LBA sector. You need to subtract the value of 'First Physical Sector of Data Area' to get it in normal LBA terms (i.e. subtract 196,608) = 2086911

Use a newer drive, that thing is ancient! You could also try a firmware update to v1.19 http://www.ricoh.com/drive/asia/exe/M72_0119.exe

Ah ok, just of AVI files, sorry I didn't see that before and assumed it was a DVD Video disc. If you run Build mode on the same content the size will be the same each time - so if the size changed, the source must have changed too.

Doesn't it just mean there's something wrong with the autorun stuff? If the autorun.inf on the burnt dvd is ok and the file it tells the OS to open is ok, I don't see why there would be a problem.

You can use ImgBurn itself to read a bootable image from another disc, have you tried that? It's on the same tab as where you'd tell it to make the image bootable - The option is called 'Create Boot Image'.

Could it be that you're selecting a different layer break position? 'Image Size' includes the file system itself. When you look in explorer at the files, that's obviously not taken into account.

Nope they're all the same, it's the same function/code being called in all modes.

The .DVD file is probably pointing to something that doesn't exist. Edit it in notepad and fix it.

The drive not recognising the discs is probably half the problem. If it doesn't support them properly then there's a VERY good chance of getting a bad burn - which is exactly what's happening here.

I assumed you'd tried more than 1. If you haven't, by all means please do so.

That's more of a sanity check than anything. I guess I could pad with zeroes but then when you make these boot images they'd always come from a device that WOULD mean their size is always a multiple of 512 bytes. If you change the appropriate options you can use the full ascii character set for the iso9660 filesystem and aren't limited to uppercase only. To make the image a multiple of 512 you'll have to pad it with 0's in a hex editor.

Have you tried at 4x? My samsung s203b doesn't like burning those at 2.4x. Switch to 4x and it's fine. The scans are far better at that speed too - which is the complete opposite from what I'd expect.

Because those tools don't check for correct layer breaks! It's easy to play dumb, it's another thing to know what you're doing and know when something isn't right.

The output mode wouldn't make a difference. If it's listing it as a dupe I don't really know how it's getting the wrong LBA to be honest. I'm still playing with the function though so gimme some time...I'm quite busy at the moment but I'll do it as soon as I can.

It was designed to be super basic and I've no intention on changing that any time soon. If you want full control stick to Nero.

Does the Mac not support UDF? You wouldn't have a problem if it does as I'm sure it would use that FS instead of the ISO9660 / Joliet ones that might also be present on the disc. Are you sure the 4GB files are what's causing the problem anyway?

Yeah but it's not required as ImgBurn supports files upto 4GB in size within those file systems - as do all versions of windows from (and including) Windows 95.

It doesn't tick the one on the front GUI so if that's what you're expecting to see, stop.

Click the one next to where it says 'Free Space:'. It's a picture of a HDD and is on most of the screens where that can be done.

To be fair, I did move this from the 'bugs' forum and that doesn't have the pink bar

The cheek of it!

1. It's probably not linked to a cell. You can only preview cells. 2. The cell is tiny? 3. It's down to the layout of the IFOs and nothing to do with the video content. If it can't find any cells to align, make some more. 4. Seamless playback linked in PCI. Does it have any impact? Yes and No. Normally the original LB is marked as non seamless. (i.e. that column will say no). Search the forum and you'll find more info on SPLIP and what it does/what you can do with it ('seamess' in general).

All double layer discs have a layer break. The layer break is a physical thing. As for being seamless or not (and assuming it's a DVD Video disc), you'd need to examine the IFO's to find out. Oh and no the blue bit doesn't mean anything - it's normal for that type of media (PTP DL).

If the drive won't complete writing the leadin, there's nothing I can do about it. ImgBurn isn't frozen, it's just waiting for the drive to finish what it's been told to do. When the drive is done (which I guess it won't ever be if you've already waited ages), ImgBurn will continue on it's merry little way. So you need to ask yourself... why won't my drive burn these discs? Why's it having problem?