Odd message after copying files to CD/RW

  • Thread starter Thread starter Doug Kanter
  • Start date Start date
D

Doug Kanter

Rebooted my computer this morning. In the CD drive, I had a CD/RW disk onto
which I'd copied some files yesterday. Saw a message saying "files are
waiting to be copied to the CD - click here to see the files." This suggests
that perhaps a previous copy process had been interrupted, which was not the
case. So, my next interpretation was that Windows compared the files on the
CD to those on my hard drive, noticed some on the HD were newer, and
expected me to update the CD. This seems unlikely, but who knows what goes
on in the minds of programmers who live on nothing but Jolt cola.

What's up with this message?
 
Doug said:
Rebooted my computer this morning. In the CD drive, I had a CD/RW disk onto
which I'd copied some files yesterday. Saw a message saying "files are
waiting to be copied to the CD - click here to see the files." This suggests
that perhaps a previous copy process had been interrupted, which was not the
case. So, my next interpretation was that Windows compared the files on the
CD to those on my hard drive, noticed some on the HD were newer, and
expected me to update the CD. This seems unlikely, but who knows what goes
on in the minds of programmers who live on nothing but Jolt cola.

What's up with this message?
better late than never...
I seem to recall it a 'feature' found in Windows XP. You can copy files
to your CD and it will see these files as pending to be burned to CD.
Just remove them (can't remember how) or burn them
-Ed
 
none said:
better late than never...
I seem to recall it a 'feature' found in Windows XP. You can copy files
to your CD and it will see these files as pending to be burned to CD.
Just remove them (can't remember how) or burn them
-Ed

It *did* give me the option of removing them, but the message was sort of
dubious. Knowing how programmers can be, I allowed for the possibility that
it might want to remove the ACTUAL files, rather than a temporary copy of
them. So, I backed up the originals, repeated the copy process, told it to
remove the files, and nothing happened to the originals. Apparently, it does
cache a copy of the files being worked on. Why it doesn't realize the burn
process is over...I have no idea.
 
It *did* give me the option of removing them, but the message was sort of
dubious. Knowing how programmers can be, I allowed for the possibility that
it might want to remove the ACTUAL files, rather than a temporary copy of
them. So, I backed up the originals, repeated the copy process, told it to
remove the files, and nothing happened to the originals. Apparently, it does
cache a copy of the files being worked on. Why it doesn't realize the burn
process is over...I have no idea.

http://support.microsoft.com/default.aspx?scid=kb;en-us;279157

The burn process is over when you tell it so, otherwise it
would have some kind of very small size or time limitation
which could tend to constantly create more sessions that
still need closed, still a finality to it all and those
sessions lead-outs and lead-ins will eat up over a dozen MB
per which can reduce available disc capacity.
 
kony said:
http://support.microsoft.com/default.aspx?scid=kb;en-us;279157

The burn process is over when you tell it so, otherwise it
would have some kind of very small size or time limitation
which could tend to constantly create more sessions that
still need closed, still a finality to it all and those
sessions lead-outs and lead-ins will eat up over a dozen MB
per which can reduce available disc capacity.

Interesting article - thanks. I guess I didn't phrase my search terms
correctly.
 
Back
Top