Note: --- May work only if you are using multicore CPUs. My configuration (may apply to another also): --- Windows XP x64 SP2, Pentium D
_Bug workaround #1:_ --- Start PSPad, run Windows Task Manager (Ctrl+Alt+Delete), select Processes tab and PSPad.exe process. Right click on it and select "Set affinity...". Then leave only one processor enabled and disable (uncheck) all other. Click OK. This prevents PSPad from running on more CPU cores and the synchronization leak will not apper (at least in my case). Note: This setting must be done before any execution of external compiler/tool. If the result in log window is once mangled, any future affinity setting would not help. _Bug workaround #2:_ --- (The same as #1 but done in other way) Run PSPAD with specified affinity. Type on command line (or create .BAT with): start "" /affinity 1 "c:\Program files\PSPad editor\PSPad.exe" Note: It is not applicable if you are launching PSPad by clicking on associated file. Note: "start" is an internal command of Windows cmd.exe, First "" parameter is program title what need to be specified because the first quoted parameter is treated as new window title. But full path to PSPad typically also need to be enclosed in "". _Indicias leading to (blind) workaround:_ --- I read your discussion about possible synchronization problems when capturing external compiler output. I have also noticed that if I run external complier "off the real" (still holding Ctrl+F9 with maximum keyboard autorepeat speed), the result of previous execution is mixed with result of successive execution (?) - it seems that the external tool can be executed even if previous execution was not finished yet. -- <http://forum.pspad.com/read.php?4,37697,40696> PSPad freeware editor http://www.pspad.com
