About how the reg entries are made with hfslip...

[Martin H]

@TommyP and Tomcat76

I am interessted in getting to learn how hfslip works internally, and the only thing im alittle unsure of is the reg-entry adding part, and so if you guys could please enlighten me alittle on this, then i would really appreciate it

Ok here goes...

As you know, then with update packs like RyanVM's and Xable's, then the authors of those packs makes a single inf that includes all the captured reg-entries that's been set by the updates and which is then executed at T-13.

However, with hfslip, then all the original infs from the updates are instead moved to \I386\ and executed from T-13(from RunOnceEx).

Those original inf files contains alot of stuff in them in addition to reg-entries, but hfslip then makes a header on those inf's, so that only some of the parts are executed and not all of them.

Am i getting this right so far ?

Anyway, from my understanding of the cmd syntax, then for non Win2K platforms, then the [DefaultInstall] section which hfslip has made and will run, is only defined as :

AddReg=Product.Add.Reg'

But for Win2K platforms, then the [DefaultInstall] section is instead set to :

AddReg=Product.Add.Reg,keys.add,MSI.AddReg,Actsetup.Reg,User.AddReg,Base.IE.AddReg,Common.Add.Reg,Ap
pCompatSetup.reg,NoPrompt.AddReg,RegisterActiveSetup,Reg.WPD,MTP.AutoPlayRegistration,reg.devices,Re
g
.Codecs,Fraunhofer.Reg,V9Reg.Core,V9Reg.Core.AddOnly,V9Reg.Univ,WMP.ARP,V9.RegPUI,WMPAddReg.PUI,WMPA
d
dReg.OSPUI,V9Reg.XP,WMP.SPAD,WMP.Reg.IEHard,Reg.WMDMHandler

I then have two questions...

1. Why is all that extra stuff only needed for Win2K and not for the rest.

2. For Win2K(Which i'm using), then is there a notisable speed penalty(in install time) by using the method that hfslip uses for applying those reg-entries in comparisson to if it was done like in the update packs ?

Btw, i'm not trying to suggest that hfslip should change how it works, but i'm just interessted in understanding and getting to learn these things

Also, i can see that this method is making hfslip non-language dependant

Also, do you guys know how nLite sets those reg-entries ?

Finally, then i would like to ask TommyP if i can have his permission to use the hfslip logo in my signature, since i would like to advertice for hfslip, whenever i make a post in other sections of this forum

Thank's in advance.

[tommyp]

Welcome to the board.

1. All of that extra INF stuff is used, but the header depends on whether the hotfix is a type 1 or type 2.

2. I suppose there could be a speed penalty by processing individual INF files, but I haven't compared the time it takes for installation. Maybe a 5-10 second penalty?

I'm not sure how NLITE works as it is closed source. However I seem to recall a command line tool to manipulate text files and to create new text files. The exe slips my head but there was some talk about it a few years back, maybe it was even on the nlite board.

Sure, you can use the HFLSIP logo.

[Martin H]

Hi tommyp

Thank you very much for answering my questions and for letting me use the hfslip logo in my signature

About the "maybe 5-10 seconds speed penalty", then that is of course totally neglible then

Again many thanks for your help and efforts in making hfslip so awesome; it's very much appreciated

CU, Martin.

[Tomcat76]

Up until some time ago, HFSLIP used the same headers for Type 1 and Type 2 hotfixes. I changed that for Type 1 hotfixes for Windows XP and Windows Server 2003 because they usually follow the "Product.Add.Reg" section naming; actually, the only exception I can think of right now for those OS's is the Windows Installer update. Of course every INF file in every update was tested. I wanted to do the same thing for Windows 2000 after that but never got around to it.

Edited March 13, 2008 by Tomcat76

[Martin H]

Hi Tomcat76

Thank you very much for clearing that up for me, mate

CU, Martin.