Doh! Sorry, I'm not a Windows user and just tried to get something in there that would make it easy for a script to update later on. I have updated the batch files and b90 will be corrected. TYVM!yorick wrote:The Windows batch files do not function. The first line should read "set VERS=1.3.b89", not "VERS=1.3.b89".
Yep, reasonable idea.The Windows batch files set the stack size to 512k. The MaptoolLauncher default is 2M. Changing that option to -Xss2M sounds prudent.
Well, having the console is one of the advantages. You don't have to go grab the .maptool/log.txt to see the log messages that way.The Windows batch files keep a command window around, although they use javaw. Using "start" would resolve this.
This has never been brought up before. What do others think?
Yes, this is a work in progress. Lee has a Java-based launcher with more bells and whistles and it will be cross-platform and hence a better choice than any of the others. I don't have a C++ compiler for Windows so I can't change the existing launcher (I know how the code would have to call opendir(3) and readdir(3), I just can't generate a binary).MaptoolLauncher.exe does not function with Java 7, showing an error about maptool-*.jar. I understand this is a bug in Java 7. A workaround could be to have the launcher do the globbing and hand a full file name to Java.
Thanks, I'll check those out. (I've added a post to the J7 for Windows thread.)JamzTheMan wrote:FYI: There are a couple of batch files that get around this limitation as well:
http://forums.rptools.net/viewtopic.php ... 7&start=25
http://forums.rptools.net/viewtopic.php ... 6&start=60