Thanks for your help with this. I think I have found the problem. If you prevent access to the command prompt, then Maxima will not run properly. Reallowing access seems to have resolved this issue.
-Robin Horton
On 2/22/10 2:43 PM, "Leo Butler" <l.butler at ed.ac.uk> wrote:
On Mon, 22 Feb 2010, Horton, Robin wrote:
< When a regular user opens XMaxima, it does not look like Maxima is started. I believe once or twice I got a timeout message. Other times, we may have exited the
< GUI too quickly for the timeout to occur.
<
< I?m still fairly new to using group policies to manipulate the OS. Any tips would be most appreciated.
Before proceeding, please verify that Maxima is not started. I believe
that winxp has a process monitor, so you can just start that up and
watch what happens when xmaxima is started. There ought
to be an admin log that logs the (failed) connection attempt, too.
Leo
--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
________________________________
This e-mail message (including any attachments) is for the sole use of
the intended recipient(s) and may contain confidential and privileged
information. If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, distribution
or copying of this message (including any attachments) is strictly
prohibited.
If you have received this message in error, please contact
the sender by reply e-mail message and destroy all copies of the
original message (including attachments).