Re: Error rendering image in VFP3.0b

OK, so how does 11 years sound then? <g> VFP3 is absolute *ancient*
history.

--
Fred
Microsoft Visual FoxPro MVP


"Gene Wirchenko" <genew@xxxxxxxxxxxxxxxxxxxxx> wrote in message
news:l831a2toos99ikta1riqgmcehhtp6ej2q3@xxxxxxxxxx
On Mon, 26 Jun 2006 07:58:37 -0700, "Dan Freeman" <spam@xxxxxxxxxxxxx>
wrote:

Since you don't remember the error message, how is anyone supposed to even
TRY to help you?

If I was guessing, I'd guess the new hardware has too much memory for VFP3
(which was obsoleted SIX versions ago).

Try five. There was no VFP 4.

And so what? I remember when there were .2 and so on
subversions. Now, I rarely see anything past .1. It make whole
number version number much less impressive.

[snip]

Sincerely,

Gene Wirchenko



.

Relevant Pages

  • Re: CE 5.0 Ram question.
    ... He wasn't guessing at the solution, that was the answer to your question. ... If the memory is ... initialized properly in hardware ... "Bryan" wrote in message ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Error rendering image in VFP3.0b
    ... If I was guessing, I'd guess the new hardware has too much memory for VFP3 ...
    (microsoft.public.fox.programmer.exchange)
  • Re: High memory
    ... memory and then copy it up above 1MB...but if you want to put ... outside the CPU, memory is seen in a completely different light...this ... 1MB with "real mode memory" labelled on it or anything...the actual memory ... the system bus to actual hardware devices...hence, ...
    (alt.lang.asm)
  • Re: Crashes and the Blue Screen of Death!
    ... but the most common cause is hardware failure. ... The most common cause of this is hardware memory corruption. ... are listed on the Windows 2000 Hardware Compatibility List. ... recommended that all users install them as they become available. ...
    (microsoft.public.win2000.general)
  • Re: The variable bit cpu
    ... > However looking at the big picture the effort to scale fixed bit hardware ... those bits are kept in the opcode rather than in each memory ... And while a *few* applications might need to scale beyond 256 bits, ... And one *big* thing you're missing here is that have a variable-bit ...
    (alt.lang.asm)