Re: Terminal server client and old dos programs
- From: "Patrick Rouse" <PatrickRouse@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 7 Nov 2005 10:03:04 -0800
When running on the console, will it run in windowed mode, or only full screen?
Does this program reference any client side ini files?
--
Patrick Rouse
Microsoft MVP - Terminal Server
http://www.sessioncomputing.com
"Jo Lambrecht" wrote:
> I wanted to reply already for the session, printing issue i have not tested
> yet.but i'l let you know.
>
> As for the session,
> It works perfect from the server console.
> If i make a TS-session on the server itself as an administrator or as a user
> i get the NTVDM-error.
>
>
> Regrads,
> Jo Lambrecht
>
>
> "Patrick Rouse" <PatrickRouse@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:27C36398-6667-45D6-A1D4-AF474026490F@xxxxxxxxxxxxxxxx
> > 1. No full-screen for DOS applications in Terminal Server. The closest
> > you
> > can get is by simulating full-screen with a window that covers the entire
> > screen. Check out FullScreenDOS.
> >
> > 2. What is your printing requirement, i.e. print to network printer or to
> > locally attached printer? Since DOS doesn't see Windows Printers, you'll
> > have to redirect LPT1 (or whatever port your app requires) to the correct
> > network printer via "NET USE LPT1: \\Server\PrinterShareName", or via WSH
> > equivalent.
> >
> > Printer Scripts here:
> > http://www.sessioncomputing.com/printing.htm
> >
> > If you need to print to the locally attached printer you can either share
> > it
> > and map it via "NET USE LPT1: \\tsclient\PrinterShareName", or script it
> > in
> > alternative methods.
> >
> > Cláudio Rodrigues has posted some Scripts for working with DOS Printers:
> > http://forums.terminal-services.net/index.php?board=12
> >
> > As for the app not functioning:
> > 1. Does it work from the console as an administrator?
> > 2. Does it run from a non-console session as an administrator?
> > 3. If neither 1 or 2 work, then you need to investigate further. If 1
> > works, but not two, then it's a session problem and may be expecting a
> > certain environment that it doesn't detect. If one and two work, but
> > non-admins can't run the app, then it's a permissions or rights issue.
> >
> > Launch filemon (from sysinternals.com), run your app and capture a log
> > file,
> > then look thru the log for errors that might explain the problem you're
> > having.
> >
> > It is possible to run DOS apps on TS, but it often takes some
> > troubleshooting & tweaking to figure out the correct configuration.
> >
> >
> > --
> > Patrick Rouse
> > Microsoft MVP - Terminal Server
> > http://www.sessioncomputing.com
> >
> >
> > "Jo Lambrecht" wrote:
> >
> >> Hi,
> >>
> >> I've tested several things, but still didn't get any further.
> >> Installed Relevos, that didn't make any difference. Installing the
> >> pervasive on another server didn't have any effect also.
> >> After installing TAME-DOS, same problem, only difference with tame-dos,
> >> if
> >> you press "ignore" 4 times at the error window (NTVDM-error), the app
> >> starts
> >> and seems to function properly. Nevertheless there are still 2 problems,
> >> the
> >> dos-app cannot go into "full screen" mode and printing seems also to be a
> >> problem in this envirmont.
> >> Running dos-apps in terminal services doesn't seem to be a peace of cake.
> >> (the problem is that this specific setup, 2 servers and clientcomputers
> >> were
> >> specially setup/bought for this purpose, the app was not tested because
> >> the
> >> app has been tested in a million combinations and on any posible and
> >> different platform, the app has never given a crimp, that was the only
> >> thing
> >> that functioned perfectly in all these different circomstances)
> >>
> >> My hopes have sunc to the bottom of the ocean,
> >> If you have any taughts about this, don't hesitate to give any comment,
> >>
> >> Regards,
> >> Jo Lambrecht
> >>
> >>
> >>
> >>
> >>
> >>
> >> "Patrick Rouse" <PatrickRouse@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> news:BC4194A6-91FC-441F-B298-74E976AB4B26@xxxxxxxxxxxxxxxx
> >> > Also, you should treat the terminal server like a DOS client, not the
> >> > pervasive server. Setup the pervasive service on another server and
> >> > setup
> >> > the terminal server as a client machine, just like you always did
> >> > before
> >> > terminal server.
> >> >
> >> > Other apps that can be used to manage the CPU & RAM used by
> >> > applications
> >> > are:
> >> >
> >> > WM Software Relevos
> >> > Appsense Performance Manager
> >> > Threadmaster (Free)
> >> > RTOSoft TScale
> >> > Aurema ArmTech
> >> > triCerat Simplify Resources (purchased from TMurgent TMUlimit)
> >> > WBI Software CPU Affinity
> >> >
> >> > These can all be found here:
> >> > http://www.sessioncomputing.com/add-on.htm
> >> >
> >> > I tend to prefer applications that manage more than DOS applications,
> >> > and
> >> > when using one of these (I used to use RBase for DOS on Terminal
> >> > Server) I
> >> > used Relevos and it worked great.
> >> >
> >> > Application installation info:
> >> > http://www.sessioncomputing.com/applications.htm
> >> >
> >> > --
> >> > Patrick Rouse
> >> > Microsoft MVP - Terminal Server
> >> > http://www.sessioncomputing.com
> >> >
> >> >
> >> > "Jeff Pitsch" wrote:
> >> >
> >> >> I don't recommend running a dos app in TS. You will need some
> >> >> software
> >> >> like
> >> >> TAME-DOS to control the dos app from taking all the processor. Try
> >> >> this
> >> >> article:
> >> >>
> >> >> Troubleshooting MS-DOS-Based Programs in Windows
> >> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;165214
> >> >>
> >> >> Jeff Pitsch
> >> >> http://www.sbcgatekeeper.com
> >> >> Your Terminal Services Security Website
> >> >>
> >> >> "Jo Lambrecht" <jo@xxxxxxxxxxxxx> wrote in message
> >> >> news:u4W65PV4FHA.2432@xxxxxxxxxxxxxxxxxxxxxxx
> >> >> > Hi,
> >> >> >
> >> >> > We have setup a small network, one SBS2003 premium server SP1 and
> >> >> > one
> >> >> > W2003 SP1 Terminal server as member server.
> >> >> > Setup went fine, using both serves goes fine as well. Clients are
> >> >> > using
> >> >> > outlook, office and several other accounting programs in terminal
> >> >> > server
> >> >> > sessions.
> >> >> > Until...
> >> >> > The company has an old dos-based program and wants to use it. When
> >> >> > a
> >> >> > user
> >> >> > sets up a terminal server session and tries to start the
> >> >> > dos-application,
> >> >> > he gets the following error "NTVDM encountered a hard error", then
> >> >> > he
> >> >> > has
> >> >> > the choice "ignore" or "close", when you choose ignore nothing
> >> >> > happens,
> >> >> > when choosing close the dosbox closes.
> >> >> >
> >> >> > The dos-application is installed on the terminal server and the
> >> >> > database
> >> >> > needed (pervasive sql) is also installed on the terminal server.
> >> >> > Starting the dos-application on the terminal server itself (testing
> >> >> > purposes) works fine.
> >> >> >
> >> >> > Is there a way to run a dos-apps in a terminal server session ? or
> >> >> > is
> >> >> > this
> >> >> > problem related to something els ?
> >> >> >
> >> >> >
> >> >> > Regards,
> >> >> > Jo Lambrecht
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>
.
- Follow-Ups:
- Re: Terminal server client and old dos programs
- From: Jo Lambrecht
- Re: Terminal server client and old dos programs
- References:
- Terminal server client and old dos programs
- From: Jo Lambrecht
- Re: Terminal server client and old dos programs
- From: Patrick Rouse
- Re: Terminal server client and old dos programs
- From: Jo Lambrecht
- Re: Terminal server client and old dos programs
- From: Jo Lambrecht
- Terminal server client and old dos programs
- Prev by Date: Re: Terminal server client and old dos programs
- Next by Date: only one time can connect to Terminal Server...
- Previous by thread: Re: Terminal server client and old dos programs
- Next by thread: Re: Terminal server client and old dos programs
- Index(es):
Relevant Pages
|