According to Drew Northup ([EMAIL PROTECTED]):
> I think you forgot something......: MS-Windows isn't an Operating System in
> the purist sense. Command.com will let you block disk access for a time
> (that is how the old NDD 7.0 and Speedisk (4.0?) used to work under DOS
> without getting "interrupted" by a disk write), but kernel.exe and thus
> kernel32.exe are "simulated multiprocessing" handlers, and thus you cannot
> (currently.., the people at MS are working on this) properly "lock out"
> access to a disk (or anything else for that matter) unless you are talking
> specifically about the "critical time" for each Win32 executable (which are
> all modules of kernel(32?).exe)--which is locked out to prevent massive
> horrid errors in any form of execution that may take place on the machine.
You must be talking about '95.
Wouter
--
* Wouter Coene * [EMAIL PROTECTED] * [EMAIL PROTECTED] *
* C.O.R.E/OMTA/Plex86 * C development/Code maniac *
* "When people run in circles we call them crazy, *
* when planets do we call it orbiting" *
