Topic: How to add Registry entries for "PC Packed" plugins: *.reg file in *.7z archive  (Read 480 times)

0 Members and 1 Guest are viewing this topic.

clsven

  • Jr. Chef
  • **
  • Date Registered: Mar 2017
  • Posts: 20
Assume I created successfully a plugin with "PC packed" utility.

It works fine.

However I need some more customizations which should be stored in Registry. I created a *.reg file with all required Registry keys/properties and add it into the *.7z archive of the other plugin files.

What I need now is a way to tell WinBuilder in "PC Packed" section not only to create a corresponding plugin from myplugin.7z but use the embedded file myregentries.reg to apply it to the Registry as well.

How can I achieve this?

If this is not possible with "PC Packed" directly maybe I have to edit the created *.plugin file manually.
Which entry do I have to add to apply myregentries.reg to Registry?

Thank you
Claudia





Lancelot

  • Gena Baker
  • Grand Chef
  • *****
  • Date Registered: Sep 2010
  • Posts: 7076
If this is not possible with "PC Packed" directly maybe I have to edit the created *.plugin file manually.

When you do that, you will notice a line with :
Code: [Select]
//Registry - Use Utils\RegCPE

which shows
+ where to put registry entries inside a plugin
+ which tool to be used

clsven

  • Jr. Chef
  • **
  • Date Registered: Mar 2017
  • Posts: 20
It works.
Thank you

It would be nice if RegCPE could be somehow integrated into "PC packed"
I mean having another entry field in "PC packed" where users can enter a *.reg script and the content is later auto-converted and auto-appended to [Process] section
« Last Edit: August 12, 2017, 07:41:41 PM by clsven »

Lancelot

  • Gena Baker
  • Grand Chef
  • *****
  • Date Registered: Sep 2010
  • Posts: 7076
On most cases where 3rd party application only saves its settings, registry conversion works out of box

BUT

Auto conversion can not fully work...... (many reasons)
And we never put crippled solutions to plugins.

That is the reason user must check result conversion

That is the reason there is
//Registry - Use Utils\RegCPE
line

so end user enforced to see registry conversion during copy-paste   :cool:

*
In the end, It mostly takes only some 10 seconds to do copy paste of 3rd party application registry settings  :wink:

It takes more time on some other cases....

:turtle:

 

Powered by EzPortal