Topic: RunScanner 2.0.0.0 ( includes x86 / x64 verisons )  (Read 10668 times)

Re: RunScanner 2.0.0.0 ( includes x86 / x64 verisons )
« Reply #20 on: February 27, 2016, 06:29:47 AM »

Lancelot

  • Gena Baker
  • Grand Chef
  • *****
  • Date Registered: Sep 2010
  • Posts: 10350
Hi Paraglider,

+ Arch,x86|x64 wrong (above driver plugin is architecture independent),
edit: more correct osfamily os dependent, besides no need such lines here.  :wink:

Since you are regular user around:
+ you already aware, use plugin naming, it cause chain follow others (see chain follow example Atari800xl above )
+ avoid using bad old bartpe habit of providing files on %ScriptDir% , this cause recent unknown winbuilder trouble on your mbam topic, it cause more troubles, and also chain follow by other users (see chain follow example Atari800xl above )

+ Use RegCPE, above codebox have unnecessary quotes, we fixed on RegCPE years ago, and RegCPE open source ..
I cleaned %99 unnecessary quotes on plugins manually, such examples like above cause chain follow of other users using unnecessary quotes......

* You should already aware all above, summary hopefully helps, from your profession you should understand more clearly than newbies ....

:turtle:
« Last Edit: February 27, 2016, 06:30:43 AM by Lancelot »

Re: RunScanner 2.0.0.0 ( includes x86 / x64 verisons )
« Reply #21 on: February 27, 2016, 01:02:56 PM »

paraglider

  • Chef
  • ***
  • Date Registered: Mar 2011
  • Posts: 144
my instructions only specified x86 / x64 drivers so arch command is required.

ScriptDir is the best place for associated files as it makes the plugin self contained.

It is a bug in your download function that it is not able to download files to ScriptDir.

Don't understand your comment about plugin naming.

I will fix my conversion program to not put in the quotes.


Re: RunScanner 2.0.0.0 ( includes x86 / x64 verisons )
« Reply #22 on: February 27, 2016, 02:32:37 PM »

Lancelot

  • Gena Baker
  • Grand Chef
  • *****
  • Date Registered: Sep 2010
  • Posts: 10350
my instructions only specified x86 / x64 drivers so arch command is required.
adding driver to a build only related to source architecture since ms makes rest registry same for all windows architectures.... practically no need such check... anyway....

ScriptDir is the best place for associated files as it makes the plugin self contained.
no it is not, as written on your mbam topic, and it does not make the plugin self contained, plugin contains nothing like your mbam plugin contains nothing.

as written on mbam topic, this cause mess on various areas which you should already know !
 or maybe you simply ignore all past troubles (known habit of old users) since we cleaned up all scriptdir provide on plugins which cause no reports of failures on scriptdir usages on topics.......

It is a bug in your download function that it is not able to download files to ScriptDir.
It seems to be more bug of winbuilder, yet another bug of using scriptdir like from past, if not let me know.
 To me It is quite waste of time to investigate already knowing some related bugs of winbuilder and not used troublemaker scriptdir to provide files on any plugin.

Don't understand your comment about plugin naming.
one of example:
http://theoven.org/index.php?topic=676.msg19477#msg19477
you marking topics read for years on current forum, already around on theoven.org for years, writing under plugin section..... !!!

well it is one of things that will not work on home made plugins in future....

I will fix my conversion program to not put in the quotes.
It is your time to waste.
RegCPE written so nicely no need to change since years,
 either use RegCPE or duplicate all RegCPE open source codes to your conversion program to fix it.

ps: Other BlueLife utilities can be found here ex: http://www.sordum.org/8478/reg-converter-v1-0/

*
also there is "Create New Empty Plugin" available , PC Packed also have small e button
Call,CreatePlugin
http://theoven.org/index.php?topic=45.0

which tidy up plugin organizations, maybe you have another program ! than simply duplicate and follow updates with your free time.

****
back to my work, simply follow paraglider, all organizations have quite good logic behind to get projects sustainable. Even you can not understand logic there is simple fact, Self proof they are still alive, compared to other bad habit projects and organizations.....


:turtle:

Re: RunScanner 2.0.0.0 ( includes x86 / x64 verisons )
« Reply #23 on: February 28, 2016, 12:05:46 AM »

ChrisR

  • XPE Baker
  • Grand Chef
  • *****
  • Date Registered: Mar 2011
  • Posts: 3494
Good finding JFX for the compressed files of Windows 10 Compact which requires wofadk.sys :thumbsup:
Compact: https://msdn.microsoft.com/en-us/library/windows/hardware/dn949267(v=vs.85).aspx

I added wofadk driver in all SE projects. Due to  lack of time I have not tested until the end.
Drivers are downloaded in Retrieve Tools with Getwaiktools and copied in tools folder.
Then, to get it in a basic building, it is copied in Copy Files plugin with the registry written in Shell & Config.


 

Powered by EzPortal