Turns out the quotes aren't needed for the task action. I must have been putting those in by default thinking the same thing a long time ago. So you can actually change your task to be without quotes (for the Program/script field), or wait until next release where I will ignore quotes for the comparison.
EPG fails to update
Forum rules
★ Download the latest EPG123 here: https://garyan2.github.io/ <> Setup guide here: https://garyan2.github.io/install.html ★
★ Download the latest EPG123 here: https://garyan2.github.io/ <> Setup guide here: https://garyan2.github.io/install.html ★
-
garyan2
- Posts: 7474
- Joined: Fri Nov 27, 2015 7:23 pm
- Location:
-
HTPC Specs:
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io
Keeping WMC alive beyond January 2020. https://garyan2.github.io
-
Space
- Posts: 2839
- Joined: Sun Jun 02, 2013 9:44 pm
- Location:
-
HTPC Specs:
I'm pretty sure that you need quotes only if you have spaces in the path or filename.
-
garyan2
- Posts: 7474
- Joined: Fri Nov 27, 2015 7:23 pm
- Location:
-
HTPC Specs:
If you were running from the command prompt or a batch file, yes... need the quotes for paths that contain spaces. They are evidently not needed for scheduled tasks (which probably adds them automatically at runtime).
- Gary
Keeping WMC alive beyond January 2020. https://garyan2.github.io
Keeping WMC alive beyond January 2020. https://garyan2.github.io
-
Space
- Posts: 2839
- Joined: Sun Jun 02, 2013 9:44 pm
- Location:
-
HTPC Specs:
With the task scheduler you specify the program in one field and the arguments in another field, so I would guess that is why there is no need to quote the spaces as there is no ambiguity as to what is the program and what are the arguments.
However, if the arguments themselves had an argument that had to be treated as a single argument and had a space in it, I would assume you would have to quote that argument.
I found this and apparently it works this way in Win7, but Win10 (unless it's been fixed since that post) has a problem with it (although that issue may only occur when using a batch file instead of an executable).
However, if the arguments themselves had an argument that had to be treated as a single argument and had a space in it, I would assume you would have to quote that argument.
I found this and apparently it works this way in Win7, but Win10 (unless it's been fixed since that post) has a problem with it (although that issue may only occur when using a batch file instead of an executable).