![]() ![]() MultiKey64 worked properly and some drivers (muitikey, alladin etc) were updated automatically from the Internet. After that yellow exclamation mark disappeared. So to disable driver signature enforcement I just press F8 and choose "disable driver signature enforcement". I tried to use ReadyDriverPlus (to disable driver signature enforcement) but because of my Windows 7 Loader eXtreme that was wrong step. ![]() It always happened - before Driver Signature Enforcement Overrider 1.3b and after that. ![]() It said that "driver was successfully installed" but when I went to Device manager -> System Devices there was yellow exclamation mark - Windows cannot verify the digital signature (Code 52). Bad news is that i was unable to complete 7 step. I rebooted my PC all day long and I cant remember which steps required rebooting. Now go to MultiKey64 folder and run install.cmd. To check if the file signed now, right click on MultiKey.sys, Properties and the second tab - there should be Digital signatures.ħ. You should start it, Enable Test Mode, then Sign a system file and insert the name and full path to your MultiKey.sys from the folder MultiKey64 (see step 5). ![]() Now I downloaded Driver Signature Enforcement Overrider 1.3b which allows you to install and load unsigned drivers dynamically on your Windows 7. (due to instructions from the downloaded package)ĥ. merge 57FD245C.reg with the registry, just double click on the file and it will ask if you want to add, click yes. I install the HASP driver v5.22 in HASP4_driver directory due to instructions from the downloaded package.Ĥ. I`m not PRO, I even didn`t know about usenet ) that`s why sometimes i didn`t know what exactly I did.ġ. I made a lot of changes to my OS, downloaded different files, tried a lot of different things. I managed to start wilcom on windows 7 64-bit. So OK, there are two news, one is good, another`s bad :) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |