Re: dos foxpro 2.6 app freezes on Windows 2003 server

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Christopher D (chris_d_at_newsgroups.nospam)
Date: 12/01/04 

Date: Wed, 1 Dec 2004 04:11:02 -0800

Hi Sean!

Nice to hear from you. We have not found a solution so far, even though
numerous things have been tried.

What I'm about to do though, as a final resort, is to install SP1 Beta. I
will install this probably today so hopefully in a couple of days we'll know
if this solves the problem or not.

Do you know if your technicians or you have already tried applying the SP1
Beta?

I'll let you know if we find anything.

Regards
Christopher

"Sean Wilson" wrote:

> Christopher
>
> In some ways I am glad you are having this problem. We have an old
> FoxPro for DOS 2.5 system which we have had to migrate from a Windows
> 95/Novell network. Because the new network is not allowed DOS
> applications, it was decided to implement the system via Citrix. This
> was to be a Windows 2003 server. Needless to say, the system
> constantly hangs. In every single case, the CPU load goes up to 49%
> (dual processor), but Task Manager does not show that it is not
> responding.
>
> The people who set up the Citrix server farm have been investigating
> this problem for a couple of months now, and we have even supplied a
> copy of the entire system to Microsoft, and no one has come up with a
> solution. I have installed the application on every operating system
> from Windows 95 to Windows 2003, and the only time it fails is when it
> is running in the Windows 2003 memory space. If the application is
> installed on the 2003 server but run from an Windows XP desktop, it
> works fine. This has been tested and found to be the case. We even
> have three other FoxPro for DOS 2.5 applications already running in
> this sort of environment. Unfortunately, this one particular
> application is running in a different environment.
>
> If there is a solution to this problem, I would love to hear about it.
>
>
> "Christopher D" <ChristopherD@discussions.microsoft.com> wrote in message news:<350452C0-79CC-471B-8804-5045561FD360@microsoft.com>...
> > Interesting. We have two GX280 running our Foxpro 2.6a app just fine. What
> > kind of problem are you experiencing? Freezing of the app or other things?
> >
> > Although these two workstations are in fact running Win2000...
> >
> > BTW, I really like your homepage Vera. I've been visiting it a couple of
> > times to keep myself updated. I also live in Sweden(Stockholm).
> >
> > Nice to chat with you.
> >
> > Regards
> > Christopher
> >
> > "Vera Noest [MVP]" wrote:
> >
> > > Yes, that's perfectly possible, and I hope so too. But we have
> > > been forced to delay upgrading our hardware, because our FoxPro
> > > 2.6 application could not run on the newest Dell GX model.
> > >
> > > --
> > > 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 10 nov 2004:
> > >
> > > > If so why is this app working fully correct on a Windows XP SP2
> > > > client with the latest hardware. I'm fully aware that client
> > > > hardware is different from server hardware. But I don't think
> > > > you're on the right track in your answer Vera.
> > > >
> > > > This morning I found W2K3 SP1 in MSDN Subscriber Downloads. This
> > > > has a newer version of NTVDM.EXE - so I guess there were a few
> > > > bugs in there. Hopefully I can apply this on our server tonight.
> > > > It will be very interesting to see the outcome.
> > > >
> > > > So I hope you're wrong in your statement Vera.
> > > >
> > > > Regards
> > > > Christopher
> > > >
> > > > "Vera Noest [MVP]" wrote:
> > > >
> > > >> 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;82146
> > > >> >> 7
> > > >> >>
> > > >> >> 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: after installing KB011829 OWA is not working anymore
    ... Windows Vista or IE 7.0 no longer includes support for the ActiveX control ... The resolution for this issue is to install hotfix KB 911829. ... and to the back-end server. ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.exchange.connectivity)
  • RE: RRAS Wizard failure
    ... SBS, now, you can jump over the Windows server 2003 sp1 installation." ... we do not recommend customer to install windows server 2003 sp2 ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • RE: Service pack version
    ... I understand that the SBS 2003 BPA suggests ... Now, you had installed Windows Server 2003 sp2 on your SBS, and the SBS ... It is recommended to install the Windows Server 2003 sp2 after install the ...
    (microsoft.public.windows.server.sbs)
  • Re: Fax on Terminal Server from SBS2K3
    ... please make sure the Fax service is installed on the TS server. ... you can try the steps below to install Shared Fax Client: ... 248340 Installing and Using Programs in Windows 2000 Terminal Services ...
    (microsoft.public.windows.server.sbs)
  • RE: Remote Access Wizard Error
    ... please let me know the detail version of your SBS. ... please go through the following document to install SBS 2003 sp1: ... Downloading and Installing Windows Small Business Server 2003 Service Pack 1 ...
    (microsoft.public.windows.server.sbs)