Re: Terminal server client and old dos programs

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

Hi,

Comparing the "set" on both console and session, there we're a few
differences, adjusting them to equal both "set's" didn't solve the problem.

I did copy a few dll's and files that we're "missing" according to the
filemon-log, but that didn't solve the problem.

After going trough many newsgroups, i noticed that many of the
ts-administrators use thirdparty software to controle apps on a terminal
servers (cpu,mem,io,etc...) So i did some testing, to see if that made a
difference, more specific,
Relevos and Tame-Dos (tame-dos is especialy for controlling dos-apps on
TS-servers (http://www.tamedos.com/)
At first it didn't make any difference, Relevos didn't do anything at all
With Tame-dos my app started if i pressed 3x the ignore-button on the
vdm-error, after setting a few parameters, my app is finaly starting without
errors.

The most important parameter in tame-dos to set was : /forcetextmode on
This is a parameter, and according to their explination it does this : Use
this if the application forces full screen mode, and you would like to keep
it in a window.

So i would like to thank you for the effort and support,all the helpfull
hints and tips you reached me.
I've learned a lot this week,

Regards,
Jo Lambrecht
Assy-Soft




"Patrick Rouse" <PatrickRouse@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A51B5C81-3494-4A31-B4D0-293CD17FBA70@xxxxxxxxxxxxxxxx
> The ones that stick out are the "FILE NOT FOUND" errors referencing
> NTVDM.exe
> and a set of DLL files in the root of the hard drive.
>
> You might want to run "set" from the cmd line in both a console and
> non-console session to compare the different environments.
>
> --
> Patrick Rouse
> Microsoft MVP - Terminal Server
> http://www.sessioncomputing.com
>
>
> "Jo Lambrecht" wrote:
>
>> Hi,
>>
>> 1. playing with the settings for the dos-box size worked ! I can get a
>> maximum size of, lets say 80% of the screen, which is perfect.
>>
>> 2. I shared my local printer and net used it to LPT1: and wonderwell it
>> worked also !!
>>
>> So, you've helped me a lot in this for which i give you my full
>> congratulations (i"m back on the surface of the ocean)
>>
>> So there's one thing left to tackle (if possible i would like to be out
>> of
>> the ocean)
>> the NTVDM-error.
>> As asked i did a check with filemon from sysinternal tools. I can't see
>> somethings in there what makes sense to me (except for the names of the
>> apps) Also i don't know what to look for, so if you would like to
>> pinpoint
>> some problems and what to look for, i would be on my way to further
>> troubleshoot the problem.
>> So in beneath some screen shots of the filemon-log-file :
>> MODEST.EXE is the dos-app, SABRO01 is the user, PVSW is the directory
>> of
>> pervasive (database)
>>
>>
>> 8 15:14:07 explorer.exe:1260 QUERY INFORMATION C:\Documents and
>> Settings\SABRO01\Desktop SUCCESS Attributes: D
>> 9 15:14:07 explorer.exe:1260 QUERY INFORMATION C:\Documents and
>> Settings\SABRO01\Desktop\MODEST.EXE.pif SUCCESS Attributes: A
>> 10 15:14:07 explorer.exe:1260 OPEN C:\Documents and Settings\ SUCCESS
>> Options: Open Directory Access: All
>> 11 15:14:07 explorer.exe:1260 DIRECTORY C:\Documents and Settings\
>> SUCCESS
>> FileBothDirectoryInformation: SABRO01
>> 12 15:14:07 explorer.exe:1260 CLOSE C:\Documents and Settings\ SUCCESS
>> 13 15:14:07 explorer.exe:1260 OPEN C:\Documents and Settings\SABRO01\
>> SUCCESS Options: Open Directory Access: All
>> 14 15:14:07 explorer.exe:1260 DIRECTORY C:\Documents and
>> Settings\SABRO01\
>> SUCCESS FileBothDirectoryInformation: Desktop
>> 15 15:14:07 explorer.exe:1260 CLOSE C:\Documents and Settings\SABRO01\
>> SUCCESS
>> 16 15:14:07 explorer.exe:1260 QUERY INFORMATION C:\Documents and
>> Settings\SABRO01\Desktop\MODEST.EXE.pif SUCCESS Attributes: A
>> 17 15:14:07 explorer.exe:1260 OPEN C:\Documents and Settings\ SUCCESS
>> Options: Open Directory Access: All
>> 18 15:14:07 explorer.exe:1260 DIRECTORY C:\Documents and Settings\
>> SUCCESS
>> FileBothDirectoryInformation: SABRO01
>> 19 15:14:07 explorer.exe:1260 CLOSE C:\Documents and Settings\ SUCCESS
>> 20 15:14:07 explorer.exe:1260 OPEN C:\Documents and Settings\SABRO01\
>> SUCCESS Options: Open Directory Access: All
>> 21 15:14:07 explorer.exe:1260 DIRECTORY C:\Documents and
>> Settings\SABRO01\
>> SUCCESS FileBothDirectoryInformation: Desktop
>> 22 15:14:07 explorer.exe:1260 CLOSE C:\Documents and Settings\SABRO01\
>> SUCCESS
>> 23 15:14:07 explorer.exe:1260 QUERY INFORMATION C:\Documents and
>> Settings\SABRO01\Desktop\MODEST.EXE.pif SUCCESS Attributes: A
>> 24 15:14:07 explorer.exe:1260 QUERY INFORMATION C:\Documents and
>> Settings\SABRO01\Desktop\MODEST.EXE.pif SUCCESS Attributes: A
>> 25 15:14:07 explorer.exe:1260 QUERY INFORMATION C:\Documents and
>> Settings\SABRO01\Desktop\MODEST.EXE.pif:Zone.Identifier NOT FOUND
>> Attributes: Error
>> 26 15:14:07 explorer.exe:1260 QUERY INFORMATION C:\Documents and
>> Settings\SABRO01\Desktop\MODEST.EXE.pif SUCCESS Attributes: A
>> 27 15:14:07 explorer.exe:1260 QUERY INFORMATION C:\Documents and
>> Settings\SABRO01\Desktop\MODEST.EXE.pif SUCCESS Att
>>
>>
>>
>>
>> 60 15:14:07 explorer.exe:1260 DIRECTORY C:\ SUCCESS
>> FileBothDirectoryInformation: Documents and Settings
>> 61 15:14:07 explorer.exe:1260 CLOSE C:\ SUCCESS
>> 62 15:14:07 explorer.exe:1260 CLOSE C:\Documents and
>> Settings\SABRO01\Desktop\MODEST.EXE.pif SUCCESS
>> 63 15:14:07 explorer.exe:1260 QUERY INFORMATION
>> C:\WINDOWS\system32\ntvdm.exe SUCCESS Attributes: A
>> 64 15:14:07 explorer.exe:1260 QUERY INFORMATION
>> C:\WINDOWS\system32\ntvdm.exe SUCCESS Attributes: A
>> 65 15:14:07 explorer.exe:1260 OPEN C:\WINDOWS\system32\ntvdm.exe SUCCESS
>> Options: Open Access: All
>> 66 15:14:07 explorer.exe:1260 OPEN C:\WINDOWS\system32\ntvdm.exe.Manifest
>> NOT FOUND Options: Open Access: All
>> 67 15:14:07 explorer.exe:1260 QUERY INFORMATION C:\Documents and
>> Settings\SABRO01\Desktop SUCCESS Attributes: D
>> 68 15:14:07 explorer.exe:1260 CLOSE C:\WINDOWS\system32\ntvdm.exe SUCCESS
>> 69 15:14:07 ntvdm.exe:3032 OPEN C:\Documents and Settings\SABRO01\Desktop
>> SUCCESS Options: Open Directory Access: Traverse
>> 70 15:14:07 ntvdm.exe:3032 QUERY INFORMATION
>> C:\WINDOWS\system32\ntvdm.exe.Local NOT FOUND Attributes: Error
>> 71 15:14:07 csrss.exe:4052 QUERY INFORMATION C:\Documents and
>> Settings\SABRO01\Desktop\ntvdm.exe NOT FOUND Attributes: Error
>> 72 15:14:07 csrss.exe:4052 QUERY INFORMATION
>> C:\??\C:\WINDOWS\system32\ntvdm.exe NAME INVALID Attributes: Error
>> 73 15:14:07 csrss.exe:4052 QUERY INFORMATION
>> C:\WINDOWS\system32\ntvdm.exe
>> SUCCESS Attributes: A
>> 74 15:14:07 csrss.exe:4052 OPEN C:\WINDOWS\system32\ntvdm.exe SUCCESS
>> Options: Open Access: All
>> 75 15:14:07 csrss.exe:4052 QUERY INFORMATION
>> C:\WINDOWS\system32\ntvdm.exe
>> SUCCESS Attributes: A
>> 76 15:14:07 csrss.exe:4052 SET INFORMATION C:\WINDOWS\system32\ntvdm.exe
>> SUCCESS FileBasicInformation
>> 77 15:14:07 csrss.exe:4052 READ C:\WINDOWS\system32\ntvdm.exe SUCCESS
>> Offset: 0 Length: 12
>> 78 15:14:07 csrss.exe:4052 QUERY INFORMATION
>> C:\WINDOWS\system32\ntvdm.exe
>> SUCCESS Length: 442880
>> 79 15:14:07 csrss.exe:4052 QUERY INFORMATION
>> C:\WINDOWS\system32\ntvdm.exe
>> SUCCESS Length: 442880
>> 80 15:14:07 csrss.exe:4052 CLOSE C:\WINDOWS\system32\ntvdm.exe SUCCESS
>> 81 15:14:07 ntvdm.exe:3032 QUERY INFORMATION
>> C:\WINDOWS\system32\apphelp.dll
>> SUCCESS Attributes: A
>> 82 15:14:07 ntvdm.exe:3032 OPEN C:\WINDOWS\system32\apphelp.dll SUCCESS
>> Options: Open Access: All
>> 83 15:14:07 ntvdm.exe:3032 CLOSE C:\WINDOWS\system32\apphelp.dll SUCCESS
>> 84 15:14:07 explorer.exe:1260 QUERY INFORMATION
>> C:\WINDOWS\system32\ntvdm.exe SUCCESS Attributes: A
>> 85 15:14:07 explorer.exe:1260 QUERY INFORMATION
>> C:\WINDOWS\system32\ntvdm.exe SUCCESS Attributes: A
>> 86 15:14:07 explorer.exe:1260 QUERY INFORMATION
>> C:\WINDOWS\system32\ntvdm.exe SUCCESS Attributes: A
>> 87 15:14:07 explorer.exe:1260 OPEN C:\WINDOWS\system32\ntvdm.exe SUCCESS
>> Options: Open Access: All
>> 88 15:14:07 ntvdm.exe:3032 QUERY INFORMATION
>> C:\WINDOWS\system32\tsappcmp.dll SUCCESS Attributes: A
>> 89 15:14:07 explorer.exe:1260 QUERY INFORMATION
>> C:\WINDOWS\system32\ntvdm.exe SUCCESS Attributes: A
>> 90 15:14:07 explorer.exe:1260 SET INFORMATION
>> C:\WINDOWS\system32\ntvdm.exe
>> SUCCESS FileBasicInformation
>> 91 15:14:07 ntvdm.exe:3032 OPEN C:\WINDOWS\system32\tsappcmp.dll SUCCESS
>> Options: Open Access: All
>> 92 15:14:07 ntvdm.exe:3032 CLOSE C:\WINDOWS\system32\tsappcmp.dll SUCCESS
>> 93 15:14:07 explorer.exe:1260 READ C:\WINDOWS\system32\ntvdm.exe SUCCESS
>> Offset: 0 Length: 12
>> 94 15:14:07 explorer.exe:1260 QUERY INFORMATION
>> C:\WINDOWS\system32\ntvdm.exe SUCCESS Length: 442880
>> 95 15:14:07 explorer.exe:1260 QUERY INFORMATION
>> C:\WINDOWS\system32\ntvdm.exe SUCCESS Length: 442880
>> 96 15:14:07 explorer.exe:1260 CLOSE C:\WINDOWS\system32\ntvdm.exe SUCCESS
>>
>>
>>
>> 209 15:14:07 ntvdm.exe:3032 OPEN C:\PVSW\BIN\BTRDRVR.SYS SUCCESS Options:
>> Open Access: All
>> 210 15:14:07 ntvdm.exe:3032 QUERY INFORMATION C:\PVSW\BIN\BTRDRVR.SYS
>> SUCCESS Length: 392
>> 211 15:14:07 ntvdm.exe:3032 QUERY INFORMATION C:\PVSW\BIN\BTRDRVR.SYS
>> SUCCESS Length: 392
>> 212 15:14:07 ntvdm.exe:3032 CLOSE C:\PVSW\BIN\BTRDRVR.SYS SUCCESS
>> 213 15:14:07 ntvdm.exe:3032 OPEN C:\PVSW\BIN\BTRDRVR.SYS SUCCESS Options:
>> Open Access: All
>> 214 15:14:07 ntvdm.exe:3032 QUERY INFORMATION C:\PVSW\BIN\BTRDRVR.SYS
>> SUCCESS Length: 392
>> 215 15:14:07 ntvdm.exe:3032 READ C:\PVSW\BIN\BTRDRVR.SYS SUCCESS Offset:
>> 0
>> Length: 26
>> 216 15:14:07 ntvdm.exe:3032 QUERY INFORMATION C:\PVSW\BIN\BTRDRVR.SYS
>> SUCCESS Length: 392
>> 217 15:14:07 ntvdm.exe:3032 READ C:\PVSW\BIN\BTRDRVR.SYS SUCCESS Offset:
>> 0
>> Length: 392
>> 218 15:14:07 ntvdm.exe:3032 CLOSE C:\PVSW\BIN\BTRDRVR.SYS SUCCESS
>> 219 15:14:07 ntvdm.exe:3032 QUERY INFORMATION
>> C:\WINDOWS\system32\BTRVDD.DLL
>> NOT FOUND Attributes: Error
>> 220 15:14:07 ntvdm.exe:3032 QUERY INFORMATION
>> C:\WINDOWS\system32\BTRVDD.DLL
>> NOT FOUND Attributes: Error
>> 221 15:14:07 ntvdm.exe:3032 QUERY INFORMATION
>> C:\WINDOWS\system\BTRVDD.DLL
>> NOT FOUND Attributes: Error
>> 222 15:14:07 ntvdm.exe:3032 QUERY INFORMATION C:\WINDOWS\BTRVDD.DLL NOT
>> FOUND Attributes: Error
>> 223 15:14:07 ntvdm.exe:3032 QUERY INFORMATION C:\Documents and
>> Settings\SABRO01\WINDOWS\BTRVDD.DLL NOT FOUND Attributes: Error
>> 224 15:14:07 ntvdm.exe:3032 QUERY INFORMATION C:\BTRVDD.DLL NOT FOUND
>> Attributes: Error
>> 225 15:14:07 ntvdm.exe:3032 QUERY INFORMATION C:\PVSW\bin\BTRVDD.DLL
>> SUCCESS
>> Attributes: A
>> 226 15:14:07 ntvdm.exe:3032 OPEN C:\PVSW\bin\BTRVDD.DLL SUCCESS Options:
>> Open Access: All
>> 227 15:14:07 ntvdm.exe:3032 CLOSE C:\PVSW\bin\BTRVDD.DLL SUCCESS
>> 228 15:14:07 ntvdm.exe:3032 QUERY INFORMATION
>> C:\WINDOWS\system32\w3btrv7.dll NOT FOUND Attributes: Error
>> 229 15:14:07 ntvdm.exe:3032 QUERY INFORMATION
>> C:\WINDOWS\system32\w3btrv7.dll NOT FOUND Attributes: Error
>> 230 15:14:07 ntvdm.exe:3032 QUERY INFORMATION
>> C:\WINDOWS\system\w3btrv7.dll
>> NOT FOUND Attributes: Error
>> 231 15:14:07 ntvdm.exe:3032 QUERY INFORMATION C:\WINDOWS\w3btrv7.dll NOT
>> FOUND Attributes: Error
>> 232 15:14:07 ntvdm.exe:3032 QUERY INFORMATION C:\Documents and
>> Settings\SABRO01\WINDOWS\w3btrv7.dll NOT FOUND Attributes: Error
>> 233 15:14:07 ntvdm.exe:3032 QUERY INFORMATION C:\w3btrv7.dll NOT FOUND
>> Attributes: Error
>> 234 15:14:07 ntvdm.exe:3032 QUERY INFORMATION C:\PVSW\bin\w3btrv7.dll
>> SUCCESS Attributes: A
>> 235 15:14:07 ntvdm.exe:3032 OPEN C:\PVSW\bin\w3btrv7.dll SUCCESS Options:
>> Open Access: All
>> 236 15:14:07 ntvdm.exe:3032 CLOSE C:\PVSW\bin\w3btrv7.dll SUCCESS
>> 237 15:14:07 ntvdm.exe:3032 OPEN C:\WINDOWS\SYSTEM32\COUNTRY.SYS SUCCESS
>> Options: Open Access: All
>> 238 15:14:07 ntvdm.exe:3032 QUERY INFORMATION
>> C:\WINDOWS\SYSTEM32\COUNTRY.SYS SUCCESS Length: 27097
>> 239 15:14:07 ntvdm.exe:3032 READ C:\WINDOWS\SYSTEM32\COUNTRY.SYS SUCCESS
>> Offset: 0 Length: 512
>> 250 15:14:07 ntvdm.exe:3032 READ C:\WINDOWS\SYSTEM32\COUNTRY.SYS SUCCESS
>> Offset: 26857 Length: 20
>> 251 15:14:07 ntvdm.exe:3032 READ C:\WINDOWS\SYSTEM32\COUNTRY.SYS SUCCESS
>> Offset: 26857 Length: 32
>> 252 15:14:07 ntvdm.exe:3032 READ C:\WINDOWS\SYSTEM32\COUNTRY.SYS SUCCESS
>> Offset: 26889 Length: 20
>> 253 15:14:07 ntvdm.exe:3032 READ C:\WINDOWS\SYSTEM32\COUNTRY.SYS SUCCESS
>> Offset: 26889 Length: 10
>>
>>
>> "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


.

Relevant Pages

  • Re: I would be worried if...
    ... an success it will be. ... These aren't real apps? ... music practice, netbook replacement, home automation, whatever). ... drawing between this and Tablet PC's. ...
    (comp.sys.mac.advocacy)
  • Re: What to do when disaster strikes but requires user input
    ... seen it used with a great deal of success where I have seen it used and all ... It is possible the apps I have seen that successfully ... the sudden flush of RETURN TO MASTER that's one thing. ... something the watchdog app was able to deal with. ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Delphi for .Net 3?
    ... Personally BDS2006 is much better than BCB6 and I've ported ... a lot of apps over to it with complete success. ... I'm a C++ developer and I've been burned by OWL, OWL2, VCL and with the ...
    (borland.public.delphi.non-technical)
  • Re: I want to migrate to Linux
    ... apps to work then I will consider it a major success and well worth the ... effort of adopting Linux. ... I guess it would be beneficial if you post the apps that work well ... Windows 100%. ...
    (comp.os.linux.hardware)
  • Re: TEMPORARILY setting qfe2 to be a DHCP server?
    ... I have had success setting up the ESP-16 MI serial hub! ... I have had success regarding every serial device (for the moment, ... skipping terminals) I had on the Cyclades Cyclom YeP PCI card in my Linux ... However, session 2 wasn't responding. ...
    (comp.sys.sun.hardware)