Page 2 of 2

Re: Read error

Posted: Sun Mar 01, 2020 10:15 pm
by higginm6
I was using a Paragon trial version.
So I bought a license, activated it.
Reformatted the drive.
Re-copied the DCP.
It opened in Dcp-O-Matic Player and verified succesfully.
Thankfully it was only a short film!

I appreciate the the time and speedy replies!

Re: Read error

Posted: Sun Mar 01, 2020 10:20 pm
by carl
Good news indeed! :)

Re: Read error

Posted: Sun Mar 01, 2020 10:46 pm
by Carsten
Can you just try to copy that PCM file again? We heard about these Paragon ext2/3 issues quite a few times.

Oops, I see it's solved.


- Carsten

Re: Read error

Posted: Mon Mar 02, 2020 10:27 am
by higginm6
I did try that at some point but to no avail.

Re: Read error

Posted: Mon Mar 02, 2020 2:18 pm
by Carsten
It would be very strange if Paragon had an issue in a test version that is solved only in a registered version (that would be a very stupid strategy). But may be that test version you downloaded simply contained a bug that is fixed in the licensed version. As I said, Paragon is known for the occasional glitch. Unfortunately, there are not many options left. The windows equivalents of these ext2/ext3 drivers are also known to be shaky. For our internal needs, I usually choose NTFS, as these drivers are more robust. Whenever I use these ext drivers, I start with a reboot, then wait a minute for the system to settle, then do nothing else that just a straight copy until it is finished, and pray...

- Carsten