ImgBurn 2.3.2.0 doesn't read all data from CD when creating an ISO file.

[Luke]

I've created an iso file. I've added to end of it some custom RAW data. When I burned it into a CD and then I read it to other iso file I noticed that these two iso files were different. The second one were smaller by 4096 bytes. When I do the same trick with Nero Express, it works just fine. I've checked it on two other computers. It's everywhere works the same way.

 

Does enyone know what's going on?

[dontasciime]

Yes but you will have to wait for him to come online.

[Luke]

I meant "anyone" :-P

[dontasciime]

what raw data are you adding is this like multisession etc.

 

bootable disc what is the iso

[Luke]

I'd like to have possibility to add any RAW data and later read it back.

[LIGHTNING UK!]

It reads as much as the 'read capacity' command reports.

 

If it's off by a few sectors, ImgBurn won't read them.

 

You can see pretty clearly in the log window / info panel on the right just how much the drive thinks is on the disc.

 

What does it say compared to what you expect to be on there?

 

Also, when you load the image to burn it, does it not report the full / correct size? There shouldn't be any reason for it to cut it short - unless the data isn't a full sectors worth - it'll truncate odd amounts of bytes.

[Luke]

I don't know why ImgBurn behaves in such strange way, because there is no problem with Nero Express I have.

It's also strange because it always cut exactly 4096 bytes, no matter what's the size of the original ISO file.

 

I tried to use wnaspi32.dll interface (from Nero) instead of the default one, but ImgBurn doesn't work properly with it either. Like it's some internal error in ImgBurn, and not in the interface.

[LIGHTNING UK!]

You're not really giving us anything to go on! Tell us the specifics!

 

How big is the image going by the file properties in Explorer?

 

How big does ImgBurn think it is once loaded in Write mode?

 

How big is it once burnt and looked at in Read mode (look in info panel on the right) ?

 

Just copy + paste everything from the info panel and log window (after burning / reading).

 

Screenshots help too.

 

As for ASPI not working, it works fine. If you have SPTD installed (part of DAEMON Tools / Alcohol), ensure you're running v1.50.

[Luke]

[...]

There shouldn't be any reason for it to cut it short - unless the data isn't a full sectors worth - it'll truncate odd amounts of bytes.

 

I think you're right. I've just noticed it truncates image to the multiplicity of 4KB.

[LIGHTNING UK!]

It will only take off the random bytes at the end, not a full sectors worth.

 

For instance, I just built a test iso from a random file on my desktop, it's size came out to:

 

I 23:14:25 Image Size: 1,245,184 bytes

 

I then used hexworkshop to insert 5 bytes on the end of it.

 

Explorer then shows the size as:

 

1.18 MB (1,245,189 bytes)

 

Once loaded into ImgBurn's Write mode, the size is still shown as:

 

1,245,184.

 

ONLY those 5 bytes have been ignored.

[Luke]

I've created image (size 1

[LIGHTNING UK!]

For whatever reason, your drive appears to report the disc only has 606 sectors written to it.

 

If it can't report the correct info, there's not much I can do.

 

Copy + paste the info from the info panel on the right when in read mode please.

[Luke]

Here's the info:

 

HP DVD Writer 940d 3H23 (ATA)

Current Profile: CD-RW

 

Disc Information:

Status: Complete

Erasable: Yes

Sessions: 1

Sectors: 606

Size: 1

[LIGHTNING UK!]

Right, yeah, it's misreporting the disc capacity.

 

The 'Get Capacity' command is returning '605' (last sector written on disc), and so when starting from 0, that gives us a readable region of 0 - 605 = 606 sectors.

 

Sectors: 606

 

This is confirmed in the TOC info

 

-> Track 01 (Mode ???, LBA: 0 - 605)

 

But then there's some odd looking gap after the track and before the leadout that wouldn't normally be there.

 

-> LeadOut (LBA: 608)

 

Hence that's where your 2 sectors are going missing.

 

I assume you've tried burning to a read CD-R rather than a CD-RW?

[Luke]

I assume you've tried burning to a read CD-R rather than a CD-RW?

 

I'm using CD-RW all the time.