>>>I generally ***always*** remove oportunistic locking in problematic networks and/or workstations. With Novell this is quite easy ( just a line in the autoexec.ncf ) but with Windows it's quite a pain...
>>
>>I'm using Windows XP. Also is it relevant for local computer too? Because I'm running my tests locally on my C drive. Do you change only the first registry item or all of them listed in the article?
>
>Yes, it can cause problems even as a workstation for local data. I just set OpLocksDisabled to 1 and EnableOpLocs to 0
>
>Jaime

Hi Jaime,

I don't have the entries mentioned in the article in the KEY specified. I don't think I have enough guts to add them on my own, so I will probably leave my registry settings intact. I made the other change suggested by Jason, but didn't run more tests yet.

I'm quite tired of these tests anyway, because it looks like we're not going to port my changes to production anytime soon, so the it's a mute point now... While looking into ProcessNewTrans I identified couple of problems and possible slow downs. One of them I discussed in another thread - we have the same BuildDetailInfo function in two places.

Some other functions can be optimized...