files screwed up ascii problem?

[tommygunner]

I had a bunch of movie files on my linux machine and I downloaded to windows machine.

Now, when I try to play them on Windows some of them work and some of them don't. The filesizes are all nearly identical to what was on Linux machine. I'm thinking that maybe that files are ascii when they should be binary or vica versa. I'm wondering how I can tell or what I need to do to fix it. Anyone have some suggestions?

[setarip]

What are the file formats/3 letter extenders of those that won't play under Windows?

[tommygunner]

my files are .avi. Some play under Windows and some don't. I have divx and everything installed so I don't think it is a codec isssue.

[setarip]

) Load one of the problematic videos file into VirtualDub (or one of its many variants) or NanDub

2) From the "File" dropdown menu, select "File Information"

3) Post (here) EVERYTHING you see (BOTH video and audio information), or post a screen capture .jpg of the information box

[tommygunner]

I get cannot detect file type when I try to open the problem files. The ones that work open fine in Virtualdub. I'm not sure what happened but when I downloaded video files via Webmin in Linux to Windows some of them are screwed up and some of them are ok.

[setarip]

"I get cannot detect file type when I try to open the problem files."

Does VirtualDub generate an error message? If so, EXACTLY what is it?

[tommygunner]

I get popup box that says Virtualdub error
"Cannot detect file type of "E:\myfile.avi".

I can't get in to look at file information

[tommygunner]

Trying to open the file in after effects gives me error:

After Effects error: an unspecified AVI or DirectShow error occurred. (1) (53 :: 33)

[tommygunner]

It looks like I'm just at a loss for all of these files.

[setarip]

It certainly sounds like the files have been corrupted.

If you are sufficiently knowledgable, you could load one of the files into a hex editor and see if the header has been corrupted...

[tommygunner]

Originally posted by setarip
It certainly sounds like the files have been corrupted.

If you are sufficiently knowledgable, you could load one of the files into a hex editor and see if the header has been corrupted...

do you know of any good hex editor programs?

[setarip]

WinHex is one...

(VirtualDub contains one, but I've never been able to get it to work properly)

[tommygunner]

Emm, it looks like a total loss. The bad files are all 00's unlike the good files. Thanks for the help.

[setarip]

"The bad files are all 00's unlike the good files."

Sorry to hear that...

"Thanks for the help."

My pleasure ;>}