Contact an Expert

What are the known conflicts between MKS NutCracker and Interix and the recommended workaround solutions?

There are three known key issues which you need to look out for:

a) BT-Basic application unable to be launched if Utilities and SDK were installed after the Agilent Medalist ICT software.
Workaround: Reinstall Utilities and SDK for UNIX in the correct sequence as described earlier (Please refer to section 3) (Please refer to the FAQ ‘How can I turn on the Services for NFS and SUA on Windows® 7 ICT controller?’

b) BT-Basic windows display multiple warning when running "Testhead is 1". This is due to the SUA environment variable “XKEYSYMDB”, which might corrupt the MKS “XENVIRONMENT” variable.
Workaround: Modify user profiles and application launch scripts as follows:

  • Edit standard user’s (engineer, calibrate, tcm, operator, user or any other users) profile.ksh found in

                   C:\Agilent_ICT\home\[username]
                   C:\Documents and Settings\[username]
                        Add the command to unset the offending variable:
                   unset XKEYSYMDB

  • Repeat the unset command in the Korn Shell scripts that starts the X applications in C:\Agilent_ICT\bin:

                   Access Consultant: ac_window.ksh
                   Board Consultant: bdeii_window.ksh
                   Fixture consultant: fc_window.ksh
                   BT-Basic: basic_startup.ksh
                       After the else # Windows_NT System
                   unset XKEYSYMDB
c) When launching Interix C-Shell or vi editor, the shell displays ‘No entry’ for terminal type “nutc”. This may be due to Inerix csh needing the env variable TERM=interix & MKS NurCracker set TERM=nutc

Workaround: Modify user profiles and application launch scripts

  • Edit standard user’s (engineer, calibrate, tcm, operator, user or any other usesr) profile.ksh found in

                  C:\Agilent_ICT\home\[username]
                  C:\Documents and Settings\[username]
                      Modify/Add following variable:
                  #export TERM=interix

 

Related FAQs:

1. How can I access my i3070/3070 ICT board directories residing on Linux/UNIX controller, if I am running my ICT controller on Windows® 7?

2. How can I turn on the Services for NFS on Windows® 7 ICT controller?

3. How can I turn on the SUA and its UNIX utility package on Windows® 7 ICT controller?

4. How can I set up File Security and board directories with NFS share?

5. How can I access board directories residing on the Linux/UNIX controller using SAMBA, if my ICT controller is on Windows® 7?


*Microsoft and Windows are trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries.