My system is a Intel Prescott with HT. I saw slimserver lockout behavior with a socketwrapper bug which would only affect single core CPUs so I think this issues may be related to single core systems.
The other factor in the socketwrapper bug was whether slim.exe was run as a user process or a service as Windows can do prioritising within a user process tree. In this bug is Slim.exe run as a user process, run on login or at system startup ? -- bpa ------------------------------------------------------------------------ bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=38571 _______________________________________________ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/discuss
