problems --making a copy of a copy

[capt pugwash]

hi
i am having a problem making a back up of a back up--- it gets to about 98% on dvd decrypter and gives a read error--- the disc plays in all my players with no problems
i have also downloaded the latest version of dvd decrypter -as i have read earlier some other people are having problems---- is this related--
i even tried to get it to my hd and it did the same through nero---it just gave a read error at about the same % in......
any help would be appreiciated
thanks capt pugwash

[revlis]

i also have this problem. it happens with maybe 90% of my backups. i've asked this question before, and the consensus seems to be bad media. you'll get problems writing to the outer edges of cheap media because the dye is unevenly distributed in that area. problem is, i've had this same problem with several different brands, and even with discs burned from different burners. i do find that the newest version of dvddecrypter will sometimes succeed (error>retry) where it had failed in the past, but this is a frustrating problem. so i guess i'm in the same boat as you: looking for a good answer to this question. good luck.

[capt pugwash]

revlis
thanks for the taking the time to reply
captain pugwash

[smearbrick1]

If you are copying a backup... you don't need a ripper. It is much easier to either copy on the fly (drive to drive... it works, I've done it) or copy (click and drag) the files from the DVD backup to your hard disk. There is no reason to use a ripper on backups. There is no encryption.

[SLK001]

There is no need to use a ripper on a copy, but if there are problems with the 1st generation copy's disc, then a ripper may be the only way to proceed, because you can tell it to ignore errors (but only to an extent - it can't fix "crap" copies).

The best way is to just drag and drop the files, but this requires that the copy be 100%. It sounds like your 1st generation copy has "issues".

[revlis]

it's just easy to use dvddecrypter (ISO read>write). this same problem happens, however, regardless of the method. i've tried dragging and dropping, using ISO Buster, AnyDVD (i know i don't need decryption), and just straight copy with Nero, and other programs. point is, like the original poster, my discs usually get stuck in the same general area - around 95% and up.

[INFRATOM]

The general answer is problem on media, scratch, dirty or weak spot on media also it could be drive throwing in errors try other drives if you have . Some drives throw in a random error in my case I have Sony dvd-rom one of those 1621 's it took me reformatting my HD and the whole cycle to determine the origin of the problem ( it would put a blank space randomly in one of the files and would run the shrink or recode out of memory space) was dvd-rom and not one of those anti-copy spywares.

[RowMan]

For me, this problem has usually been chalked up to bad media. Now I ALWAYS verify the data immediately after the burn. If I don't, the disc may play OK on my standalone, but I might not be able to copy it or move the contents to my HD if needed.

Recently, I got a 50 pack of Hewlett-Packard discs. Almost every other one could not properly verify after a burn. I then burned the same data to either a TDK or Fuji disc and 99% of the time they verified OK. (You can still occasionally get a bad one even with a good brand.)

Moral of the story... Always verify your data after a burn. It may take longer, but at least you'll know you've got a good disc.

[mstone321]

Please suggest a verify method....

thanks,

[Baldrick]

you can use nero cd dvd speed, dvdinfopro
read http://www.digitalfaq.com/media/dvdmedia.htm (scroll down to the bottom)

[dvdguy4]

Theres always cut, copy, and paste

[revlis]

i don't quite get the point of verifying. i mean, you verify, find out that you have a bad disc (which we know will still play properly), so you keep burning with the hope that one will eventually verify properly? i don't get the logic.

[smearbrick1]

The general answer is problem on media, scratch, dirty or weak spot on media also it could be drive throwing in errors try other drives if you have . Some drives throw in a random error in my case I have Sony dvd-rom one of those 1621 's it took me reformatting my HD and the whole cycle to determine the origin of the problem ( it would put a blank space randomly in one of the files and would run the shrink or recode out of memory space) was dvd-rom and not one of those anti-copy spywares.

What are you talking about? DVD roms inserting blank "spaces" randomly when you are ripping? I don't think so. The authoring houses are putting blank, bogus frames in the dvd structures to hinder ripping, but your dvd-rom doesn't do this...

[RowMan]

i don't quite get the point of verifying. i mean, you verify, find out that you have a bad disc (which we know will still play properly), so you keep burning with the hope that one will eventually verify properly? i don't get the logic.

It's a matter of having a fully functional disc. Sure, if you have a bad disc it will likely still play OK on a standalone (or may not), but what if you need to take that disc and copy it back to your computer? You may not be able to if the files could not be read from the unverifiable disc.

Please suggest a verify method....

I usually burn ISO files with DVD Decrypter and there is a check box to verify after burning. Unfortunately, I'm not familiar with how to this with other burning programs, but I assume it is possible.

[INFRATOM]

my Sony dvdrom was putting the blanks , it was not reading the sector or was dropping frames saving to HD. I determined it was the drive doing it while ripping. I replaced the drive with NEC 3520 problem stopped. I explained what I went through to get to the bottom of it, strange everything looked normal but would drive the SW out of memory space. I could see tha blank frames while scanning with shrink if I deleted them then it was ok.

[INFRATOM]

my Sony dvdrom was putting the blanks , it was not reading the sector or was dropping frames saving to HD. I determined it was the drive doing it while ripping. I replaced the drive with NEC 3520 problem stopped. I explained what I went through to get to the bottom of it, strange everything looked normal but would drive the SW out of memory space. I could see tha blank frames while scanning with shrink if I deleted them then it was ok.

[nerd1701d]

If it's a "backup", Why not just go back to the original?

[BobK]

i don't quite get the point of verifying. i mean, you verify, find out that you have a bad disc (which we know will still play properly), so you keep burning with the hope that one will eventually verify properly? i don't get the logic.

The logic is that you verify after you burn to see if you have a bad disk. When you get a bad disk, you reburn to a new disk. If you constantly get bad disks (or bad burns) then you try to figure out why they're bad and fix the problem.

If you wait until after you've burned a couple hundred disks and then find out they're all bad, it wasn't very logical to not verify and fix whatever caused it sooner.