Windows 2003 Standard Edition: Can not remove Read only Attribute

Hi all,

I have a windows 2003 Std Ed. server that I have uploaded the files from a SQL Server 2000 Ent Ed. CD to. I am unable to install the program because I can not remove the read-only permissions from the folder or subfolders. I have read MS's KB article and understand this is a "feature" and have tried their listed work around (using the attrib command). I've also found a few other work arounds such as giving EVERYONE full control and removing the propagation of rights from the parent folder. Unfortunately none of this has fixed my issue. At this point I'm staring to wonder if it's an anti-piracy feature and it's just because the files I uploaded are copied from a SQL Server CD. Unfortunately, I don't have the ability to walk over and drop the CD in the tray as this server is in another state. Any direction/suggestions would be greatly appreciated.....

Mark

 

Have you tried logging on with an admin account and taking ownership of the folder then changing the attribute?

 

Hi,

Thanks for the response! Unfortunately, I am logged in as the administrator and have verified that the Administrator account is the owner of the folder.

Mark

 

You could create an ISO of the CD in your location, copy it across then use a utility to mount it like another CD drive in Windows.
You could then install the application as normal as Windows will think it is coming off this new "CD" drive.

Just a thought...

Simon.

 

I have a similar problem trying to integrate a forum on my website. It's all being served from my local machine, so it's no one else's problem but mine ; but perl can't write what it needs to because my folders and files are read-only ; and they won't change! even with the syntax...

 

Thanks for the replies!

Sembee: I like this idea a lot and think I'll give it a try. Can you recommend a utility for the mounting?

Bibby: Are you using W2K3? If so which edition? If you know which folders need to be writ table you could try the command line approach. Something like attrib -R <file name> /S /D might work for you. I think my inability to make the command work for me is due to some kind of built-in software police not liking my copy of a MS product taken from a CD.

I'll tell you though. I find Microsoft's continual intrusiveness to be extremely aggravating. This "by design" feature where the OS knows better than the admin is ridiculous. Eventually, it will likely be where Windows comes with all the applications pre-configured by the version you purchase (I.E. Web Edition, Database Edition, E-Mail edition) and you just plug it in and watch it go. Admins won't have any rights except to change specific settings, and if they don't like the way it runs their welcome to go find another OS. I think my frustration is compounded by the contrast between Windows and the other OSes I work with on a daily basis. I'm used to being able to get under the hood and do whatever I need to do without question. To not be able to disable a built-in "feature" leaves me curled up on the floor in a fetal position mumbling to myself. Sorry for the rant, but I had to vent.

 

Actually, my problem wasn't what I thought it was. Another post on this board gave me the clue that a folder's Properties / Read-Only applied only to the files and not the folder itself. I was flipped out because it likes to highlight read-only by default. All I needed was a more complete copy of Perl to run the script instead of what my server offered. I'm serving webpages, FTP, and now a forum from my local machine running WinXP on DSL. If I power down or close the programs, my pages vanish, but I always have the same FQDM when I decide to return. Here's what I've been using:

• WinXP Pro
• Instantserver's MiniPortal Webserver built on Apache 1.3.?
• Bulletproof FTP Server
• a name with dyndns.org Free service for dynamic IP addresses
• DDU updater updates my IP to dyndns.org, free
• Arts Core's CuteCast Forum looks great, FREE
• ActivePerl to run cutecast better than Apache

------------------------
http://bibby.serveftp.org
Please don't make fun, I'm an unemployed 24 year old. trying to teach himself HTML and javascript ; I am one hell a bass player, so don't shy away from the mp3s.
------------------------
I figure you guys are probably up to something more professional and demanding, but maybe the fix to mandrich's problem could be as simple as fixing mine. Having never dealt with Win2K3, any SQL, or some far off server, I could be way off base here. If I understand correctly that you copied the files from the CD to the server then yes it will be read-only. Copy to your PC first instead and try to manipulate the attributes. The structure likely as an autorun.inf, so burning a copy might be helpful; but shouldn't be required (If you're allowed to even do that). Maybe you were taken back by a folder's read-only status the way that I was ; that it's not an accurate flag. Check the files contained within for their status; and if you can write to the folder with a .txt or something, then it's not a read-only folder. So It could be something entirely different: but I doubt that it's an anti-piracy thing. hmm such a long answer for an amatuer opinion.

 

Hey Bibby,

I'll give that a shot. That would most likely answer my question about if it's a CD thing or a "You can't copy SQL thing ". I'm hoping that if I can upload it in folder form without the Read-only attribute that the system won't apply the attribute after the fact. I'll post the results. Thanks for the input!

Mark

 

Hey Bibby,

It worked!!! I've done this installation on a number of remote Win2000 servers and never had this attributes issue, so it probably never would have occurred to me to copy it over to my local drive, change attributes, and THEN upload it. What a PITA! Anyhow, my deepest thanks for your help! Your idea saved the day!

Mark

 

NICE!!
My pleasure.
Now if I can only get a job like yours!
My good news is I'm back to serving food!

Take care mandrich.