J
John McGhie
Yes. What you say is correct.
All of the folders on a Windows machine are restricted by the privileges of
the user ID that owns them.
Nothing should ever by in the root of the C drive in a modern Windows
Machine: that space is all owned by the System and would require you to pass
the Administrator password across the network, which is a security no-no.
The other reason is that the Windows disk format has a hard limit on how
many objects can be in the root of a drive.
In modern versions of Windows, all user data should be under a user ID
within "Documents and Settings". If you move stuff there, you would then
need to create a Share for that location, re-log the Mac on to that
location, and move the files in from the Windows machine so they pick up the
correct permissions.
Cheers
This email is my business email -- Please do not email me about forum
matters unless you intend to pay!
--
John McGhie, Microsoft MVP (Word, Mac Word), Consultant Technical Writer,
McGhie Information Engineering Pty Ltd
Sydney, Australia. | Ph: +61 (0)4 1209 1410
+61 4 1209 1410, mailto:[email protected]
All of the folders on a Windows machine are restricted by the privileges of
the user ID that owns them.
Nothing should ever by in the root of the C drive in a modern Windows
Machine: that space is all owned by the System and would require you to pass
the Administrator password across the network, which is a security no-no.
The other reason is that the Windows disk format has a hard limit on how
many objects can be in the root of a drive.
In modern versions of Windows, all user data should be under a user ID
within "Documents and Settings". If you move stuff there, you would then
need to create a Share for that location, re-log the Mac on to that
location, and move the files in from the Windows machine so they pick up the
correct permissions.
Cheers
THIS RESOLVED MY SIMILAR ISSUE:
Had the issue with saving Microsoft Office 2008 files back to the shared
drive of a Microsoft Windows XP Home machine. Had not performed an update of
the Mac but had rebuilt the Microsoft Windows machine, only this time I had
placed the shared folder inside the users My Documents directory.
The work failed to save from the Mac but was saving fine when mounted on
another Microsoft Windows machine.
Turns out that prior to the Microsoft Windows rebuild, the share was at the
root of C:\. Whereas after the rebuild I placed the share in the users My
Documents directory. By moving the share back to the root of C:\ all is now
well.
My guess is that for some reason the Microsoft Windows share is superimposing
restrictions upon the shared folder if it is inside the home directory of
some particular user.
This email is my business email -- Please do not email me about forum
matters unless you intend to pay!
--
John McGhie, Microsoft MVP (Word, Mac Word), Consultant Technical Writer,
McGhie Information Engineering Pty Ltd
Sydney, Australia. | Ph: +61 (0)4 1209 1410
+61 4 1209 1410, mailto:[email protected]