Posts posted by mooms
-
-
15 hours ago, pennsylvaniaron said:
If I were to write the script I would have started with 1 (not 0)
I don't think it's an option, but I don't know vbs at all.
15 hours ago, pennsylvaniaron said:I'm wondering if we will be able to incorporate this somehow in our updates or take advantage of it somehow?
We'll see.
-
3 hours ago, pennsylvaniaron said:
mooms thx for the list.
Hey I didn't write this small little script (telemetry) but why would its creator have a number ((dim hideupdates (4)) that is 1 LESS than the number of updates that is being hidden. Stuff like that doesn't make sense to me. I would think the average person who edits the file for the first time (for me not my first time but it's been awhile) sees say 6 updates, they would put a "6" hide dimupdates(6) in the file. easy peasy. Just my 2 cents...
regards..
Pay attention and you will see it starts with 0 and not 1
hideupdates(0)
-
Perso j'ai cette liste:
Dim hideupdates(20) 'TO ADD 1 EDIT THE (11) AND ADD another hideupdates(#) ' https://support.microsoft.com/fr-fr/help/3150513/latest-compatibility-definition-update-for-windows hideupdates(0) = "KB3150513" ' https://support.microsoft.com/fr-fr/help/3021917/update-to-windows-7-sp1-for-performance-improvements hideupdates(1) = "KB3021917" ' https://support.microsoft.com/fr-fr/help/3068708/update-for-customer-experience-and-diagnostic-telemetry hideupdates(2) = "KB3068708" ' https://support.microsoft.com/fr-fr/help/3080149/update-for-customer-experience-and-diagnostic-telemetry hideupdates(3) = "KB3080149" ' Silverlight hideupdates(4) = "KB2512827" hideupdates(5) = "KB2526954" hideupdates(6) = "KB2617986" hideupdates(7) = "KB2636927" hideupdates(8) = "KB2668562" hideupdates(9) = "KB2977218" hideupdates(10) = "KB3056819" hideupdates(11) = "KB3080333" hideupdates(12) = "KB3106614" hideupdates(13) = "KB3126036" hideupdates(14) = "KB3162593" hideupdates(15) = "KB3182373" hideupdates(16) = "KB3193713" hideupdates(17) = "KB4013867" hideupdates(18) = "KB4017094" hideupdates(19) = "KB4023307" hideupdates(20) = "KB4481252"
-
-
J'ai testé l'intégration avec l'UL du mois de Mars en supprimant KB4489878 et en ajoutant KB4493472, aucun autre KB prioritaire demandé (à part le bout de SP1 comme d'habitude)
Testé avec WinToolkit 1.7.0.3 sur une image de Win7 x64 Pro, et réalisé sous Win7 x64 Pro, tous les KB sont bien intégrés dans l'ordre.
-
-
-
-
-
-
-
On 3/22/2019 at 9:55 PM, shhnedo said:
This number usually corresponds to the last 2 digits of the year when the version is released(at least that's MY understanding).
No, they simply skipped the version 13 (MS seems to be superstitious), so the real new version should be 15.
- 2005 is v8
- 2008 is v9
- 2010 is v10
- 2012 is v11
- 2013 is v12
- 2015/2017/2019 is v14
-
-
-
For Win7, you could explain that removing the file ei.cfg will make any iso a "multi edition" or "universal" disc.
Maybe adding the function in the app could be a good idea.
Kai Liu have developed some utilities for that: http://code.kliu.org/misc/winisoutils/
Check ei.cfg Removal Utility, it is released under BSD license and the source code is in the zip file.
-
-
-
-
-
-
-
-
-
Utilitaires [25.04.01]
in Installateurs customisés
Version 19.05.10