Hi again.
> On all Windows files, we should get in the habit of adding
>
> %1 %2 %3 %4 %5 %6 %7 %8 %9
True.
> Could I ask everyone to view having to use a .bat file on Windows as a
bug -
> xmaxima.exe should work without it, and it should set things like
> MAXIMA_PREFIX for the maxima to run "out of the box". If MAXIMA_PREFIX
isn't
> set right by xmaxima then it's xmaxima's (my :-) fault and a bug.
I agree but the maxima binary will need to be launched by xmaxima in a build
specific way as you probably read in James' other email today.
Here is a preliminary hack I used to get rid of the need for maxima.bat in
mynstallation directory:
RCS file: /cvsroot/maxima/maxima/interfaces/xmaxima/Tkmaxima/Cygwin.tcl,v
retrieving revision 1.1
diff -r1.1 Cygwin.tcl
1a2,5
> # Check for an environment variable set by xmaxima-local
> # and if not, set MAXIMA_PREFIX in a way compatible with
> # the assumption that this tcl script was executed from
> # an installed bin directory rather than a source tree.
3c7,13
< # Voodo for CYGWIN
---
> if { ! [info exists env(MAXIMA_XMAXIMADIR)] } {
> set pwd [pwd]
> set env(MAXIMA_PREFIX) "$pwd/../"
> set env(XMAXIMA_MAXIMA)
"$pwd/../lib/maxima/5.9.0rc1/binary-gcl/maxima"
> }
>
> # Voodoo for CYGWIN
This works when I double click on "xmaxima.tcl" in the bin directory. It
just launches the GCL binary directly without arguments. Probably also
needs to set a variable with the arguments to be presented to whatever the
launching binary will be for CLISP and CMUCL.
I don't know off-hand how the freewrap executable does all this.
> My fault, now fixed, but this code is for when you hit a socket failure.
> Because you were talking to a remote server, it could be either a
> run-of-the-mill socket failure, or a more serious problem in the code
> with timeouts.
>
> What I have raised in the list as "the socket bug" is when this
> occurs with the local maxima, which is still done by sockets, but
> socket failures should be extremely rare. For the local maxima, it usally
> means that the local maxima has died, and if so, you get a slightly
> different error message:
>
> ...You must Restart..."
OK, I applied your "set mess" fix and it was OK - the problem occurred
because when "plot.o" is not found in the chaotic difference equation
netmath page it kills the local maxima and further calculation requests lead
to the socket error. I have not experienced any trouble other than this
with sockets on Win 2000.
> Can you post this as a Request for Enhancement in the Bugs list of the
> Sourceforge site?
Done.
Anyway this is all really a furphy, I should really do further testing with
Dave's new package, rather than living in Hacksville.
Cheers
Mike Thomas.