How to edit a manifest file on portable copy?


Daniel McGee
 

Hello all


Have just one add-on left to be updated to NVDA 2023.1


Not sure if I'm missing it, but have installed a portable version of 2023.1


So the question.


If I install the previous add-on compatible with 2022.4. What would be the next steps to go about editing the manifest file on the portable copy?


My logic, if the manifest tweak doesn't work with portable copy, then I can just delete and no harm done to my main installation.


I can hear you all saying now, don't do it! It's just that I have read a previous tutorial explaining how to try the work around. However, it never mentioned how one would try this on a portable copy.


Hence my inquiring.


Daniel


 

On Wed, Mar 29, 2023 at 05:15 PM, Daniel McGee wrote:
Not sure if I'm missing it, but have installed a portable version of 2023.1
-
The following is for clarity:  You cannot and do not install a portable copy, as installing means just that, and involves registry changes to the machine by the installer.  You set-up a portable copy, but it's not installed.

That being said, in the tutorial I wrote, , I stated that for installed NVDA the manifest file for a given add-on would be under the appropriate add-on folder inside %APPDATA%\nvda\addons.

It is in the corresponding spot under whatever folder you used to set up the portable copy in.  I'd just navigate to that folder, let's say it's F:\NVDA\portable, then use File Explorer search on addons, one word, no hyphen.

In portable programs all things they use/access reside somewhere in the folder structure directly beneath whatever folder they were set up in.  I can't be any more specific as any given user could pick any random folder in which to set up a portable program.
--

Brian Virginia, USA Windows 11 Pro, 64-Bit, Version 22H2, Build 22621; Office 2016, Version 16.0.15726.20188, 32-bit

It is much easier to be critical than to be correct.

       ~ Benjamin Disraeli, 1804-1881


Rui Fontes
 

Inside the folder where you have placed the portable copy, look for the folder userConfig.

Inside you will find the addons folder.


Best regards,

Rui Fontes
NVDA portuguese team


Às 22:45 de 29/03/2023, Brian Vogel escreveu:

On Wed, Mar 29, 2023 at 05:15 PM, Daniel McGee wrote:

Not sure if I'm missing it, but have installed a portable version of
2023.1
-
The following is for clarity:  You cannot and do not install a portable copy, as installing means just that, and involves registry changes to the machine by the installer.  You set-up a portable copy, but it's not installed.

That being said, in the tutorial I wrote, , I stated that for installed NVDA the manifest file for a given add-on would be under the appropriate add-on folder inside %APPDATA%\nvda\addons.

It is in the corresponding spot under whatever folder you used to set up the portable copy in.  I'd just navigate to that folder, let's say it's F:\NVDA\portable, then use File Explorer search on addons, one word, no hyphen.

In portable programs all things they use/access reside somewhere in the folder structure directly beneath whatever folder they were set up in.  I can't be any more specific as any given user could pick any random folder in which to set up a portable program.
--

Brian - Virginia, USA - Windows 11 Pro, 64-Bit, Version 22H2, Build 22621; Office 2016, Version 16.0.15726.20188, 32-bit

*It is much easier to be critical than to be correct.*

~ Benjamin Disraeli, 1804-1881





Rui Fontes
 

Except the location of the addons folder, the process is exactly the same...

The location of the folder is on my prior message...


Best regards,

Rui Fontes
NVDA portuguese team


Às 22:15 de 29/03/2023, Daniel McGee escreveu:

Hello all


Have just one add-on left to be updated to NVDA 2023.1


Not sure if I'm missing it, but have installed a portable version of 2023.1


So the question.


If I install the previous add-on compatible with 2022.4. What would be the next steps to go about editing the manifest file on the portable copy?


My logic, if the manifest tweak doesn't work with portable copy, then I can just delete and no harm done to my main installation.


I can hear you all saying now, don't do it! It's just that I have read a previous tutorial explaining how to try the work around. However, it never mentioned how one would try this on a portable copy.


Hence my inquiring.


Daniel





Brian's Mail list account
 

Well the fact is its a lot easier on portable copies as the user config is in the main folder for nvda, not moved as it would be on a normal installation. And yes, if it works then installing a copy from that version will put the newly modified copy in its rightful place. Also, yes again you can delete the add on from the temp then reinstall the nvda from that copy and the add on will go as well. However,if you intend to meddle with the code to try to fix it, its wise to have yet another portable copy or the original add on archive to hand.
The one I'm expecting to have break next is the 3D sounds one, since it has lots of deprecation warnings, and one supposes when the version of the compiler is changed these will need to be replaced by new syntax.
Brian

--
bglists@...
Sent via blueyonder.(Virgin media)
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Daniel McGee" <danielmcgee134@...>
To: <nvda@nvda.groups.io>
Sent: Wednesday, March 29, 2023 10:15 PM
Subject: [nvda] How to edit a manifest file on portable copy?


Hello all


Have just one add-on left to be updated to NVDA 2023.1


Not sure if I'm missing it, but have installed a portable version of 2023.1


So the question.


If I install the previous add-on compatible with 2022.4. What would be
the next steps to go about editing the manifest file on the portable copy?


My logic, if the manifest tweak doesn't work with portable copy, then I
can just delete and no harm done to my main installation.


I can hear you all saying now, don't do it! It's just that I have read a
previous tutorial explaining how to try the work around. However, it
never mentioned how one would try this on a portable copy.


Hence my inquiring.


Daniel