Multisim 11 only uses one CPU core during simulation

Question

Hi,
Just recently I've been using MultiSim again, v11 if that matters, and simulating goes slow, to my opinion that is.
Now there are two things that I've noticed:
- Multisim only uses one of two CPU cores during simulation, not both;
- I've enabled CPU throttle (AMD's Cool'n'Quiet) but corespeed remains very low even though Multisim needs CPU power while simulating.
The simulating of a NE555-based LED-flash circuit requires about 28 seconds to get to 100ms in the simulation. Now if I can get the CPU to throttle up, by for example having Prime95 stress one of the two cores, then the simulation only requires 12 seconds to get to 100ms.
So here are my two questions:
1. Is Multisim 11 capable of using more than one CPU core while simulating? If yes, how can I get it to use more than one?
2. Probably not the right forum to ask, but is there a way to force Windows 7 Ultimate x64 to throttle up the CPU when Multisim starts simulating? Since Multisim does not seem to stress the only core it uses enough to throttle it up. Using Prime95 on one core does trigger a throttle up.
With regards,
Bart Grefte
Relevant specs:
Windows 7 Ultimate x64
Multisim v11
AMD A4-3400
16GB RAM

Answer 1

Completely forgot this topic....
Is there a good reason why there is no multicore support? Multisim can certainly use it for simulating.
As for the CPU throttling, I found a batch that can increase/decrease the "minimum processor state"-setting and it works immediately, no reboot required.
@echo off
powercfg.exe -getactivescheme > "%userprofile%\appdata\~apo.tmp"
set /p v_currentscheme= <"%userprofile%\appdata\~apo.tmp"
set v_currentscheme=%v_currentscheme:~24,36%
del "%userprofile%\appdata\~apo.tmp"
powercfg -setacvalueindex %v_currentscheme% 54533251-82be-4824-96c1-47b60b740d00 893dee8e-2bef-41e0-89c6-b55d0929964c %1
powercfg -setdcvalueindex %v_currentscheme% 54533251-82be-4824-96c1-47b60b740d00 893dee8e-2bef-41e0-89c6-b55d0929964c %1
powercfg -s %v_currentscheme%
exit
Usage is simple:
Start -> run -> c:\pathtobatch.bat 100
for "minimum processor state"-setting at 100%
Start -> run -> c:\pathtobatch.bat 5
for "minimum processor state"-setting at 5%
Please note that "set v_currentscheme=%v_currentscheme:~24,36%" is not the same for every language. The original batch had "set v_currentscheme=%v_currentscheme:~19,36%" (most likely for the English version of Windows 7), but since my Windows install is in Dutch, I had to change it in order for it to work.
Running the batch with @echo off removed will show why.