A
Adam Albright
If I knew which Microsoft Redmond boy wonder wrote the code for
improving "security" in Vista I'd have my hands around his throat
about now!
Just kidding... but damn, in the real world, this is a disaster for
anybody that moves files around on their system a lot like I do.
Consider:
People send me via the Internet or email, video files which I edit and
return. Simple enough. Well, used to be.
I have things set up to put raw files in a folder in my E drive.
I work on files in folders on my F drive.
I place finished files in a folder on my G drive.
I just checked the security tab on each hard drive. All are set to
"everyone" and permissions are wide open. Anybody can do pretty much
anything. That shouldn't matter anyway since I AM the only user on
this PC. So unless I'm missing something I should should be able to
move files back and forth between hard drives WITHOUT Windows nagging
about it.
So you would think.
Not even close!
This is the silly part:
In order to work on the files I first move them from drive E to F.
Windows doesn't nag at all, and with one exception, still unexplained,
it lets my video editing software write modified files which start out
as "raw" from the E drive to my F drive without complaining if I save
under the same name or a new one.
I just finshed working on one of these files. All I want to do it move
it to my G drive. Which was in XP a very simple process. Click on the
file in Windows Explorer, cut, then paste where you want it moved to
or just drag and drop, whatever...
A new feature in Vista assuming the file is the same name now brings
up a more detailed warning box and asks if you want to overwrite the
older file showing the date and size of each. That's good. However if
you say yes, it starts, then immediately stops, darken your screen and
starts to nag for permission to move the file before it actually does
the move.
The $64,000 dollar question is why since all drives have 'everyone'
permission and therefore such operations should proceed without issue.
Perhaps some Microsoft programmer thought this was improving security.
Well to test this "security" further I fired up Bounce Back which is
my automated backup application. It is pretty slick in that it can
scan my entire system, all 2 TB worth then it presents a detailed list
of all files that have changed since my last backup. It flags
everything, deleted files, renamed files, files not backed up, etc..
Now watch Bounce Back drive a truck sized hole through Vista security.
Bounce Back tells me 1,427 files have changed since my last backup.
The number is higher then usual because I was doing some house
cleaning. Here's the rub. To do the backup Bounce Back needs to read
files and WRITE newer versions to different hard drives or it adds
files that previously had no backups or it finds and asks if I want to
purge files I deleted that at one time I did have backups for.
Hmm.. I say yes, sit back and watch Bounce Back access and WRITE to
every hard drive I have and do its thing. Not once did Vista utter a
peep, yet to move just one file manually as I explained in the
beginning, Vista goes nuts.
Somebody explain why this is "good" security. Vista doesn't challenge
the moving and deleting of over a thousand files some application
moves around, but screams like a stuck pig if I try to move one file
manually.
improving "security" in Vista I'd have my hands around his throat
about now!
Just kidding... but damn, in the real world, this is a disaster for
anybody that moves files around on their system a lot like I do.
Consider:
People send me via the Internet or email, video files which I edit and
return. Simple enough. Well, used to be.
I have things set up to put raw files in a folder in my E drive.
I work on files in folders on my F drive.
I place finished files in a folder on my G drive.
I just checked the security tab on each hard drive. All are set to
"everyone" and permissions are wide open. Anybody can do pretty much
anything. That shouldn't matter anyway since I AM the only user on
this PC. So unless I'm missing something I should should be able to
move files back and forth between hard drives WITHOUT Windows nagging
about it.
So you would think.
Not even close!
This is the silly part:
In order to work on the files I first move them from drive E to F.
Windows doesn't nag at all, and with one exception, still unexplained,
it lets my video editing software write modified files which start out
as "raw" from the E drive to my F drive without complaining if I save
under the same name or a new one.
I just finshed working on one of these files. All I want to do it move
it to my G drive. Which was in XP a very simple process. Click on the
file in Windows Explorer, cut, then paste where you want it moved to
or just drag and drop, whatever...
A new feature in Vista assuming the file is the same name now brings
up a more detailed warning box and asks if you want to overwrite the
older file showing the date and size of each. That's good. However if
you say yes, it starts, then immediately stops, darken your screen and
starts to nag for permission to move the file before it actually does
the move.
The $64,000 dollar question is why since all drives have 'everyone'
permission and therefore such operations should proceed without issue.
Perhaps some Microsoft programmer thought this was improving security.
Well to test this "security" further I fired up Bounce Back which is
my automated backup application. It is pretty slick in that it can
scan my entire system, all 2 TB worth then it presents a detailed list
of all files that have changed since my last backup. It flags
everything, deleted files, renamed files, files not backed up, etc..
Now watch Bounce Back drive a truck sized hole through Vista security.
Bounce Back tells me 1,427 files have changed since my last backup.
The number is higher then usual because I was doing some house
cleaning. Here's the rub. To do the backup Bounce Back needs to read
files and WRITE newer versions to different hard drives or it adds
files that previously had no backups or it finds and asks if I want to
purge files I deleted that at one time I did have backups for.
Hmm.. I say yes, sit back and watch Bounce Back access and WRITE to
every hard drive I have and do its thing. Not once did Vista utter a
peep, yet to move just one file manually as I explained in the
beginning, Vista goes nuts.
Somebody explain why this is "good" security. Vista doesn't challenge
the moving and deleting of over a thousand files some application
moves around, but screams like a stuck pig if I try to move one file
manually.