Not too long ago all our computers at work were upgraded. The new systems are much faster, and run Windows XP (the old systems ran WinNT). Soon after the new systems were installed I noticed that Microsoft had added yet another "feature" to their OS - zip compression.
I guess they have a critical need to crush even the tiny amount of competition they get from PKzip and WinZip - either that, or they figure that with Bush and the Republicans in power they can get away with anything.
But here's the funny thing: Microsoft's zip feature sucks. I had an emergency request to zip a couple of files for an urgent transmission. I zipped them them and was just about to send them when on an impulse, I did a quick test-unzip.
Son of a gun! Although I had requested no such thing, the unzipped files recapitulated the entire server folder structure where they were originally created. They should have simply unzipped normally into my C drive, but instead they created a P:/folder/subfolder/subsubfolder/ and put the unzipped files in that. So I deleted the zip file, went back, and made sure that I hadn't checked "include folder structure" or whatever it was. I hadn't.
What to do? I moved the files into the root C drive and tried re-zipping them. They still came out with some sort of messed-up folder structure (I can't remember exactly what it was, because at this point I was panicking a bit). Finally I moved the files onto a server and over to an old computer that still ran WinZIP. Five seconds later I had a perfect Zip file ready to go.
And that wasn't the only problem with the XP Zip "facility". Later I discovered that it often simply wouldn't unzip certain files; I'd click on the files, and nothing would happen. I'd right-click and chose Open or Extract; still nothing. No matter what I did XP simply wouldn't unzip those files, and I couldn't figure out why. WinZIP on my old machine had no problem with the files, so the whole thing was quite a mystery.
Unfortunately the old machine with WinZIP was scheduled to be replaced with a new XP machine soon - I didn't have a choice about that - so I put in a request to have WinZIP installed on the new machine. A few days later I got a call back from IT:
At this point the tech fell back on Standard Response A, which is, assume that the user is a moron who doesn't know how to tie their shoes, much less use a computer. I'm used to that particular ploy, though, and am pretty good at proving that I am, in fact, qualified for my job. In fact, I'm generally more knowledgeable about the software I work with than the IT people.
My point made, the tech agreed to kick the request back upstairs for reconsideration. Three days later the phone rang:
Variations on this dialog were repeated a couple more times over the next two weeks. Finally one day I came in to a voicemail from a relatively high-level and sensible IT guy. He's one of the people who I've worked with a bit, and knows that I can generally back up what I say. Within a couple of hours, I had the latest version of WinZIP installed on my machine.
The program only costs $29 anyway. I can't believe the grief they put me through over 29 bucks!
I guess they have a critical need to crush even the tiny amount of competition they get from PKzip and WinZip - either that, or they figure that with Bush and the Republicans in power they can get away with anything.
But here's the funny thing: Microsoft's zip feature sucks. I had an emergency request to zip a couple of files for an urgent transmission. I zipped them them and was just about to send them when on an impulse, I did a quick test-unzip.
Son of a gun! Although I had requested no such thing, the unzipped files recapitulated the entire server folder structure where they were originally created. They should have simply unzipped normally into my C drive, but instead they created a P:/folder/subfolder/subsubfolder/ and put the unzipped files in that. So I deleted the zip file, went back, and made sure that I hadn't checked "include folder structure" or whatever it was. I hadn't.
What to do? I moved the files into the root C drive and tried re-zipping them. They still came out with some sort of messed-up folder structure (I can't remember exactly what it was, because at this point I was panicking a bit). Finally I moved the files onto a server and over to an old computer that still ran WinZIP. Five seconds later I had a perfect Zip file ready to go.
And that wasn't the only problem with the XP Zip "facility". Later I discovered that it often simply wouldn't unzip certain files; I'd click on the files, and nothing would happen. I'd right-click and chose Open or Extract; still nothing. No matter what I did XP simply wouldn't unzip those files, and I couldn't figure out why. WinZIP on my old machine had no problem with the files, so the whole thing was quite a mystery.
Unfortunately the old machine with WinZIP was scheduled to be replaced with a new XP machine soon - I didn't have a choice about that - so I put in a request to have WinZIP installed on the new machine. A few days later I got a call back from IT:
Tech: "You don't need to have WinZIP. That function is built into XP."
Me: "But it doesn't work."
Tech: "What are you trying to do?"
Me: "Zip files to send to clients." (duh)
At this point the tech fell back on Standard Response A, which is, assume that the user is a moron who doesn't know how to tie their shoes, much less use a computer. I'm used to that particular ploy, though, and am pretty good at proving that I am, in fact, qualified for my job. In fact, I'm generally more knowledgeable about the software I work with than the IT people.
My point made, the tech agreed to kick the request back upstairs for reconsideration. Three days later the phone rang:
Tech: "Corporate Security has turned down your request. They say you don't need to have WinZIP. That function is built into XP."
Me: "*sigh*. That fuction does not work correctly."
Tech: "Tell me what you want to do, and I'll tell you how to do it with the XP zip program."
Me: "I need to zip multiple files without recursing the folder structure and password-protect them."
Tech: "You select-"
Me (interrupting): "-the files that I want to zip, then right-click on them and select "Add to compressed folder" from the resulting drop-down menu. I've tried that. It doesn't work. What's more, it won't unzip a number of the files I'm recieving from our clients. I can send you the files, if you want. Look, these are business-critical files, and I can't perform my job without zipping them."
Tech (after a pause): "I'll check with Security again and get back to you."
Me: "Thanks."
Variations on this dialog were repeated a couple more times over the next two weeks. Finally one day I came in to a voicemail from a relatively high-level and sensible IT guy. He's one of the people who I've worked with a bit, and knows that I can generally back up what I say. Within a couple of hours, I had the latest version of WinZIP installed on my machine.
The program only costs $29 anyway. I can't believe the grief they put me through over 29 bucks!