Ruud van Velsen
(Hey THIS is FUN)
2022-09-30 05:37 PM
Here's.... 4.69

Hi everyone,

here's the final build of KiXtart 4.69

New functionality/enhancements:

1) Added support for Windows 11, Windows Server 2019, 2022
2) Added @RELEASEID - Windows release ID (eg: 1909, 2003, etc)
3) Added @RELEASENAME - Windows release name (eg: 21H2)
4) Fixed issue with reading binary/resourcelist registry values
5) Added support for reading QWORD registry values
6) Improved errormessage when UDF name conflicts with built-in function

As always: thanks for your help getting this build done and keep scripting!

Ruud

PS - For what it's worth, these are the file-hashes:
KIX32.ex_ 7B53FFAA35DC219216E8BDCB7F8045DC00EAFEAD488A798EF0CDC1A972403179
WKIX32.ex_ 4BDF7478F6BB8EC8ED09378600880C2F279714A094832EEAA26EC99B4DD63511
kixtart.dll CA12E6ABA06B60A4E2D8A0FB2CD4966AC4A9D9CE936E1391DCE795EC082BC5EA
kix2010_469.zip 59BB1B1134D5785488938729D0665380E463C855BF8559FD1EE19AE434C8B883


AllenAdministrator
(KiX Supporter)
2022-10-01 06:42 PM
Re: Here's.... 4.69

Thank you Ruud. Apologies for not getting back with you earlier this year. I'll slowly start putting 4.69 through its paces.

Henriques
(Fresh Scripter)
2022-10-02 09:03 PM
Re: Here's.... 4.69

I see that the kix2010.doc wasn't updated. Date is still from 23-05-2015.
After looking I found that at least from version 4.66 and up it wasn't updated.


Ruud van Velsen
(Hey THIS is FUN)
2022-10-03 11:20 AM
Re: Here's.... 4.69

Yes... good catch. Haven't updated the doc.
I'll put this on the todo list...


Henriques
(Fresh Scripter)
2022-10-03 11:04 PM
Re: Here's.... 4.69

I also found that @CPU gives a wrong type.
In my case @CPU says I have a Intel Pentium Celeron, I have however an Intel® Core™ i7-10750H CPU @ 2.60GHz


Ruud van Velsen
(Hey THIS is FUN)
2022-10-04 03:18 PM
Re: Here's.... 4.69

Good one, thanks.
Determining the CPU name is an art. Haven't looked at that code for some time - I'll see if I can update it.


ChristopheM
(Hey THIS is FUN)
2022-10-09 05:17 PM
Re: Here's.... 4.69

Hello Henriques,
if kix macro @CPU gives you wrong informations, you can get values with WMI.
 Code:
$strComputer = "."
$sQuery	= "select * From Win32_processor"

$objWMIService=GetObject('winmgmts:{impersonationlevel=impersonate}\\'+$strcomputer+'\root\cimv2')
$arrProcessors = $objWMiService.ExecQuery( $sQuery, , 16 )


for each $processor in $arrProcessors
	"name           : " $processor.name ?
	"Architecture   : " $processor.AddressWidth " bits" ?
	"current freq   : " $processor.CurrentClockSpeed " MHz" ?
	"maximum freq   : " $processor.MaxClockSpeed " MHz" ?
	"nb of cores    : " $processor.NumberOfCores ?
	"actives cores  : " $processor.NumberOfEnabledCore ?
	"logical cores  : " $processor.NumberOfLogicalProcessors
	if ($processor.NumberOfEnabledCore <>  $processor.NumberOfLogicalProcessors)
		" (hyper-threading activated)" ?
	else
		?
	endif
next

On my workstation, the result is :
 Quote:
name : Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz
Architecture : 64 bits
current freq : 1600 MHz
maximum freq : 1800 MHz
nb of cores : 4
actives cores : 4
logical cores : 8 (hyper-threading activated)

If you want to reuse the code,you can create a very simple function (supposing all processors are identicals).
 Code:
function getCPU()
	$strComputer = "."
	$sQuery	= "select * From Win32_processor"

	$objWMIService=GetObject('winmgmts:{impersonationlevel=impersonate}\\'+$strcomputer+'\root\cimv2')
	$arrProcessors = $objWMiService.ExecQuery( $sQuery, , 16 )

	for each $processor in $arrProcessors
		$getCPU = $processor.name
	next
endfunction


Ruud van Velsen
(Hey THIS is FUN)
2022-10-10 10:04 AM
Re: Here's.... 4.69

Just to let you know 4.70 is in the works - with a much improved @CPU :-)

Ruud van Velsen
(Hey THIS is FUN)
2022-10-14 05:29 PM
Re: Here's.... 4.69

Just out: 4.70 - this should fix your issue with @CPU.

(and I updated the doc :-))


Henriques
(Fresh Scripter)
2022-10-14 06:00 PM
Re: Here's.... 4.69

But where's the link to download 4.70?

Ruud van Velsen
(Hey THIS is FUN)
2022-10-17 10:26 AM
Re: Here's.... 4.69

Ah yes... managed to miss that in the first edit... it's in there now.

And even better: ntdoc just updated the downloads section!