Right click fox tray icon

One question about AnyDVD beta.

Is there debug code added to the beta version(s), beyond what would normally be found in the released version?

Yes, I tested it with the "on the Fly" option and the Read and Write options. It seems to have been fixed. I used TYG-02 media at 12X. The only thing that still puzzles me is the "Time remaining" jumps all around when using the "ON the Fly" option, I don't think it did before. I will do more testing. I am going to post the new file below, with the new write .dll
I 8:32:03 PM CloneCD Version 5.2.7.1 started!
I 8:32:03 PM ElbyCDIO Driver 5.1.0.1
I 8:32:03 PM ElbyCDIO.dll 5.1.1.2
I 8:32:03 PM CCDDriver.dll 5.0.0.1
I 8:32:03 PM ElbyECC.dll 4.0.0.0
I 8:32:03 PM WriteDVD.dll 2.5.2.9
I 8:32:03 PM Registered to: Alan
I 8:32:03 PM Searching for SCSI/ATAPI devices...
I 8:32:03 PM Device Scan found 0 CD-ROMs and 3 CD-Writers!

Reading through this thread and one other it looks like when reading straight from dvd using shrink\recode and ripguard movies and doing full backups the "out of memory" error still occurs must rip files to hard drive first. Can any one confirm this?

Yes, but according to what James said it shouldn't occur anymore.

using clonecd with a verbatim +r dl disc and the on the fly option, i backed up doom a lot faster than with clonedvd2. just wondering if there are more errors with using the on the fly option and if there is a quality difference between on the fly and writing to hd first then burn?

No.

No, but you should make sure that reader and writer are not on the same IDE cable. Further, you should burn with a lower speed.
If you want to copy "on the fly" with CloneDVD, you can do it as well:
Insert Source & Destination discs, click "Write Existing Data" in CloneDVD, select input and output, done.

It does, if reader and writer are on the same IDE cable, and/or you selected a write speed which is to high. When copying on the fly, you should burn slower. If the stream from the source disc is slower than your write speed, you will have a buffer underrun. Burn-Proof (or similar) will kick in, writing will stop for a short while, then continue. This will cause the remaining time to "jump around". Same can happen if you have scratches on the source disc, causing retries.

this might be a dumb question, but im going to ask anyway. the reader i used was an internal one and the burner is my new lg gsa 2166d external burner. since one is internal and the other external would they be on the same ide channel? also i did notice the time was jumping around, so i just need to lower the speed? one last thing, clonecd doesnt mess around with the layer break, it copies it excatly, i heard clonedvd does something to it?

James,
Just to be clear here. I have always thought that members who say "copy on the fly" were using the term loosely to indicate they were simply using one of CloneDVD's first two methods, "CloneDVD Titles" or "CloneDVD" (rather than "Write Existing Data"). Since I know that with those two methods, CloneDVD actually goes through a read (rip) to HDD step followed by a write (burn) to burner from the HDD step after that ... so I thought I was just excusing the use of the term "on the fly" by other members.

I never thought of using the third method, "Write Existing Data" to do anything other than to burn files ripped to the HDD via Windows Explorer (and now the new "AnyDVD Ripper" feature of 5.9.1.1). But I infer from what you have said that one can use the "Write Existing Data" method to set the source as a DVD-ROM drive and the destination as the DVD-RW drive. Is that correct?

That is indeed "on the fly"! But why do it that way? Like I said, I never thought of that, but it sounds somewhat unreliable and trouble prone even though my IDE configuration is setup as you suggested:

IDE0 Master HDD (OS & Backup Programs)
IDE0 Slave DVD-ROM
IDE1 Master DVD-RW
IDE1 Slave HDD (Pagefile only: have 1GB RAM, so I'm not sure this drive is needed)

And the read surface of the original would have to be in pristine condition, yes?

So, would this be correct order of reliability for the different backup methods?
>Most reliable:
1. Use the new AnyDVD Ripper and burn with "Write Existing Data"

2. Use Windows Explorer and burn with "Write Existing Data"

3. Use either of the "CloneDVD Titles" or "CloneDVD " methods.

4. Use the "Write Existing Data" to copy "on the fly" from ROM to RW drives.
>Least reliable

The "Write Existing Data" method does not allow for removal of Title Sets, Audio/Subtitle Tracks or Splitting onto two disks, correct?

I have had GREAT success using, almost exclusively, either of the "CloneDVD Titles" or "CloneDVD " methods. After two and a half years using CloneDVD, my inexperience in, or even a need to use "Write Existing Data" may be because I have never encountered the "manufacturing defects" so many claim. I have always thought they were a convenient myth to explain bad backup methodology ... all those retail-exchanged movies on a hundred different threads! ... and me only ever encountering 2 or 3 movies that I had unexplained errors when trying to backup! And the fact that AnyDVD removes purposeful (protection) structural authoring "defects". And also, perhaps that I use a one-function, standalone backup rig without conflicts. And that most of my originals collection are in pristine condition.

By the way, does "AnyDVD Ripper" help with originals that have surface scratches or dings?

Thanks,
Whisperer

A bit confused and clarification needed for ANYDVD 5.9.1.1 Release Notes.

"Note: To use DVDDecrypter with AnyDVD set I/O Model to SPTI or ElbyCDIO.
Set CSS Cracking method to none. Disable checking for structure
protection."


Re: DVD DECRYPTER:
Should both these be UNCHECKED. Turned OFF. Are there any others?

FILE MODE (Currently Checked):
"REMOVE IFO STRUCTURE PROTECTION"

IFO MODE (Currently Unchecked):
"REMOVE STRUCTURE PROTECTION"