We have some simple procedures running on VPF 3.0b under Windows 98SE.
(On the basis if it ain't broke don't fix it!)


I'd like to get these moved across to a Win XP Pro m/c. (prior to more
complex migration.)

Have tried to install VPF 3.0b on XP[1], but when run, get "Insufficient
memory error"

I rather assume there's a config setting missing, but can anyone help,
please?

(yes I have Googled, but can't see references to older than v.6)

Dell XPPro Pentium 4, 1Gb memory

Thanks

Mike
--
Michael J Davis

<>{
"The very man who has argued you down,
will sometimes be found, years later,
to have been influenced by what you said." CSLewis
<>{

Michael,
You have at least two choices:
1) Reduce the amount of system memory to under 768MB - that's the most VFP 3.0b
supports.
2) Update to a newer VFP - everything beyond 3.0b has no built in memory limits.
VFP 9.0 SP1 is current.

Rick

"Michael J Davis" <miked (AT) trustsof (DOT) demon.co.uk> wrote

Rick

Thank you so much - that's really helpful. I guessed it might be that.
So no artificial ways of limiting memory, then?

Ta.

Mike

Rick Bean <rgbean (AT) NOSPAMmelange-inc (DOT) com> opined
[The reply-to address is valid for 30 days from this posting]
--
Michael J Davis

Pictures at http://www.flickr.com/photos/watchman/
<><
For this is what the Lord has said to me,
"Go and post a Watchman and let
him report what he sees." Isa 21:6
<><

Mike,
Nope - you'll have to actually 'pull' the extra memory out! <g>. This is all
because VFP 3.0 memory handling was a kludge to support both Windows 3.x
(16-bit) and Windows 95/NT (32-bit). VFP 5.0 -> is strictly for 32-bit Windows
OS's and did memory handing properly!

Rick

"Michael J Davis" <miked (AT) trustsof (DOT) demon.co.uk> wrote

Michael J Davis schrieb:
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

Rick Bean <rgbean (AT) NOSPAMmelange-inc (DOT) com> opined
Thanks, Rick!

Mike

[The reply-to address is valid for 30 days from this posting]
--
Michael J Davis

Pictures at http://www.flickr.com/photos/watchman/
<><
For this is what the Lord has said to me,
"Go and post a Watchman and let
him report what he sees." Isa 21:6
<><

Thomas Ganss
<tganss_at_t_dash_online_dot_de-remove-all-after-first-real-dash (AT) yahoo (DOT) co
m> opined
It sounds as though it certainly does. I guess I can have an alternative
boot sequence!

Many thanks

Mike

--
Michael J Davis

<><
To earn the right to complain
ensure you are lavish with your praise.
<><

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 (AT) yahoo (DOT) com>
wrote in message news:dseskp$h2t$00$1 (AT) news (DOT) t-online.com...

In message <11v15qk4gg59m6d (AT) corp (DOT) supernews.com>, Rick Bean
<rgbean (AT) NOSPAMmelange-inc (DOT) com> writes
I'm not really into XP (even though we've got an XP Home and an XP Pro
machine.

I had a quick 'go' at limiting the memory to 712Mb through the config
menu, but FoxPro came up and then complained it was going to tell Dad.
(I need to make sure it is 3.0b that's loaded though.)

I'll report back if I get it to work. Thanks for the 'head's up'!

Mike

[The reply-to address is valid for 30 days from this posting]
--
Michael J Davis
http://www.trustsof.demon.co.uk
<><
For this is what the Lord has said to me,
"Go and post a Watchman and let
him report what he sees." Isa 21:6
<><