I know. You said it here, too, Dave. :-)
In that thread I recommended getting rid of the fancy-pants SYS(3050) call entirely and just hardcode the value you want to use. There's enough other hearsay out there that says allocating anything more than 512MB will not speed up VFP performance and may actually degrade it. But as Uncle Ted always tells us, you have to test in your environment to truly optimize.
--
rk -----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Dave Crozier Sent: Thursday, November 17, 2016 12:03 PM To: profoxtech@leafe.com Subject: RE: Guess the problem? VFP9, HyperV, 2012R2
As I said in that old thread Richard... works on 32 bit but not 64 bit.
Dave
-----Original Message----- From: ProFox [mailto:profox-bounces@leafe.com] On Behalf Of Richard Kaye Sent: 17 November 2016 16:56 To: profox@leafe.com Subject: RE: Guess the problem? VFP9, HyperV, 2012R2
RE: the memory discussion
https://leafe.com/archives/full_thread/477799
SYS(3050) falls over with large integer values.
--
rk -----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Malcolm Greene Sent: Thursday, November 17, 2016 11:35 AM To: profoxtech@leafe.com Subject: Re: Guess the problem? VFP9, HyperV, 2012R2
Hi Dave,
If you are meaning setting the buffers in VFP using a variant of:
=SYS(3050, 1, MIN(536870912, VAL(SYS(3050, 1, 0)))) && Foreground Buffers =SYS(3050, 2, MIN(536870912, VAL(SYS(3050, 1, 0)))) && Background Buffers
Then beware that this does NOT work on Windows 7 64 bit and causes the VFP app to become unstable.
Yes, that's what I was thinking. Thanks for that update.
Malcolm
[excessive quoting removed by server]