🚀 go-pugleaf

Robert G. Hoover wrote:
> I switched from SetDIBitsToDevice() to DrawDibDraw() because of an
> earlier discussion about "thread-safe" video routines. There seems to be
> no improvement in execution.

I've been doing a little research on this, and it seems that I may be wrong. 
In tests, StretchDIBits and DrawDibDraw both worked in a multi-threaded 
situation.

So, I'd suggest using StretchDIBits.

> And to make matters worse, all my programs run flawlessly on slower
> machines. Is it possible that "we" have crossed a yield threshold where
> the processors are running faster than WinXP can manage? "Windows XP was
> not originally designed to support performance states on multiprocessor
> configurations" (http://support.microsoft.com/kb/896256/en-us)

No - I have a dual-core, and everything works perfectly. It is most likely 
that you're running into multi-threading issues, causing your programs to 
behave erratically.

> Also, the DualCore runs 10x slower on the frame rate, possibly
> indicating that the 2 processors are fighting over the same memory space?

You could be having memory problems, but without seeing the code, it is hard 
to say.

Jon