You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First I want to thank you for your help, vdesk is a usefull program.
Explain the problem:
Recently i have activated Ubuntu subsystem in my w10, my idea was "have one desktop for each OS" adding a small script to start a second vdek with ubuntu bash when i log in my windows account.
If I try to open bash through vdesk, or system cannot find bash.exe, or issues access denied:
C:\Users\javipc\Desktop>vdesk run-on 1 qq.bat
qq.bat contains:
bash
pause::
I have created a .lnk with admin privileges to bash.exe, and then the error issues is access denied.
I have found a workaround using psexec, but is not a good solution, i don't want to type my password literally.
Thanks again for your help, and if you need more info tell me.
Regards.
The text was updated successfully, but these errors were encountered:
This has been fixed in v1.0.1 (see https://github.com/eksime/VDesk/tree/v1.0.1)
It should now be possible to launch bash directly with VDesk.
Be advised the command line syntax has changed. It is now vdesk on:1 run:bash
Hi eksime,
First I want to thank you for your help, vdesk is a usefull program.
Explain the problem:
Recently i have activated Ubuntu subsystem in my w10, my idea was "have one desktop for each OS" adding a small script to start a second vdek with ubuntu bash when i log in my windows account.
If I try to open bash through vdesk, or system cannot find bash.exe, or issues access denied:
C:\Users\javipc\Desktop>vdesk run-on 1 qq.bat
qq.bat contains:
bash
pause::
I have created a .lnk with admin privileges to bash.exe, and then the error issues is access denied.
I have found a workaround using psexec, but is not a good solution, i don't want to type my password literally.
Thanks again for your help, and if you need more info tell me.
Regards.
The text was updated successfully, but these errors were encountered: