The three VFP files that are needed, to my knowledge, are
GDIPLUS.DLL
VFP9R.DLL
VFP9RENU.DLL
Not sure about the GDIPLUS.DLL, but I'm using XFRX to write PDF files
for reports, and I think it likes having GDIPLUS.DLL around.
I did notice that the runtime files I've been distributing with my apps
are dated 12/2004. I'm wondering if maybe these are pre SP2 (assuming
there was an update to the VFP9R and VFP9RENU files with the SP2.) The
file version shows 9.0.0.2412 while the ones on my system show
9.0.0.5815. Hmmm, update is in order.
Installed new runtime files, rebooted, getting the same performance.
DANG! Wow, I was hopeful there for a minute...
By the way, I did try two different releases of ctGRID....version 3.0
and v4.01. Same performance.
Mike
> What other files are necessary to run VFP9.exe, in order to run vfp9.exe
> Myapp
>
>
>
> On Fri, Mar 4, 2011 at 10:42 AM, Mike Copeland<mlcopel...@gmail.com> wrote:
>
>> Done. Thanks Mike!
>>
>> As I said in another response, I have used this in all my Windows VFP
>> apps for many years...it was already in the application I'm having speed
>> issues with...I re-enabled it and unfortunately it didn't help.
>>
>> ****************************************
>> func SetMem
>> * Requests free RAM memory value from Windows, sets VFP to only utilize
>> that amount.
>> * Prevents slow performance for users who run many apps at the same time.
>> * Keep with CHARTOBIN function below!!
>> LOCAL lnAvailableMem, lpMemoryStatus, lnPct
>> DECLARE GlobalMemoryStatus IN Win32API STRING @lpMemoryStatus
>> lpMemoryStatus = REPLICATE(CHR(0), 32)
>> GlobalMemoryStatus(@lpMemoryStatus)
>> lnAvailableMem = CharToBin(SUBSTR(lpMemoryStatus, 13, 4))
>> * Fine tuning option. Specify a decimal value to allocate less than
>> 100%
>> * i.e. .5 would be 50%
>> *!* lnPct = 1
>> *!* IF TYPE("main.nSetMemoryPct") == "N"
>> *!* lnPct = goApp.nSetMemoryPct
>> *!* ENDIF
>> *!* lnAvailableMem = (lnAvailableMem * lnPct)
>> SYS(3050, 1, lnAvailableMem)
>> SYS(3050, 2, (lnAvailableMem/2) )
>> RETURN lnAvailableMem
>> *********************************************
>> func CharToBin
>> param tcWord
>> * only called by SETMEM()
>> LOCAL lnChar, lnWord
>> lnWord = 0
>> FOR lnChar = 1 TO LEN(tcWord)
>> lnWord = lnWord + (ASC(SUBSTR(tcWord, lnChar, 1)) * (2 ^ (8 *
>> (lnChar - 1))))
>> ENDFOR
>> RETURN lnWord
>> *********************************************
>>
>> I'm pretty sure that's the one.
>>
>> Mike
>>
>>> On 3/3/2011 10:55 AM, Tracy Pearson wrote:
>>>> I wonder if this much memory ends up swapping.
>>>> This might be a good reason to change the SYS(3050) settings.
>>>> Perhaps your Config.fpw might need the old MEMLIMIT, which may not work
>> in
>>>> VFP 9 at all
>>> Use Ed Leafe's Setmemory.prg. It's in the Downloads section on ProFox.
>>>
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
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/4d705fa0.6080...@ggisoft.com
** 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.
