From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15035 invoked from network); 13 Feb 1999 07:27:45 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 13 Feb 1999 07:27:45 -0000 Received: (qmail 29056 invoked by alias); 13 Feb 1999 07:25:29 -0000 Mailing-List: contact zsh-users-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 2146 Received: (qmail 29049 invoked from network); 13 Feb 1999 07:25:24 -0000 From: "Bart Schaefer" Message-Id: <990212232455.ZM14241@candle.brasslantern.com> Date: Fri, 12 Feb 1999 23:24:55 -0800 In-Reply-To: <3AABFE76426DD211AC3000805FFE11768A7131@hq-msg04.nwest.mccaw.com> Comments: In reply to "Trinh, Timothy" "RE: Problem running zsh on WinNT 4.0" (Feb 12, 4:49pm) References: <3AABFE76426DD211AC3000805FFE11768A7131@hq-msg04.nwest.mccaw.com> X-Mailer: Z-Mail (4.0b.820 20aug96) To: "Trinh, Timothy" , "'zsh-users@math.gatech.edu '" Subject: Re: Problem running zsh on WinNT 4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Feb 12, 4:49pm, Trinh, Timothy wrote: } Subject: RE: Problem running zsh on WinNT 4.0 } } Hello ALL, } } I am not able to run shell script } like I do on Unix. When I do an ls -l on the shell script, } do not see any x permissions on the shell script. There's not really any such thing as "x permission" in NT. Anything with the right file extension (.exe, .bat, ...) has "execute permission." I don't recall exactly how zsh's internal tests for executable-ness are resolved in Amol's port. } Is there a particular way of executing the shell script via the zsh } program on WinNT4.0? I don't believe so. } Do I need to name the shell script in a } certain way in order for it to execute? Zsh first attempts to let the system run the named file, and then when (if) that fails it looks at it for a #! line. So ... If you give the script a .exe extension, NT will try to run it as a binary, I think. Not good. If you give it a .bat extension, it'll try to run it as a batch file. That's probably even worse, as bits of the script might actually look sensible enough to the batch processor to cause something to happen. } I have tried including the } following line at the beginning of the shell script: } } #!c:/bin/zsh/zhs.exe ^^ Did you spell "zsh.exe" correctly in the shell script? Otherwise I'm without clue. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com