Skip to main content
Question

.bat Why the script bellow does't work in Windows 10? It worked in Windows7. What is the problem?

  • July 3, 2018
  • 7 replies
  • 16 views

Forum|alt.badge.img

REM KÖR FME

 

"C:\\apps\\FME\\2016\\fme.exe" entre1.fmw

 

"C:\\apps\\FME\\2016\\fme.exe" entre2.fmw

 

"C:\\apps\\FME\\2016\\fme.exe" entre3.fmw

pause

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

7 replies

fmelizard
Safer
Forum|alt.badge.img+20
  • Safer
  • 3719 replies
  • July 3, 2018
Hi @margareta What error are you getting? Is fme.exe running in your process manager?

 

 


Forum|alt.badge.img
  • Author
  • 4 replies
  • July 4, 2018

it's look like:

C:\\Windows>REM KÍR FME

C:\\Windows>"C:\\apps\\FME\\2016\\fme.exe" entre1.fmw

 

FME 2016.1.3.2 (20170214 - Build 16717 - WIN32)

 

FME Desktop ESRI Edition (floating)

 

Permanent License.

 

Machine host name is: L-18DBF2262DC4

 

Operating System: Microsoft Windows 10 64-bit (Build 14393)

 

Copyright (c) 1994 - 2016, Safe Software Inc.

 

Safe Software Inc.

 

File entre1.fmw could not be opened

 

Program Terminating

i do it directly from C: prompt


david_r
Celebrity
  • 8391 replies
  • July 4, 2018

Based on the error message you need to specify the complete path to your workspace files. Example:

"C:\apps\FME\2016\fme.exe" "c:\users\myself\documents\fme\entre1.fmw"

If you don't, FME will try to look for the workspace file in your current directory, which in your case seems to default to c:\windows


Forum|alt.badge.img
  • Author
  • 4 replies
  • July 4, 2018

With start get I even this:

CMD.EXE was started with the above path as the current directory.

 

UNC paths are not supported. Defaulting to Windows directory.


david_r
Celebrity
  • 8391 replies
  • July 4, 2018

With start get I even this:

CMD.EXE was started with the above path as the current directory.

 

UNC paths are not supported. Defaulting to Windows directory.

Is it possible that you've defined a default current directory to a UNC network resource (e.g. "\\\\server\\share1\\share2")? That would explain the warning.

 

But as long as you specify the full fme.exe and workspace path, it shouldn't make any difference, you can then safely ignore the warning.

Forum|alt.badge.img
  • Author
  • 4 replies
  • July 4, 2018

Thank you very much. It works!


  • 1 reply
  • October 31, 2018

thank you for the information.