MIke
It's not Vista per se but the amount of RAM being over 4 GB.
I've changed to using GlobalMemoryStatusEx rather than GlobalMemoryStatus:
DECLARE GlobalMemoryStatusEx IN Win32API STRING @lcBuffer
lcBuffer = long2str(64) + REPLICATE(CHR(0), 60)
=GlobalMemoryStatusEx(@lcBuffer)
lnAvailableMem = str2dlong(Substr(lcBuffer, 17,8))
... and also putting the whole thing in a TRY CATCH.
MB Software Solutions, LLC wrote:
> I've got a customer who's running my app that's worked fine in other
> non-Vista installations but for his Vista laptop it's erroring on the
> SYS(3050,x) lines.
>
> I'm not surprised I guess since Vista is sooo strict on any system
> changes. My plan now is to check the windows version using OS() and
> skip the SETMEMORY routine if it's Vista.
>
> Any alternative ideas to that? We went in a gave the app Full Control
> privileges (or so we thought).
>
> tia!
> --Mike
>
>
--
Cheers
============
Brian Abbott
============
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
