Log in

View Full Version : Oversized iso


oliparcol
23rd May 2006, 17:53
Hi,

I will try to do my best to explain my problem. As a french, it's a little bit complicated for me to communicate in english. So, I use DVD-RB 1.09.3 with cce trial version 2.70.2.4. I don't use dvd-rb installer but the zip file. After rebuild, the final size of the dvd is ok (4.38 gig). I try to use "Output to iso image file" (so I have mkisofs.exe put in dvd-rb rep) but I always get the error: "- There appears to have been an ISO write error.". So I build iso file with ImgTool to burn it with ImgBurn. The problem is the iso file is always 2 or 3 mega over the limit. I burn it nevertheless but, when I watch the burned dvd, it miss 10-20 sec of the end...

Someone know the origin of the problem ?

Thanks,
Oliparcol

SAPSTAR
23rd May 2006, 19:34
Hi,

I will try to do my best to explain my problem. As a french, it's a little bit complicated for me to communicate in english. So, I use DVD-RB 1.09.3 with cce trial version 2.70.2.4. I don't use dvd-rb installer but the zip file. After rebuild, the final size of the dvd is ok (4.38 gig). I try to use "Output to iso image file" (so I have mkisofs.exe put in dvd-rb rep) but I always get the error: "- There appears to have been an ISO write error.". So I build iso file with ImgTool to burn it with ImgBurn. The problem is the iso file is always 2 or 3 mega over the limit. I burn it nevertheless but, when I watch the burned dvd, it miss 10-20 sec of the end...

Someone know the origin of the problem ?

Thanks,
Oliparcol

Did you modify the CCETargetSector parameter?! If yes, you should keep it at its default value, if no you may also reduce the number of passes....

You can PM in french......

jdobbs
23rd May 2006, 21:32
If you're getting output that large it usually means you've modified the TargetSectors value... I highly recommend using the default values. There are very good reasons why it was set the way it was. The possibility of oversizing was only one of them.

rahzel
24th May 2006, 02:11
2260000 seems to be a safe number, but if you use the default, you definitely shouldnt go over.

oliparcol
24th May 2006, 11:18
ok thanks, I will keep default value and I will see what happen...