How do I install and use WinPcap? - windows

I went to winpcap.org today, downloaded the installer, and installed WinPcap on my Windows 7 laptop PC. However, the folder where it was installed contains only an installation log, an executable called rpcapd.exe, and an uninstall executable. When I run rpcapd.exe a dos shell appears:
Press CTLR+C to stop the server...
and nothing happens until I press CTRL+C, which closes the window. When I create a project in Microsoft Visual Studio and include < pcap.h >, I'm told there is no such file or directory. A search of my computer yields no results. I've tried reinstalling a couple times but with no new results. What am I missing here?

Development with WinPcap requires both the driver install, as well as the developer's pack. Have you installed the developer's pack?

Related

Unable to install Plattform IO IDE

I’m constantly failing to install Platform IO IDE for Visual Studio Code or Atom. I’m working on OSX with High Sierra.
I have two users, both are Admins. The first user can install with VSC and Atom just fine. The second user always gets this error message:
PIP: Error: spawn /Volumes/Macintosh
HD/Users/micha/.platformio/penv/bin/pip ENOENT
I already tried to delete the .platformio folder and start over, without success. The error shows up for Visual Studio Code and Atom.
Any ideas?
Well, not a solution, but a suitable workaround.
I installed platformio core with homebrew, which works fine. Then I installed the IDE plugin, which seams to detect that the core is already there and does not try to instal it a second time.
I did this for Visual Studio Code.
I am on Windows, I tried to install platform-io vs extension to use exsting anaconda.
After setting platformio-ide.useBuiltinPIOCore to false and platformio-ide.customPATH to "path/to/py27", I am able to install platformio with existing python vEnv, but it ended up in an endless loop [press restart -> checking install -> please restart]
After adjusting the customPath to pointing to both pio.exe and python.exe residing directory, it works all right:
platformio-ide.customPATH: "path/to/py27;path/to/py27/Scripts"
I think you can adjust these setting to make these two users use seperate venv, so that there won't be any permission conflict or related issues.

Visual Studio Installation Error | Invalid Drive

I know there's a ton of there install error posts but I have tried EVERYTHING from editing the registry to command line parameters, I cannot get VS Community to install.
A couple of years ago I tried to install VS Community to my old E:\ drive. That drive corrupted and/or stopped working, so I got a new drive (F:) and am currently trying to install it. I would be fine with installing it on my C:\ if necessary. I'm running Windows 10 Pro 64x.
I have also tried,
Disabling all firewalls
Re-downloading the installer
Deleting the VS Folders from Local and Program Files
Literally everything I've seen here and on other forums. Oddly, the installer does not create log files in Temp either, so I'm at a loss of stuff to show.
And lastly, in apps, Visual Studio Community 2015 is listed with uninstall, however, when I go to uninstall, it also throws an error (no error code) saying:
Fatal Error while installing.
And the exact install error:
Invalid Drive
There's no error code but there is a grayed out box containing the drive path E:\
Honestly, I'm about ready to explode, I've been trying to install this nonsense for the last year. I wish installers were still the simple Windows Installer Wizard style, but of course developers have to come around and mess that up. Ironic though, the purpose of having this software is to make a app...let alone deal with one.
According to your description, the VS installation location defaults to the old invalid drive E:. This is because once a set of shared components is installed, we install all the other components to the same directory structure. When you have multiple editions installed, this saves disk space since shared files occupy the same location on disk – not to mention results in faster install times since Windows Installer doesn’t copy the same bits again.
Heath Stewart has instructions on how to find the products that also installed these shared components and remove them; after that you should be able to modify VS installation location.
Download and install http://psmsi.codeplex.com. These are general-purpose PowerShell cmdlets I created for all sorts of development and troubleshooting operations for Windows Installer-based installs. You do not need to elevate to install them, though if you pre-elevate you can install them per-machine (by default they are per-user).
Open an elevated PowerShell command prompt and run the following to discover which products have installed the key shared component:
get-msicomponentinfo '{777CBCAC-12AB-4A57-A753-4A7D23B484D3}' |
get-msiproductinfo
If you’re fine with uninstalling all the listed products (especially given that you’re probably going to install RTM next), run the following:
get-msicomponentinfo '{777CBCAC-12AB-4A57-A753-4A7D23B484D3}' |
get-msiproductinfo | uninstall-msiproduct -properties IGNOREDEPENDENCIES=ALL

Compatibility Mode error when installing Visual Studio SDK (vssdk)

