Quote:

No problem. Can you please provide either a Microsoft KB or other URL where there is documented proof of this error you speak of.




If there would be a KB, there would be a fix.
I just got "some" computers in our network and some of them have 512MB RAM. Strangely some report 512MB and some of them report e.g. 504/503MB (!). I'm collecting that info via login-script currently and adjust our database accordingly. I'm now using a "round-up" algo that will fit badly reported RAM into the right amount, but that's REXX.

BTW. In fact actually they report 511MB and my code fixes those into 512MB. Also some are reported as BEING 512MB (without fixing them). Very strange.

[QUOTE]
NOTE: Your current code does appear to support the NoVarsInStrings option, just thought I would mention it as you are a new member here and may not know.



I'm using NoVarsInStrings myself. Doing without this option produces unreadable code (at least imho). I don't use DIMs anywhere though.

Also about that >2GB problem. I already know some (non bloated) solution. Will include that and post the new code then. Thanx for testing.


Edited by M_Kiewitz (2005-02-16 09:53 AM)