Using the read-only attribute

  • Thread starter Thread starter ms
  • Start date Start date
M

ms

I recently had a thread where a utility had modified my boot.ini file.

Can boot.ini be set to read-only attribute and W2K still works normally?
IIRC, operation does not change boot.ini, so read-only would only protect
the file from problems.

Are there any other critical files like this that it would be useful to set
as read-only?

ms
 
ms said:
I recently had a thread where a utility had modified my boot.ini file.

Can boot.ini be set to read-only attribute and W2K still works normally?
IIRC, operation does not change boot.ini, so read-only would only protect
the file from problems.

Are there any other critical files like this that it would be useful to
set
as read-only?

ms
Click to expand...

Setting the read-only attribute (and probably the hidden attribute) will
protect boot.ini from inadvertent deletion. However, this will not protect
the file against modification by poorly written programs or by malware. They
can reset any attribute, same as you can, and they certainly will.
 
Setting the read-only attribute (and probably the hidden attribute)
will protect boot.ini from inadvertent deletion. However, this will
not protect the file against modification by poorly written programs
or by malware. They can reset any attribute, same as you can, and they
certainly will.
Click to expand...
Thanks, not good news. I was thinking of changing config.sys and my empty
autoexec.bat to read-only, but as you say, no help there.

ms
 
ms said:
Thanks, not good news. I was thinking of changing config.sys and my empty
autoexec.bat to read-only, but as you say, no help there.

ms
Click to expand...

Since config.sys and autoexec.bat are ignored by Windows 2000, it does not
matter one way or another what you do with them.
 
Back
Top