how to open .gms from cmd?

forticella
forticella
edited January 2016 in User Scripts
hello, i am really need help

i am trying to open a .gms file from cmd, i am successfully open another type of file from cmd but not .gms

here´s what i´ve typed on cmd "C:\Program Files\GlobalMapper16_64bit\global_mapper.exe" "C:\Users\TEMP\Desktop\script\script1.gms"

i try to open script1.gms manually from GM16 and it works perfectly.
script1.gms contains some load file and buffer creation script

is there anything missing from my command line? is there anything that i can do about it? please help me
Tagged:

Answers

  • bmg_bob
    bmg_bob Global Mapper Programmer
    Answer ✓
    First, make sure you have the latest version of Global Mapper 16.

    Your command line looks correct.  What happens when you run this command?  Do you get an error message of some kind?
  • forticella
    forticella
    hello bob, i am currently use GM16.1, is that the problem? is this version isn´t compatible?

    should i put another command or anything to make my script1.gms works from  cmd?
  • bmg_bob
    bmg_bob Global Mapper Programmer
    The command you used should work in GM 16.  What happened when you ran the command.  Did you get an error message?  When you run a script from the command line, you will not see the Global Mapper window appear.  Global Mapper will run the script without a window.  Have you tried using the SET_LOG_FILE command to create a file that contains all of the output messages?
  • JaneH
    JaneH
    Hi there, i cannot seem to run my .gms from command prompt either. It runs successfully if I manually open GM and run it in the app.

    in cmd my command is 

    C:\Users\amss>"C:\Program Files\GlobalMapper19_64bit\global_mapper.exe" "C:\Users\amss\Desktop\BatchClipLazToXYZ_noLog.gms"

    After a couple of seconds I get an error window that says "Global Mapper 19 has stopped working" and the only button available is "Close Program". No output is created at all.

    I have tried a .gms with log messages and have also removed those log message to see if that made any difference.

    The script is readng from a networked computer mapped drive and writing to a local folder.

    Please help!

    Thanks
    Jane
  • gilbertdr
    gilbertdr Global Mapper User
    Hello,

    I am having this same exact problem with GlobalMapper19_64bit.  Have there been any updates with this issue?

    Please note that I'm experiencing the crash even with the simplest of .gms files:

    GLOBAL_MAPPER_SCRIPT VERSION=1.00 LOG_TO_COMMAND_PROMPT="YES"
    LOG_MESSAGE Testing...

    Thanks,

    -- Dan

  • gilbertdr
    gilbertdr Global Mapper User
    Nevermind.  I just updated to GM 19.1 and the issue is resolved.
  • bmg_bob
    bmg_bob Global Mapper Programmer
    Hello,

    I have not been able to reproduce this problem using Global Mapper 19.1.  First, I suggest getting the latest release of Global Mapper 19.1 from our web site.  If you are still having this problem with the latest version, it's possible that there will be some additional information in the Global Mapper log file.  Here is how to produce the most useful log file:
    1. In the Configuration window, go to the General | Advance tab.
    2. Under Logging, set the Log Detail Level to "Debug"
    3. Take note of the location of the log file in the text box
    4. Click OK
    5. Close Global Mapper
    6. Browse to the location where the log file is stored, and delete the log file (errlog.txt, by default)
    7. Attempt to run your script from the command line
    8. Afterwards, create a zip archive containing the log file and attach it to a forum post
    Cheers,
    Bob
  • gilbertdr
    gilbertdr Global Mapper User
    bmg_bob said:
    Hello,

    I have not been able to reproduce this problem using Global Mapper 19.1.  First, I suggest getting the latest release of Global Mapper 19.1 from our web site.  If you are still having this problem with the latest version, it's possible that there will be some additional information in the Global Mapper log file.  Here is how to produce the most useful log file:
    1. In the Configuration window, go to the General | Advance tab.
    2. Under Logging, set the Log Detail Level to "Debug"
    3. Take note of the location of the log file in the text box
    4. Click OK
    5. Close Global Mapper
    6. Browse to the location where the log file is stored, and delete the log file (errlog.txt, by default)
    7. Attempt to run your script from the command line
    8. Afterwards, create a zip archive containing the log file and attach it to a forum post
    Cheers,
    Bob
    Hi Bob.   Looks like our responses crossed.  As I mentioned with my followup the update to Global Mapper 19.1 did in fact resolve the issue.  Thanks for the quick reply, though.
  • mangre
    mangre Global Mapper User
    Bob,
    Would this be the same issue I have with running windows scheduler? As I can run a .gms manually, but not with windows scheduler.

    Regards
    Paul
  • bmg_bob
    bmg_bob Global Mapper Programmer
    mangre said:
    Would this be the same issue I have with running windows scheduler? As I can run a .gms manually, but not with windows scheduler.

    Hello,

    Can you be more specific about your workflow and the results?  I have not tried running a script (or anything else, for that matter) using Windows Scheduler.

    What version of Global Mapper are you using?

    Cheers,
    Bob

Categories

In this Discussion