Re: [foxboro] remote DM's on multi-headed machine

 
Brian, 

  

I have set up Exceed sessions with specific targets assigned to the DM's. 

We did not bother about the screen variables though. 

  

I do not have the WP in front of me , but If I remember right , the dmcfg 

File looked something like this : 

  

For a Dual Head WP0001 with 4 DM licenses, opening DM Named WP0001 on 

bottom screen,DM Named WP0002 on top screen, DM Named WP0003 on Remote PC1, 

&DM Named WP0004 on Remote PC2 

  

REMPC1 &REMPC2 are alias names defined in my /etc/hosts file 

  

# NAME  <lbug>  <dmname> <dedicated mon>  <type> 

  

    NAME  WP0001  WP0001        .0         Engineer 

    NAME  WP0001  WP0002        .1         View_Only 

    NAME  WP0001  WP0003        REMPC1     View_Only 

    NAME  WP0001  WP0004        REMPC2     View_Only 

  

Regards 

GOPS 

Aramco Mobil Refinery 

  

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Brian Bates
Sent: Thursday, April 29, 2004 4:28 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] remote DM's on multi-headed machine 

  

  

  

  

  

  

GOPS 

  

I am setting up a W2000 machine running "terminal services", and exceed 9.0 

for terminal services. 

This will enable us to remotely start a virtual PC on your PC (similar to 

VNC). 

Like VNC, for every terminal that is started up the display number is 

incremented. :0, :1, :2, etc. 

  

This works fine with DM's that are unassigned in dmcfg, I can get a DM on 

:0, :1.:2 etc. 

When I assign the machine name of the "terminal server", it can get a DM 

only on :0. 

  

The comments at the top of the dmcfg file show to use  the following: 

      .0                for the primary (local) head 

      .1                for second (local) head 

      .-                for either local head 

      xxx               Xserver name of remote terminal 

      $screen_variable  user-defined SCREEN variable 

      -                 any monitor (undedicated DM) 

  

With $screen_variable configured with the SCREEN section properly 

configured, only the primary head :0 works. 

With "-" configured, *ALL* of the terminal sessions can call up DM's. 

...I need to be able to call up specific DM's on this machine. 

  

I tried to combine "screen_variable" and ".-" and used "screen_variable.-", 

but with this config. the DM would not work on any machine. 

  

      -Brian 

  

  

  

  

                                                                               
nbsp

                      gop@xxxxxxxx                                             
/P

                      Sent by:                 To:      
foxboro@xxxxxxxxxxxxx                           

                      foxboro-bounce@fr        cc:                             
nbsp

                      eelists.org              Subject:  Re: [foxboro]
remoteDM's on multi-headed       

                                                machine                        
nbsp

                                                                               
/P

                      04/29/2004 12:40                                         
nbsp

                      AM                                                       
nbsp        

                      Please respond to                                        
nbsp

                      foxboro                                                  
nbsp

                                                                               
/P

                                                                               
nbsp

  

  

  

  

  

  

  

Brian, 

  

What are you using to emulate the X-Windows ? Exceed or VNC ? Or are you 

justsharing X-Windows across WP's ?With VNC, this works in a different way, 

because you can start several server sessions on the same machine and the 

endusers can open  remote desktop instances :0 or :1 etc . 

  

While using Exceed Emulation or other WP's to share DM's, you are actually 

exporting the DM to that machine . You should have additional DM licenses 

configured in the host machine . And the names of every DM has to be 

defined 

in the dmcfg file ( either floating or with a dedicated station alias name 

). 

  

Hope this helps. 

  

GOPS 

  

----- Original Message ----- 

  

From: Brian Bates <batesb@xxxxxxxxxxx> 

  

Date: Wednesday, April 28, 2004 10:19 pm 

  

Subject: [foxboro] remote DM's on multi-headed machine 

  

  

  

>  

>  

>  

>  

>Hi all 

>  

>Does anybody out there know how to configure the dmcfg to allow 

>remote DM's 

>on multiple heads of a remote host? 

>If a DM is unassigned, then I can start remote DM's on :0, :1 :2 

>etc. ... 

>no problem. 

>  

>If I assign the DM to a specific machine, then I can only start a 

>DM on :0, 

>all other "heads" get the message "No Display Manager available 

>for this 

>Screen". 

>  

>Any ideas out there? 

>  

>-Brian Bates 

>Bowater, Thunder Bay. 

>  

>  

>  

>_______________________________________________________________________ 

>  

  

  

  

  

_______________________________________________________________________ 

This mailing list is neither sponsored nor endorsed by Invensys Process 

Systems (formerly The Foxboro Company). Use the info you obtain here at 

your own risks. Read http://www.thecassandraproject.org/disclaimer.html 

  

foxboro mailing list:             http://www.freelists.org/list/foxboro 

to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join 

to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave 

  
 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: