News & Training
Route designated when installing driver
It has been a long time since this symptom existed...due to being too uncomfortable I am asking some questions. I make and add the product driver only used in the business as component, and install the remaining chipsets or graphic-related drivers directly at XPE. At this time, I have inconvenience not to automatically find the system file, pci.sys in the folder of windowssystem32drivers and the dll file existing at windowssystem32, but to manually designate one by one. Finding out through googling... From image file, windowsinflayout.inf file, [SourceDisksNames.x86] item 1 = %cdname%,%cdtagfilei%,,i386 2 = "%cd2name%","%cd2tagfilei%",,cmpnentstabletpci386 3 = "%cd2name%","%cd2tagfilei%",,cmpnentsmediactri386 4 = "%cd2name%","%cd2tagfilei%",,cmpnentsnetfxi386 100 = %spcdname%,%spcdtagfilei%,,i386,1 I tried it once as a sentence saying “When the above part is eliminated it will work.” existed...fortunately it automatically found the related file and caused to be installed. However instead a few service items were not uploaded. Obviously I added it to components...Looking at the booting state following FBA the proper service did not exist at all even in the list. For example....wireless zero configuration...this kind of thing... Eventually such a method through Google search does not seem to be an answer. When installing a driver, I will appreciate your help with how to settle such a symptom to directly find the proper file one by one with all the file being surely in dirvers folder or system32 folder.