>>
>>I did some testing and sure enough, when my 2.6 batch routine is running APPEND FROM ... TYPE DELI and feeding in a textfile with 100,000+ lines, this Extended Wait State error gets logged. Not always, but 6 out of 15 tests gave error. I recompiled the code in VFP5.0a and the error went away.
>>
>Does it maybe misreport the batch routines activity as "wait state", because during the mass append it doesn't use anything but disk? No interface event ever fires, no clicks, no bells, no whistles. The thunking layer probably doesn't go into much detail on reporting the 16-bit app's activity (it has more important things to do), so you get what you get.
>
>VFP 5.0 surely communicates more directly with the system and doesn't misreport.
>
>Well, I gave it a try. Geek enough?

=D) That's exactly my thinking on this matter Dragan. I know the 16-bit process is not truly stuck in a wait state because I see the harddisk light going to town.