On Tue, 13 Nov 2001, Michael Beddow wrote:
Just one very minor thing. The current startup batch file won't go beyond the initial message if your Windows install is not itself on drive c: (e.g. on my system which runs Win2K from E:) That's because cygwin.bat assumes that c: is the current drive, which it won't be if the command processor was invoked from a Windows installation on another drive. Simple fix (and harmless to people who have everything on C:). Insert the line C: into cygwin.bat immediately before the cd \cygwin line. Then the batch file will continue correctly, no matter where Windows itself lives.
Thanks. Looking at the code now, I'm not quite sure why it needs to be hard-coded to C:\Cygwin. I'm sure there used to be a reason, but unfortunately it hasn't always been under CVS so now I can't find out why. AFAICS, the only thing that is now location-dependent is the PATH environment variable, which has to include the ...\cygwin and ...\cygwin\usr\X11R6\bin paths. It might work to say set PATH=%0\..;%PATH%;%0\..\cygwin\bin;%0\..\cygwin\usr\X11R6\bin and delete the "cd \cygwin" line. I will try this out at some point. If it works, it means it might also be possible to install onto a network mapped drive. (There's no feasible way for batch files to run directly from UNC paths because a UNC path cannot be a working directory for cmd.exe...). Michael