From Talk:K3bViewing a history listing Time User Activity Comment 09:49, 14 February 2013 Annew (talk | contribs) New reply created (Reply to Why does 700 MB expand to 703.1 MB?) 20:22, 13 February 2013 Yecril71pl (talk | contribs) New thread created When I select 700 MB for the disc capacity, K3b sets the actual capacity to 703.1 MB and allows me to burn that much. That sometimes leads to errors in the burning process which cdrecord is often unable to detect. It can also happen that the reader is unable to read some files from a disc that verified correctly in the recorder. MoreHistory View source Link toYecril71pl (talk) 20:22, 13 February 2013 Overburning like this has been possible for years. It has always been unreliable. If you set K3B to use 700MB disks, make sure that what you are proposing is slightly less than that. If I recall correctly a small amount of space is required for writing system information. Parent MoreHistory View source Link toannew (talk) 09:49, 14 February 2013 Retrieved from "https://userbase.kde.org/Thread:Talk:K3b/Why_does_700_MB_expand_to_703.1_MB%3F#Why_does_700.C2.A0MB_expand_to_703.1.C2.A0MB.3F_1994"