Pioneer A-06 and the A-07xl

[Muzik_man]

I have had problems getting "perfect copy" burns. I have backed up software and moveies using Nero 6.3 Ultra and used the Verification utility to check my copies and I alway get 2-4 usually corrupt files. I have had this with both drives and with a fresh install of Win XP Pro. I am wondering if it could be anything else. I have talked to Pioneer and tried everything they suggested like going back to a 40 pin ATA cable. They would look at the drives if I sent them in but I don't think this is the problem. Could it be MB related? I am using a Soyo P4-VDA MB with a 2.4g Intel processor. Thanks for any input.

[Ian]

What media are you using?

[Justin42]

I always have had really bad luck with Nero and DVD burning with verify-- seems like stuff always fails verify no matter what. I gave up and just use RecordNow for doing DVD work. :/

[Muzik_man]

i have used tdk and imation +R and jvc and verbatim -RW same results on all. just tried it on my roomates and all ok now. ever heard of a bad MB causing issues? Soyo?

[Rich]

I had verify problems with Roxio, Nero, and cdcheck. Then I tried opening a dos windows and tried: fc d:\*.* f:\*.* and that had files fail too.

Finally I found the binary switch for fc (file compare) and did:
fc /b d:\*.* f:\*.*
and it passed (within that folder)

Windows XP had comp.exe which needs no switch.
comp d:\*.* f:\*.*

and if you have too many files just pipe it to a file:
comp d:\*.* f:\*.* >> results.txt

I read somewhere that it has to do with padding when the files are burned.

Try the above on those files you had fail their verify.

Hope this helps.

Rrrrich

[dodecahedron]

do you know what's the difference between fc and comp ?

[Rich]

do you know what's the difference between fc and comp ?

Nope. And I'm a little curious myself, but I don't know.

Rrrrich

[dodecahedron]

you also said you had problems with CDCheck.
can you elaborate?
CDCheck has worked very well for me.

[Rich]

you also said you had problems with CDCheck.
can you elaborate?
CDCheck has worked very well for me.

I used cdcheck many times and was fairly pleased but then I started having nothing but failures.

Finally I tried the fc and it failed too and finally I found out about the binary switch for fc and then at that time (like 6 months ago) found out about comp.exe.

I had burns where cdcheck failed and when I ran comp.exe on the files they passed.

I then encountered a message thread or a web page (I forget) that described the problem with padding being added during a burn; I assume for the purpose of filling out a block. This padding would actually have no affect when using the copied (burned) file, but when checking it there would be an error.

I guess using the binary switch '/b' with fc, or just using comp.exe remedies this situation and only the file is checked; with padding or without.

I've even used comp.exe with .iso's and .nrg's (nero) by using nero's drive image to mount an image. I then used comp.exe and sometimes 'fc /b' to compare the files in the image drive with those on a burned disk and had success.

As I told a friend locally; I can see the data on a burned disk actually matching the source data on a hard disk and yet wrongly failing the test, but, if two such data sets pass a compare I believe it would be astronomical difficult for them to actually be different. It would be so incredibly difficult to pass the test and be different.

Your 13 hours ahead of me. That should be about 10 til 2pm now.

Rich

[dodecahedron]

odd.
i might try to get into this.
i had such a thing (CDCheck reporting a difference, fc or comp reporting identical) just once. i don't even remember what it was, i just put it off for a fluke

Your 13 hours ahead of me. That should be about 10 til 2pm now.

???

[Rich]

Your 13 hours ahead of me. That should be about 10 til 2pm now.

???

I just saw your in Isreal, I'm in Hawaii on the other side of the planet!


Aloha,
Rrrrich

[Muzik_man]

The issues I am seeing are bad back-ups or copies such as software that ACTUALLY has a bad file because it won't install from the back-up and tells me there is a corrupt file. Also when, say you back up a DVD movie through compression software, if you verified the copy to the original compressed file there would be a few errors. If you looked at the files they would be there but they would be corrupt and you would notice this when watching the movie by seeing glitches or hang-ups during the movie. As I said though, when I installed my drive in a different computer it passed every test and when I used his drive in my system it failed in mine. So it has to be motherboard related. Just don't know why.