MDGx, on Dec 5 2005, 10:55 PM, said:
WinME hotfixes contain CAT files which are digital signatures [MDSum or MD5Sum probably ??] of newly installed files, and because of that System Restore always updates its database accordingly.
The INF file usually contain a postsetup command to run [generic example]:
after respective CAT file was copied to %windir%\INF\CATALOG folder.
I have never tried to find out how CAT files are created by MS.
Hope this helps.
I supposed something like that. In fact, I never seen any use of .CAT files in Windows 98 SE, is this different in Windows Me?
I just looked at some Q310695 fix and the sequence (in the form of .SED file lines) is:
QFEREG.INF contains lines:
CopyFiles = Register.cat
RunPostSetupCommands = UnprotectMe
1="CAT File Source","",1
WSE22366.cat = 1
Register.Cat = 17,CATALOG; Windir\inf\catalog directory
;The following command will register the CAT file. Add another entry
;just like it if there are more than one, specifying the next CAT.
So at first tha .CAT file is copied to
So at first the catalog file is copied to Windir\inf\catalog directory and then it is registered.
And after this, 310695UP.INF copies file to three locations: (unneeded lines removd)
WMeUpd.Copy.VMM32 = 22
So this is the official way.
But what is the meaning of "Options" and "Install" directories?
Can we do the same in the servicepack? For all official updates/hotfixes for sure, the procedure would be:
1. To copy all .CAT files from MS fixes
2. To register them by SUCATREG
3. To copy all files as it is done at present, maybe also into "Options" and "Install" directories.
The question - how it is with unofficial, patched files? They never have correct .CAT file. I suppose this file has to be signed by Microsoft to be valid.
If it is possible to switch SFP off, copy any updated files (with no .CAT files), reboot and switch SFP on, what are these .CAT files meaningful at all?
I also suppose that could be possible to switch off the SFP by the installator, or not?
I don't have Windows ME experience but I believe there should be a way how to handle everything by the Service Pack installator.