bug in extracting read-only files from zip file

[Guest]

When XP copies files from a "Compressed folder" into another directory, that
is to say, extracts from a zip file, it creates a temp folder inside
C:\Documents and Settings\<username>\Local Settings\Temp but forgets to
delete the temp folder afterwards if the files are readonly. So, the temp
directory fills up. Microsoft says call 800-MICROSOFT for reporting bugs. In
case anyone in the US reads this, they can do so. Meanwhile, I've posted this
on my blog hnsws.blogspot.com also.

 

[GHalleck]

When XP copies files from a "Compressed folder" into another directory, that
is to say, extracts from a zip file, it creates a temp folder inside
C:\Documents and Settings\<username>\Local Settings\Temp but forgets to
delete the temp folder afterwards if the files are readonly. So, the temp
directory fills up. Microsoft says call 800-MICROSOFT for reporting bugs. In
case anyone in the US reads this, they can do so. Meanwhile, I've posted this
on my blog hnsws.blogspot.com also.

Cannot call it a "bug" since removal of the temporary files is a
function of the installation program in the extracted folder. But
the real issue is whether or not the installation programmer knows
how to manage the situation. More often than not, the knowledgeable
user will do the extraction to a designated folder that feasibly
could be "anywhere" in the computer. Removal, therefore, depends on
the user doing it. So, what "bug"?

 

[Rock]

When XP copies files from a "Compressed folder" into another directory,
that
is to say, extracts from a zip file, it creates a temp folder inside
C:\Documents and Settings\<username>\Local Settings\Temp but forgets to
delete the temp folder afterwards if the files are readonly. So, the temp
directory fills up. Microsoft says call 800-MICROSOFT for reporting bugs.
In
case anyone in the US reads this, they can do so.
Why?

Meanwhile, I've posted this on my blog hnsws.blogspot.com also.

Ok, so?