MIME-Version: 1.0
In-Reply-To: <1343201120.87444.YahooMailNeo@web162104.mail.bf1.yahoo.com>
References: <1343201120.87444.YahooMailNeo@web162104.mail.bf1.yahoo.com>
Date: Thu, 26 Jul 2012 08:24:56 -0600
Message-ID: <CAFWoy7GA+XatS93YiKcy0wgb-o_MoL=SQpwpfrqdd1PHHd3NUQ@mail.gmail.com>
Subject: Re: VB script error in Cygwin
From: Keith Christian <keith1christian@gmail.com>
To: Eric Padriquez <eric_padriquez@yahoo.com>, cygwin@cygwin.com
Content-Type: text/plain; charset=ISO-8859-1
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

I usually write a CMD.EXE script that in turn, runs cscript and its *.vbs file.

Example:

The following lines are a cmd "batch" file called bar.cmd


	@echo on
	echo.This is "bar.cmd," a CMD.EXE script, which will be invoked by Cygwin
	echo.Run a vbscript called "foo.vbs"
	cscript foo.vbs
	echo."foo.vbs" is complete
	echo.Done, now exiting "bar.cmd"
	exit


** First ** ---- run bar.cmd within a CMD.EXE window to be sure it and
foo.vbs are working properly outside of Cygwin.

** Second** ---- from within Cygwin's bash (or other) shell, run bar.cmd:

$ cmd /c bar.cmd

Watch for output or results from "foo.vbs" during the run.

========== Keith

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple