
Naive question from an outdated Techy - GDI heap status in VB6
Quote:
>I have recently moved from VB3 to VB6, painful to say the least. I used to
>be able to check the user and GDI memories in 16-bit version using Win API
>GetFreeSystemResources.
>For VB6, Microsoft manuals point me in the direction of GlobalMemoryStatus
>API call in Kernel32, I cannot find any correlation.
There isn't a direct one. User and GDI memory are allocated
and designed quite differently in Win32.
Quote:
>The irksome thing is that the Stress utility supplied as part of Visual
>Studio seems to report this successfully and this matches with system
>resources reported by the venerable My Computer Right Click performance
>figures.
But only in Win95, which still has an extended 16-bit GDI
layer. Win32 has no such support; in fact, the stress utility
you mentioned, when run on WinNT, displays the message
"Can't run 16-bit Windows program - This application
is not supported by Microsoft Windows NT".
That information is only entirely accurate for the 16-bit
subsystem. You can't get an exact correlation in 32-bit
code. There are alternative metrics available; as Adrian
indicated, post what you need to find out, and perhaps
we can help.