can't see files in compressed folder

[Alex]

Hi,

I have a compressed 'zip' folder that's been sent to me and I can't see the
files in it on my windows XP machine.

If I scan it for viruses using McAfee on my machine, it see's and scans and
lists the files just fine.
If i use winzip on another machine I can see the files just fine.
If I use windows 2003 server to open the file then it see's the files just
fine i.e. more up to date version of compressed folders.

My problem is no Windows XP machines are able to see the contents of the
Compressed 'Zip' folder. Everyone I've tried it on is fully patched. I've
never experienced this problem before and can see the contents of other
compressed 'zip' folders and create them just fine.

I'm worried that my users may receive more files like this from the source
they got them from and seeing that win2k3 opens it just fine I wondered if
there was any fix available?

tia
alex

 

[David Candy]

Any of the filenames got commas in them.

 

[Alex]

A slight update to this is that I've just copied the zipfldr.dll file from a
win2k3 server which has also fixed the problem.

Obviously I'd prefer not to use this as a solution - who knows what the
reprecussions may be. It suggests though that there's definitely a problem
with the zipfldr.dll that comes with WindowsXP and that there should be an
update to it ???

 

[Alex]

Yes, and removing the comma has fixed the problem.

Is there a patch expected for this do you know ?

Do you know when this bug crept in, because by all accounts things were
working fine until I patched this guys machine several weeks ago - but you
can never trust users to be factually correct


Any of the filenames got commas in them.

 

[Alex]

Nevermind, found it
http://support.microsoft.com/default.aspx?scid=kb;en-us;813942

Thanks for the pointer

 

[David Candy]

Type zipfldr in help while online. Read it carefully as if you ask, as 90% of people do, "how do I get it" you'll be treated as an idiot.

Though the server one should be ok, it's just that XP will/may replace it at some stage with the faulty one (Windows File Protection/System File Checker).

It is caused by an update and the update will also be in help (buffer overrun hotfix).