<span style="color:#323232;">Note: We do need to explicitly close FCBs. Reasons are as follows: If we
</span><span style="color:#323232;">; are running in the no-sharing no-network environment, we are simulating the
</span><span style="color:#323232;">; 2.0 world and thus if the user doesn't close the file, that is his problem
</span><span style="color:#323232;">; BUT... the cache remains in a state with garbage that may be reused by the
</span><span style="color:#323232;">; next process. We scan the set and blast the ref counts of the FCBs we own.
</span><span style="color:#323232;">;
</span><span style="color:#323232;">; If sharing is loaded, then the following call to close process will
</span><span style="color:#323232;">; correctly close all FCBs. We will then need to walk the list AFTER here.
</span><span style="color:#323232;">;
</span><span style="color:#323232;">; Finally, the following call to NET_Abort will cause an EOP to be sent to all
</span><span style="color:#323232;">; known network resources. These resources are then responsible for cleaning
</span><span style="color:#323232;">; up after this process.
</span><span style="color:#323232;">;
</span><span style="color:#323232;">; Sleazy, eh?~
</span>