clipper slow on Windows 2000

[mvosa]

I'm moving a clipper application from a Novell O/S server to a Windows 2000 Server O/S. The application runs great on W95 work stations but processes data very slow on W98 & W2K work stations. Moving between screens or scrolling a report on screen are OK, it is just the processing of data that is slow.

Please Help!
Thanks

 

[JockMullin]

Hi, Mvosa

There seem to be two main areas where clipper dos apps have problems in some versions of Windows - memory management and overlays in particular and also in CPU boundedness when awaiting keyboard input.

Thread288-236860 discusses the first area and thread288-191093 the latter.

Have you taken a look at these discussions? If they don't seem to apply to your case pls post back.

Best regards
Jock

 

[azad110]

hi dear.
i have this case too,i study it and undestand that
function rlock() is very slow in win2000.
you can test it.
if you can solve it ,plz inware me(aazad_amir@yahoo.com).

 

[dalloca]

Please take a look on the subject "dos aplication on windows 2000" here in the same forum. There you will find the answer.

Regards

Rob

 

[mvosa]

I've worked with MS to resolve this issue. I've copied their conclusion here.


We have determined that the difference in performance between Windows 95 and Windows 98 / 2000 is the handling of FlushFileBuffers. Windows 95 does not handle these requests properly, so there is no delay while the OS processes data from cache to disk. The behavior in Windows 2000 is the correct behavior for the operating system, while Windows 95 is not properly handling flushing. My guess would be that the designers of the database engine you are using did not take the delay from file flushing into account since the functionality didn’t work properly in earlier operating systems. For more information about FlushFileBuffers please see:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/fileio/base/flushfilebuffers.asp

There is not a simple solution to this behavior, since the OS is performing as expected. You could work on tuning your file cache, but this may not yield much greater performance:

http://www.microsoft.com/technet/tr...indows2000serv/maintain/optimize/wperfch7.asp

Please let me know if you have any further questions. Thank you,



Matthew Justice
Microsoft Support Professional, MCSE