>I'm not sure I buy that reasoning. If it was a VFP problem, it would exhibit that problem regardless of type of disk. It seems from Ed Rauh's testing that SCSI at least (and Fiber Channel and FireWire [don't remember if he tested those]) don't have this problem.
>
>As for the problem "only" manifesting itself in VFP - all versions of the Fox have had a long and colourful history of pointing out weaknesses in hardware, drivers, and OS. To maximize performance, VFP may be using obscure calls that aren't made in other vendors' products. Or, could it be (*gasp*) that VFP uses undocumented calls that other vendors won't even know about?

I wish I had my FP1.02 help file here. Somewhere in the introductory chapters, it explicitly said why it was possible to get memory corruption with FP (mind you, it was the days of LIM/EMS, UMB and XMS on 286es and 386es, 486es being still very few around) because FP played by the book in addressing memory in certain ways, while nobody else was doing it, so if you are experiencing crashes with the following products [long list of caching, RAM disk and other TSR stuff followed, or was just implied by description]...

I wouldn't wonder if the history repeated.