This is the mail archive of the
mailing list for the Cygwin project.
RE: cscript errors out from daemon
- From: "Dan Vasaru" <dvasaru at broadpark dot no>
- To: <cygwin at cygwin dot com>
- Date: Wed, 25 Sep 2002 18:13:27 +0200
- Subject: RE: cscript errors out from daemon
I don't see the problem on my w2k system :
You are successfully logged in to this server!!!
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
Usage: CScript scriptname.extension [option...] [arguments...]
As to debugging your problem, I suggest:
1) login via telnet/ssh and type:
This is WINNT/system32/cscript on my system.
2) try getting a dump of the crashed CSCRIPT. Run/Install Dr Watson as
default debugger, and instruct it to create a dumpfile:
c:\> drwtsn32 -i
Send me a zipped version of the dump file, or try to debug it yourself
using windbg from the free Microsoft "Debugging Tools for Windows"
From: firstname.lastname@example.org [mailto:email@example.com]On Behalf
Sent: Wednesday, September 25, 2002 5:55 PM
Subject: cscript errors out from daemon
(See attached file: cygcheck.out)
I am trying to run a bash script than in turn calls a vbscript from cron
using cscript.exe. I get a dialog box displaying an error about cscript not
being able to initialize. Application popup: cscript.exe - Application
Error : The application failed to initialize properly (0xc0000005). Click
on OK to terminate the application.
I have also noticed that I cannot run cscript after logging in via telnet
or ssh. I am assuming that cygwin has a problem of running cscript from
within a daemon?
Is there any solution to be able to run cscript from cron, ssh, telnet,
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html