RE: dos foxpro 2.6 app freezes on Windows 2003 server

From: Vera Noest [MVP] (Vera.Noest_at_remove-this.hem.utfors.se)
Date: 11/10/04


Date: Wed, 10 Nov 2004 05:51:06 -0800

This is not a problem with NTVDM in Windows 2003, it's a problem
with FoxPro 2.6

This version is simply too old to be able to run on newer hardware
/ OS.

 --
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*

"=?Utf-8?B?Q2hyaXN0b3BoZXIgRA==?="
<ChristopherD@discussions.microsoft.com> wrote on 09 nov 2004:

> So no one has a slightest clue about this one? I've seen other
> postings(2 or 3) regarding the same problem so this must be
> something that is wrong in Windows 2003 NTVDM. It would help
> alot if someone knew something about NTVDM and possible changes.
> Also if someone knows if the NTVDM.EXE and NTVDMD.DLL maybe has
> changed in Service Pack 1. I guess some of you MVPs out there
> maybe have a Beta of Service Pack 1 for W2K3, if so an
> indication on versionnumber change would be much appreciated.
>
> I guess also there are some MS people watching these threads,
> doesn't anyone have anything to suggest?
>
> Thanks in advance
> Christopher
>
> "Christopher D" wrote:
>
>> Hi!
>>
>> We have an old DOS Foxpro 2.6 app which freezes on our new Dell
>> PowerEdge 1850 Windows 2003 Terminal Services server.
>>
>> It has worked flawlessly under our old NT4 TSE server for many
>> years. But now we have to move over to this new server.
>>
>> Right now I've only moved over 3 users to be able to test this
>> new server setup. And with these three users active we get
>> about two crashes or freezes a day in total. So it's not
>> frequent. But I'm worried that if I add all 25 users this will
>> escalate. Also the users will not accept one or two hangups
>> per day...
>>
>> I have tried the following and no luck so far:
>>
>> - Removed antivirus software from server
>> - Tried all compatibility modes
>> - upgraded to all latest drivers and BIOS versions
>> - changed registry key to defaultseparatevdm=Yes just to be
>> sure - tried TAMEDos
>> - disabled HyperThreading on server
>> - checked and doublechecked autoexec.nt and config.nt
>> - removed MS04-32 which was said to update NTVDM.dll just to
>> find out that on 2003 it did not :-( but it was worth a try :-)
>> - installed the following patches since I thought that they
>> somehow could help:
>> - installerat följande patchar:
>> Terminal Server stops responding when idle sessions are being
>> ended http://support.microsoft.com/?kbid=828662
>>
>> Terminal Services stops responding on your Windows Server 2003
>> server http://support.microsoft.com/?kbid=832971
>>
>> Windows Server 2003 Terminal Server Stops Responding
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;821467
>>
>> So far nothing has helped, the DOS app freezes at random
>> points. No special events can be connected to the freezing. The
>> users are doing different things and the app can hang anywhere
>> at anytime - no pattern whatsoever. Also nothing in Event Log.
>>
>> We don't have any problems with performance. CPU time is ok and
>> also memory allocation is under control. The app uses 12Mb of
>> RAM and CPU is when working with the app around 5-10%. When not
>> working with it it goes down to 0% as it should. So that's not
>> a problem.
>>
>> Has anybody else seen any similar behaviour in DOS apps under
>> NTVDM?
>>
>> Any input whatsoever is highly appreciated, because I'm really
>> stuck here.
>>
>> Regards
>> Christopher



Relevant Pages

  • RE: Beginners Questions
    ... We do use Windows form on the presentation layer which is on ... terminal server and call web services on the business logic side. ... of using "proxy" authentication on SQL Server. ... > I have written an app with a Windows Forms UI that is deployed to clients ...
    (microsoft.public.dotnet.distributed_apps)
  • Re: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
    ... app works perfectly on Windows 2000 server, but after moving same app to ... I am running my app on HP DL380 server, on a HP ProCurve switched network, ...
    (microsoft.public.inetserver.asp.general)
  • Re: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
    ... app works perfectly on Windows 2000 server, but after moving same app to ... I am running my app on HP DL380 server, on a HP ProCurve switched network, ...
    (microsoft.public.sqlserver.programming)
  • Re: Permissions - giving "everyone" full permissions is bad ?
    ... >Now I want to deploy this app to a windows 2003 web edition server, so my customers can test the app. ... >So I go into the properties for the dir where this TXT file is, and adds ASPNET user and gives it "modify" permissions - no luck! ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: NTVDM Error Message
    ... Then try uninstall and reinstall your Sound card and also look for Firmware ... Troubleshooting NTVDM and WOW Startup Errorshttp://support.microsoft.com/kb/q220155/ ... Microsoft Windows NT Server 4.0, Terminal Server Edition, ...
    (microsoft.public.windowsxp.help_and_support)