|
|
|
|
#1 |
|
Member
|
Possible to detect Hyper Threading?
EDIT: Actually I know how to find it I just don't know how to have the installer discover it.
The hyper-threaded kernel file is originally named ntkrnlmp.exe but when it's copied to a HT machine it's renamed to ntoskrnl.exe. However in the Version tab in the Original Filename field it still says "ntkrnlmp.exe" How can I get the installer to read that value into a variable? |
|
|
|
|
|
#2 |
|
Member
|
Okay it turns out I found the solution using the sysinfo.dll plugin.
I searched the NSIS Archive for sysinfo and it didn't find anything, but in the actual Downloads section it was listed alphabetically. The original demo code was designed to use macros to pass parameters and it required physically extracting the dll to a temp directory. I moddified the code however to work without macros for my instance, and to use the plugin call. Here is the code if anyone is interested: code: |
|
|
|
|
|
#3 | |
|
Junior Member
Join Date: Sep 2003
Location: Roswell, GA
Posts: 44
|
Quote:
Cheers! Luke |
|
|
|
|
|
|
#4 |
|
M.I.A.
[NSIS Dev, Mod] Join Date: Oct 2001
Location: Israel
Posts: 11,343
|
http://or1cedar.intel.com/media/trai...t_v1/tutorial/ contains a code example for detecting hyper-threading. It shouldn't be hard to put that into a plug-in.
NSIS FAQ | NSIS Home Page | Donate $ "I hear and I forget. I see and I remember. I do and I understand." -- Confucius |
|
|
|
![]() |
|
|||||||
| Thread Tools | Search this Thread |
| Display Modes | |
|
|