Running MS-DOS distributed aplication

[JanG]

We have a customer that has still use a MS-DOS based application. They have
upgraded all their PC's to Windows XP Pro and thus this MSDOS application
does not run very well. However it runs OK on their terminal server (Win2K),
and they would like to use this app as a distribudet application. (A lot of
their users ca not use terminal server as their primary desktop because of
hardware communication etc).

My problem is that when I use this application in distributed mode, the
trm-session "hangs" after you exits the program. And the you are not able to
log in again and start a new session. I have looked through the MS SSupport
pages/Knowledge base and searched the Google, but I am having trouble where
to look.

Anyone that knows where the problem sits or where I can find more info about
running MSDOS apps as distributed application on Win2K trm server?

Thx in advance!

JanG

 

[Matthew Harris [MVP]]

Can you give some more details about how the session hangs
when you exit the DOS program?

-M

 

[Matthew Harris [MVP]]

Try this: Connect to the terminal server as a normal user
would, run the DOS program, then close it. Then, on a
different session, open up the tsadmin.exe and see what
processes are running in the session with the (now) closed
DOS box. What processes are running?

-M

 

[JanG]

Thx Again

While in the Dos Apps, I see the following:
CSRSS.EXE
WINLOGON.EXE
RDPCLIP.EXE
NALSTART.EXE
NTVDM.EXE

After i closed the DOS APP I can now see:
CSRSS.EXE
WINLOGON.EXE
RDPCLIP.EXE
NALSTART.EXE

As far as I can see, the NTVDM is the DOS APP "handler" NT Virtual Device
Manager or something like that....

Any hints?


JanG

 

[JanG]

Hello Mattew

I have isolated the problem, The user group with the problem had the
NALSTART included in their Login Script. When it was removed, things worked
the way they should.

Thx for pointing me in the correct direction!

JanG