Robert's way would be the best as winrar can use both cores which will get
the work done faster while remaining responsive (priority change). I
wouldn't encourage users to go around and start playing with advanced
settings that can either degrade their performance (this case) or make them
think they are more knowledgeable than they are. I can see the person's
next post be, "Help I browsed around in the registry and deleted some
entries and now the XXXX doesn't work".
If you don't know what the red button does, don't push it. When you know
what the red button does, you don't push it still unless instructed to.
"Bytesback" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>
> Robert Moir;236591 Wrote:
>> "Bytesback" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>
>> > Ye Gods !!! With this attitude we wont learn anything !
>>
>> I've learnt plenty, thanks.
>>
>> > Just as an example, If I have downloaded a huge RAR file, and I want
>> to
>> > unpack it but still use the computer ( Normally it tie up all the
>> > resources until its fininshed ) I would set affinty to one of the
>> > processors and allow the other one to carry on with everything else.
>>
>> Fair point. I myself would change the process priority to 'below
>> normal', so
>> it runs as more of a background task, thus enabling it to use all the
>> resources it wants to, provided I am not using them myself. This would
>> enable it to take advantage of either core should it find spare
>> resources to
>> do so, and also allow it to duck out of the way a bit if my normal use
>> is
>> using a lot of processor time.
>>
>> I wouldn't like to say if my solution is 'better' or 'worse' than
>> yours, but
>> it's an interesting thought isn't it?
>
>
> My apologies for being rude 
>
> However, if you dont tinker and "get stuck in" you dont learn. Pleased
> to see that you do 
>
> That is an interesting point you have, proves theres more than one way
> to do it 
>
>
> --
> Bytesback