Blackout Display

[piert]

Now getting an additional importerror for DLL load:

[kgschlosser]

ok in the plugin folder make a new text document. edit that file and paste in the following code

Code: Select all

def __bootstrap__():
    global __bootstrap__
    global __loader__
    global __file__
    import sys
    import imp
    __file__ += 'd'
    
    del __bootstrap__
    del __loader__
    
    mod = imp.load_dynamic(__name__, __file__)
    
    sys.modules[__name__] = mod
    
__bootstrap__()

rename the file to libWinVirtualDesktop.py

[piert]

I assume the file needs to be in the WindowsVirtualDesktop plugin-folder (see top of the picture below).
Still getting the same errors after restarting (as admin or non-admin).

Ps: I was not able to save the notepad's .py file directly in the plugin folder. I had to save into another folder (I choose the documents folder) instead. Then, I cut and pasted the file into the plugin folder. This was only possible after I confirmed administrator's permission to do so. I don't know if that can be related to the error messages?

[kgschlosser]

I am going to have to mess about with it a bit. It seems to be an EG related issue.

If you copy the libWinVirtualDesktop.pyd file to program files (x86)\EventGhost\lib27\site-packages
and delete the libWinVirtualDesktop.py file from the plugin folder it should run without issue.

where did you put the plugin? into %programdata%\eventghost\plugins? or in program files (x86)\EventGhost\plugins??? If you are running Windows 10.. which you are. I would suggest putting it in %programdata%\eventghost\plugins because the program files folder has been locked up pretty good in Windows 10.

[piert]

Per your suggestion I have deleted from program files (x86)\EventGhost\plugins and now using only the %programdata%\eventghost\plugins folder.

Still the same problem, unfortunately:

[piert]

I am not sure if this is relevant, but if I choose 'File - options' in Eventghost, I get the following error about a language problem:

[kgschlosser]

we know about the language problem. the guy that heads up the github repo has vanished. I am unable to get a old of him. I need to send a message to carsonf the guy that set up the github repo and have him grant me permissions on it so that things can start moving again.

did you try moving the pyd file?

[piert]

Yes, see screen capture of my previous-previous post which also shows the resulting error in the log.

[kgschlosser]

I saw where you said you moved the plugin to %programdata% I didn't see here you said that you also tried moving the pyd file to the site packages folder.

[piert]

You are right that I did not say it, but the top of the screencapture included the respective folders with the status after moving the files per your suggestion

[kgschlosser]

yeah but it doesn't tell me if you moved that pyd file or not.

[piert]

Yes, I did move it there.

[kgschlosser]

ok you are going to have to give me some time to mess with it.. I am not sure if it cannot be located by EG or if it is an issue with the actual dll loading.

Because of that "unstable" API I told you about with Windows 10. This could be one of those issues. What build of 10 are you running?

[piert]

OS Name Microsoft Windows 10 Pro
Version 10.0.18362 Build 18362
As mentioned, running as a virtual machine inside Virtualbox.

[kgschlosser]

Code: Select all

18362.418 	2019-10-08 	KB 4517389
18362.388 	2019-10-03 	KB 4524147
18362.387 	2019-09-26 	KB 4517211
18362.357 	2019-09-23 	KB 4522016
18362.356 	2019-09-10 	KB 4515384
18362.329 	2019-08-30 	KB 4512941
18362.295 	2019-08-13 	KB 4512508
18362.267 	2019-07-26 	KB 4505903
18362.239 	2019-07-09 	KB 4507453
18362.207 	2019-06-27 	KB 4501375
18362.175 	2019-06-11 	KB 4503293
18362.145 	2019-05-29 	KB 4497935
18362.116 	2019-05-21	KB 4505057

ok so here is a list of the 18362 builds and their release dates.. and the KB that applies to it.. Do you happen to know which one you are running? I am asking this because I know a few months back Microsoft made a change to the Virtual Desktop API so if you are using an older build then a few months ago That could be the reason why it is throwing an error