Roxio's drag-to-disc often-times makes the CD unreadable at the
destination computer after a few uses. In terms of reliability, what
are your anecdotes on more reliable packages?
Paul wrote:
> Roxio's drag-to-disc often-times makes the CD unreadable at the
> destination computer after a few uses. In terms of reliability, what
> are your anecdotes on more reliable packages?
>
> Thx.
Just burn a regular disk with CD software. Drag to disk is a packet
writing software which is notorious for problems. Both with the disks
created and conflicting with other applications. Other versions of
packet writing software are Nero InCD, Sonic DLA, and there are others.
Stay away from them.
Also if writing to RW disks, that is another item that will go bad at
any time. They are only good for things like transferring between
computers. Basically a 1 time use for that write. They can and do go bad
at any time. I personally would rather write to a regular CD and throw
it away afterwards. Only a few cents.
On Apr 1, 7:51 pm, Marlin Singer <marlin.sin...@verizon.SPAMDAM.net>
wrote:
> Paul wrote:
> > Roxio's drag-to-disc often-times makes the CD unreadable at the
> > destination computer after a few uses. In terms of reliability, what
> > are your anecdotes on more reliable packages?
>
> > Thx.
>
> Just burn a regular disk with CD software. Drag to disk is a packet
> writing software which is notorious for problems. Both with the disks
> created and conflicting with other applications. Other versions of
> packet writing software are Nero InCD, Sonic DLA, and there are others.
> Stay away from them.
>
> Also if writing to RW disks, that is another item that will go bad at
> any time. They are only good for things like transferring between
> computers. Basically a 1 time use for that write. They can and do go bad
> at any time. I personally would rather write to a regular CD and throw
> it away afterwards. Only a few cents.
Hmm. Could do that. And get around the 106 character limit on the
file path by zipping up file trees. Thanks!
Paul wrote:
> On Apr 1, 7:51 pm, Marlin Singer <marlin.sin...@verizon.SPAMDAM.net>
> wrote:
>> Paul wrote:
>>> Roxio's drag-to-disc often-times makes the CD unreadable at the
>>> destination computer after a few uses. In terms of reliability, what
>>> are your anecdotes on more reliable packages?
>>> Thx.
>> Just burn a regular disk with CD software. Drag to disk is a packet
>> writing software which is notorious for problems. Both with the disks
>> created and conflicting with other applications. Other versions of
>> packet writing software are Nero InCD, Sonic DLA, and there are others.
>> Stay away from them.
>>
>> Also if writing to RW disks, that is another item that will go bad at
>> any time. They are only good for things like transferring between
>> computers. Basically a 1 time use for that write. They can and do go bad
>> at any time. I personally would rather write to a regular CD and throw
>> it away afterwards. Only a few cents.
>
> Hmm. Could do that. And get around the 106 character limit on the
> file path by zipping up file trees. Thanks!
If you are re-using the media as a temporary storage medium, you are
much better to go with flash drives. They're getting very inexpensive
these days with 1GB and greater capacity.
Dave Cohen
On Apr 2, 11:16 pm, Paul <Paul.Domas...@gmail.com> wrote:
> On Apr 1, 7:51 pm, Marlin Singer <marlin.sin...@verizon.SPAMDAM.net>
> wrote:
>
>
>
> > Paul wrote:
> > > Roxio's drag-to-disc often-times makes the CD unreadable at the
> > > destination computer after a few uses. In terms of reliability, what
> > > are your anecdotes on more reliable packages?
>
> > > Thx.
>
> > Just burn a regular disk with CD software. Drag to disk is a packet
> > writing software which is notorious for problems. Both with the disks
> > created and conflicting with other applications. Other versions of
> > packet writing software are Nero InCD, Sonic DLA, and there are others.
> > Stay away from them.
>
> > Also if writing to RW disks, that is another item that will go bad at
> > any time. They are only good for things like transferring between
> > computers. Basically a 1 time use for that write. They can and do go bad
> > at any time. I personally would rather write to a regular CD and throw
> > it away afterwards. Only a few cents.
>
> Hmm. Could do that. And get around the 106 character limit on the
> file path by zipping up file trees. Thanks!
Well, multisession burns certainly work, but I haven't had ocassion to
give it enough of a test drive to determine whether it works for a
greater number of sessions than drag-to-disc. I realize that drag-to-
disc doesn't have sessions in the same manner as regular burns, but I
mean sessions of file transfers, each consisting of possibly more than
one file. So far, however, discussions with colleagues reveals that
even regular multisession burns stop working after a few sessions,
well before the CD capacity is approached. I'm aware that there's a
lot of overhead for each session, but I suspect that this isn't cause
of the CD failure.
Another strange behaviour I'm seeing is that if you choose not to
import the previous session, you are not permitted to continue with
the burning of the new session on the same CD. You are prompted for a
blank CD. Very strange, I find.
On Apr 4, 3:57 pm, Dave Cohen <u...@example.net> wrote:
> Paul wrote:
> > On Apr 1, 7:51 pm, Marlin Singer <marlin.sin...@verizon.SPAMDAM.net>
> > wrote:
> >> Paul wrote:
> >>> Roxio's drag-to-disc often-times makes the CD unreadable at the
> >>> destination computer after a few uses. In terms of reliability, what
> >>> are your anecdotes on more reliable packages?
> >>> Thx.
> >> Just burn a regular disk with CD software. Drag to disk is a packet
> >> writing software which is notorious for problems. Both with the disks
> >> created and conflicting with other applications. Other versions of
> >> packet writing software are Nero InCD, Sonic DLA, and there are others.
> >> Stay away from them.
>
> >> Also if writing to RW disks, that is another item that will go bad at
> >> any time. They are only good for things like transferring between
> >> computers. Basically a 1 time use for that write. They can and do go bad
> >> at any time. I personally would rather write to a regular CD and throw
> >> it away afterwards. Only a few cents.
>
> > Hmm. Could do that. And get around the 106 character limit on the
> > file path by zipping up file trees. Thanks!
>
> If you are re-using the media as a temporary storage medium, you are
> much better to go with flash drives. They're getting very inexpensive
> these days with 1GB and greater capacity.
> Dave Cohen
Paul wrote:
> On Apr 2, 11:16 pm, Paul <Paul.Domas...@gmail.com> wrote:
>> On Apr 1, 7:51 pm, Marlin Singer <marlin.sin...@verizon.SPAMDAM.net>
>> wrote:
>>
>>
>>
>>> Paul wrote:
>>>> Roxio's drag-to-disc often-times makes the CD unreadable at the
>>>> destination computer after a few uses. In terms of reliability, what
>>>> are your anecdotes on more reliable packages?
>>>> Thx.
>>> Just burn a regular disk with CD software. Drag to disk is a packet
>>> writing software which is notorious for problems. Both with the disks
>>> created and conflicting with other applications. Other versions of
>>> packet writing software are Nero InCD, Sonic DLA, and there are others.
>>> Stay away from them.
>>> Also if writing to RW disks, that is another item that will go bad at
>>> any time. They are only good for things like transferring between
>>> computers. Basically a 1 time use for that write. They can and do go bad
>>> at any time. I personally would rather write to a regular CD and throw
>>> it away afterwards. Only a few cents.
>> Hmm. Could do that. And get around the 106 character limit on the
>> file path by zipping up file trees. Thanks!
>
> Well, multisession burns certainly work, but I haven't had ocassion to
> give it enough of a test drive to determine whether it works for a
> greater number of sessions than drag-to-disc. I realize that drag-to-
> disc doesn't have sessions in the same manner as regular burns, but I
> mean sessions of file transfers, each consisting of possibly more than
> one file. So far, however, discussions with colleagues reveals that
> even regular multisession burns stop working after a few sessions,
> well before the CD capacity is approached. I'm aware that there's a
> lot of overhead for each session, but I suspect that this isn't cause
> of the CD failure.
>
> Another strange behaviour I'm seeing is that if you choose not to
> import the previous session, you are not permitted to continue with
> the burning of the new session on the same CD. You are prompted for a
> blank CD. Very strange, I find.
I've never had a problem with too many sessions but I can't say I
normally burn that many. On a CD, the overhead is around 15mb. The
reason you need to tell the burning software you are going to use
multi-session has to do with how it leaves the cd state. I believe it
creates a new empty session and leaves it open but I might be all wet on
that one.
The default is to normally use multi session (for data) unless you come
across something that doesn't like to read it. My portable cd player
that plays .mp3 will play a multi session .mp3. Audio cd's are normally
closed.
Dave Cohen
On Apr 5, 2:26 pm, Dave Cohen <u...@example.net> wrote:
> Paul wrote:
> > On Apr 2, 11:16 pm, Paul <Paul.Domas...@gmail.com> wrote:
> >> On Apr 1, 7:51 pm, Marlin Singer <marlin.sin...@verizon.SPAMDAM.net>
> >> wrote:
>
> >>> Paul wrote:
> >>>> Roxio's drag-to-disc often-times makes the CD unreadable at the
> >>>> destination computer after a few uses. In terms of reliability, what
> >>>> are your anecdotes on more reliable packages?
> >>>> Thx.
> >>> Just burn a regular disk with CD software. Drag to disk is a packet
> >>> writing software which is notorious for problems. Both with the disks
> >>> created and conflicting with other applications. Other versions of
> >>> packet writing software are Nero InCD, Sonic DLA, and there are others.
> >>> Stay away from them.
> >>> Also if writing to RW disks, that is another item that will go bad at
> >>> any time. They are only good for things like transferring between
> >>> computers. Basically a 1 time use for that write. They can and do go bad
> >>> at any time. I personally would rather write to a regular CD and throw
> >>> it away afterwards. Only a few cents.
> >> Hmm. Could do that. And get around the 106 character limit on the
> >> file path by zipping up file trees. Thanks!
>
> > Well, multisession burns certainly work, but I haven't had ocassion to
> > give it enough of a test drive to determine whether it works for a
> > greater number of sessions than drag-to-disc. I realize that drag-to-
> > disc doesn't have sessions in the same manner as regular burns, but I
> > mean sessions of file transfers, each consisting of possibly more than
> > one file. So far, however, discussions with colleagues reveals that
> > even regular multisession burns stop working after a few sessions,
> > well before the CD capacity is approached. I'm aware that there's a
> > lot of overhead for each session, but I suspect that this isn't cause
> > of the CD failure.
>
> > Another strange behaviour I'm seeing is that if you choose not to
> > import the previous session, you are not permitted to continue with
> > the burning of the new session on the same CD. You are prompted for a
> > blank CD. Very strange, I find.
>
> I've never had a problem with too many sessions but I can't say I
> normally burn that many. On a CD, the overhead is around 15mb. The
> reason you need to tell the burning software you are going to use
> multi-session has to do with how it leaves the cd state. I believe it
> creates a new empty session and leaves it open but I might be all wet on
> that one.
> The default is to normally use multi session (for data) unless you come
> across something that doesn't like to read it. My portable cd player
> that plays .mp3 will play a multi session .mp3. Audio cd's are normally
> closed.
> Dave Cohen
This is just data, and it is indeed set to multisession. I just chose
not to import the previous session, which causes the prompting for a
blank CD.