If this is your first visit, be sure to check out the FAQ by clicking the link above.
You may have to register before you can post: click the register link above to proceed.
To start viewing messages, select the forum that you want to visit from the selection below.

Maurice wrote:
Using Linux (Mageia-5) I copied some .MTS video files to a Christmas
visitor's USB flash drive to take home to her Windows 7 to play back.
Checked that they played back OK under Mageia (VLC).

But when I tried it on my Windows 7, the system denied the existence of
the whole folder on the flassh drive (though no such problem with a
folder
of.jpg files on same flash drive.)

[Then tried with a different folder name, but this time it said the
folder was empty...]

Anyone know of a way to persuade Windows 7 to play ball here, please?

[Is converting all .MTS to .MOV the only way?]

Sounds like a permissions issue. Take ownership of the folder and
inherit ownership onto all child objects. Then set all permissions for
the Everyone pseudo-account and also recurse or inherit the permissions
onto all child objects.

Easier to get Take Ownership. It adds a registry entry that runs the
the takeown.exe and icacls.exe command-mode programs to take ownership
and change permissions to All while recursing through the child objects.
You could run the same commands from a shell (with admin permissions)
but the registry entry with the command line is much easier. After
install, open Windows Explorer, right-click on a folder or file, and
select Take Ownership.

Does mean, however, the object is visible in Windows Explorer so you can
right-click on it to select Take Ownership. Did you check the
file/folder attributes using the attrib.exe command in an admin-level
shell (cmd.exe)? For a folder object, be sure to include the /D switch.
Run "attrib /?" to get help.

No, it seems to be simply that W7 will have nothing to do with .MTS
files, to the
extent that it ignores folders that contain nothing but them.

In one of my checks on W7 with the .MTS folder, it offered to 'fix it',
and after checking
the result I found that it had simply changed all the "*.MTS" to "*.CHK"
and renamed the
folder "FOUND.000"!

To confirm this, I converted one of the .MTS files to .MOV, put that in a
new folder on
the flash drive, and plugged that into W7.
Result: It found that folder and agreed the file was there, then played
it back
normally...

So now I'm going to similarly convert all the other MTS files and put
that on the flash
drives as a replacement video folder for the visitor to take home.

Maurice wrote:
In one of my checks on W7 with the .MTS folder, it offered to 'fix it',
and after checking
the result I found that it had simply changed all the "*.MTS" to "*.CHK"
and renamed the
folder "FOUND.000"!

No, it did not change the extensions of the files. CHK files are
recovered file fragments due to a corrupted file system. chkdsk could
not ascertain for sure to which original file an orphaned cluster
belongs so it reallocates the cluster into the file system giving it a
generic fileXXXX.chk filename. CHK files are lost/orphaned fragments of
files that are protected from overwriting by allocating them to new .chk
files in the existing file system. You should run 'chkdsk drive: /r'
on that flash drive. It has a corrupted file system, or had a corrupted
file system if the "fix" was to run chkdsk.

Note that chkdsk might fix problems now but flash drives operate
differently than do magnetic media. If the reserve space is not getting
used to mask bad sectors on the flash media so no bad ones are ever
found, the flash drive is going bad. The firmware inside the flash
drive responsible for wear levelling and masking should make the drive
look always look good until the reserve space gets used up, there's no
further space for masking bad memory blocks, and the drive
catastrophically fails. If a flash drive starts to go bad, chkdsk might
be a temporary cure but I'd get the files that I could off that drive
and discard it.

You can find all sorts of flash drive test tools. Most will write gobs
of data to the drive. Flash drives have a maximum number of write
cycles and such testing reduces their lifespan. Because flash has a
limited write cycle durability, they will die. Sometimes suddenly,
sometimes getting flaky but will get worse and then die suddenly. If
you write a lot to flash media, consider it disposable media.

If chkdsk fixes a flash drive, hopefully it was a logical structure
problem only in the file system. If the errors were due to media
defects, look at getting the files onto different media.

You might also consider what file system is on that flash drive. FAT
has no error recovery for files that were left open when the OS crashed
or the processes were killed that had files open on that media. NTFS
includes journaling which can be used to rebuild the cached/buffered
data that failed to get written to the media. FAT is more portable but
NTFS is safer.

No, it seems to be simply that W7 will have nothing to do with .MTS
files, to the
extent that it ignores folders that contain nothing but them.

I wasn't able to duplicate that behavior here on Win 7.
In one of my checks on W7 with the .MTS folder, it offered to 'fix it',
and after checking
the result I found that it had simply changed all the "*.MTS" to "*.CHK"
and renamed the
folder "FOUND.000"!

Sounds like chkdsk ran and corrected some errors. You might try another
flash drive.

Maurice wrote:
Using Linux (Mageia-5) I copied some .MTS video files to a Christmas
visitor's USB flash drive to take home to her Windows 7 to play back.
Checked that they played back OK under Mageia (VLC).

But when I tried it on my Windows 7, the system denied the existence of
the whole folder on the flassh drive (though no such problem with a
folder
of.jpg files on same flash drive.)

[Then tried with a different folder name, but this time it said the
folder was empty...]

Anyone know of a way to persuade Windows 7 to play ball here, please?

[Is converting all .MTS to .MOV the only way?]

Do you use "Safely Remove" or in Linux, do
dismounts before pulling USB sticks ? Maybe the
file system took minor damage.

When a file has an unknown extension or even no
extension, that should not affect visibility.

As for permissions, generally Linux does not
apply an "unbreakable" permission to things
it adds. Linux is not supposed to have support
for SIDs on NTFS. The day Linux gets full support
for every file system feature, is the day it'll
become useless for maintenance.

And I've not run into Linux changing some attribute
bits either (like a Hidden attribute).

No, it seems to be simply that W7 will have nothing to do with
.MTS files, to the
extent that it ignores folders that contain nothing but them.

Windows doesn't do that. I don't know of any OS off the top of my
head that ignores a folder/directory because it contains files
unknown to it.
In one of my checks on W7 with the .MTS folder, it offered to 'fix
it', and after checking
the result I found that it had simply changed all the "*.MTS" to
"*.CHK" and renamed the
folder "FOUND.000"!

That isn't Windows complaining about not knowing what to do with MTS
files, it's complaining about file system issues. It thinks the file
contents on the stick are corrupted. Did you tell your Linux machine
you were done with the stick prior to removing it? Or, did you just
pull it when you thought you copied the last file?
To confirm this, I converted one of the .MTS files to .MOV, put
that in a new folder on
the flash drive, and plugged that into W7.
Result: It found that folder and agreed the file was there, then
played
it back
normally...

That isn't confirming what you think it is. Probably just as well to
convert the files to a more known container, but, aside from that;
you didn't confirm windows itself has a problem with the original
files. What you confirmed was that Windows had a problem with the
file system present on the usb stick.

VanguardLH Tue, 26
Dec 2017 20:49:56 GMT in alt.windows7.general, wrote:
No, it did not change the extensions of the files. CHK files are
recovered file fragments due to a corrupted file system. chkdsk
could not ascertain for sure to which original file an orphaned
cluster belongs so it reallocates the cluster into the file system
giving it a generic fileXXXX.chk filename. CHK files are
lost/orphaned fragments of files that are protected from
overwriting by allocating them to new .chk files in the existing
file system. You should run 'chkdsk drive: /r' on that flash
drive. It has a corrupted file system, or had a corrupted file
system if the "fix" was to run chkdsk.

Yep. To further elaborate on what you wrote that I snipped for brevity,
it's possible the user partially corrupted the drive contents by
removing it from his Linux machine too soon. By that I mean, didn't
tell his linux machine he was done with the drive and just pulled it.

Yes, of course.
When a file has an unknown extension or even no extension, that
should not affect visibility.

It did in this case.

Erm, no. What you observed was file system corruption. You confirmed
that via chkdsk. Windows does not 'hide' files or refuse to access
folders which you think contain files unknown to it. That's just not
how it works.
had no problems on Windows 7. Only the one with .MTS files...
Happy with .MOV equivalents.

You had some sort of issue copying those files from your linux
machine over to that stick. To the point where Windows thought the
folder contents were corrupt. Btw, just because Windows has trouble
reading something doesn't mean that Linux will as well or that it'll
be as severe on a linux system. With that said, just because your
Linux machine thinks all is well with the world on the drive, doesn't
necessarily mean it is. Linux 'cheats' in some respects.

On Thu, 28 Dec 2017 22:23:32 +0000, Diesel wrote:
You had some sort of issue copying those files from your linux machine
over to that stick. To the point where Windows thought the folder
contents were corrupt.

No, only W7 had a problem. File system etc all exactly the same for all
directories on the drive.
Only if the files in a certain directory had filetype 'MTS' did W7
ignore
the whole directory, whereas if the same directory instead contained
'MOV'
files it was happy as proverbial sand boy. QED.

| No, only W7 had a problem. File system etc all exactly the same for all
| directories on the drive.
| Only if the files in a certain directory had filetype 'MTS' did W7
| ignore
| the whole directory, whereas if the same directory instead contained
| 'MOV'
| files it was happy as proverbial sand boy.

One thing you might check: Look in the Registry
under HKCR\.mts and see what's there. I have it
marked as a video file. I suspect VLC did that. It's
possible that .mts can also be something else that's
hidden by default. (If hiding "hidden" files is enabled.)

Why not just install VLC? I wouldn't put anything
past Microsoft when it comes to trying to push their
own media player.