No it doesn't. Those programs let you bind hlds to another CPU, but it
stays local to that CPU. Removing the call would let the app wander over
all the CPU's again and the bug would return.

- Alfred

Steven Hartland wrote:
> Surely that has the same effect as removing the binding to a single
> processor which would be a quick fix?
>
>     Steve
> ----- Original Message -----
> From: "Alfred Reynolds" <[EMAIL PROTECTED]>
>
>> Use one of the many programs mentioned on this list to work around
>> the problem for now. The full fix requires significant changes to
>> our timing architecture (to stop trusting windows) and isn't a quick
>> fix.
>
>
>
> ================================================
> This e.mail is private and confidential between Multiplay (UK) Ltd.
> and the person or entity to whom it is addressed. In the event of
> misdirection, the recipient is prohibited from using, copying,
> printing or otherwise disseminating it or any information contained
> in it.
>
> In the event of misdirection, illegible or incomplete transmission
> please telephone (023) 8024 3137
> or return the E.mail to [EMAIL PROTECTED]
>
>
> _______________________________________________
> To unsubscribe, edit your list preferences, or view the list
> archives, please visit:
> http://list.valvesoftware.com/mailman/listinfo/hlds

_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds

Reply via email to