RogueSpear wrote:That was my intention... to human build the .inf sections for each hotfix. Surely it wouldn't be too offensive to Microsoft to distribute a text file with custom information in it.
The program/script would simply put everything together. It seems like this would be similar to how the Integrator currently works, only down one level deeper. Needing to take into account if someone tries to include two hotfixes where one supercedes another and other such conflicts.
Hi. consider that entries for different languages will not look the same.
that means, all files' buildchecksums timestamps versions locactions and filenames CAN be readed by the original KBxxxxxx.exe.
for timestamp, we can use code2^16's way. and... we just use the original timestamp(the GMT one..), then at T-13 let codec2^16's utility do its work.
we can build this part of registry entries and other common entries in this way.
for other entries, we should use let updatepack builders submit the entries for their own languages.
and well, we should also allow for any exception.
for instance, M$'s mmc 3.0 hotfix uses zh-chs for simplified chinese resources, however the correct code for china should be zh-cn(and later releases use this one...). so i've hacked it to zh-cn. No problem.
then, notice this
241 = system32\PreInstall\WinSE\wxp_x86_0804_v1
242 = SoftwareDistribution\DataStore
244 = "Network Diagnostic"
245 = system32\Macromed\Flash
246 = system32\zh-cn
247 = l2schemas
we should indicate folder serials for fixed ones, otherwise if two packs set a same serial for different folders, things will happen. (that is why booooooggy change his wmp11 pack to intergrator... i think....)
by last, i hope that this project will come ture.
this also can offer a benifit that allows users to choose hotfixes they want(well... for example some unoffical hotfixes only avaliable in sepific languages)