Base owner priority question
jz81
October 29th, 2009
I have a layer with file system priority of 70. In this layer I have a file: C:\test.txt (which contains the following text: "layer").
In the base, I have a file: C:\test.txt (which contains the following text: "base").
When I start winword.exe (from the base, this application hasn't been virtualized) and open C:\test.txt ... I get the file which contains "layer".
However I thought because winword was running from the base, the base's files would have a "BASE OWNER" priority (i.e. 65.5).
Why is winword opening the file in the layer?
Docs somewhat unclear
If you consult the documentation, from the perspective of an application running in the base, resources in the base have a priority of 75.5
However, I agree that there appears to be ambiguity between the definition of an app running in the base, and an app running outside a layer (which has a priority of 65.5) - presumably this refers to an app running in another layer.
Ideally, the manual should clarify the precise definition of running "outside a layer" so that there is no ambiguity about whether running in the base falls into this description or not.
Try changing your layer from 70 to 75.6 and see if you then get the functionality you are expecting.
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Delving deeper ...
In delving deeper Jared Payne elaborates on layer prioritization (because the SVS white paper isn't clear):
Here are the definitions of Base owner and Base
Base owner: Priorities of bases's files from the perspective of an application running the base: 65.5
Base: Priorities of the base's files from the perspective of an application running in an application layer: 75.5
I see no ambiguity here and it makes sense to me. However the program just doesn't behave this way.
test.txt in the base should have in the scenario described priority 65.5.
Is this a bug or are the definitions in Jared's article wrong?
Version Info
For reference purposes:
Used SVS version:
SVSCMD: 2.1.3062
FSLLIB32.DLL: 2.1.3062
FSLX.SYS: 2.1.3062
OFD.DLL: 0.0.0
OFDSRV.DLL: 0.0.0
This could not be reproduced in SWV 6.1.5104.
So it works in the newest
So it works in the newest version but is broken in 2.1? Am I reading you correct?
If a forum post solves your problem please flag is as the solution
I you like an article, blog post or download vote it up
Works in newest version
Yes, it appears to work in the newest version
So is all the documentation consistent?
Is the documentation consistent and if not, can this be rectified as a priority and included in the QA testing for future releases?
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
I was actually talking to a
I was actually talking to a dev about priority the other day, for some other issue, and it does look like the numbers listed for each priority owner in our documentation is incorrect.
If a forum post solves your problem please flag is as the solution
I you like an article, blog post or download vote it up
Can you get this fixed and and post update for download?
Hi Jordan,
Can you get the source file fixed and made available for download from Connect or any other convenient location?
From experience, unless the doc authors are given a regular kick, they never update or correct stuff....;-D
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Ya there's a bug up on it and
Ya there's a bug up on it and I can easily post the correct info on Connect because we won't be revising our documentation until the next release.
If a forum post solves your problem please flag is as the solution
I you like an article, blog post or download vote it up
Would you like to reply?
Login or Register to post your comment.