John O'Rourke wrote:
> Hi,
>
> I appreciate your suggestion in allowing the blocked communication
> between Zone alarm and maxima.exe and wxmaxima.exe but I reviewed the
> blocked communication logs and although maxima appears on the list it
> says that the action taken was "allowed" which is because in the
> individual program handlings I super accept anything with maxima or
> wxmaxima in it and allow incoming and outgoing communications. Sadly
> the software still can't connect either directly through the command
> line interpreter in the bin subdirectory using the batch file , in the
> lib subdirectory using maxima.exe or using the wxmaxima gui. The just
> start and immediately stop running or issue the can't connect message.
>
Sorry, i cannot help much more since i am using maxima on Unix machines, and
i don't have this problem. However i can venture another suggestion. Looking
at sockstat (which displays socket usage on my machine) i see:
niobe% sockstat
USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS
michel lisp 21616 4 tcp4 127.0.0.1:23072 127.0.0.1:4010
michel wxmaxima 21612 5 stream -> /tmp/.X11-unix/X0
michel wxmaxima 21612 6 tcp4 127.0.0.1:4010 *:*
michel wxmaxima 21612 8 tcp4 127.0.0.1:4010 127.0.0.1:23072
.... not relevant for maxima.
Here one sees that wxmaxima has a communication channel on port 4010,
connected to maxima on port 23072, but notice that the corrsponding program
is not called maxima, but lisp (i am using cmucl and the lisp program is
then called lisp). This is perhaps what is biting you with zone alarm.
Try to figure out the name of the lisp program which you are using to run
maxima.
By the way, the stream socket appearing in second position is communication
with the X Window system for display of the GUI.
--
Michel Talon