From help-octave-request at bevo dot che dot wisc dot edu  Thu Jan 28 15:22:31 1999
Subject: Re: Problems installing under Windows 95
From: "Dave Borger" <dborger at wilshire dot com>
To: "John W. Eaton" <jwe at bevo dot che dot wisc dot edu>
CC: help-octave at bevo dot che dot wisc dot edu
Date: Thu, 28 Jan 1999 13:20:04 -0800

In trying to track down my installation problem I have observed that while
"installing m files in $fcnfiledir" that the script file is interupted by
a stack fault error:

xargs caused a stack fault in module KERNAL32.DLL at 0137:bff725c5

I had missed this earlier because it appeared that the script continued,
but perhaps not without skipping a portion of the installation.

Dave

John W. Eaton wrote:

> On 27-Jan-1999, Dave Borger <dborger at wilshire dot com> wrote:
>
> | Because of the installation problems previously mentioned, I thought
> | maybe I should re-run the installation now that I had the proper
> | FIND.  Now both 'sh ./install-octave' and 'bash ./install-octave'
> | report that CAT.EXE is not found, despite the fact that it is on a
> | directory in my path.  Now, as you may know, the default path used
> | by the Cygnus USERTOOLs installation is rather long and I could have
> | easily mistyped in when I added it to my PATH.  However, from the
> | directory from which I am trying to install Octave I can type 'cat
> | install-octave' and, sure enough, the contents of the file are
> | listed out.
>
> Something seems to be wrong with your setup if cat is not found.  I'm
> sorry, but I have no idea how to fix this for you.
>
> | In your response below you as if I have bash installed 'as /bin/sh.'
> | I'm unsure what you mean by that.  I have bash on the same path as
> | cat and if I type 'bash' from any directory it returns the bash
> | prompt.  (Again, forgive my ignorance, but what is the relationship
> | of bash and sh?)
>
> The shell scripts distributed with Octave expect to find a Unix shell
> in /bin.  Bash will work for that.  You need to create a directory
> called c:\bin and put a copy of bash there, but it must be named
> sh.exe.
>
> | On the matter of the C/D directory, it seems that your solution
> | still requires that the installation be physically on the C drive
> | which, due to space, is what I am trying to avoid.
>
> No.  If you do this:
>
>   mkdir /d_drive
>   mount d: /d_drive
>
> then /d_drive should actually point to the d: drive and /d_drive/foo
> should be equivalent to d:\foo.
>
> jwe