Re: File compatibility issues with LAN drive

JosephKK wrote:
Joerg notthisjoergsch@xxxxxxxxxxxxxxxxxxxxx posted to
sci.electronics.design:

John Devereux wrote:
Joerg <notthisjoergsch@xxxxxxxxxxxxxxxxxxxxx> writes:

Greg Neill wrote:
"Joerg" <notthisjoergsch@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:TlB3j.1452$Vq.834@xxxxxxxxxxxxxxxxxxxxxxx

Data doesn't get corrupted. Even super-large files are perfectly
ok. It's just that the PC wants to start them as an application
while it treats local files with same extension as data files
and launches them correctly into (and not as) an application.
Maybe it's a file name length issue with the NFS
implementation. If the path + filename length
is greater than a user defined or default length
(255 characters I believe), then perhaps it's
getting truncated or otherwise mucked up, or the
error is not being handled correctly.

Can you try copying or renaming one of the suspect
files to a short length name and placing it in
a top level directory on the drive?

Didn't work :-(

When calling the file from within an application everything is
fine. When clicking the files it errors, the local PC fails to
launch the application registered for that file extension.
I seem to recall an issue with samba interoperation with
linux. Windows did not have a file "executable" flag, whereas linux
does. So samba would default to setting the flag when writing a
file to disc, making all files "executable". Now this would
normally not make any difference from the point of view of windows.
But perhaps windows has smartened up and is now interpreting this
flag somehow?

Making _all_ files executable? Somehow that doesn't strike me as a
particularly smart move ... But yeah, this could indeed be the
problem because Windows always wants to start them as executables.
Doesn't explain the unzip problem though. Winzip refuses a file on
the LAN drive. Once moved to a local drive it accepts it.

Thanks for the hint.


There are some really wild differences between *nix file permissions
systems and NFTS file system permissions. The default Samba install
does not remap these very well. Typically setting all permissions to
yes.


All the more reason to stay away from Linux and all that. It'll just create more non-productive debug work, and I've got enough productive work right now.

I'll just do regular mirror copies onto the XP machine which "fixes" it.

--
Regards, Joerg

http://www.analogconsultants.com/
.

Relevant Pages

  • Re: File compatibility issues with LAN drive
    ... launch the application registered for that file extension. ... normally not make any difference from the point of view of windows. ... problem because Windows always wants to start them as executables. ... There are some really wild differences between *nix file permissions ...
    (sci.electronics.design)
  • Re: File compatibility issues with LAN drive
    ... treats local files with same extension as data files and launches them ... the application registered for that file extension. ... Windows did not have a file "executable" flag, ... So samba would default to setting the flag when writing a file ...
    (sci.electronics.design)
  • Re: File compatibility issues with LAN drive
    ... the application registered for that file extension. ... Windows did not have a file "executable" flag, ... So samba would default to setting the flag when writing a file ... this could indeed be the problem because Windows always wants to start them as executables. ...
    (sci.electronics.design)
  • Re: Really easy cygwin / gcc question
    ... if you're running from the CYGWIN shell you ... Windows or DOS. ... to have the .exe extension, as it doesn't mean anything special. ... so executables always have names ending in ...
    (comp.lang.c)
  • Re: Christina Aguilera caught back stage NUDE - Yerrrr. VIRUS ALERT AGAIN. SEE THE OTHERS!!!!!
    ... Under windows the types that should raise a flag in your head saying "ah ... under windows if "hide extension of known file types" ...
    (comp.lang.java)