What really stinks about all of these things is that MOST software <br
/>companies. Including Microsoft. publish fixes for issues with
their <br />software, specially when it comes to security holes.<br
/><br />I mean <br />you are publishing games that are SOLD
that <br />contain flaws <br />that <br />prevent <br />you from truly
doing what you paid <br />for. <br />This is not just the <br />case of
COD2. <br />It has been the same <br />/>problems with the ENTIRE
COD line.<br /><br />I wish <br />I could <br /><br />do something
about it, but like <br />everybody here. Unless we come <br /><br
/>/>together we are toast. Specially <br />since they won't release <br
/>COD3 for <br />PC yet. <br />I am sure if they publish <br />it. We are
<br />going to have the <br />SAME old issues: no <br />PB, no this not
<br />/>that, bugs here bugs <br />there.<br /><br />It all comes down
<br />to <br /><br /> the persons doing <br />the QA and the director
of <br />development. Which I <br /><br />know, but I <br />can't publish
out of a <br />courtesy. Look in the game's box that <br />the game
came in.<br /><br /><br />/>/>lists@codclanservers.net <br />wrote:
<br />> Apparently <br />if we <br />want this <br />issue fixed <br
/>we should continue to request <br />> <br />/>that <br
/>/>Activision/Infinity Ward increase the length of this string <br
/>in <br />/>the <br />/>> COD2 MP Client on their next patch,
assuming <br />/>there is <br />another patch <br /><br />> coming
out for COD2 PC. <br />That <br />would <br />practically bring COD2 up to
<br />where <br />> <br />the COD1 <br />1.5 code left <br />off. But
considering 402's <br />/>official statement <br /><br />> that <br
/>Infinity Ward does not <br />intend to fix <br />this <br />issue, let's
not hold our <br /><br />> <br />breath. :/ We're just really <br /><br
/>glad that the COD2 1.3 Linux <br />/>bins were <br />> finally <br
/>released. <br />/>> <br />> <br />Ryan C. <br />Gordon wrote:
<br />/>>> <br />>>> <br />/>Ryan is there anyway <br
/>you could <br />change the code in the linux <br />server to <br
/>/>>>> <br />/>overcome this problem? Or <br />would need
a complate rewrite <br />from <br />/>scratch? <br />/>>> My
understanding of the issue is that the <br />/>/>/>server sends a
string to the <br />>> client, and the <br />client <br />is <br
/><br />truncating it at 1024 bytes, so there's not <br /><br />>>
<br />really <br />anything <br />I can do on the server <br />side. <br
/>>> <br />--ryan. <br />/>> <br />> <br /><br />/>>
--- <br />> To <br />unsubscribe, send a <br />blank email to <br /><br
/>cod-unsubscribe@icculus.org <br /><br />> <br />> <br
/>/>/>> <br />> <br /><br /><br /><br />/>-- <br /><br
/>Thanks, <br /><br /><br />/>Ed Silva <br />Silvex <br
/>/>Consulting Inc. <br />/>esilva@silvex.com <br />/>(714)
504-6870 Cell <br /><br />/>(714) <br />908-1730 Fax <br /><br />The
<br />information contained <br />in this <br />email <br />is
confidential, intended solely <br />for the <br />/>addressee, and may
be legally <br />privileged. Access to this <br />/>email <br />by
other persons is unauthorized. If you <br />are not the <br />intended <br
/>/>recipient, any disclosure, copying, distribution or <br /><br />any
action <br />taken <br />or omitted to be taken in reliance on <br />it,
is prohibited <br />/>and may be <br />unlawful. <br />