So, the COD files not only broke MPLAB, but WinZip too?

That's great.

Jc.

At 12:11 PM 5/7/99 -0400, you wrote:
>Thought you guys might get a kick out of this one.
>
>I usually use WinZIP to take snapshots of my code all during the course of
>the day, storing all the zip files in a directory to allow me to go back
>and see what I changed, etc.  A poor-man's VCS, if you would.
>
>A couple days ago I did my usual drag-and-drop of the source (and .HEX,
>.COD, .BAK, etc) files onto a WinZIP window.  WHen I did, it would cause me
>to get a fatal error dialog from it.
>
>Strange.
>
>So I did all the .C, .H files.  It worked.  Added more files. It worked.
>Tried the .COD - it blew up.  Now, mind you, this is the first time a .COD
>has ever done this to me.  I changed a few lines in the app and the problem
>went away.  Weird.
>
>So, I reported this to Winzip.com and attached the offending file.  A
>couple days later I got back a note that said the file I was sending them
>"looked" like a .LZH file, but when WinZIP tried to open it as such it fell
>apart.
>
>Yes, this is a bug in WinZIP, but they have no reason to try to fix the bug
>since it's such a rare thing to occur.
>
>Thought that was neat.  PIC .COD file breaks WinZIP!
>
>The reason I mention it is that sometimes our tools will break and we don't
>know why.  Don't think it's something you did!
>
>Another point is, if you want good tech support help, sometimes you need to
>take the initiative.  I identified the file for them which caused the
>error- they just looked at it and told me why it did what it did.
>
>Andy
>
>==================================================================
>   Montana Design Tech Support - http://www.montanadesign.com
>==================================================================
>
>