|
I'm not sure those problems can be
solved, as I think they're *designed* to work that way. But I can tell you
a possible reason *why* it does that.
Well, the icon is a 0-byte file
because the real data is in the resource.frk folder or the .appledouble
folder. It's a 0-byte file with resources (basically, the Macintosh header
for the file) that are stored elsewhere. The system wouldn't know to look
for Icon's resources unless there was a placeholder. As for file names
larger than 27 characters not being seen by Windows (at least, I think that's
what you're talking about), there is a limit to how long a Windows file name can
be. It may be 27 characters. It may be that Windows NT chooses to
ignore files that long rather than deal with chopping off the end of it and try
to track that "really long file name which " is actually "really long file
name which is more than 27 characters long" and not "really long file name
which is at least 40 characters long" (each would be truncated the
same way).
----- Original Message -----
|
- Netatalk and Transfer between MAC and Windows NT J�rgen Knott
- Re: Netatalk and Transfer between MAC and Wi... Marc J. Miller
- Re: Netatalk and Transfer between MAC and Wi... Harry Zink/Netatalk List
- Re: Netatalk and Transfer between MAC an... Hauke Fath
- Re: Netatalk and Transfer between MAC and Wi... J�rgen Knott
