vbdasc@[EMAIL PROTECTED]
wrote:
> Hi all,
> Has anyone noticed some unusual problems when running Clipper programs
> on Windows Server 2003? I sup****t a program, made by Clipper 5.3b
> +Exospace, and some customers have installed it on Windows Server 2003
> (Terminal Server), and run it using Remote Desktop. However, the
> program runs exceptionally unstably, cra****ng very frequently and
> giving various errors, including an "Out of memory" error which I've
> never seen before. The same program runs without serious problems on a
> wide variety of machines/operating systems, including DOS,Linux/
> DOSEMU,Windows 95/98/ME/NT4/2000/XP. I have read that Windows Server
> 2003 cripples the NT Virtual Dos Machine, giving it less memory than
> in previous versions of Windows, but don't know if this can be related
> to the problem. Does anyone have any experience in this subject or
> thoughts to share?
>
> TIA,
> Vassil Daskalov
A few things :-
1) On the server amend the properties of C:\WINDOWS\_DEFAULT.PIF to
adjust DOS settings, especially those relating to memory.
2) Try Blinker 7 instead of ExoSpace if you have it. (The Blinker that
comes with Clipper is crippled to Real mode if I remember correctly)
3) Corrupt databases or indexes can give strange messages.
4) Make sure Clipper is patched with the Time slicing patch. (sorry
can't remember the link)
5) Ensure Op****tunistic locking is disabled :
http://www.witzend.co.uk/html/nt_networking.html
6) If all else fails, move the application to the xHarbour compiler.
Regards
"aardvark"
|
