Richard,

I certainly would consider a "virtual desktop" as a prime candidate for cause. Also *ANY* other "non-standard" stuff which amy be "great for debugging" but also 'great little buggers'!

Frankly I'm surprised you ranted as you did without having gotten down to a "BASIC" system first. Easier to blame others than oneself, I guess.

From now on, take chill-pills only AFTER confirming that a "vanilla" system still shows problems.

Jim N

>Jim Booth wrote:
>>Richard,
>>
>>The single most common cause of Illegal opreation errors is a conflict with the video driver software being used on the machine. Illegal operation is comming from the OS and not VFP, it indicates that VFP has tried to reference a memory location that some other software has locked. Video drivers are famous for not respecting the memory space of other applications that are running. They do this to speed upo performance of the video by bypassing the the OS's memory allocation routines and grabbing their own memory.
>>
>>Try using the Standard SuperVGS driver that shps with windows and see if it has any affect on you illegal operation errors.
>>
> Thanks for the reply, Jim. At last I at least have *something* to go on. I am using a Matrox Mystique, runnning a virtual desktop larger than the physical size of the monitor (great for de-bugging...) Others are using Matrox Millennium, #9, and S3 cards. I will try a "plain vanilla" driver and hope for the best. Thanks again for the tip...
>
>-RW-