bcsman - about size.
It's not a problem, your burning software should tell you when you've overstuffed the compilation.
However, to compliment Inertia's point:
The definition of a kilobyte is usually 1024 bytes. That's fairly commonly accepted now.
However, a Megabyte is referenced by various forms. What is called decimal, and what the world usually expects, is one million. However, it's sometimes referenced as 1,000 kilobytes, and sometimes it's a K of K's, or 1024 x 1024, to keep it a power of 2.
The Gigabyte is just as bad. Depending on the care taken by the programmer, an application might consider a Gigabyte as 1,000 x 1024 x 1024, or as 1024 x 1024 x 1024, or as 1000 x 1000 x 1024, or as the world should expect, exactly one billion.
I spent a few hours, in 1998, fretting over a lost 20 Mbytes on a Seagate hard drive, simply because the BIOS defined a Mbyte as 1024 x 1024, but Seagate defined a Mbyte as one million bytes.
In fact, they both referred to the same number of bytes - but it was like comparing miles to kilometers.
....and I'll bet that doesn't help one little bit, either!