Nando

> it's the first time that I hear this; you may want to download a copy of
> handle/nthandle from sysinternals and look at what process is really
> holding up your files.

It is a rare occurance now, but W2k is STILL not acceptable to my end customers.
We are running 24/7 on NT4/Sp6a with 'all the tweeks' while the soak system for
testing W2k has yet to stay up more than three weeks at a time, and until it can
they will not change.

The fundamental problem may be going to be addressed since I here rummers that
Microsoft are going to put in the proper replacement for NTFS, some time in the
next 5 years. Add 5 years to make it stable and we will be fine <grin>.

I think 90% of my time should be paid for by Microsoft - I've just spent 3 days
putting my development machine back together after a W2k crumble. I could have
done it in a few hours except I have documented everthing and have CD copies of
all that is installed since most of the updates over the last 6 months could
only be done via an internet connection.

.NET may be a good idea - but I pay them UK£400 a year for MSDN and don't get
any support so why should they change when they start charing everbody the same
way! IBM have a lot to answer for by not actually bothering to select a decent
processor and operating system and creating this mess.

--
Lester Caine
-----------------------------
L.S.Caine Electronic Services