This can be usefull for troubleshouting later problems with replacing some files with doublicated names in DRIVER.CAB too. But if you rename other files from the packages you should try to rename all entries refferencing this file in an appropriate installation INF. I even advise you to rename INF according to the driver type: MYMODEM.INF, MYSOUND.INF, MYVIDEO.INF, etc. What happens if there are files with the same names? You can rename them. Place all your extracted driver files into DRIVERCAB (for later updates it's better to place drivers in separate subfolders like DRIVECAB\Modem, DRIVECAB\Sound, DRIVECAB\Video, etc.). Or you can use Universal Extractor.įor finding right files among all extracted binaries and getting rid of some garbage I recommend using simple and great tool - Driver Compressor (but you have to extract cabbed files again after using it).Ĭreate folder HFEXPERT in HFSLIP directory, go inside this folder and create the folder DRIVERCAB. ![]() Most drivers that come in one EXE file could be extracted with archievers like WinRar. (Simple method of integrating SATA/RAID drivers could be found here.)Īll driver binaries should be in extracted format as if they are used for installation through OEM folder structure or like in Bashrat the Sneaky's drivers packs. ![]() There is a very simple method of integrating your drivers into Windows source with HFSLIP.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |