Record locking

[Mike Schwartz-PC Support & Services]

> As I insinuated earlier, there were three potential users working
> simultaneously and all of them could have had the same number since the
> network/windows was holding the changes in cache rather than immediately
> writing back to the files on the station that was acting as server as
> soon as one station had asked for a new number.  There was enough lag
> --
> William Akers

	John is still not used to thinking in terms of "Windows", although
PFSYNC and the other things we have discussed do help the Windows caching
problems (but don't necessarily cure them).  I don't recall seeing these
problems occur on any of the Unix systems I've worked with.

	I don't necessarily think it's all Windows fault, because there will
inevitably be timing issues as we try to run old code on faster machines.
Just try and pull out an old copy of Xenix and run it on a brand new
computer.  Xenix did a lot of things via timing loops, and it would probably
fail miserably on new hardware.

Mike Schwartz