butos Posted January 14, 2006 Share Posted January 14, 2006 Hi everyone,i was wondering if there's a way to change order nlite applies hotfix selected in hotfix page. I tried choosing them in desired order but it seems that nlite applies then in random order.Any ideas?Thanx,Filippo Link to comment Share on other sites More sharing options...
Camarade_Tux Posted January 14, 2006 Share Posted January 14, 2006 AFAIK, no.But it's not needed since nLite will check it is not overwriting a most up-to-date file with an older one. Link to comment Share on other sites More sharing options...
butos Posted January 14, 2006 Author Share Posted January 14, 2006 I think it would be usefull to be able to choose which update run for first... For example: i would run ryanvm update pack and LATER other updates, the same way Siginet integrator works.Filippo Link to comment Share on other sites More sharing options...
boggen Posted January 14, 2006 Share Posted January 14, 2006 file version, date created, date modified, can be decieving. even on microsoft www for slipstreaming they recommend appling hotfixs in order they came out, and NOT by KB number, file version, date created, date modified.wonder if nlite has built in database of hotfixs vs filename? Link to comment Share on other sites More sharing options...
nuhi Posted January 14, 2006 Share Posted January 14, 2006 nLite integrates Update packs (RVM and others) first then regular hotfixes (which you may choose to be installed by build date by clicking on that Column header) then it integrates XPize last. Link to comment Share on other sites More sharing options...
butos Posted January 15, 2006 Author Share Posted January 15, 2006 And what about addons such as ryanvm or custom made? Is there a policy about them? I would suggest executing first ryanvm addon and then other ones, so that newer files (or even newer hotfixes) are kept.But it seems to me that now, nlite just runs then randomly.Filippo Link to comment Share on other sites More sharing options...
nuhi Posted January 15, 2006 Share Posted January 15, 2006 Do you seriously think it does it randomly It goes how they are sorted on the Hotfix page.With only the rule I stated in last post, first CAB packs then Hotfixes then Xpize.Meaning when you click BuildDate it will integrate first oldest CAB pack then others as they are sorted...same goes for Hotfixes.But I do agree that moving individual hotfixes manually would be a good addition, like in GuiRunOnce tabpage. Gonna add that. Link to comment Share on other sites More sharing options...
3 of 7 Posted February 27, 2006 Share Posted February 27, 2006 AFAIK, no.But it's not needed since nLite will check it is not overwriting a most up-to-date file with an older one.I have a question about this, when it says" do you want to keep this file?" I'm assuming it means the newer one correct? Link to comment Share on other sites More sharing options...
nuhi Posted February 27, 2006 Share Posted February 27, 2006 Yes. Link to comment Share on other sites More sharing options...
johnnygoodface Posted November 25, 2006 Share Posted November 25, 2006 (edited) Hmmm... And what about those Microsoft Hotfixes that:1) Don't have any BuildDate, like KB923789, KB886903 (Screenshot 1)2) A wrong BuildDate format, like KB917734 (Screenshot 2)How will nLite react?Would this explain why nLite is asking me many times if I want to overwrite or not an already existing fix (dll) thruout the hotfix implementation?Regards,Johnny Edited November 25, 2006 by johnnygoodface Link to comment Share on other sites More sharing options...
-.-PhanTom-.- Posted November 25, 2006 Share Posted November 25, 2006 What I do is to sort them by "KB" number..so the ones with the lowest number appear first - they should also be the oldest ones, right?The date field is f***ed - inconsistent Link to comment Share on other sites More sharing options...
johnnygoodface Posted November 25, 2006 Share Posted November 25, 2006 Hi,Unfortunatly no ... You can't allways rely on KB ordering because Microsoft has a tendency of screwing the order up themselves I think I'll keep using the BuildDate and simply remove the faulty ones and let the Windows Update site take care of those missing ones afterworth...Cheers Link to comment Share on other sites More sharing options...
Camarade_Tux Posted November 25, 2006 Share Posted November 25, 2006 Updated file versions. Link to comment Share on other sites More sharing options...
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