Re: VPF v3.0b on XP Prof.
- From: "Rick Bean" <rgbean@xxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 13 Feb 2006 09:27:25 -0500
Thomas,
While I haven't tried this on an XP machine, I did on Win 9x, and it didn't seem to help VFP 3.0b - it may be using an API call to check the physical memory. I really hope it works in XP. (Of course I don't even have 3.0 installed anymore to test - just 5.0 -> 9.0 and no memory problems there! <g>)
Rick
"Thomas Ganss" <tganss_at_t_dash_online_dot_de-remove-all-after-first-real-dash@xxxxxxxxx> wrote in message news:dseskp$h2t$00$1@xxxxxxxxxxxxxxxxxxxx
Michael J Davis schrieb:
Rick
Thank you so much - that's really helpful. I guessed it might be that. So no artificial ways of limiting memory, then?
Depends on your definition of "artificial". I often reduce the memory acessible to the OS (for perf tests across a simulated spectrum of memory distribution) via the "/maxmem=xxx" switch in the boot.ini.
Just copy your usual line in the boot.ini, add /maxmem=700 and change
the description to something very clear like
"reduced Mem[700] for VFP3.0b"
and you are in business after rebooting with that starting line.
HTH
thomas
.
- Follow-Ups:
- Re: VPF v3.0b on XP Prof.
- From: Michael J Davis
- Re: VPF v3.0b on XP Prof.
- References:
- VPF v3.0b on XP Prof.
- From: Michael J Davis
- Re: VPF v3.0b on XP Prof.
- From: Rick Bean
- Re: VPF v3.0b on XP Prof.
- From: Michael J Davis
- Re: VPF v3.0b on XP Prof.
- From: Thomas Ganss
- VPF v3.0b on XP Prof.
- Prev by Date: Re: VPF v3.0b on XP Prof.
- Next by Date: Re: VPF v3.0b on XP Prof.
- Previous by thread: Re: VPF v3.0b on XP Prof.
- Next by thread: Re: VPF v3.0b on XP Prof.
- Index(es):
Relevant Pages
|