 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
ROUND TWO!
Originally, K3b, the Linux burning application, said I had 113 MB free space on
the DVD during the burning operation. So I added a bunch more files. On the
next draft, K3b said I had 10.3 MB free space. Whew! Only when it went
actually to start the burn, it said there wasn't enough room for the operation.
So I removed another 15 MB. Same deal. Then I removed more until it said it
had 46MB free space. Then it worked.
Q: How can you predict what will actually fit on a disk? What measurement is
absolutely correct?
I'm also wondering, if I were to delete thumbs.db's (across thousands of
image-containing directories), how long until Windows puts them back. I'm also
not sure that's the only problem with predicting DVD-fitting. Could the
directories themselves be taking up a nontrivial amount of space, (an amount
calculated by one routine of K3b but not the other?)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
gregjohn <pte### [at] yahoo com> wrote:
> Originally, K3b, the Linux burning application, said I had 113 MB free space on
> the DVD during the burning operation. So I added a bunch more files. On the
> next draft, K3b said I had 10.3 MB free space. Whew! Only when it went
> actually to start the burn, it said there wasn't enough room for the operation.
> So I removed another 15 MB. Same deal. Then I removed more until it said it
> had 46MB free space. Then it worked.
I have noticed the same phenomenon with k3b: It fails to account for some
extra data needed to burn the DVD (I assume it's probably some kind of
bookkeeping data or whatever which a data DVD needs) when it estimates
the space still available. If you fill it up completely, it will just say
it cannot create the DVD. You have to leave some space.
I have always wondered why it does that. Maybe a bug or an oversight?
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
gregjohn wrote:
> Q: How can you predict what will actually fit on a disk? What measurement is
> absolutely correct?
It's not hard. You know what sectors you need to burn and how many sectors
are on the disk. K3b just has a bug. It's either not accounting for
fragmentation or not accounting for directory size. If you have directories
with huge numbers of small files, it could be either.
> I'm also wondering, if I were to delete thumbs.db's (across thousands of
> image-containing directories), how long until Windows puts them back.
Until you use the explorer to go back to that directory and browse the
images again, at least in XP.
--
Darren New, San Diego CA, USA (PST)
"We'd like you to back-port all the changes in 2.0
back to version 1.0."
"We've done that already. We call it 2.0."
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Darren New <dne### [at] sanrrcom> wrote:
>
> It's not hard. You know what sectors you need to burn ...
>
How?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
gregjohn wrote:
>> It's not hard. You know what sectors you need to burn ...
> How?
If you don't know what you need to burn into each sector, your CD burning
software sucks. :-) How could you *not* know which sectors you need to burn?
--
Darren New, San Diego CA, USA (PST)
"We'd like you to back-port all the changes in 2.0
back to version 1.0."
"We've done that already. We call it 2.0."
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Darren New <dne### [at] sanrrcom> wrote:
> gregjohn wrote:
> >> It's not hard. You know what sectors you need to burn ...
> > How?
>
> If you don't know what you need to burn into each sector, your CD burning
> software sucks. :-) How could you *not* know which sectors you need to burn?
>
AFAIK, Neither Roxio on the XP platform nor K3b on the Linux one gives *sector*
information until it's deep into the burning process. Can you name an app
that tells you sectors up front & show a screen grab of how it's presented?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
gregjohn wrote:
> Darren New <dne### [at] sanrrcom> wrote:
>> gregjohn wrote:
>>>> It's not hard. You know what sectors you need to burn ...
>>> How?
>> If you don't know what you need to burn into each sector, your CD burning
>> software sucks. :-) How could you *not* know which sectors you need to burn?
>>
>
>
> AFAIK, Neither Roxio on the XP platform nor K3b on the Linux one gives *sector*
> information until it's deep into the burning process. Can you name an app
> that tells you sectors up front & show a screen grab of how it's presented?
Maybe I'm being unclear. By "you" I mean "the application" or perhaps "the
programmer of the application". How does a program burn a CD without
knowing every byte it writes to the CD? How does it not know exactly how
many bytes it's going to write? How does it not know whether that many bytes
fit on a standard size CD?
If the application can burn the CD, it can certainly figure out how many
bytes it's going to burn, yes? If it tells you it will fit and then it
doesn't, it's because it's not using the same algorithm to lay out the files
for the burn as it's using to calculate the space used, and that's a bug.
--
Darren New, San Diego CA, USA (PST)
"We'd like you to back-port all the changes in 2.0
back to version 1.0."
"We've done that already. We call it 2.0."
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
