Cache Posted September 22, 2009 Posted September 22, 2009 Hi, Before the summer I was quite impressed with myself that I managed to create an MST to add a licence file to an install for Logicator and so could deploy it nice and easily using group policy. The only downside was that I couldn't get it to remove the licence file when it was uninstalled, but that didn't concern me to much and I would live with it. Now I'm thinking of doing the same for a couple of other packages and it's bugging me that I couldn't get this one to uninstall the licence file. Before I go through and create a couple more, can any point me in the direction of where I messed up on the original one for logicator so that I could get it to uninstall any files I add using orca? Thanks!
powdarrmonkey Posted September 22, 2009 Posted September 22, 2009 IIRC, you need to register them in the uninstall table too, or they'll get left behind (I don't have a copy of orca in front of me to help further, sorry). 1
meastaugh1 Posted September 22, 2009 Posted September 22, 2009 Also check that the attributes value of the component (to which the file belongs) does not include the permanent value (16) which would also cause the file to reside following an uninstall. 1
AngryTechnician Posted September 22, 2009 Posted September 22, 2009 Any file installed either by the .msi or an .mst should not have to be registered in the RemoveFile table unless the file is going to change after the install takes place, because any file originally installed is removed by default*. However, if it is changed, it will be left behind by the uninstall process, and that's when you need to use RemoveFile. If you take a look at your average .msi and you will see very little (if anything) in the RemoveFile table for this very reason. * Except for the reason stated by meastaugh1 above; or if it's a shared DLL, or similar, in which case more complicated logic applies. 2
Cache Posted September 23, 2009 Author Posted September 23, 2009 Thanks for the replys. In Orca I can see the RemoveFile table and my file isn't listed in here and doesn't (or shouldn't) change from when it is installed, so is the removefile table the same as the uninstall table or am I going blind? The componant doesn't have a 16 anywhere in it apart from the media (because that's all the instructions I could find which would help me do it, to create my own media) and the media last sequence is 1316 but I didn't think that would matter. Any other places I can look? Thanks.
meastaugh1 Posted September 23, 2009 Posted September 23, 2009 Thanks for the replys. The componant doesn't have a 16 anywhere in it apart from the media (because that's all the instructions I could find which would help me do it, to create my own media) and the media last sequence is 1316 but I didn't think that would matter. Thanks. To clarify, the attributes column stores multiple bits as a byte. Not sure if that's the correct term, but it stores multiple settings as a single value. Eg: Setting A=1 Setting B=2 Setting C=4 Setting D=8 So a value of 11 would mean setting A, B and D were enabled. Component Table (Windows)
Cache Posted September 23, 2009 Author Posted September 23, 2009 Hmmm, will check again when I get chance again tomorrow. This is probably why my head hurts so much and why I was so happy when it installed the file. Thanks.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now