I found a bug in NCPFS that I haven't the time to fix right now.Here's the problem: if a file contains an extended (Charcodes 128-255) character, especially ` (or a even worse, an word converted ' (curled apostrophe) NCPFS goes butter side down on the directory listing.
It doesn't hand the machine, but it does cause some serious issues on our network, is there a way to make NCPFS understand extended characters in file names?
I would appreciate this being patched. I'll get round to it post-exams if nobody else does. Chris
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
- Follow-Ups:
- Re: NCPFS can't handle extended characters.
- From: Alan Cox <[email protected]>
- Re: NCPFS can't handle extended characters.
- From: Chris Malton <[email protected]>
- Re: NCPFS can't handle extended characters.
- Prev by Date: is TIF_NOTIFY_RESUME used?
- Next by Date: Re: NCPFS can't handle extended characters.
- Previous by thread: is TIF_NOTIFY_RESUME used?
- Next by thread: Re: NCPFS can't handle extended characters.
- Index(es):