Global Mapper v26.0

Problem with lock.lck file getting locked by multiple proccesses

Hi there,

An application we have uses the GlobalMapper SDK (v22.1).

I need to have several sessions of the application open at the same time and occassionally get this error, as it looks like GM is writing to the same Temp directory for all of my sessions.



Is there any way I can get GM to write to unique directories (perhaps based on its processID), so I don't get this locking issue.



Any advice appreciated

Regards,

Mat.

Comments