PDA

View Full Version : There is not enough space to burn this compilation onto a disc

smokafatty
03-24-2004, 03:20 AM
I've tried alcohol 120 and nero and both give me that message. I'm trying to burn from a princo dvd-r to a ritek dvd-r. Any help would be much appreciated. Thanks.
sweep
03-24-2004, 06:34 AM
within nero there is a "enable overburn" box this works with audio but not sure if will work with dvd.
dangerouseddy
03-24-2004, 06:46 AM
you cant overburn to a dvd-r.
BlackDiamondJr
03-24-2004, 10:19 AM
A friend had that exact same problem while trying to copy an unknown DVD brand to Ritek G04. He finally went out to Office Depot and bought a spindle of their brand, cheap stuff. Some of them worked fine and some still gave the "not enough space" message. None of the Riteks would work. It was obviously media related, even within the same spindle there were issues.
smokafatty
03-24-2004, 02:13 PM
Just tried fuji brand and still no luck. I noticed in alcohol it said the image was 4.38 gb is that larger than a normal dvdr? Is there a program to shrink it down without having to rip and reconvert all the discs? (its a 16 disc set I'm trying to burn)
BlackDiamondJr
03-24-2004, 05:29 PM
Just tried fuji brand and still no luck. I noticed in alcohol it said the image was 4.38 gb is that larger than a normal dvdr? Is there a program to shrink it down without having to rip and reconvert all the discs? (its a 16 disc set I'm trying to burn)
Not to my knowledge.
Unless you get luck with the media it appears that you might have to redo the compilation and reduce the size.
paxrax
03-24-2004, 06:01 PM
i used to get that a lot, burn with recordnow max using the wizard and all it asks is if you want to continue, click yes and away you go, no more probs. anyway, neros crap lol!
smokafatty
03-24-2004, 09:47 PM
recordnow max worked great! Thanks for all the replies :)
PhilEnfield
03-25-2004, 08:01 PM
I've had this a few times with Nero.
If you copy the disk to your Hard Drive and burn it from there, you will find it works no problem. It only seems to happen when doing disk to disk copying.
I imagine it might be something to do with overheads ... not really sure, but it only seems to happen on certain disks (backups).