It says my disc is to small but it aint!!!

[gatamig]

Hi guys
Got a prob burning to DVD using nero as it doesnt recognise the size of the disc correctly and throws out my file saying there is not enough space on the disc.
The project I am burning is only 4,194 gigs and the disc is 4,7 gigs so there should be room.
I am using Nero 5.5 and have upgraded to the highest pos from the Nero site. This is used with an NEC 2500.
Is there any way I can change the way Nero sees this disc or something.
I know it seems a small problem to a lot of you but I just cant seem to solve it!!!
Thanks a lot.
Gatamig

[SLK001]

Trust me, if NERO says that you don't have enough room on your disc, then you don't have enough room on your disc.

You are being mislead by the byte, kilobyte, megabyte, gigabyte numbers.

Highlight all the files you want to burn to disc, then right-click on them and select PROPERTIES. The pop-up box will show you the true size in bytes.

[offline]

You are being mislead by the byte, kilobyte, megabyte, gigabyte numbers

Correct. You are also mislead about the capacity of DVDR - it is 4.35 gig.
Either get rid of stuff, or write to a folder and use Nero Recode to
shrink that bit that overhangs.

[gatamig]

Thanks for the reply. It says 4,294 When highlighted which is still way small enough to go on the disc dont you think. I just dont know. What do you think?
Gatamig

[offline]

4,294

Perhaps Nero wants to add bits during the authoring process. Maybe
there is a safety gap added within the program (quite normal.) I'm not sure.

You could download a copy of imgtoolburn and see if that fixes
the problem (it uses the nero burning SDK only when turning a
VIDEO_TS folder into a burnt DVD)

[SLK001]

4,294? 4,294 what? You should be able to tell me EXACTLY the size of the files (ie, 4,294,335,147 bytes).

Why don't you show us the files that you are trying to burn with NERO.

[gatamig]

This is the size of it 4.00 GB (4,294,967,296 bytes) and it is a Nero CD image file that I converted with nero vision saved it to the hard drive and now I have the problem
Cheers matey.
Gatamig

[spectroelectro]

One of the most obvious reasons for this problems is authoring a DVD with ac3 and feeding the separate elementary video & audio streams into a DVD authoring program. Some authoring programs automatically convert the ac3 stream to a WAV file, bloating up the size of the final disc image by 600 to 800 megabytes.
Another possibility? You might be just a few kilobytes or megs over the roughly 4.29 gig limit.
Solutions: if you're using a WAV file, convert it to ac3. This will save you between 600 and 800 megs of space.
If you're already using an ac3 audio track, run ReJig on the m2v video
file and select a filesize 200 megs smaller than it already is. Then re-author.

[Gazorgan]

There's overhead in the lead-in and lead out, as well a few MB more. Your probably a few MB over. You should target a tad smaller to allow for this (I typically reserve 50 MB for slop).

[dcsos]

Nero has often presented me with this debacle..
I've always rsponded by burning the project with RECORD NOW MAX successfully..
Most oversized looking projects do burn fine in nero, but one outt a hundred give me same problem as you..Even tho I am not burning from an image file.. It loks small enough, but nero says "TOO BIG"
when once RECORD NOW MAX couldn't handle the burn that for whatever reason NERO choked on, then the old ROXIO program comes in handy.. Roxio 5 (upgradaed to do DVD) is a terrible program ..but when there is no other choice..and the project is over 4 gig..it does the trick!

[SLK001]

But guys, he's trying to burn an image file (and, I'm assuming that he is using "image burn"). His file should easily fit on a DVD-R. He's probably trying to burn it in a "non-image" mode. UDF and ISO formats require all files to be less than 2^30 bytes in size.

[dcsos]

My first instinct is its a bug in NERO with certain "kind" of files.
Don't know why, but it must've happened 5 times in total to me over 500 burns, but NERO just never could burn what was obviously a small enough project....

These kind of errors had no rhyme or reason..
You know how when you look at the file size on a project and it can be slightly different when you look at the same weight of files moved from FAT 32 to NTFS surface?
Well I say don't even take time thinking about it-- find a fast workaround and move on