If it were really a problem with endian-ness, the file probably wouldn't play at all (header info having been screwed up by byte swapping, not to mention errors at every sample even if you could uncompress the file).

If it were a CRLF problem (as suggested above), the file sizes would not be right -- one version of a given upload file would be slightly bigger than the other -- UNLESS...

Could it be that the amount of uploaded data being written at the server is determined by something in the MIME header, rather than the amount of data actually received? Apologies if this is a stupid scenario -- I'm not that well versed in the conventions for upload transactions -- but if the header reports N bytes (based on the size of the client's disk file) and sends N+x bytes (because some LF's were converted to CRLF), or even N-x bytes (because CRLF byte pairs were converted to LF), would the server still write exactly N bytes (truncating or padded as needed)?

Are you absolutely sure that the file in question was stored correctly on the Vista box before being uploaded via a Vista browser? I've seen a number of cases where people went through tiresome cycles of debugging and testing, but failed to notice that the corruption really started before the data reached the system being tested.

(updated to simplify 2nd paragraph)

In reply to Re: CGI Upload and MP3 Endianness on Unix versus Win32 by graff
in thread CGI Upload and MP3 Endianness on Unix versus Win32 by aplonis

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.