On 6/4/2012 6:25 PM, Johnny Billquist wrote: On 2012-06-04 16:14, Brian Hechinger wrote: On 6/4/2012 7:55 AM, Dave McGuire wrote: It detects the idle loop patterns in some OSs and throttles back the simulator, so the host system isn't sitting there burning CPU to execute the guest OS's idle loop. Right, but I'm curious what it needs to know about the host OS to accomplish that. There is nothing that would be required that is special in the host OS. simh already needs to tweak things all the time to run. Just sitting still for a moment is what is needed. If one Unix can do it, so can all of them. Hmmmmm. I should look at the source but I'm not sure I'll know what I'm looking at. :) If you *really* want to know, I suppose I could go and dig through the code and locate the code... Well it's not a huge deal although it would be nice. I'd be curious to know what it is that triggers this error on Solaris only. -brian