Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
NT
apps
dfs
dns
domain
dsmnfpnw
embedded
fsft
mail
misc
oemdsp.preinstall
personalfax
print
protocol.ipx
protocol.misc
protocol.ras
protocol.routing
protocol.tcpip
registry
setup
terminalserv.app.
terminalserv.client
terminalserv.connectivity
terminalserv.domain
terminalserv.misc
terminalserv.prot.rdp
terminalserv.prot.tcpip
terminalserv.setup
terminalserv.user
windowsnt.wntsee
  
 
date: Fri, 9 Jun 2006 07:04:01 -0700,    group: microsoft.public.windowsnt.terminalserver.setup        back       


Idle time   
We have Windows2003, that runs a DOS application. When a session goes idle it 
create locks in this DOS application.  Where or How can i disable the idle 
status?

Also why or How the idle status affect the process for this DOS application?
date: Fri, 9 Jun 2006 07:04:01 -0700   author:   Jeanette

Re: Idle time   
By constantly moving the mouse :-)

Seriously, you can't disable the idle status, it's just an indication 
that no user input has occurred in the session.
You can set a time-out limit on idle sessions, and have them reset or 
disconnect automatically after a specific duration, but I don't think 
that that is what you are asking for.

If I understand you correctly, your DOS application locks up when the 
session is idle. What exactly happens? Can you resume the session by 
moving the mouse? Can you continue to run other applications in the 
session after it has been idle, or does the whole session lock up?
_________________________________________________________
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?SmVhbmV0dGU=?= 
wrote on 09 jun 2006 in
microsoft.public.windowsnt.terminalserver.setup: 

> We have Windows2003, that runs a DOS application. When a session
> goes idle it create locks in this DOS application.  Where or How
> can i disable the idle status?
> 
> Also why or How the idle status affect the process for this DOS
> application?
date: Fri, 09 Jun 2006 13:10:57 -0700   author:   Vera Noest [MVP]

Re: Idle time   
only the DOS application locks up. As soon as we log off the idle session 
that are running this DOS application the locks are gone. We run about 15 to 
20 sessions in our windows2003 server.
There is any low priotiry that apply when a session goes idle?

"Vera Noest [MVP]" wrote:

> By constantly moving the mouse :-)
> 
> Seriously, you can't disable the idle status, it's just an indication 
> that no user input has occurred in the session.
> You can set a time-out limit on idle sessions, and have them reset or 
> disconnect automatically after a specific duration, but I don't think 
> that that is what you are asking for.
> 
> If I understand you correctly, your DOS application locks up when the 
> session is idle. What exactly happens? Can you resume the session by 
> moving the mouse? Can you continue to run other applications in the 
> session after it has been idle, or does the whole session lock up?
> _________________________________________________________
> 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?SmVhbmV0dGU=?= 
> wrote on 09 jun 2006 in
> microsoft.public.windowsnt.terminalserver.setup: 
> 
> > We have Windows2003, that runs a DOS application. When a session
> > goes idle it create locks in this DOS application.  Where or How
> > can i disable the idle status?
> > 
> > Also why or How the idle status affect the process for this DOS
> > application? 
>
date: Mon, 12 Jun 2006 09:30:01 -0700   author:   Jeanette

Re: Idle time   
Do you mean that the whole server locks up, until you have killed 
the idle session with the DOS app in it? I got the impression that 
it is only the DOS app which hangs (i.e. locking its own session).

I don't know what you could do about this with native Windows 
settings, DOS applications are known to behave badly. You could try 
a 3rd party tool like TameDOS, http://www.tamedos.com/.
_________________________________________________________
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?SmVhbmV0dGU=?= 
wrote on 12 jun 2006 in
microsoft.public.windowsnt.terminalserver.setup: 

> only the DOS application locks up. As soon as we log off the
> idle session that are running this DOS application the locks are
> gone. We run about 15 to 20 sessions in our windows2003 server.
> There is any low priotiry that apply when a session goes idle?
> 
> "Vera Noest [MVP]" wrote:
> 
>> By constantly moving the mouse :-)
>> 
>> Seriously, you can't disable the idle status, it's just an
>> indication that no user input has occurred in the session.
>> You can set a time-out limit on idle sessions, and have them
>> reset or disconnect automatically after a specific duration,
>> but I don't think that that is what you are asking for.
>> 
>> If I understand you correctly, your DOS application locks up
>> when the session is idle. What exactly happens? Can you resume
>> the session by moving the mouse? Can you continue to run other
>> applications in the session after it has been idle, or does the
>> whole session lock up? 
>> _________________________________________________________ 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?SmVhbmV0dGU=?= 
>> wrote on 09 jun 2006 in
>> microsoft.public.windowsnt.terminalserver.setup: 
>> 
>> > We have Windows2003, that runs a DOS application. When a
>> > session goes idle it create locks in this DOS application. 
>> > Where or How can i disable the idle status?
>> > 
>> > Also why or How the idle status affect the process for this
>> > DOS application?
date: Mon, 12 Jun 2006 11:32:25 -0700   author:   Vera Noest [MVP]

