Showing posts with label ITE. Show all posts
Showing posts with label ITE. Show all posts

Wednesday, February 8, 2017

How To Install X11VNC on Red Hat Linux (ITE)

1. download installer here
Click me to download X11vnc installer
download the file > x11vnc-0.9.13.tar.gz

2. unzip the file and cd to source directory
(un-tar the x11vnc+libvncserver tarball)
# gzip -dc x11vnc-0.9.13.tar.gz | tar -xvf -
# cd x11vnc-0.9.13

3. compile the source code
(run configure and then run make)
# ./configure
# make
> you may notice some warnings about missing libraries. ignore it for now unless it says critical error

4. run x11vnc server
# cd x11vnc
# ./x11vnc

5. if you need the IP of the linux machine
#ifconfig


Wednesday, July 6, 2016

How to Install and Test CURI

  • Download CURI package from Expedite (Software Support)
    • Make sure to choose the right version 
      • enVision 
        • isg_enVision_curi-<version.<arch>.rpm
        • e.g. isg_enVision_curi-1.12-1.117.cnt4.6.i386.rpm 
      • Unison
        • isg_unison_curi-<version>.<arch>.rpm
        • e.g. isg_unison_curi-1.12-2.117.cnt4.6.i386.rpm
    • Note: The above filename convention is supposed to be for versions older than 112. However, newer versions such as the example above (version 117) are still observed to be following the old naming convention. refer to curi deployment presentation for this issue
  • Install CURI package
    • login as root
    • >rpm -ivh <curi>.rpm
    • make sure not to use -uvh as option
  • Check for install locations
    • Windows: c:\opt\ateTools\curi\CURI_<release>
    • Linux: /opt/ateTools/curi/CURI_<version>
      • e.g. installing isg_enVision_curi-1.12-1.117.cnt4.6.i386.rpm
        • Install location: /opt/ateTools/curi/CURI_CURI_1.12_1.117
      • e.g. installing isg_unison_curi-1.12-2.117.cnt4.6.i386.rpm
        • Install location: /opt/ateTools/curi/CURI_CURI_1.12_2.117
    • Symbolic links: /opt/ateTools/curi/
      • Legacy - ITE and enVision
        • CURI=> <curi directory>
      • Unison
        • unison => <curi directory>
    • CURI config file locations
      • Unison: /opt/ateTools/curi/unison/config/curi_conf.xml
      • enVision: /opt/ateTools/curi/CURI/config/curi_conf.xml
  • Optional: Change write permissions of curi_conf.xml
    • curi_conf.xml can be found here:
      • Unison: /opt/ateTools/curi/unison/config/curi_conf.xml
      • enVision: /opt/ateTools/curi/CURI/config/curi_conf.xml
  • Verify if CURI is installed correctly
    • Linux
      • /opt/ateTools/curi/CURI_<release>/bin/test_curi 
      • /opt/ateTools/curi/CURI_<release>/bin/test_curi -noTestLoop
        • option to not enter into loop mode
      • Ignore the "FAILED: onEquipment not supported..." in the output log
    • Windows
      • C;\opt\ateTools\curi\CURI_<release>bin/test_curi.exe
    • Above commands will list all equipment this CURI release knows. if no list comes out, something is wrong


How to uninstall CURI from CentOS
  • login as root
  • to find the installed curi package, execute this command
    • >rpm -qa | grep curi 
  • rpm -e <curi>

Install locations:
  • Windows: c:\opt\ateTools\curi\CURI_<release>
  • Linux: /opt/ateTools/curi
    • Pre v112
      • /opt/ateTools/curi/CURI_<release>
    • v112 and higher
      • /opt/ateTools/curi/diamond-curi-<release>
      • /opt/ateTools/curi/enVision-curi-<release>
      • /opt/ateTools/curi/unison-curi-<release>
      • note that the diamond is for ITE
  • Symbolic links
    • Legacy - ITE and enVision
      • CURI=> <curi directory>
    • Unison
      • unison => <curi directory>
  • CURI config file locations
    • Unison
      • /opt/ateTools/curi/unison/config/curi_conf.xml
    • enVision
      • /opt/ateTools/curi/CURI/config/curi_conf.xml

How to verify if CURI is installed correctly
  • Linux
    • /opt/ateTools/curi/CURI_<release>/bin/test_curi 
    • /opt/ateTools/curi/CURI_<release>/bin/test_curi -noTestLoop
      • option to not enter into loop mode
  • Windows
    • C;\opt\ateTools\curi\CURI_<release>bin/test_curi.exe
  • Above commands will list all equipment this CURI release knows. if no list comes out, something is wrong