>|> tar/cpio/pax started bothering about some compressing problems.
>|but in that case you surely would have included more specifics such as the
>|text of the error messages or maybe even a vague recollection of what they
>|may have referred to... can you, perhaps, recreate it and give more
>|detail?
>sorry, you can perhaps imagine the situation:
>my friend called me just after his development workstation
>broke, and it's his first time with a unix shell ;-)
First, consider using --- http://www.sysinternals.com/recover.htm ---
freeware or shareware NTFS disaster recovery utilities : this might solve
this very specific problem. Many utilities aroud include sources, but one
needs some knowledge of Win32 API and SDKs to get benefice of them.
I had "some" success with basic dd/cat to recover broken NTFS disks. :-)
>i just wondered if this might be a very typical problem with ntfs; i
>don't have the docu for the ntfs module here ( _very_ old kernel..)
>
>|2) One is going to appear on my desk within the next week or two.
>|
>|So, NT support will be improving dramatically. Soon. If only because I
>|will be stuck with it...
http://www.sysinternals.com/defrag.htm is prolly the start point for NTFS
rookies. Russinovich papers are just the best free souce on information I
ever found about NT concepts.
Also being a rookie with all this, I humbly feel that full NFTS-writing
support for Linux will be a pain, just because some of NTFS concepts, such
as ACLs, ADSs and journalling, would be a pain for the poor lil'kernel
unuware of such concepts.
>sure, be prepared for the worst, because it *is* the worst ;-)
>like to tell us what you need it for ?
luck, prolly.
--
Pierre MONDIE : SSR : 74-78
