It sounds to me that it's probably not a MASON problem but a problem
with the mason.bat file. We'll check it out and get back to you; but
if you like you might beat us to the punch by poking around there.
MASON's script files are very straightforward: they add to the
CLASSPATH the mason directory and any jar file located inside the
mason directory. Then they run [java sim.display.Console] and that's
about it. My guess is the CLASSPATH setup is being broken because of
the spaces, either by the script or by Sun's VM.
On Jun 27, 2006, at 4:14 PM, Colson, Nathaniel W wrote:
> Hello all,
> I am a researcher at UCF and I am trying to create a simulation
> with MASON on a public lab computer. However, the only directory I
> have permissions to run MASON from is "Documents and Settings\user
> \desktop", and the spaces in the folder name (Documents and
> Settings) are managing to break MASON as it starts up (aka. I run
> the mason.bat script, a blank console appears momentarily, and then
> closes without warning or error message). If I run it straight from
> the C:\ directory of other machines it starts up fine, but I don't
> have write access to C:\ on the lab computer I need to use.
> So my question is, what kind of effort would it take to sift
> through MASON's system code and make it robust enough to handle
> those spaces? Is that even possible, and if so where would I start?
> Thanks in advance,
> Nathaniel Colson
> University of Central Florida
> NSF-UCF 2006 REU
> [log in to unmask]