by Barry4679 » Sat Feb 10, 2024 12:26 am
Dryst wrote: ↑Fri Feb 09, 2024 8:28 pm
The script closes MMW5, but it does not start after closing. This is your issue, correct?
Correct.
Dryst wrote: ↑Fri Feb 09, 2024 8:28 pm
Did you install Media Monkey 5 to a different location than default? This would be a reason it is not starting for you. Try doing a WIndows Key + R and enter the following within the Run, Open input that appears:
"C:\Program Files (x86)\MediaMonkey 5\MediaMonkey.exe"
If you click OK, will MMW5 launch and be visible? My guess is the answer is no. This is all the PowerShell script is doing.
Also, this script was written assuming you have a 64-bit OS. If you have 32-bit this could be another issue.
I have 65 bit OS.
MM5 installed in the default location.
The Windows key + R test works OK, ie. MM5 starts
Also as I said before the script works as advertised if I run it in the PowerShell ISE or via the "Run with PowerShell" option in the content menu for the script file.
Must be something I don't know about a running a task manually from the Task Scheduler, or how to create a task inside the scheduler w/o a trigger, or a maybe it is a rights issue.
I don't need an answer to this, I was just trying to springboard into the an evaluation of the Task Scheduler, arising from your posting.
Dryst wrote: ↑Fri Feb 09, 2024 8:43 pm
If MMW5 was reliable, I would have no need for this script.
It's not reliable. That is the issue.
I am not arguing this point.
Personally I find MM5 to be stable, but then I work within a narrow path, and don't push out into weeds by trying to run music 24*7 etc.
I can pretty much crash MM5 at will.
The steps are:
- Try something outside of my narrow path
The point that I was trying to make was that your script appears to be more generally applicable than your thread title suggests.
And for that general Use Case it more easy to setup than your post suggests, because there is no need to go anywhere need the Windows task Scheduler.
[quote=Dryst post_id=517026 time=1707528534 user_id=116831]
The script closes MMW5, but it does not start after closing. This is your issue, correct?
[/quote]
Correct.
[quote=Dryst post_id=517026 time=1707528534 user_id=116831]
Did you install Media Monkey 5 to a different location than default? This would be a reason it is not starting for you. Try doing a WIndows Key + R and enter the following within the Run, Open input that appears:
"C:\Program Files (x86)\MediaMonkey 5\MediaMonkey.exe"
If you click OK, will MMW5 launch and be visible? My guess is the answer is no. This is all the PowerShell script is doing.
Also, this script was written assuming you have a 64-bit OS. If you have 32-bit this could be another issue.
[/quote]
I have 65 bit OS.
MM5 installed in the default location.
The Windows key + R test works OK, ie. MM5 starts
Also as I said before the script works as advertised if I run it in the PowerShell ISE or via the "Run with PowerShell" option in the content menu for the script file.
Must be something I don't know about a running a task manually from the Task Scheduler, or how to create a task inside the scheduler w/o a trigger, or a maybe it is a rights issue.
I don't need an answer to this, I was just trying to springboard into the an evaluation of the Task Scheduler, arising from your posting.
[quote=Dryst post_id=517028 time=1707529434 user_id=116831]
If MMW5 was reliable, I would have no need for this script.
It's not reliable. That is the issue.
[/quote]
I am not arguing this point.
Personally I find MM5 to be stable, but then I work within a narrow path, and don't push out into weeds by trying to run music 24*7 etc.
I can pretty much crash MM5 at will.
The steps are:
[list=1]Try something outside of my narrow path :D [/list]
The point that I was trying to make was that your script appears to be more generally applicable than your thread title suggests.
And for that general Use Case it more easy to setup than your post suggests, because there is no need to go anywhere need the Windows task Scheduler.