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?
-- John Devereux
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.
-- Regards, Joerg http://www.analogconsultants.com/
There's one other thing you might want to check: See which 'Zone' Windows thinks this server is in and whether the appropriate application launch permissions are set.
This is a long shot, since (as I understand your OP) Windows is trying to execute this as a command. That's a lower security threshold than opening it in an installed application.
-- Paul Hovnanian mailto:Paul@Hovnanian.com ------------------------------------------------------------------ Broken pipe. Command flooded basement.
Any idea where to check that? Tried under properties, admin etc. Nada.
Here is the real puzzler: Windows 2000 Pro on another PC do not have that problem! Thou shalt never upgrade to a "new and improved" Windows unless you absolutely have to. And I had to since Dell only allowed to go back to XP (so I could dodge the Vista bullet) but they said no to Win2K :-(
-- Regards, Joerg http://www.analogconsultants.com/
I doubt it. The executable bit only affects what happens if you try to execute the file on the Unix system on which the Samba server is running. It isn't visible to a Windows system.
Are you sure?
Earlier, you wrote:
That isn't the same thing as treating it as an executable.
Also, try examining the Security tab in the file's Properties dialog. You might need to disable the "Simple File Sharing" option in the Explorer preferences to get that tab to appear. It may be that the LAN drive is trying to provide NTFS-style ACLs and getting it wrong.
ISTR that permission to "execute" a file (i.e. double-clicking on it icon in explorer) can be restricted separately from trying to read a file (e.g. File->Open within in the application).
in
Failure
one
Lenovo is the same, though they will still support Win2K drivers for recent ThinkPads. No SMP though.
-- Keith
Joerg snipped-for-privacy@removethispacbell.net posted to sci.electronics.design:
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.
Where is that security tab? In properties all it said is open with a spreadsheet program. The XP system barfs on that, the Win2K system opens it properly.
Maybe. But it sure doesn't make any sense to me. What good does that do if you can circumvent it by simply opening from within the app?
-- Regards, Joerg http://www.analogconsultants.com/
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/
in
Failure
one
Nope I've seen something about 'Zones', probably under firewall stuff, when attempting to help some poor slob with their Windows boxes. But I don't have one myself.
-- Paul Hovnanian paul@hovnanian.com ----------------------------------------------------------------------- Procrastinators: The leaders for tomorrow.
in
Failure
one
Ok, the firewall is hardware here and all this is behind it. This firewall has two zones: The one on the inside is treated as friendly territory, the one towards the WAN is treated like the Bronx at 2:00am.
-- Regards, Joerg http://www.analogconsultants.com/
For files on my local (NTFS) disks, the properties dialog has three tabs: General, Security, and Summary. For files on a Samba share, the Summary tab is missing.
If the Security tab isn't shown, it can be enabled by disabling the option:
Tools -> Folder Options ... -> View (tab) -> Use simple file sharing (Recommended)
I presume that it's intended mainly for binary executables.
Joerg snipped-for-privacy@removethispacbell.net posted to sci.electronics.design:
Each to their own, at home Linux is my production environment. The workplace has MSwin user boxes and Unix servers. Each system is fine by itself, it is mixing them that causes the headaches.
drive I
it's
PC in
file
Failure
one
on a
Each system runs (assuming its not disabled) its own software firewall. Permissions are asigned to various functions depending on what 'Zone' the data and/or executable is in.
Its possible to configure the system to 'see' the local LAN as a more trustworthy zone and then assign it permissions similar to the local hard drive.
Don't ask me how. It takes me a fair amount of time to find this stuff each time some poor unfortunate (aka Windows user) asks me for assistance.
-- Paul Hovnanian paul@hovnanian.com ----------------------------------------------------------------------- Procrastinators: The leaders for tomorrow.
Joerg wrote:
JeffM wrote:
Jim Thomps>Can the new M$hit abortions save in the old formats?
Yup. OOXML/*.xmlx is an *addition* It's mainly that the *default* format has changed.
M$ Office **will** do ODF as well (with a plug-in). M$ has the best plug-in[1]--but they didn't put it on *their* site and are making all other efforts to distance themselves from OpenDocument Format:
ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.