Thanks for the info guys.
After running FPSC, here is the contents of the contents of the FPSC-MapEditor.log file:
8623156 : Time Stamp Activity Started
8623205 : FPSC-MapEditor.exe Begin
8624391 : FPSC-MapEditor.exe Loop Starts
The fpscreator.log file shows
8605554 - InitInstance...
8605554 - Testing for multiple versions
8605555 - None found - okay to proceed
8605555 - Loading language data...
8605555 - Getting current directory...
8605555 - X:\FPS Creator
8605555 - Starting file map...
8605562 - Parse command line...
8605562 - AfxOleInit...
8605564 - AfxEnableControlContainer...
8605564 - SetRegistryKey...
8605564 - EnableUserTools...
8605564 - Main Init...
8605573 - CMultiDocTemplate...
8605574 - LoadFrame...
8605756 - ProcessShellCommand...
8605782 - OnFileNew...
8605787 - CEditorDoc::OnNewDocument
8605788 - CEditorDoc::SetCurrentDirectory
8605788 - X:\FPS Creator
8605792 - START EDITOR
8619962 - START - success
8619962 - FINISHED
8619962 - CEditorDoc::End
8620004 - DoModal...
8624403 - App Started...
When I have to close FPSC through task manager the following gets added to the fpscreator.log file
8946114 - CMainFrame::OnClose - 908 = 1
8968063 - CMainFrame::OnClose - 908 = 1
8972351 - CMainFrame::OnClose - 908 = 1
Unfortunately, it doesn't look like there is anything useful in there to indicate why this is happening.
@maxd - Yep, I have tried re-starting it several times but it still doesn't work for me. What I have noticed though is if I close down FPSC using task manager and then keep restarting if I look at the processes tab of Task Manager I get several FPSC-MapEditor.exe processes running. If I close all those down, when I next run FPSC I go back to the "This application has encountered a problem ..." dialog box.