On Fri, Nov 13, 2009 at 10:42 AM, Jennifer Adams <span dir="ltr"><<a href="mailto:jma@cola.iges.org">jma@cola.iges.org</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style="word-wrap:break-word"><br><div><blockquote type="cite"><div>________________________________________<br>From: Huddleston, John<br>Sent: Friday, November 13, 2009 7:27 AM<br>To: <a href="mailto:GRADSUSR@LIST.CINECA.IT" target="_blank">GRADSUSR@LIST.CINECA.IT</a><br>
Subject: RE: Grads for Windows version 2 installation problems<br><br>Jason<br><br>Arlindo's suggestion to use the installer is best if you are not "systems" oriented with Windows.<br><br>The binaries you are trying to use are based on the pure UNIX code; so, there is no mounting and unmounting of a "C:\Cygwin" directory. For production work on a windows system, these binaries are better qualified.<br>
<br></div></blockquote></div></div></blockquote><div><br></div><div>Well, this mounting/unmounting only takes place if there is no cygwin installed and it was introduced for a good reason. Without it you will have problems with the "!" shell-escape command when cygwin is not installed, and "/tmp" may not be found which may cause opendap to misbehave. Have you tested your binaries on a machine without a cygwin installation?</div>
<div><br></div><div>Your point is well taken, for a production environment the superpack is a bit of an overkill, although I am not sure it has any major performance drawback. This is the reason why I also include a bin and gex tarballs for those users having a cygwin installation already. The superpack is intended for those who do not want to bother with it.</div>
<div><br></div><div> Arlindo</div><div><br></div></div>-- <br>Arlindo da Silva<br><a href="mailto:dasilva@alum.mit.edu">dasilva@alum.mit.edu</a><br>