Bug in SWV 6.1.5126 ? => Modification of the read only zone of a layer
Updated: 29 Jul 2010 | 5 comments
I notice this behavior
- Description :
1 – create an empty layer
2 – create a registry key MyKey on « read only » zone, and a value on this key value=value
3 – create a reg file reg which modify the MyKey key with a new value value=value2
4 – activate the layer
5 – in a command window launch the command regedit /s reg file
6- deactivate the layer and go to explore the read only zone of the layer
- résult: value=value2 on the read only zone of the layer instead of being on the “inscriptible zone”.
So that mean that if you reset the layer for exemple, it will not be on the same state that you have when you had imported it.
Discussion Filed Under:
Comments
The problem still exists on SWV 6.1 SP4
The problem still exists on SWV 6.1 SP4
That's expected behavior,
That's expected behavior, because I think you're seeing the changes in the base and not inside the layer.
To do what you're wanting to do activate the layer and then execute (run application from layer) your command prompt.
If a forum post solves your problem please flag is as the solution
Thank's for your answer Jordan but ....
Are you sure that it's a normal behavior when you execute a process in the base (not from thelayer) which modify registry keys that still exist on the layer, then modifications are applicate on the "read only" zone?
Because it's typically what ican do but don't want to ???
(I insist : the step 5 is a command which is not launch from the layer)
When you execute something
When you execute something from the base the changes go to the base. When you deactivate the layer the registry in the layer doesn't exist anymore so the the changes you're seeing are not in the layer but in the base of the machine.
Also what can be going on is the .REG file that has the changes are for the RO sublayer (ie HKLM\Layer_1\HK\Software\Test) so regardless of how you load them the changes will be going to that location.
If a forum post solves your problem please flag is as the solution
This is what i expect and see in the previous version
This is what i expect and see in the previous version but not with the 6.1.5126.
Did you test step by step what i describe?
You can also modifiy manualy the registry from the base.
I am sure you will be suprise...
Would you like to reply?
Login or Register to post your comment.