with Windows XP Home all shared folders are read only

[David Lieberman]

I have written an application which resides on a Windows
XP Home edition computer and I want to execute the
application on other machines on my lan. when the
application reads files on the host machine everything
works fine but when the application attempts to write to
a file it doesn't work.

I tried turning off read-only on the folders in which the
file exists. While the command is accepted it doesn't
turn it off. When I check it is still read-only.

I found a KB article which said to use the attrib command
line. I did but that didn't work either.

Now I found another KB article saying that this was a
problem introduced by SP 1. Does anybody have a work
around? Will this "fix" be fixed in SP2?

Any help greatly appreciated.

David

 

[Chuck]

I have written an application which resides on a Windows
XP Home edition computer and I want to execute the
application on other machines on my lan. when the
application reads files on the host machine everything
works fine but when the application attempts to write to
a file it doesn't work.

I tried turning off read-only on the folders in which the
file exists. While the command is accepted it doesn't
turn it off. When I check it is still read-only.

I found a KB article which said to use the attrib command
line. I did but that didn't work either.

Now I found another KB article saying that this was a
problem introduced by SP 1. Does anybody have a work
around? Will this "fix" be fixed in SP2?

Any help greatly appreciated.

David

David,

When you run this application, are you running it locally on each computer, or
from your host machine, across the network?

What folders are you trying to write to? If you're accessing shared folders,
some shares may be read only by default. Other folders may not be accessible.
In XP Home, you access by the Guest account, so whatever permissions the Guest
account has, you are stuck with.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

 

[David Lieberman]

Chuck,

Thanks for your interest. Let me try to clarify the
configuration.

Computer 1 is a Win XP Home machine. The application
resides on it and the files it uses are in a folder on
that machine.

Computer 2 is a Win 98 machine. I go into Network
Neighborhood and find Machine 1. I double click on the
application residing on Machine 1. The application
starts.

As long as the application just does file reads on the
folders on machine 1 everything works fine but as soon as
it attempts to open one of the files for read-write I get
a permission violation.

David

 

[Chuck]

Chuck,

Thanks for your interest. Let me try to clarify the
configuration.

Computer 1 is a Win XP Home machine. The application
resides on it and the files it uses are in a folder on
that machine.

Computer 2 is a Win 98 machine. I go into Network
Neighborhood and find Machine 1. I double click on the
application residing on Machine 1. The application
starts.

As long as the application just does file reads on the
folders on machine 1 everything works fine but as soon as
it attempts to open one of the files for read-write I get
a permission violation.

David,

Kewl. Yet another opportunity to learn how well XP Home shares files with
Windows 9x.

Windows XP uses user-level access. XP Home, which uses Simple File Sharing,
provides user-level access thru the Guest account.

Windows 98 can use either share-level access or user-level access. See Page 36:
User-Level Access:
<http://www.microsoft.com/downloads/...db-aef8-4bef-925e-7ac9be791028&DisplayLang=en>.

I would guess that the folders that you're trying to access across the network
are configured for read-only access. When you "tried turning off read-only",
was it as folder attributes, or sharing?

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.