ClassFactory cannot supply help

[cdrips]

I'm not sure what this is related to, it's got me confused. I get this error "ClassFactory cannot supply requested class". Searched the forum, says file not complete, but I'm sure it is. I encoded a movie and I transfer over to another drive. Plays fine on first drive, then I get that error on second drive. Then, I transfer from second drive over to first drive and plays fine again on first drive? Any idea on what this can be? Although, right now it actually opens up on the second drive, but this time with what seems like glitching blocks everywhere and smearing and sound all out of sync. If this is a bad drive, then wouldn't it not transfer the file to the first drive again correctly?

I tried testing this by making my encode and zipping it up in smaller parts and making a crc check to it. Transfer smaller files in parts over to 2nd drive, crc check it and it passes. I extract my encode and I get the error msg. Weird. Any help?

[tao52]

I would lover to help you, however we need some more information. What program are you using to encode? What codec are you using? Is your source somehow encrypted? What OS are you running? Well I think you get my point, just give us some more info.

[r6d2]

Originally posted by cdrips
If this is a bad drive, then wouldn't it not transfer the file to the first drive again correctly?
If by "transfer" you mean some sort of disk-to-disk copy, software which do that can be more resilient to errors or just silent about them. Players may be dumber when merely playing.

Comparing byte-by-byte the source and destination images will tell you if the transfer really was done perfectly.

(I'm thinking of a bad drive.)

[Tuning]

Originally posted by r6d2
Comparing byte-by-byte the source and destination images will tell you if the transfer really was done perfectly.
(I'm thinking of a bad drive.)
No I don't think it is bcoz of bad drives(sectors).See he could copy back to first drive from the second drive and file plays well.
Then, I transfer from second drive over to first drive and plays fine again on first drive?
:confused:
I think he had encrypted/Compressed the second drive or some thing like that.That is causing the problem.

[r6d2]

Originally posted by Tuning
No I don't think it is bcoz of bad drives(sectors).See he could copy back to first drive from the second drive and file plays well.
I said that because I don't know if he actually played the whole movie or not after the transfer. And a byte compare will take much less time than watching the whole movie, besides being by far a more perfect test than the eye/ear equipment.

[cdrips]

Oops, seems I forgot about the important stuff. I'm running WinXP. Harddrives are both 200gb WD's. One important fact is that the first disk is on a regular IDE controller while the 2nd one is also on an IDE controller, but it's a raid ide controller from an Epox 8k5a3. However, I have 2 other drives raided on the Epox's raid controllers and they exhibit none of these weird problems. I'm not sure if this has anything to do with the way I'm encoding because transfers to different drives work fine. Latest xvid build from Koepi and latest alpha ffdshow. When encoding, bframes at 2, chromo motion and chroma optimizer enabled. (maybe that's why?)

Yes, by transfer I mean disk to disk copy by simply dragging the file to the 2nd drive. When dragging from 2nd to 1st the size in bytes does not change, does not change from 1st to 2nd either.

About playing the whole movie. I don't know if this just effects movies or not, but dragging an exe over, the exe will still open fine.

What is really weird is, after dragging over old movies encoded with the stable xvid build, it plays fine. I'll test some more about this old build theory, but I don't think that's the reason and it's really something else I'm missing. I don't think compression is on either because I can not find that option since it's on the raid ide and it tells me it's a scsi drive, but I will continue looking.

[r6d2]

Sorry, @cdrips, I thought that by drives you were refering to DVD drives. My answer was pertaining to that. Hardware errors on hard drives would not go unnoticed to the XP OS.

Also, by byte-by-byte comparison I meant that, not just the sizes (a tool for this is for instance FileSync.)

As per the new info you add, I'm clueless about that weird behaviour.