Version 25.8 and Win98 SE
 

I noticed that the actual Version from the FTP server (Zip-date 5.12.08) isn't running under Windows 98 (SE). A message-Box appears saying that it need's Kernel32.dll:GlobalMemoryStatus.ex.

25.7 just did fine....

I'll try dynamically linking to that procedure

Whoa, version 25.8 is out already? :grin:

[quote=ixfd64;152400]Whoa, version 25.8 is out already? :grin:[/quote]
Not really, just a preview version.

[QUOTE=Mini-Geek;152420]Not really, just a preview version.[/QUOTE]

Is it likely to be released before the holidays? As over the holidays I will be visiting a couple of relatives whom I have 'borged' and would like to update to the latest but also stable version.

M.

[quote=Prime95;152287]I'll try dynamically linking to that procedure[/quote]

Hmm, do you try it against the error, or is the error because you used dynamically linking?

[QUOTE=Phantomas;152535]Hmm, do you try it against the error, or is the error because you used dynamically linking?[/QUOTE]

It was not dynamically linked. Build 3 it will be.

great to hear, so i don't have to throw the old engine out of the race :smile:

Windows 95B
 

[QUOTE=Prime95;152287]I'll try dynamically linking to that procedure[/QUOTE]

A different but related result here? The attached is what I get if I try to run V25.7 under Win95B, (and no I am not that sad, I booted the Win95 machine to get out a CD-ROM I had left in the CD drive about 12 months ago. So I thought what the heck give it a whirl!)

Version 25 may well not run on Win95. I've no plans to fix any Win95 bugs.

[quote=Prime95;152287]I'll try dynamically linking to that procedure[/quote]

Hmmpf, Version 25.8b3 shows the same error message "Prime95.exe is linked to missing export-kernel32.dll:GlobalMemoryStatusEx".

As I googled Win98/95 only did support "GlobalMemoryStatus" that returns a structure
[code]typedef struct _MEMORYSTATUS {
DWORD dwLength;
DWORD dwMemoryLoad;
DWORD dwTotalPhys;
DWORD dwAvailPhys;
DWORD dwTotalPageFile;
DWORD dwAvailPageFile;
DWORD dwTotalVirtual;
DWORD dwAvailVirtual;
} MEMORYSTATUS, *LPMEMORYSTATUS;
[B]dwLength[/B]Specifies the size, in bytes, of the [B]MEMORYSTATUS[/B] structure. Set this member to sizeof(MEMORYSTATUS) when passing it to the [B]GlobalMemoryStatus[/B] function.
[B]dwMemoryLoad[/B]Specifies a number between zero and 100 that gives a general idea of current memory use, in which zero indicates no memory use and 100 indicates full memory use.
[B]dwTotalPhys[/B]Indicates the total number of bytes of physical memory.[B]
[/B][B]dwAvailPhys[/B]Indicates the number of bytes of physical memory available.[B]
[/B][B]dwTotalPageFile[/B]Indicates the total number of bytes that can be stored in the paging file. This number does not represent the physical size of the paging file on disk.
[B]dwAvailPageFile[/B]Indicates the number of bytes available in the paging file.
[B]dwTotalVirtual[/B]Indicates the total number of bytes that can be described in the user mode portion of the virtual address space of the calling process.[B]
[/B][B]dwAvailVirtual[/B]Indicates the number of bytes of unreserved and uncommitted memory in the user mode portion of the virtual address space of the calling process.
[/code]NT/2000/XP & Vista also supports "GlobalMemoryStatusEx" that returns

[code]typedef struct _MEMORYSTATUSEX {
DWORD dwLength;
DWORD dwMemoryLoad;
DWORDLONG ullTotalPhys;
DWORDLONG ullAvailPhys;
DWORDLONG ullTotalPageFile;
DWORDLONG ullAvailPageFile;
DWORDLONG ullTotalVirtual;
DWORDLONG ullAvailVirtual;
DWORDLONG ullAvailExtendedVirtual;
} MEMORYSTATUSEX,
*LPMEMORYSTATUSEX;
[B]Members[/B]

