CatRoot catmast/mastmast

  • Thread starter Thread starter Roadhawk
  • Start date Start date
R

Roadhawk

Hello,

I've got problems with the files catmast.cbd and hashmast.cbd. I know what
they are used for and i know that you never should delete them or your
(driver) signing will be messed up.

But... the fact is that some software (doesn't matter which one) has
replaced those files with crappy ones, not originating from my system.

Is there a tool or Windows API for regerating the cbd-files?
SetupCopyOEMInf from the Setup API is not good enough...

Operating system: Windows 2000, this means that CatRoot2-map is not
implemented yet and ebd.log doesn't exist either yet...

Best regards.
Roadhawk
 
Hi Roadhawk.

I sent you those two files via email [both very small] from a Windows 2000
Server install of mine. I know you are using Pro, but they are probably the
same. Rename the existing files and give them a try if you want. --- Steve
 
Thanks, but the cbd-files are bound to the local system. For example, when
you install a videodriver, windows will generate a oem??.inf file in the
inf-directory. When the driver is signed, it will create a corresponding
oem??.cat-file in the catroot folder. At the end of the sequence windows
will modify the catroot.cbd with this updated information.

So these files are not exchangable. In my case (for example) a videodriver
could get named oem1.inf and on another computer named oem2.inf, so it's not
possible to copy the cbd-files from a computer to another computer.

Thanks for your support anyuway :-)


Steven L Umbach said:
Hi Roadhawk.

I sent you those two files via email [both very small] from a Windows 2000
Server install of mine. I know you are using Pro, but they are probably the
same. Rename the existing files and give them a try if you want. --- Steve


Roadhawk said:
Hello,

I've got problems with the files catmast.cbd and hashmast.cbd. I know what
they are used for and i know that you never should delete them or your
(driver) signing will be messed up.

But... the fact is that some software (doesn't matter which one) has
replaced those files with crappy ones, not originating from my system.

Is there a tool or Windows API for regerating the cbd-files?
SetupCopyOEMInf from the Setup API is not good enough...

Operating system: Windows 2000, this means that CatRoot2-map is not
implemented yet and ebd.log doesn't exist either yet...

Best regards.
Roadhawk
Click to expand...
Click to expand...
 
Back
Top