Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tasks running and ready, but not affecting lock screen #2

Open
mcgeochd opened this issue Oct 25, 2022 · 2 comments
Open

Tasks running and ready, but not affecting lock screen #2

mcgeochd opened this issue Oct 25, 2022 · 2 comments

Comments

@mcgeochd
Copy link

mcgeochd commented Oct 25, 2022

I followed this guide to setup Wintermelon: https://www.ilovefreesoftware.com/16/windows/how-to-show-lock-screen-on-both-displays-in-dual-monitor-set-up.html, trying twice with the files in Program Files and in Downloads with no luck.

image

The tasks point to the correct location of the exe as well, but the lock screen still only shows on one monitor.

image

@mcgeochd
Copy link
Author

I actually just managed to fix this. The guide I linked doesn't mention .NET core but it is required, secondly, the guide tells you to modify the script paths incorrectly, they should actually look like this:

image

@arun-goud
Copy link
Owner

@mcgeochd Glad you were able to resolve it. I'm not the author of the article you pointed out but the author there has done a great job posting screenshots which make the installation process very clear. There is some customization going on there such as changing the bin path in the powershell script. In the README I've in this repo I specify the publish location as Target location=bin\Release\netcoreapp3.1\publish\ and in requirements I've mentioned that .NET core runtime (or SDK, which comes with the runtime) is required. The powershell install scripts should not need any modifications if you follow my README. Also, beware, do not use exe files found online. You can install the free version of Visual Studio and build the exe out of the C# solution project file yourself. I intentionally excluded the exe from the repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants