Problem with lockfiles, and file ownership(?)

[Mike Schwartz]

> However, I would certainly like to discover why it fails on my system,
because
> I won't feel comfortable putting it in production for my clients unless I
know
> it is not going to crash at some point in the future.  I turned off my
Western
> Digital real time backups, but that made no difference either.  Still
searching
> for ideas.
> 
> Del

     I've run into filePro read/write errors on a few Windows workstations
and solved them by these three methods:

    The first one was related to the graphics card in the computer.   (This
sounds very strange, like the problem "couldn't possibly be related to the
price of tea in China", but changing the graphics card fixed the filePro
write problems.)

     Oddly enough, I've usually found a graphics card issue in workstations
that high-powered gaming/engineering graphics cards.  I swapped out the
graphics cards and the filePro writes worked OK.  Of course, the engineers
weren't happy that their cad programs wouldn't run very well on a standard
graphics cards, so we ended up installing cheap laptops next to their cad
workstations, so that they could do the filePro work on the laptop.

     The second strange filePro write situation had to do with low-powered
(under-powered) computers.  I worked with some IBM Intellistations that had
only a 95 watt power supply in them.  (Yes, ninety-five watts...)  I solved
the filePro write problem by installing SSD hard drives to replace the
mechanical SATA drives.  I also removed the modem card, since none of these
PC's needed a modem.  

     The third filePro write issue I had related to a crushed network cable.
This only occurred once.  The network connection seemed OK as far as copying
large files from the computer to the server, returned pings and other tests.
But when I traced the network cable back, I saw that it was crushed (bent at
a sharp 90 degree angle) where somebody pushed a desk tight against the
wall.     
     
Hope that helps!

Mike Schwartz