Reproducing the cygwin X problems

[Jon TURNEY]

Mike Ayers wrote:
>> From: Dan Tsafrir
>> Sent: Tuesday, February 24, 2009 11:03 PM
> 
>> However, in an attempt to test your hypothesis, I've set the affinity
>> of XWin.exe, emacs, and the vncviewer to only use CPU0 (through the
>> task manager).
> 
> 	I don't think this is a valid test.  What is wanted is a P4 single-core hyperthreader with BIOS hyperthread enable (or a multi processor and a screwdriver).  Anyone have a single/nulti switchable handy?  I'll check my BIOS next reboot.

I think a boot.ini entry with /onecpu is the way to do this.

But I'm not saying that these problems don't exist on single-core machines 
(they do, as I am able to reproduce something like the behaviour mentioned), 
I'm just saying the behaviour may be different (as I don't see exactly the 
behaviour described), and I do not have the resources to test on a 
multiple-core machine.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/