On Sun, 6 May 2012 12:40:29 -0500, Bill Godfrey yak36...@yahoo.com wrote:
On Sat, 5 May 2012 08:54:52 -0500, Paul Edwards wrote:
Most likely the original byte was x'14' which is also quite common in this
location in zip files. In code page 437 and its cousins, x'14' is the
paragraph sign. In
Too many unknowns to be of much help.
Can't even begin to answer your question about what software would produce a
given corruption pattern; there are -so- many possibilities where a translation
might occur and thus corrupt the data. Indeed, the corruption might be as
massive as what you are
On Thu, 10 May 2012 14:23:10 +, Hal Merritt wrote:
I don't know of any good way to attack this withoug going all the way back to
initial file creation, understand the file attributes (to include local code
page), then step through the transmission process understanding exactly what
is
On Sat, 5 May 2012 08:54:52 -0500, Paul Edwards wrote:
I have a zip file that appears to have been produced using pkzip for z/OS.
However, it looks like it has been transmitted using some sort of text
protocol, because the high bit has been stripped from most bytes, and some
other bytes appear
Having just done this, I speak from experience
Almost every file transfer product will transfer either text or binary.
Most have a feature that will make a choice for you. I used the make a
choice for me option and wound up scrambling the three files I had
transmitted. I changed the
On Sat, 5 May 2012 08:54:52 -0500, Paul Edwards wrote:
I have a zip file that appears to have been produced using pkzip for z/OS.
However, it looks like it has been transmitted using some sort of text
protocol, because the high bit has been stripped from most bytes, and some
other bytes appear
6 matches
Mail list logo
