>>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.
>

It's a Win32 call, so I'd bet you're right.

>>Ever think about working as a tech editor? < g >
>
>Actually, I have dreams about that. Of course, I wake up in cold sweat.

As long as you wake up eventually, you're still OK...