On 02 Dec 15  15:16:39, Mark Hofmann said the following to Nick Andre:

MH> I'm not familiar with setting processor-affinity, but since I plan on
MH> upgrading my "tossing VM" that runs D'Bridge and inbound
BinkP for WWIVnet
MH> from XP to Windows 7 32-bit later this year, I'm interested in knowing more
MH> about that.

It is my understanding that the reason this problem happens is because Windows
attempts to share some of the program's instructions across a multi-core CPU. 
Since D'Bridge has some time-sensitive "mission critical" code, the NTVDM 
process ends up mishandling some of the execution.

You start Task Manager, right-click on the D'Bridge process, and click "Set 
affinity". You then assign only one CPU to run it on. I have it set here for 
CPU-0 and that solved the problem instantly.

Nick

--- Renegade vY2Ka2