>>And quickly, too! Even if SetErrorMode() is properly set to 1 so that the Critical Error is passed through to VFP to handle rather than firing up NT's A/R/I messagebox, it takes significant time to either read the drive by bringing it up to speed and reading the free space, or to time out because there's no disk present. Nice catch here, George - faster, cleaner, and OS insensitive!
>
>Thank you, Ed, and thanks for keeping me straight on the DISKSPACE() thing in the past. Do I need to say that the SetErrorMode() thing also was around (and could be used in this way) in Win16? Didn't think so.
>
>>Ever think about working as a tech editor? < g >
>
>Actually, I have dreams about that. Of course, I wake up in cold sweat.

Is there any other way to wake up? I figure if I ever do wake up with out the sweats, then I must be dead! Has nothing to do with being a tech editor, but do to the recent thread I now have something else to fear. John a lawyer, and Ed as a sysop. :)

Jeff