2015-05-20 23:28:55 +0200 answered a question What's the best way to batch convert ODF to PDF on Windows? FWIW, answer of rafik here gives a reasonable solution. Note also another information at the abovementioned page. 2015-05-20 19:58:30 +0200 commented answer convert-to command line parameter P.S. In a .bat file (script) you need to change %f to %%f. 2015-05-20 19:48:08 +0200 commented answer convert-to command line parameter FWIW: 1. Yes. 2. IMO, setting the path concerns executable files only (but I am not an guru for MS-DOS/Windows shell) 3. Yes (as an implication of 2.) 4. Very probably yes but I can't tell you how - MS-DOS shell manual should say more. But executing at first the set command and afterwards the for command solves the situation in any case (the path you set is definitely valid at least until the command prompt session terminates). Or you can create a .bat file and separate commands by newline. 2015-05-20 19:27:27 +0200 commented answer convert-to command line parameter [continued] it is not necessary to call it via start /wait command. Unfortunately, it is NOT true. At least on Windows Vista (I know, horrible OS - but it was not on my computer) it is necessary to use start /wait even in a batch, otherwise the conversion collapses. Update: Primary source for the incorrect information about the start command (Microsoft's site). LO version: 4.3.6. 2015-05-20 19:24:34 +0200 commented answer convert-to command line parameter One more addendum: It is possible to read - for example here: http://www.computerhope.com/starthlp.htm , www.microsoft.com is silent about that - that “When executing an application that is a 32-bit GUI application, CMD.EXE does not wait for the application to terminate before returning to the command prompt. This new behavior does NOT occur if executing within a command script.”; so it should imply that when executing soffice.exe from a batch script,