Windows 10 can't load plugin
Quote from Wrangler on May 19, 2020, 10:49 pmHas anyone else had reports of win10 throwing an error in loading the plugin .nbr to the temp dir? I have 2 customers today who reported this error. I suspect a bad windows 10 update. Also, does anyone know how to tell which plugin it is? 8C4EE09F.nbr doesn't help a whole lot. I had them install and run with administrator privileges and it still gives the errors. The program is installed off the c:\ root.
Has anyone else had reports of win10 throwing an error in loading the plugin .nbr to the temp dir? I have 2 customers today who reported this error. I suspect a bad windows 10 update. Also, does anyone know how to tell which plugin it is? 8C4EE09F.nbr doesn't help a whole lot. I had them install and run with administrator privileges and it still gives the errors. The program is installed off the c:\ root.
Quote from rasl on May 20, 2020, 6:44 pmYou can open it with a hex editor and look for the hex string 53007400720069006E006700460069006C00650049006E0066006F
which in text mode looks like: S.t.r.i.n.g.F.i.l.e.I.n.f.o.
below should be the name of the plugin.
If you don't want to do this, upload it to some place where you can take it to analyze it.
You can open it with a hex editor and look for the hex string 53007400720069006E006700460069006C00650049006E0066006F
which in text mode looks like: S.t.r.i.n.g.F.i.l.e.I.n.f.o.
below should be the name of the plugin.
If you don't want to do this, upload it to some place where you can take it to analyze it.
Quote from Wrangler on May 20, 2020, 8:08 pmThanks for the response rasl. I was able to use a hex editor and find the plugin name. Problem is, the filenames are randomly generated and the program uses more than one plugin, so it is impossible to tell who is causing the problem. I'm running win7 so I can't recreate the issue.
Hopefully microsoft will fix the problem in a future update.
Thanks for the response rasl. I was able to use a hex editor and find the plugin name. Problem is, the filenames are randomly generated and the program uses more than one plugin, so it is impossible to tell who is causing the problem. I'm running win7 so I can't recreate the issue.
Hopefully microsoft will fix the problem in a future update.
Quote from rasl on May 20, 2020, 9:15 pmBut when windows gives the error it must refer to the plugin that produces it (example 8C4EE09F.nbr), there it must take it from temp and analyze it
But when windows gives the error it must refer to the plugin that produces it (example 8C4EE09F.nbr), there it must take it from temp and analyze it
Quote from Wrangler on May 20, 2020, 9:29 pmYes. I understand that. But I can't ask my customers to try to find the file, download a hex editor and find the name in it for me. Not everybody is as computer savvy as we are. :)
If you have win10 with all updates installed and would like to try and reproduce the error for me, that would be great.
Download: http://farmwrangler.com/fs19dashboard.html
Note: The program won't run unless you give it a path to the game's savegame folder after starting it the first time. Just browse and select any file. Besides, it should already have loaded the plugins by that time.
Yes. I understand that. But I can't ask my customers to try to find the file, download a hex editor and find the name in it for me. Not everybody is as computer savvy as we are. :)
If you have win10 with all updates installed and would like to try and reproduce the error for me, that would be great.
Download: http://farmwrangler.com/fs19dashboard.html
Note: The program won't run unless you give it a path to the game's savegame folder after starting it the first time. Just browse and select any file. Besides, it should already have loaded the plugins by that time.
Quote from HPW on May 21, 2020, 8:54 amHello,
As a Workaround to the Problem you could consider to not compile the plugins into the Exe.
But this would leave the clear names of the plugins in the app Directory.
Also loading will get faster because no file-extracting and decompressing.
In the Archiv is a Diskussion and solution to make plugins named similar to the app-name:
https://archive.visualneo.com/viewtopic.php?f=5&t=18741
Regards
Hans-Peter
Hello,
As a Workaround to the Problem you could consider to not compile the plugins into the Exe.
But this would leave the clear names of the plugins in the app Directory.
Also loading will get faster because no file-extracting and decompressing.
In the Archiv is a Diskussion and solution to make plugins named similar to the app-name:
https://archive.visualneo.com/viewtopic.php?f=5&t=18741
Regards
Hans-Peter
Quote from Wrangler on May 21, 2020, 11:07 pmThanks everyone for the input. I appreciate it. I haven't had any other reports besides the first two. Next update I won't compress the plugins and see what happens.
Thanks everyone for the input. I appreciate it. I haven't had any other reports besides the first two. Next update I won't compress the plugins and see what happens.