From: jp AT nuancecom DOT com (JP Shipherd)
Subject: NT Scheduler & mounted drive
7 Mar 1997 08:49:12 -0800
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <3.0.32.19970306202414.00a09df0.cygnus.gnu-win32@awesome.nuance.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Sender: jp AT awesome DOT nuance DOT com
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Original-To: gnu-win32 AT cygnus DOT com
Original-Sender: owner-gnu-win32 AT cygnus DOT com

Does anyone use the NT Sheduler?  I'm trying to include Win32 into our
nightly build cycle but am running into a strange problem.  Here is my setup:

First I've got a file nightly.bat.  This essentially starts bash and tells
it to run go.nightly.

go.nightly cd's to a source directory on a drive that was mounted with the
-b and -m options.  After that it just does a make.

go.nightly (run in a bash shell) by itself works
nightly.bat (run from a dos prompt) works

when it is run by the schedule service make complains that there is no
Makefile.

If I rename Makefile to make.w32 (and run make -f make.w32), it starts up,
but dies as soon as it comes it needs to deal with a file with uppercase
characters in it's name.

As I said, this works fine if I type it in from the command line.  The
scheduler also has no problems doing make on a Makefile on my local drive.

Has anyone tried anything like this?  Does anyone out there have insight
into the NT Scheduler and how it might be interacting with mount?  I'm
thinking about posting something similar to one of the ms.prog.win32 type
newsgroups but I suspect that someone who knows how mount works would have
a better chance at knowing what is happening.

Thanks,
--jp

-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".