FiveTech Software tech support forums

Antonio, aquí la segunda parte: Error: Unresolved external '_HB_FUN_DRAWTHEMED' referenced from P:\32BITS\FWH\LIB\FIVEHX.LIB|DIALOG Error: Unresolved external '_HB_FUN_GETDLGBASEUNITS' referenced from P:\32BITS\FWH\LIB\FIVEHX.LIB|DIALOG Error: Unresolved external '_HB_FUN_CDLG2CHR' referenced from P...

... and superscript font Enhancement: set / get hyperlink and detect format in text selected New sample Testrtf5.prg and testrtf5.rc * Fix: function nExtMem() is returning now the same value in both 32 and 64 bits. It keeps returning zero for xHb.com * Fix: function GetCpuSpeed() now reads from the ...

This can resolve my problem.

I'll try

Tks
R

You can implement a function nExtMemOld() that will return the old value: HB_FUNC( NEXTMEMOLD ){   MEMORYSTATUS mst;   memset( &mst, 0, sizeof( MEMORYSTATUS ) );   mst.dwLength = sizeof( MEMORYSTATUS );   GlobalMemoryStatus( &mst );   hb_retnl(...

Understood the new function works well, BUT this not resolved my problem !

I will be not not able to detect the old RAM detected.

And i cannot sum 1 gb, as suggested, to the total RAM, because if a custmer has just 2 GB of real RAM i will get more than 2 GB of calculate RAM.

Thanks any

#include "FiveWin.ch"function Main()   LOCAL cMemoria, nBytes, nKBytes, nMBytes, nGBytes   nBytes  := nExtMem()    nKBytes := nBytes / 1014    nMBytes := nKBytes / 1024    nGBytes := nMBytes / 1014  ...

If you need your old values you could call GlobalMemoryStatus() but beware of this: https://msdn.microsoft.com/es-es/library/windows/desktop/aa366586(v=vs.85).aspx On computers with more than 4 GB of memory, the GlobalMemoryStatus function can return incorrect information, report...

Romeo,

We migrated to Windows API GlobalMemoryStatusEx() as it provides a better result than GlobalMemoryStatus(), thats why it changed.

https://msdn.microsoft.com/es-es/library/windows/desktop/aa366589(v=vs.85).aspx

And we are going to keep using it.

Hi all, My PC has Windows 7 32bit with 4 Gb/RAM In my old version of FWH (8.10) the function nExtMem() gives 2147483647 (2GB) In my new version of FWH (16.01 build 2) the same function nExtMem() gives 3219574784 (2,998... gb) Is there any logic relation between them ? ...

Günther,

* Fix: function nExtMem() is returning now the same value in both
32 and 64 bits. It keeps returning zero for xHb.com

Included in FWH 16.04

... be nearly right. Antonio, see also http://forums.fivetechsupport.com/viewtopic.php?f=3&t=32188&p=189722#p189722. There are problems with nextmem()!

... problem with this combination (Harbour, MSVC 2015 and fwh 16.03) It freezes the application when any runtime error is occured. I have found that nExtMem freze it. function NEXTMEM()return 0 solve the problem. It display the error description. But when I press the Quit button, application ...

... 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, in 16.03 GetCPUSpeed() is coded to "999". No support for 64 in source!

"HKEY_LOCAL_MACHINE\HARDWARE\DESCRIPTION\System\CentralProcessor\0\~MHz"
and compare it with 32 bits GetCPUSpeed() value ?

nextmem() gives in 64 a negative value! I will test this further tomorrow.

Antonio,
GetCPUSpeed() and nExtMem() gives wrong results on 64Bit!