Path: utzoo!censor!geac!jtsv16!uunet!cs.utexas.edu!mailrus!purdue!mentor.cc.purdue.edu!pur-ee!gapp
From: gapp@pur-ee.UUCP (GAPP Research)
Newsgroups: comp.sys.ibm.pc
Subject: Searching failure of COMMAND.COM
Message-ID: <12957@pur-ee.UUCP>
Date: 22 Sep 89 16:25:48 GMT
Reply-To: aynang@ed.ecn.purdue.edu (Aynang Yang)
Distribution: usa
Organization: Purdue University Engineering Computer Network
Lines: 42

Cheers,

	 I tested a program that I received recently, and found this
	 searching failure problem when I tried to execute some of its
	 included options. I then was kicked out from the program.

	 The program creates it an independent directory c:\X. All its 
	 modules stays under it. It also creates a subdirectory c:\X\Y 
	 as its working environment. To run the program, a shell (.BAT) 
	 command switches the current directory to that working directory
	 Y. When I run this program via a number of options it supported,
	 it says,

     Specified COMMAND search directry bad
     Specified COMMAND search directry bad
     Specified COMMAND search directry bad
     Specified COMMAND search directry bad
     Specified COMMAND search directry bad

	 Command v. 3.10 (C) Copyright Microsoft Corp 181, 1985

     C>

	 When I checked this with 
	 c>set
	 it shows
	 PATH=
	 COMSPEC=/COMMAND.COM

	 Then I have to do "exit" to let me go back to DOS, lost
	 all the efforts I have done with the program.

	 Is there anything I did wrong with the system? The COMSPEC is
	 specified in config.sys. What caused this funny problem?

	 Any help is appreciated. Please email to the address below. I am
	 using a lab account to post this.

	 --aynang

	 Internet: aynang@ed.ecn.purdue.edu
	 UUCP: pur-ee!ed!aynang