On 2014-06-03 18:56, ratzi wrote:
> But in the end dolphin should do the job. See a posting to follow.
Yes, it should.
But over the years, I got better results with ‘mc’ than with most GUI
file browsers. As it doesn’t have to bother with drawing nice graphics
on the screen, it is faster and simpler.
> Now MacOS 9 adds a file ‘FINDER.DAT’ and sometimes a folder ‘RESOURCE.FRK’
> in every folder of a USB pen drive, which itself is formated FAT32.
>
> I already made the following experience: making a backup to a windows volume of a USB pen drive -
> that by MacOS 9 has been ‘amended’ this way - results in that ‘scandisk’ of windows thinks that
> the volume has errors and has to be repaired!
> But if I manually delete all these 'FINDER.DAT’s and 'RESOURCE.FRK’s beforehand,
> scandisk is completely happy!
Oh? :-o
I found this note in a forum (2004): “Unlike windows, which relies on
the extension to determine what a file is, the Macintosh uses the
resource fork folder to tell it what is what. I believe finder.dat holds
window settings (what size the folder was viewed at, how the icons were
arranged, etc.)…”
(http://www.highdots.com/forums/macromedia-dreamweaver/what-finder-dat-files-85858.html)
And this other, even better (2002):
“To copy a macintosh file into MS-DOS disk and back without loosing
anything, the system creates in each folder two hidden items, a file
named “finder.dat” and a subfolder named “resource.frk”.”
“The data fork is stored in the normal folder, under the main name of
the file. The resource fork is stored in the resource folder under a
truncated name.”
(http://www.windowsbbs.com/legacy-windows/2480-what-finder-dat.html)
And the wikipedia has more:
http://en.wikipedia.org/wiki/Resource_fork
“The resource fork is a construct of the (classic) Mac OS operating
system used to store structured data in a file, alongside unstructured
data stored within the data fork. A resource fork stores information in
a specific form, containing details such as icon bitmaps, the shapes of
windows, definitions of menus and their contents, and application code
(machine code). For example, a word processing file might store its text
in the data fork, while storing any embedded images in the same file’s
resource fork. The resource fork is used mostly by executables, but
every file is able to have a resource fork.”
…
“Currently, OS X supports resource forks on Windows SMB shares by
creating a hidden file in the same directory with the data fork file,
with the characters “._” at the beginning of the file name. However,
this may be annoying for some users, especially because some Windows
power users always keep hidden files visible. Besides, Windows does not
treat those files correctly as the file itself is moved or removed. A
few resource fork files created by OS X on an SMB share can be disabled
by an Apple supported action.”
But nowhere can I find a reference explaining your problem, they should
be just files.
>> I know of a certain proprietary application that does a good job of
>> recovering files out of a bad ntfs partition, and it is not expensive,
>> if that’s what you want… (yes, I tried photorec first. Horrible).
>
> Thank you.
> Maybe I’ll contact you on that if everything here goes wrong.
>
> But usually I prefer to have a sufficient number of backup copies (which
> just decreased by one, see above),
> instead of relying on such tools:
Oh, indeed backups are the best thing to have, absolutely
I know of that tool because I had to help a friend. The ntfs filesystem
was corrupted beyond repair, even by Windows. A certain metadata
structure on the disk had been destroyed (I don’t remember the name of
the structure). I tried several opensource tools, got nowhere (photorec
just recovered some multimedia files). The home page of photorec had
advice for this particular problem, and recommended two proprietary
tools for it… It was not expensive and it worked.
> I just bricked a USB pen drive using ‘testdisk’ included on the GParted
> live CD … it’s light went out for ever after telling ‘testdisk’ to
> write the changes to the partition table.
Wow!
> This USB pen drive doesn’t even appear anymore in the list of dolphin of
> partitions/drives available.
> But it still hinders my BIOS from booting when it is plugged - kind of a
> zombie, now.
Plug it afterward booting, and look at the end of /var/log/messages just
after doing it.
If the stick is accessible, it could be reformatted.
> Code:
> --------------------
> myHost:~ # iotop -o
> If ‘iotop’ is not a typo you can use command-not-found to lookup the package that contains it, like this:
> cnf iotop
> myHost:~ #
> --------------------
>
>
> Probably that one needs a .rpm which I haven’t installed.
and “cnf iotop”, as the message says would tell you the exact package to
install, and the exact command line to use.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)