Welcome to the MacNN Forums.

Ilja · Mar 17, 2003, 07:43 AM

I've got a account with webdav support, connected to this server. But when I want to save with OfficeX or textedit to this drive it says it can't save (or the save-button is disabled....)

Anybody knows why?

Ilja · Mar 18, 2003, 06:35 AM

anyone?

nicnab · Mar 18, 2003, 07:05 AM

sorry man but there's a billion possible causes to this. when you look at the info pane of that folder - does it tell you that you have write access? try dropping a file into the folder. if that works, you have write access.

Ilja · Mar 18, 2003, 11:03 AM

it says I have write access, but dropping a file doesn't work.... Guess I have to contact the ISP

Ilja · Mar 19, 2003, 06:09 AM

ok, I emailed the provider of this webdav service and according to him it's a well known problem and it's due to the way Mac OSX handles 'recource forks'

According to him places Mac OSX files (recource forks) in every folder that's created (and that includes webdav folders). These files start with a 'dot', like '.desktop' and the unix server (that's where this webdav server runs on) sees them therefore as hidden. As soon as Mac OSX wants to open the webdav folder unix can't find these hidden files and Mac OSX gives an error.

According to the guy Unix developers sees it as a Mac OSX fault and Mac OSX vice versa...

Anyone who can tell me more about this or knows a solution?

nicnab · Mar 19, 2003, 06:51 AM

this sounds weird... i mean yes mox makes little resource-fork-replacements in every non mac-filesystem. they're always called .filename . this is a little annoying when you zip up directories on a windows machine after accessing it with a mac. you get a bunch of files that windows will show. but that we have to live with.

but i don't understand why unix wouldn't find these files anymore. it is a unix thing to store settings in dot-files - that's why they're not shows when you do a normal ls.

a good solution would be to tell the service provider to switch everything over to mac os x. why bother with anything inferior? :o)

Ilja · Mar 19, 2003, 10:03 AM

Originally posted by nicnab:
this sounds weird... i mean yes mox makes little resource-fork-replacements in every non mac-filesystem. they're always called .filename . this is a little annoying when you zip up directories on a windows machine after accessing it with a mac. you get a bunch of files that windows will show. but that we have to live with.

but i don't understand why unix wouldn't find these files anymore. it is a unix thing to store settings in dot-files - that's why they're not shows when you do a normal ls.

a good solution would be to tell the service provider to switch everything over to mac os x. why bother with anything inferior? :o)

, I'll tell 'm that!

Anyway, I only got this from the guy that's working there, don't know anything myself on these matters. But they told me they were gonna make a workaround on this...