DDump images unburnable with burnatonce?!

Hi...

I've just tried to make a copy of UT2003 CD1, reading the disc with DDump (Frontend) and burning with burnatonce.
Following settings:

DDump Frontend:
Selected disc dump method: SecuRom
Advanced Settings: FULLINDEX & NODETECT

burnatonce:
Use Raw Driver
Buffer Protection
Overburn
Finalise Disc
Buffers: 128
Autohide Settings
Check Cue Files


The Problem is: burnatonce told me the IMAGE itself (without lead-in which is displayed seperately during the burning process) is 844MB!

And as expected, burnatonce started having problems at ~95%, the drive slowed down, then burned again, slowed down again, even started making scratching noises. I switched off the main power for my PC, switched it on again and got the disc out of the drive - it even smelled weird.

Well, it seems that I've not destroyed my drive but could anyone explain WTF has happened here?! I'm KINDA worried about that...

TIA...

NetSoerfer

P.S.: I'm used my Litey LTR-48125W for both ripping & burning... damn, how come I always forget something? *shir*
 
Use nero and see in the menu :
Recorder > Medium Info ( it imports all the sessions ) , you'll be able to see the real size occupied on the CDR , like Poko says .
 
You can't use discdump for securom protected cds. Discdump's securom mode can extract an image with the sub-codes but there isn't any program that can burn the image produced.
 
Top