|
I'm trying to figure out how to give a few users zero screens. -rf > -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l- > bounces@xxxxxxxxxxxx] On Behalf Of Booth Martin > Sent: Friday, July 23, 2004 2:50 PM > To: Midrange Systems Technical Discussion > Subject: RE: How to open a client access session from another session > > Thats just the opposite of what I want. I want one user to have 2 > screens. > :( Thanks > > > > --------------------------------- > > Booth Martin > > http://www.martinvt.com > > --------------------------------- > > -------Original Message------- > > > > From: Midrange Systems Technical Discussion > > Date: 07/23/04 13:06:44 > > To: 'Midrange Systems Technical Discussion' > > Subject: RE: How to open a client access session from another session > > > > I have a utility which allows two people to share a session. Input is > > accepted from either user and they both see the resulting display. I use > it > > for training. > > > > Albert York > > > > > > -----Original Message----- > > From: midrange-l-bounces@xxxxxxxxxxxx > > [SMTP:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Booth Martin > > Sent: Friday, July 23, 2004 10:27 AM > > To: Midrange Systems Technical Discussion > > Subject: How to open a client access session from another > > session > > > > how to open a client access session from another session... > > > > Tom Liotta showed me a neat way to display data from a green screen > > program > > onto a second session. > > > > Next small step is to open the second session, and find the device > > name for > > that new session. STRPCCMD works if I set up a specially defined > > ..ws file > > on the PC but I wonder if there's a more embracing way. Any > > suggestions? > > > > --------------------------------- > > Booth Martin > > http://www.martinvt.com > > --------------------------------- > > -- > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) > > mailing list > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > > or email: MIDRANGE-L-request@xxxxxxxxxxxx > > Before posting, please take a moment to review the archives > > at http://archive.midrange.com/midrange-l. > > -- > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > > or email: MIDRANGE-L-request@xxxxxxxxxxxx > > Before posting, please take a moment to review the archives > > at http://archive.midrange.com/midrange-l. > > > > > -- > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.