Hi,
I use PDFCreator to convert many Word documents into PDF automatically.
To do this I use the command line.
Unfortunately, according to the documents I'm converted, I need to change some settings.
In the various parameters of the command line I noticed / OptionsFile .
Unfortunately I have a little trouble understanding its operation and the help section that corresponds is not very explicit "
Specifies the specific parameters that must use PDFCreator.
Example: pdfcreator.exe / OptionsFile "C: \\ MyPDFCreator.ini"
(Note: With this option (and a bit of work) you can use more than one printer per machine.) "
In fact, although I specify a file. INI set properly, PDFCreator systematically take the default settings.
Do you have an idea for my problem?
Regards,
Alexandre.
Hello,
I have exactly the same problem.
When I launch pdfcreator with /OptionsFiles, the options are well assigned, but in fact, it is the options of the default profile that are used...
Any idea. thanks in advance
regards
thierry
Hi,
in my computer (Win Vista, PDFCreator 0.9.9) the following command works:
pdfcreator /OptionsFile"c:\\temp\\pdfcreator.ini" /PF"c:\\temp\\test.txt"
The whole content of pdfcreator.ini:
[Options]
AutosaveDirectory=M:\\
AutosaveFilename=pdfcreator
AutosaveFormat=0
StartStandardProgram=0
UseAutosave=1
UseAutosaveDirectory=1
But I have somewhat different problem:
- the window of PDFCreator stays opened
- when I use /NoStart option, the window is closed, but the /OptionsFile is not read (auto-save does not work)
Any solution?
With regards,
Mirek
Hello Mirek,
I think i will explore your way, with no /NoStart and then use a pskill ou stop-process (with powershell)... to stop the pdfcreator.exe
I'll try next Monday
thank you
thierry
Hi,
I managed to use the /OptionsFiles paramater. But I've the same problem as Mirrek.
So I kill the PDFCreator process then I restart PDFCreator as many time as I want to print documents and that's work perfectly.
But I think it's not a good way to use PDFCreator . . .
I hope this problem will be resolved soon or we will be given details of the use of sweat /NoStart.
Regards,
Alexandre.