Have just discovered this great website. If you guys can't help, no one can.
And so far, none of the solutions I've seen here or elsewhere has worked for me.
Before deploying to Afghanistan last year, I backed up all my data to two CDs, then deleted all the data from our home computer just in case the house was burgled while wife was at work.
While gone, wife had problem with the computer. Friend loaned us a spare computer with XP. What a difference in speed, especially during bootup. So when I returned I started fresh, reformatting the hard drive and installing XP w/SP2. Works great.
Except that the files I put back onto the computer from the CDs are marked read only.
Now we all know why that is, and we know all you have to do is uncheck the box. To make it better, we can tell Windows to also reset the subfolders.
As we also know, it doesn't work, whether tried as user or administrator. Googling this problem shows it's a common one.
Microsoft's solution is to use the old attrib command to reset the read-only attribute. It doesn't work, either. I'm comfortable enough with DOS to know I was doing it right. Also, another post found on Google said it didn't work for him either.
I found a folder on my drive with only a few .doc files and checked them one by one. None of them was marked read-only, yet the folder was.
So why does this matter?
Because when I try to edit my personal website with FrontPage, I get this: Server error, cannot open file "service.lck" for writing.
I get the error only when I'm logged in as user. When logged in as administrator, no error message. Googling the error message is what led me to the read-only solution.
But I don't want to be connected to the Internet when logged in as administrator. (Paranoia? Yes.) So I've got to edit the website as administrator, switch over to user, log on to the Internet (dial-up, no less), publish the changes, find a change didn't work well, switch back as administrator, fiddle with it, switch back to user, log back on the internet, see what it looks like ... ad nauseum.
It appears that read-only attribute is a "feature" of Win XP, and is unfixable. Or is it?
Or is the service.lck error message fixable another way?
And so far, none of the solutions I've seen here or elsewhere has worked for me.
Before deploying to Afghanistan last year, I backed up all my data to two CDs, then deleted all the data from our home computer just in case the house was burgled while wife was at work.
While gone, wife had problem with the computer. Friend loaned us a spare computer with XP. What a difference in speed, especially during bootup. So when I returned I started fresh, reformatting the hard drive and installing XP w/SP2. Works great.
Except that the files I put back onto the computer from the CDs are marked read only.
Now we all know why that is, and we know all you have to do is uncheck the box. To make it better, we can tell Windows to also reset the subfolders.
As we also know, it doesn't work, whether tried as user or administrator. Googling this problem shows it's a common one.
Microsoft's solution is to use the old attrib command to reset the read-only attribute. It doesn't work, either. I'm comfortable enough with DOS to know I was doing it right. Also, another post found on Google said it didn't work for him either.
I found a folder on my drive with only a few .doc files and checked them one by one. None of them was marked read-only, yet the folder was.
So why does this matter?
Because when I try to edit my personal website with FrontPage, I get this: Server error, cannot open file "service.lck" for writing.
I get the error only when I'm logged in as user. When logged in as administrator, no error message. Googling the error message is what led me to the read-only solution.
But I don't want to be connected to the Internet when logged in as administrator. (Paranoia? Yes.) So I've got to edit the website as administrator, switch over to user, log on to the Internet (dial-up, no less), publish the changes, find a change didn't work well, switch back as administrator, fiddle with it, switch back to user, log back on the internet, see what it looks like ... ad nauseum.
It appears that read-only attribute is a "feature" of Win XP, and is unfixable. Or is it?
Or is the service.lck error message fixable another way?