Per the posted questions, the additional info below. 1. DOSEMU+FreeDOS and CLIPPER Locking issue Reply: My specific scenario is as follow: 1a. I do not have source code to the software. 1b. From the original DOS batch file supplied by vendor, I can see that it setups the clipper path, so I assume it should be clipper-based. 1c. The clipper-based software is also likely re-compiled with 3rd party tools. I am not 100% sure on this. I attempted this path initially because I wanted to solve the 100% CPU problem and there are several DOS tools out there that can help if you have a standard Clipper-based setup. During the course of doing this I remember 1 or 2 tools that can check the compiled code (low-level) to see whether it has the loop present and change it, but the software I have gave negative result. (according to info, that loop is pretty common on old dos program, the negative result likely means that the local software has some non-standard changes compared to straight clipper compile.) 1d. Eventually I received an advice from list member to use a specialize tool and I did that. However, I need to do additional nice level tuning and CPU affinity control to get to acceptable setup. the above is to explain the clipper-based software background. Now on to locking. 2. For now, I have many users doing READ and upto 3 doing WRITE. 3. Maybe that is why locking problem is minimal. I am still observing since this is 1st week of deployment. Prior to the deployment I have a test where I open 4 instances of the same data entry screen (key in PO)(so likely accessing the same tables and potentials locking issue) However, they seemed to progress without any problems at the time of testing. ST -- To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
