JomiTech Forums

Basically what you are seeing is MSBuild being invoked separately for each file that has local options. This means that only one file is passed to TwineCompile, resulting in the file counts being wrong, and only 1 thread being used for the files. We're looking into ways to process this differently, ...

Open the following folder and delete the mtbcc32PortStack.dat file:

2000/XP:
C:\Documents And Settings\<UserName>\Local Settings\Application Data\TwineCompile

Vista/7:
C:\Users\<UserName>\AppData\Local\TwineCompile

Can you copy and paste the command-line from the console window into here?

Try closing them (TwineCompile -> Close Executors) and see how many you get on the next compile.

How many mtbcc32CompileExecutor processes are running in the background when you have 4 threads with only 2 CPUs?

Interesting, it looks like an XE issue. The codebase for all the plugins is the same, so I wonder if there is a VCL bug here. I'll have to investigate.

The windows timer has a minimum resolution of 10ms, so in the next update to TwineCompile, we'll remove 0ms and replace it with 10ms.

Thanks for reporting this. After investigation, it appears that the VCL TTimer control will not enable with an Interval of 0. So an interval of 0 is not possible.

I can't reproduce this. The dialog stays on the last selected item for me and does not revert to the Threading page.

What OS/IDE are you using?

Is the right thread count passed to mtbcc32? It should appear on the command line as -threadsX where X is the number of threads.