[B]dwLength[/B]The size of the structure, in bytes. You must set this member before calling [B]GlobalMemoryStatusEx[/B].
[B]dwMemoryLoad[/B]A number between 0 and 100 that specifies the approximate percentage of physical memory that is in use (0 indicates no memory use and 100 indicates full memory use).
[B]ullTotalPhys[/B]The amount of actual physical memory, in bytes.
[B]ullAvailPhys[/B]The amount of physical memory currently available, in bytes. This is the amount of physical memory that can be immediately reused without having to write its contents to disk first. It is the sum of the size of the standby, free, and zero lists.
[B]ullTotalPageFile[/B]The current committed memory limit for the system or the current process, whichever is smaller, in bytes. To get the system-wide committed memory limit, call [URL="http://msdn.microsoft.com/en-us/library/ms683210%28VS.85%29.aspx"][B]GetPerformanceInfo[/B][/URL].
[B]ullAvailPageFile[/B]The maximum amount of memory the current process can commit, in bytes. This value is equal to or smaller than the system-wide available commit value. To calculate the system-wide available commit value, call [B]GetPerformanceInfo[/B] and subtract the value of [B]CommitTotal[/B] from the value of [B]CommitLimit[/B].
[B]ullTotalVirtual[/B]The size of the user-mode portion of the virtual address space of the calling process, in bytes. This value depends on the type of process, the type of processor, and the configuration of the operating system. For example, this value is approximately 2 GB for most 32-bit processes on an x86 processor and approximately 3 GB for 32-bit processes that are large address aware running on a system with [URL="http://msdn.microsoft.com/en-us/library/bb613473%28VS.85%29.aspx"]4-gigabyte tuning[/URL] enabled.
[B]ullAvailVirtual[/B]The amount of unreserved and uncommitted memory currently in the user-mode portion of the virtual address space of the calling process, in bytes.
[B]ullAvailExtendedVirtual[/B]Reserved. This value is always 0.
[/code]so the type changed to dwordlong, and an extra info AvailExtendedVirtual that isn't supported now.

Would id be possible to use the older form on w98/w95 systems? Yes I know, it will lead to ugly code.....

Doh. I dynamically got the pointer to the procedure and then forgot to use it. Try again now with build 4.

[quote=Prime95;153201]Doh. I dynamically got the pointer to the procedure and then forgot to use it. Try again now with build 4.[/quote]

That's much better now. Works fine. Thank you George....

[quote=Phantomas;153273]That's much better now. Works fine. Thank you George....[/quote]

And the best: the Benchmark is completing now!
So I lead the page with a huge gap to the next competitor :smile:

CPU Model Speed
(MHz)15.07M
to
17.55M
(896K)17.55M
to
20.05M
(1024K)20.05M
to
24.93M
(1280K)24.93M
to
29.69M
(1536K)29.69M
to
34.56M
(1792K)34.56M
to
39.50M
(2048K)39.50M
to
49.10M
(2560K) ▴49.10M
to
58.52M
(3072K)58.52M
to
68.13M
(3584K)68.13M
to
77.91M
(4096K)Trial
fac
65
bits Intel Pentium1194122.184735.5521933.5176138.23118521.42146534.47203660.43261590.74313004.35366901.93787.01Intel Celeron 2.40GHz2394478.92347.03450.38513.87614.13798.027138.61833.29601.541725.0448.70

[quote=Phantomas;153273]That's much better now. Works fine. Thank you George....[/quote]

And the best: the Benchmark is completing now!
So I lead the page with a huge gap to the next competitor :smile:
[CODE]

CPU Model Speed
(MHz)15.07M
to
17.55M
(896K)17.55M
to
20.05M
(1024K)20.05M
to
24.93M
(1280K)24.93M
to
29.69M
(1536K)29.69M
to
34.56M
(1792K)34.56M
to
39.50M
(2048K)39.50M
to
49.10M
(2560K) ▴49.10M
to
58.52M
(3072K)58.52M
to
68.13M
(3584K)68.13M
to
77.91M
(4096K)Trial
fac
65
bits Intel Pentium1194122.184735.5521933.5176138.23118521.42146534.47203660.43261590.74313004.35366901.93787.01Intel Celeron 2.40GHz2394478.92347.03450.38513.87614.13798.027138.61833.29601.541725.0448.70[/CODE]

(/$§/&"-Tables!

[code]
[FONT=Times New Roman][FONT=Courier New]CPU Model Speed (896K) (1024K) (1280K) (1536K) (1792K) (2048K) (2560K) (3072K) (3584K) (4096K) Trial 65 bits
Intel Pentium 119 4122.18 4735.55 21933.51 76138.23 118521.42 146534.47 203660.43 261590.74 313004.35 366901.93 787.01
Intel Celeron 2.40GHz 2394 478.92 347.03 450.38 513.87 614.13 798.02 7138.61 833.29 601.54 1725.04 48.70[/FONT]
[/FONT]
[/code]