Re: Idle time   
i see...
i have another question..is the idle sensitivity supported in Windows 2003 
server?
to adjust the CPU time allotted for DOS based program

"Vera Noest [MVP]" wrote:

> Do you mean that the whole server locks up, until you have killed 
> the idle session with the DOS app in it? I got the impression that 
> it is only the DOS app which hangs (i.e. locking its own session).
> 
> I don't know what you could do about this with native Windows 
> settings, DOS applications are known to behave badly. You could try 
> a 3rd party tool like TameDOS, http://www.tamedos.com/.
> _________________________________________________________
> 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?SmVhbmV0dGU=?= 
> wrote on 12 jun 2006 in
> microsoft.public.windowsnt.terminalserver.setup: 
> 
> > only the DOS application locks up. As soon as we log off the
> > idle session that are running this DOS application the locks are
> > gone. We run about 15 to 20 sessions in our windows2003 server.
> > There is any low priotiry that apply when a session goes idle?
> > 
> > "Vera Noest [MVP]" wrote:
> > 
> >> By constantly moving the mouse :-)
> >> 
> >> Seriously, you can't disable the idle status, it's just an
> >> indication that no user input has occurred in the session.
> >> You can set a time-out limit on idle sessions, and have them
> >> reset or disconnect automatically after a specific duration,
> >> but I don't think that that is what you are asking for.
> >> 
> >> If I understand you correctly, your DOS application locks up
> >> when the session is idle. What exactly happens? Can you resume
> >> the session by moving the mouse? Can you continue to run other
> >> applications in the session after it has been idle, or does the
> >> whole session lock up? 
> >> _________________________________________________________ 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?SmVhbmV0dGU=?= 
> >> wrote on 09 jun 2006 in
> >> microsoft.public.windowsnt.terminalserver.setup: 
> >> 
> >> > We have Windows2003, that runs a DOS application. When a
> >> > session goes idle it create locks in this DOS application. 
> >> > Where or How can i disable the idle status?
> >> > 
> >> > Also why or How the idle status affect the process for this
> >> > DOS application? 
>
date: Mon, 12 Jun 2006 14:35:02 -0700   author:   Jeanette

Re: Idle time   
I've no idea what you mean with "the idle sensitivity". Could you 
explain a bit more?

There are as I said lots of 3rd party tools which allow you to 
throttle your applications.
Patrick Rouse has a list of them:

http://www.sessioncomputing.com/add-on.htm
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting:  http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?SmVhbmV0dGU=?= 
wrote on 12 jun 2006: 

> i see...
> i have another question..is the idle sensitivity supported in
> Windows 2003 server?
> to adjust the CPU time allotted for DOS based program
> 
> "Vera Noest [MVP]" wrote:
> 
>> Do you mean that the whole server locks up, until you have
>> killed the idle session with the DOS app in it? I got the
>> impression that it is only the DOS app which hangs (i.e.
>> locking its own session). 
>> 
>> I don't know what you could do about this with native Windows 
>> settings, DOS applications are known to behave badly. You could
>> try a 3rd party tool like TameDOS, http://www.tamedos.com/.
>> _________________________________________________________
>> 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?SmVhbmV0dGU=?= 
>> wrote on 12 jun 2006 in
>> microsoft.public.windowsnt.terminalserver.setup: 
>> 
>> > only the DOS application locks up. As soon as we log off the
>> > idle session that are running this DOS application the locks
>> > are gone. We run about 15 to 20 sessions in our windows2003
>> > server. There is any low priotiry that apply when a session
>> > goes idle? 
>> > 
>> > "Vera Noest [MVP]" wrote:
>> > 
>> >> By constantly moving the mouse :-)
>> >> 
>> >> Seriously, you can't disable the idle status, it's just an
>> >> indication that no user input has occurred in the session.
>> >> You can set a time-out limit on idle sessions, and have them
>> >> reset or disconnect automatically after a specific duration,
>> >> but I don't think that that is what you are asking for.
>> >> 
>> >> If I understand you correctly, your DOS application locks up
>> >> when the session is idle. What exactly happens? Can you
>> >> resume the session by moving the mouse? Can you continue to
>> >> run other applications in the session after it has been
>> >> idle, or does the whole session lock up? 
>> >> _________________________________________________________
>> >> 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?SmVhbmV0dGU=?=
>> >>  wrote on 09 jun 2006 in
>> >> microsoft.public.windowsnt.terminalserver.setup: 
>> >> 
>> >> > We have Windows2003, that runs a DOS application. When a
>> >> > session goes idle it create locks in this DOS application.
>> >> > Where or How can i disable the idle status?
>> >> > 
>> >> > Also why or How the idle status affect the process for
>> >> > this DOS application?
date: Tue, 13 Jun 2006 07:44:09 -0700   author:   Vera Noest [MVP]

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us