Whenever I try to install the Visual Studio SDK I get the following error:
Windows Program Compatibility mode is on. Turn it off and then try Setup again.
I have checked and Compatibility mode is not turned on. From what I've read, renaming the installer to vssdk_full.exe should help. That hasn't had any impact.
I got the installer from Microsoft's website.
What do I need to do to get this to install?
Are you installing on Windows 10? If so, then I have the same problem and it seems as though the current SDK setup is checking the Windows version and 10 isn't currently supported. See https://social.technet.microsoft.com/Forums/en-US/77c61be0-1303-4040-a587-62843d321159/visual-studio-2013-sdk?forum=WinPreview2014General for more info
I have managed to get it to install on windows 10, download the sdk, it will download vssdk_full.exe, run this with /layout path which will extract the actual setup file.
Then set compatibility on the new file to win 8 and it will install just fine.
You might not need to do the/layout thing but that is what I did.
ed
I had the same problem. I downloaded .iso file with install package form the internet. Then I mounted it using PowerISO and tried to start it from virtual CD drive. It ended up in the same message as above.
I looked it up and thought that in Properties of .exe install file, it's enough to uncheck some boxes compability section. But nothing was checked.
Soon afterwards I unzipped the package to a temporary directory with PowerISO and installed Visual from there. Worked without problems.
I had this problem, I renamed the instalation file to "vssdk_full.exe" and it installed without problems.

Teechart pro v 3.0 (issues)

Sorry if i'm asking this on the wrong forum...
Hello. We use Teechart pro v.3.0 (yeah...it's old) in one of our projects here...We upgraded our pc's and so the SO in the process...we use Win 7 enterprise 32bits now.
We've installed this component in our pcs and it works fine..but not on my pc. My installation process won't complete. It gets stuck on "updating system configuration". When i check its installation folder, it seems to be ok...here's what i've tried so far:
1) Registered its .OCX files
2) Put the OCX files in the system and system32 folders (there's a .txt file that asks you to do so)
None of the above worked for me. And here's more...i can't uninstall it. It should have a Installation.log file inside its folder but there isn't one, since my installation process didn't finish...
I've got the .ocx files from my co-workers pcs but no success..i thought that uninstalling it and installing it again could work..how can i uninstall it without having to format my pc?
You can install/uninstall using regsvr32 command as I explained here. For example, to register an .ocx control use:
regsvr32 InstallPath\TeeChart7.ocx
To unregister:
regsvr32 -u InstallPath\TeeChart7.ocx

CVSNT install hangs forever in Windows XP 64-bit

I need to access some source code stored on SourceForge using CVS.
I used (many computers ago) to use WinCVS, so I downloaded it from SourceForge and installed it on this machine, which runs Windows XP 64-bit (latest SP).
However, during the second part of the install, when it tries to install CVSNT, the install asks all the usual questions, and hangs during the actual install.
I have traced the install using ProcMon, and the installer starts up, creates a temporary file in my temp directory (which is on drive E:), and then executes it.
I can't see any particular reason why the install hangs - there is no obvious loop. Both the original installer, and the temporary file create 2 threads, and one thread exits. So I guess the other thread is waiting for something which never happens.
Any idea how to proceed from here?
The issue is that the installer doesn't like the default installation path of c:\Program files (x86)\cvsnt — if you use c:\cvsnt the installer will proceed.
Update: this appears correct. If you still would like it in the default location under C:\Program Files (x86)..., use the 8.3 name (you can find it with dir /x), usually C:\PROGRA~2. As you can see in the screenshot, the last step appears correctly now. With a path with a space in it, it would hang forever.
Second part of wincvs --> cvsnt.exe get hangs with windows 7 due to incompatible, So you may try tortoiseCVS. It has the portable version and also working fine
SOLUTION FOR Windows 8 64-bit:
On Windows 8 64-bit I was unable to install CVSNT (even to c:\cvsnt), but I solved the problem by simple copy the whole CVTNT directory from my old pc.
I copied to C:\Program Files (x86)\cvsnt (exact location where wincvs expected to find cvsnt).
We had a similar problem on a machine at work (the difference being it was Windows 7 64-bit in our case). Even though the user had admin privileges, we were only able to resolve the issue by logging on directly as the admin before installing cvsnt.
Do not install the version of CVSNT that comes with WinCVS. It's an old, outdated, buggy version. Install a later release (at least 2.5.0.4).

Resources