-
Notifications
You must be signed in to change notification settings - Fork 21
Run from a shared folder or mounted drive (UNC path) #267
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
Comments
This message pops up when the embedded Python interpreter fails to initialize, which usually happens when some files/dlls are missing in a normal environment. I'm not familiar with how VDI works under the hood but the init step that fails and leads to this message only involves a single function call to the Python interpreter, which does not provide precise error code/message when something goes wrong in this case. Hence the vague nature of this message. Since file redirection did not have time to take place (i.e. Python to Keypirinha), Keypirinha's log file may not be of any help neither so perhaps you can try Keypirinha's SDK and see if the Python interpreter prints something useful on a console:
|
Closing this due to no feedback |
Hi @polyvertex, I checked the output of interpreter, but it's the same as that of normal non-VDI machine. Just let me ask a question. Regards, |
Due to a limitation from the embedded Python interpreter, Keypirinha should be able to run from a network storage only if the network folder is mounted as a drive first (itself or its parent). See #190. Can you do that from your VDI environment? |
Hi, Thanks for your advice. I created new portable.ini and set portable_dir using Drive character.
2018-03-12 08:03:06.352 [i] Official packages: \?\UNC\xxx.xxx.xxx.xxx\taka-t\Keypirinha\default\Packages Regards, |
Mmmh for the purpose of this test, you should not need to create the |
Yes, your test seems correct. In the light of your test, there might be a way to solve this but it's nothing you can do unfortunately and you will have to wait for a next release of Keypirinha. Thank you for taking the time to perform these tests. Technical details: Keypirinha calls the |
Hi @polyvertex , Thanks for your input. And create the sample source just modifying the parameter as following, then run it on my environment specifying files on mounted drive, but it always returns UNC path. Regards, |
Yes Also, since you seem to run a Japanese version of the OS, it might be that KP doesn't fully support the localized path separator ( |
Sorry for my ambiguity, and the UNC path returned from the sample code show the shared folder path(\?\UNC\xxx.xxx.xxx.xxx.local\taka-t...), not the mounted drive. Yes, KP works perfectly on my local drive with Japanese OS. Regards, |
Thanks for confirming |
This should be fixed in v2.19, please give it a try! |
Hi @polyvertex , It works on my VDI env! Regards, |
Hi,
I'm using virtual desktop environment called VDI at my office, that strictly limits user control over their desktop use.
(VDI)
https://www.microsoft.com/en-us/cloud-platform/desktop-virtualization
I put the 64bit portable of Keypirinha on the VDI desktop and tried it, but keypirinha.exe outputs following error when I double click it:
those binaries that I tried perfectly works on my ordinary laptop, so i think the cause is not in the corrupted files of Keypirinha, but my special VDI environment.
So, I want to know the fundamental cause of the message to do some workarounds. Could you advise any ideas to know the cause?
Regards,
The text was updated successfully, but these errors were encountered: