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,
University of Central Florida
NSF-UCF 2006 REU
[log in to unmask]