Discussion in 'CloneDVD' started by rbenard, Jan 11, 2008.

  1. rbenard

    rbenard New Member

    1. cloning 3:10 to yuma, copy appeared successful, no error thrown.

    When I checked the Hard drive directory a 0 size file 3 (no extension) was there. I used "3:10 to yuma.iso" for the file name.

    please consider either precheck or post check of name format of iso file. This may be a bug.

    2. After the first part of the clone process (creating DVD titles), I like to remove the original (while 'creating ISO/UDF image') and put in the next DVD to clone. After the first clone is finished, I hit the back arrow to get to the select drive screen. Suggestion: at this point, allow CloneDVD2 to see the disc has changed and rescan the disc for the new titles/etc. The current action runs a 'diagnosing/recovering dvd' routine.

    Greatest product on the market!
    Last edited: Jan 11, 2008
  2. James

    James Redfox Development Team Staff Member

    Colons in filenames are illegal, but you're right, it should check this.

    CloneDVD cannot "see" this (it operates generically on files), just hit "enter" in the DVD Video path to force a rescan. Or click "Restart" and then "Copy ..." or "Clone ..." buttons.
  3. Mike Miller

    Mike Miller New Member

    I would like to point out that now that more than 7.5 years have passed, the behavior is the same when the filename has a colon in it: a zero byte file with a truncated filename is produced (the filename ends with the last character before the colon). I'm using AnyDVD and CloneDVD2 This suprised me because I thought that earlier versions warned me about colons, but maybe I'm not remembering accurately.
  4. DrinkLyeAndDie

    DrinkLyeAndDie Retired Moderator

    I don't see why this wouldn't be an easy fix. Just add a check and voila. It probably got lost somewhere in a todo list. Someone needs to nudge someone over at Elaborate Bytes.
  5. James

    James Redfox Development Team Staff Member

    Actually, it isn't as simple as it looks. CloneDVD will throw a more or less cryptic error, if it can't open or create a file (the parameter is incorrect or something like that). It doesn't check for the validity of the filename beforehand, and this is IMHO the right thing to do (the rules may change with OS versions or local / remote filesystems).
    With NTFS, this method fails with a name like "3:10 to yuma.iso", as creating a file with this name actually does succeed. A file "3" with a data extension "10 to yuma.iso" is created, and CloneDVD will happily write the image into the data extension.
    Probably not what the user intended. :rolleyes: