16 bit Legacy App & NTVDM.EXE

[Guest Jim Ransford]

I have a 16 bit app (FormFlow 2.22) that I want users to use with Terminal

Services. When one is connected through Remote Desktop and the app is run,

an error occurs. "NTVDM encountered a hard error."

 

A search of Microsoft for that error turns up Article #937932, 5/30/07 that

indicates a fix is needed for Wow32.dll. I will attempt to get this when MS

support opens on Monday.

 

However, I can run the app successfully on the Windows 2003 Small Business

R2 server. But I get this error, as noted above, when I run the app through

Remote Desktop.

 

My question is: What would cause the difference? If an app runs

successfully on the server itself, shouldn't it run as well using Remote

Desktop?

 

Maybe this is more academic than practical but I would appreciate a response.

 

Thank you!

[Guest Vera Noest [MVP]]

Re: 16 bit Legacy App & NTVDM.EXE

 

The "Applies To" section of KB937932 specifically mentions all

versions of Windows 2003 Server, but not SBS2003. Maybe the problem

simply doesn't occur on SBS2003?

 

You can also request a hot fix from this website:

 

Hotfix Request Web Submission Form

https://support.microsoft.com/common/survey.aspx?scid=sw;en;1399

&showpage=1&WS=hotfix

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

=?Utf-8?B?SmltIFJhbnNmb3Jk?=

<JimRansford@discussions.microsoft.com> wrote on 07 okt 2007 in

microsoft.public.windows.terminal_services:

> I have a 16 bit app (FormFlow 2.22) that I want users to use

> with Terminal Services. When one is connected through Remote

> Desktop and the app is run, an error occurs. "NTVDM encountered

> a hard error."

>

> A search of Microsoft for that error turns up Article #937932,

> 5/30/07 that indicates a fix is needed for Wow32.dll. I will

> attempt to get this when MS support opens on Monday.

>

> However, I can run the app successfully on the Windows 2003

> Small Business R2 server. But I get this error, as noted above,

> when I run the app through Remote Desktop.

>

> My question is: What would cause the difference? If an app runs

> successfully on the server itself, shouldn't it run as well

> using Remote Desktop?

>

> Maybe this is more academic than practical but I would

> appreciate a response.

>

> Thank you!

[Guest Jim Ransford]

Re: 16 bit Legacy App & NTVDM.EXE

 

Vera -

 

Hmm... I'll try that. I'll put Server 2003 on a VM, install my app and see

what happens. Thanks for the suggestion. I'll let you know the result.

 

BTW, I did get the hotfix this morning and it did not solve the problem with

SBS 2003.

 

Jim

 

"Vera Noest [MVP]" wrote:

> The "Applies To" section of KB937932 specifically mentions all

> versions of Windows 2003 Server, but not SBS2003. Maybe the problem

> simply doesn't occur on SBS2003?

>

> You can also request a hot fix from this website:

>

> Hotfix Request Web Submission Form

> https://support.microsoft.com/common/survey.aspx?scid=sw;en;1399

> &showpage=1&WS=hotfix

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting: http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

>

> =?Utf-8?B?SmltIFJhbnNmb3Jk?=

> <JimRansford@discussions.microsoft.com> wrote on 07 okt 2007 in

> microsoft.public.windows.terminal_services:

>

> > I have a 16 bit app (FormFlow 2.22) that I want users to use

> > with Terminal Services. When one is connected through Remote

> > Desktop and the app is run, an error occurs. "NTVDM encountered

> > a hard error."

> >

> > A search of Microsoft for that error turns up Article #937932,

> > 5/30/07 that indicates a fix is needed for Wow32.dll. I will

> > attempt to get this when MS support opens on Monday.

> >

> > However, I can run the app successfully on the Windows 2003

> > Small Business R2 server. But I get this error, as noted above,

> > when I run the app through Remote Desktop.

> >

> > My question is: What would cause the difference? If an app runs

> > successfully on the server itself, shouldn't it run as well

> > using Remote Desktop?

> >

> > Maybe this is more academic than practical but I would

> > appreciate a response.

> >

> > Thank you!

>