Hello:
I have been experiencing problems in burning/copying with DVD Copy Pro since I upgraded to version 3.1.3.4 earlier this morning. My currentconfigurations are as follows:
DVD Copy Pro Version 3.1.3.4 (Set at default)
AnyDVD Version 6.3.1.5 (Set at default)
Currently using Verbatim single or dual-layer blank media to make exact copies only
Using original DVD's to copy from/on to blank media
Windows XP Operating System
Since upgrading, I receive the following message from the DVD Copy Propop-up message screen:
The process "AnyDVD" was detected with the setting "Copy protection based on unreadable sectors" enabled. This setting is not compatible with the concurrent use of of 1 Click's CPRx setting. We recommend you disable CPRx if you wish to use AnyDVD for bad sector error correction. Click the "OK" button to disable CPRx for this DVD.
I never had a problem nor have I ever received this type of message before, until now with this upgrade. Does anyone know of a bug within version 3.1.3.4? Is there anything else I can do to get back to trouble free copying? Best, and thanks,
Mark
I have been experiencing problems in burning/copying with DVD Copy Pro since I upgraded to version 3.1.3.4 earlier this morning. My currentconfigurations are as follows:
DVD Copy Pro Version 3.1.3.4 (Set at default)
AnyDVD Version 6.3.1.5 (Set at default)
Currently using Verbatim single or dual-layer blank media to make exact copies only
Using original DVD's to copy from/on to blank media
Windows XP Operating System
Since upgrading, I receive the following message from the DVD Copy Propop-up message screen:
The process "AnyDVD" was detected with the setting "Copy protection based on unreadable sectors" enabled. This setting is not compatible with the concurrent use of of 1 Click's CPRx setting. We recommend you disable CPRx if you wish to use AnyDVD for bad sector error correction. Click the "OK" button to disable CPRx for this DVD.
I never had a problem nor have I ever received this type of message before, until now with this upgrade. Does anyone know of a bug within version 3.1.3.4? Is there anything else I can do to get back to trouble free copying? Best, and thanks,
Mark