On 6/3/11 12:33 PM, MB Software Solutions, LLC wrote: > On 6/3/2011 2:50 PM, Dan Olsson wrote: >> > At 2011-06-03 20:39, you wrote: >>> >> Turns out, Ed's setmemory.prg fails on 64-bit Windows 7, probably >>> >> because available memory reports> 2 GB and then we try to set memory >>> >> to it. >> > >> > How does it not work? >> > >> > I use 64-bit W7 with 8GB ram and have no problems - but on the other >> > hand I don't set VFP mem to more than 2GB, why would I? > > Exactly...that was my "workaround" -- just set the max to 2GB.
I just modified setmemory to use a max. of around 1 GB - can't see why it would need more than 100 MB. Testing now and will deploy in a few minutes. Our first user with 64-bit and memory > 2 GB installed our application yesterday, and it seemed to work until it hit the setmemory call (in my base report form class). Paul _______________________________________________ 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.
