Post by thread:MPLab simulation speed?

Guy's, I remember some talk about MPLab running slow unless you move the mouse around or do some miscellaneous keyboard action (something to do with interrupt activity?). But I don't remember seeing a resolution to the problem. Did I miss it? Is there some setting someplace to avoid having to do this? Thanks. --rob--

Rob Santello wrote: > > Guy's, > > I remember some talk about MPLab running slow unless you move the mouse > around or do some miscellaneous keyboard action (something to do with > interrupt activity?). But I don't remember seeing a resolution to the > problem. Did I miss it? Is there some setting someplace to avoid having > to do this? I recently discovered that Windoze will not work with an extended keyboard queue in a DOS session, unless you generate some kind of input events for that window. Just waving the pointer over the window will work, but when you don't the program just sits there waiting for more keyboard input (which is put in the queue already by a small utility) while Windoze spends a few zillion cycles in an empty loop in the kernel. Frank (wondering why he isn't running OS/2 Warp 4...) ------------------------------------------------------------------------ Frank A. Vorstenbosch <UCE_ACCEPT="NONE"> Mobile: +44-976-430 569 Wimbledon, London SW19 Home: +44-181-544 1865 spam_OUTfrankTakeThisOuTfalstaff.demon.co.uk Office: +44-181-636 3391

>> >> I remember some talk about MPLab running slow unless you move the mouse >> around or do some miscellaneous keyboard action (something to do with >> interrupt activity?). But I don't remember seeing a resolution to the >> problem. Did I miss it? Is there some setting someplace to avoid having >> to do this? >Frank A. Vorstenbosch wrote: >I recently discovered that Windoze will not work with an extended keyboard >queue in a DOS session, unless you generate some kind of input events for >that window. Just waving the pointer over the window will work, but when >you don't the program just sits there waiting for more keyboard input >(which is put in the queue already by a small utility) while Windoze spends >a few zillion cycles in an empty loop in the kernel. Ok so I am right in thinking it's one of those Windows 'problems' right? And ... there is no 'fix' or work-around for this? Does everyone sit there and 'wiggle' their mouse while the simulator is running? Hope I'm not ignorantly over-looking something obvious here... Thanks, --rob--