I have .inf file with a brother .sys file in the same folder.
they are drivers for plug and play device via usb .
When i try double click / right click the .inf file and pressing "Install"
It does not work, but if i try from "Device Manager" and choose to install manually with a given path - it installs OK.
How can i handle this, to make the inf file installable.. ?
Thanks.
there is a perl script tool called "chkinf"
http://msdn.microsoft.com/en-us/library/windows/hardware/ff543461(v=vs.85).aspx
to verify the correctness of inf files.
in addition in order to install inf properly it should have [defaultinstall] statement in it.
this is not the correct way to install a device driver.
the right way is to use a tool like, DPInst.exe
Guide is at
http://blogs.technet.com/b/svengruenitz/archive/2008/07/02/driver-installation-and-updating-made-easy-dpinst-exe.aspx
enjoy.
Related
How do I import/export my custom preferences for Spyder? e.g. if I am installing it on a new machine and would like to import my color/interpreter/keymapping defaults from my original installation.
(Spyder maintainer here) Sorry, there's no way to import/export our Preferences right now.
However, you can look for a directory called .spyder{-py3}/config (Windows, macOS) or ~/.config/spyder{-py3}/config (Linux) in your home or Users directory. That directory contains a file called spyder.ini, which has all user preferences. You should be able to copy/paste that file among computers without problems (although we haven't tested that).
If you find any trouble with that method, you can reset your preferences by opening a system terminal (cmd.exe, Terminal.app or xterm) and running there
spyder --reset
On my computer I have a file
c:\users\xxx.spyder-py3\config\spyder.ini
This file is used by both, Spyder 4.2.5 in Anaconda base environment and by Spyder 5 in a separate venv.
I'm trying to write simple firewall that can drop packet by filter. For this purpose i'm use WinDivert. I'm load WinDivert.dll and add WinDivert.lib and WinDivert32.sys to project folder. Then i try use WinDivertOpen() to install WinDivertDriver. The result is always negative.
What do I do wrong and how can I successfully install the driver? Code example.
I solved this problem in the following way.
1) In Project->Properties->Linker->Input->Additional Dependencies set path to WinDivert.lib .
2) Moved to root folder files WinDivert.dll and WinDivert32.sys.
3) Include windivert.h to my project.
4) Set my PC in TESTSIGNING Boot Configuration (Use for this Windows Driver Kit 7.1.0.).
5) Restart PC.
If these steps did not help you should build WinDivert from sources with Windows Driver Kit 7.1.0. and Visual Studio 12 or higher as it is described here
How do I determine if an application is built by Electron or not?
Could I always find specific file or binary on Electron apps?
Please give me some advice, thanks.
There are a few "non-futureproof" ways to check if an app was built on Electron and they vary depending of the OS.
You will need to go in your application folder (for example Applications for macOS, Program Files for Windows or /usr/share for Linux...
Here are some examples of the files/directory you may find in your application folder:
Linux / Win32
These two OS have basically the same structure, so it's pretty easy to check what you want
locales/
resources/
blink_image_resources_200_percent.pak
chrome_100_percent.pak
chrome_200_percent.pak
content_resources_200_percent.pak
content_shell.pak
icudtl.dat
vkswiftshader.dll
vkswiftshader_icd.json
There are also some files like
libffmpeg.so / ffmpeg.dll
libnode.so / node.dll
depending of the OS you're on.
macOS
It's a bit more complicated here. You might need to check the Info.plist file to see if there is any reference to Electron.
As unseen_damage said, you can also check in [app folder]/Contents/Resources if there is an app.asar as .asar files are specifically created for Electron.
Anyway, all those files may see their names changes someday, so don't consider them as a reliable way to check if "any" app is built on Electron, it's more of a manual way to check it.
MacOs
To find all Electron apps by finding the .asar file on your mac, use this.
open Terminal
run this command
find /Applications -name '*.asar' -print
MAC:
open a terminal type cd /Applications, then, change directory (cd) into the name of the application you want to check. For example, if it is iTunes, you would do the following /Applications/iTunes.app/Contents/Resources. If you see an app.asar file, or something similar with the .asar suffix, it is most likely an Electron App.
Windows:
Open up the program files directory of the application you are wondering about, and check the file folder for any file with .asar suffix. This can be done via the search, terminal, etc.
Bottom line- Electron apps, when packaged, are bundled into an asar file, and you can search for this file extension to see if the program was built with electron.
Documentation- http://electron.atom.io/docs/tutorial/application-packaging/
macOS
You can also run the following terminal command:
find /Applications -name "*Electron Framework*" | cut -d/ -f3 | sort -u | cut -d. -f1
This will output an alphabetized and cleaned up list of just the application names.
Source: https://talk.macpowerusers.com/t/why-the-dislike-of-electron-apps/20697/20
I want to create MAC installer and would like to know which type of installer suitable for my requirements?
My Requirements are
I have bash script which does following operation
Get Hardware ID and some details specific to the hardware
Construct XML
Generate PLIST
Download an DMG file from internet (Using curl)
Mount DMG
Launch .app inside the DMG.
Can you please suggest me whether I can go the DMG or use PackageMaker to create .PKG file?
Thanks
Bala
I am not aware of anyways to trigger a script on mounting a DMG. But here you have a solution by creating a PKG with pre-install/post install scripts.
Your bash script can be added as pre-install or post-install script of the PKG. It doesn't really matter whether you are adding it as pre/post install scripts, since your PKG is just going to execute the scripts and not doing any file copy etc.
If needed you can embed the PKG in a DMG, so that it becomes a mount disk. Also DMG can show the license files if needed.
I'm trying to create an NSIS installer that installs an inf file. The inf file is extracted from the installer to the correct place, and then I use:
nsExec::ExecToLog '"$SYSDIR\PnPutil.exe" /a "$INSTDIR\driver\xser.inf"'
However, the command does not seem to get executed at all - the install log doesn't print anything - not success nor failure. I've checked thoroughly the command line and it points to the right PnPutil path. I've also checked that it's being run with administrator privileges and it also looks correct. Replacing PnPutil.exe with a different executable in the System32 directory also seem to work without any problem. What am I missing here?
If this only happens on 64bit systems you can try to disable FS redirection around the call to nsExec::ExecToLog by using the macros in x64.nsh:
!include x64.nsh
${DisableX64FSRedirection}
nsExec::ExecToLog '"$SYSDIR\PnPutil.exe" /a "$INSTDIR\driver\xser.inf"'
${EnableX64FSRedirection}