That is governed by your PATH variable. For Bourne shell (/bin/sh), include this line in your .profile before the "export PATH" line: PATH=3D$PATH:. For C shell (/bin/csh), add this line after all your other "set path" lines: set path=3D($path .) I'm not sure about the Korn shell, as I don't use it. You should know that including the local directory by adding . as I show you here is a security risk. A quick Google search should show you the reason for that. Duc --=20 Duc M. Do Carrollton Plant Dow Corning Corp. Carrollton, KY, US -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Weiss, Andreas Sent: Wednesday, August 23, 2006 11:40 AM To: foxboro@xxxxxxxxxxxxx Subject: [foxboro] Unix Shell: path environment variable Hi List, where can I configure that behaviour how the unix shell deals with programs that should be started? examples: # mytool.ksh mytool.ksh: not found # #./mytool.ksh is working # I know that is an option that is configurable but I forgot where. Regards, Andreas =20 _______________________________________________________________________ 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: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave