Antonio,
GetCPUSpeed() and nExtMem() gives wrong results on 64Bit!
Antonio,
GetCPUSpeed() and nExtMem() gives wrong results on 64Bit!
Günther,
Could you check:
"HKEY_LOCAL_MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0\~MHz"
and compare it with 32 bits GetCPUSpeed() value ?
HB_FUNC( NEXTMEM ) // --> nHardwareMemory
{
MEMORYSTATUSEX mst;
memset( &mst, 0, sizeof( MEMORYSTATUSEX ) );
mst.dwLength = sizeof( MEMORYSTATUSEX );
GlobalMemoryStatusEx( &mst );
hb_retnll( mst.ullTotalPhys );
}"HKEY_LOCAL_MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0\~MHz"
and compare it with 32 bits GetCPUSpeed() value ?
Antonio, GetCPUSpeed() gives also in 32Bit different values. From 183Mhz over 2017Mhz(is right) to 3719Mhz.
In 64Bit gives always 999Mhz. I see on source, the function is not ready!
nExtmem gives in 32Bit the correct value, in 64 Bit gives a ( cValToChar( Int( nExtMem() / ( 1024 * 1024 ) ) + 1 ) ) the value of minus(!)-1062
Antonio, any news on that problems?
Günther,
I have been busy working to complete the Windows 10 Toasts support.
How may I help you ? Is the info from the registry ok ?
Antonio, in case of the memory-size i compile your code with Borland 7.1 and the result is ok! With the libs from FWH the result is wrong and negative. Maybe you are not compile the mem.c in the right way??
The GetCPUSpeed() gives always 999. You should write a new function for 64Bit or use the registry-value. It seems to be nearly right.
Antonio, see also viewtopic.php?f=3&t=32188&p=189722#p189722. There are problems with nextmem()!
Günther,
Included in FWH 16.04
Günther,
Included in FWH 16.04
Antonio, thanks! Super, as all time!