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.
Related
I use a 64-bit Windows 10 machine. I was trying to install Anaconda by following the steps mentioned on this DataCamp page. I was expecting a .exe file, instead, I got a .pkg file. I don't know how to open the .pkg file. I could see .exe files in Anaconda's archive. Not sure which one to download. Any help?
I had the same issue. You have to choose windows option cos it does not automatically detect you system. The default selected is for mac OS and thus it will download the pkg version. Its after downloading that I found out and had to redownload it.
Its really a poor web design, since the options don't really appear as options (they appear as saying anaconda is available in all these platforms) and are visibly in another section.
By default the anaconda website will set the option to MAC OS(.pkg is MAC extension) change and download by windows it works!
Anaconda often downloads the pkg version for Macs. If using windows you might want the .exe version. Make sure you click Windows on the main page to download that installer. You can also go here: https://repo.anaconda.com/archive/
Find the .exe version for windows - download it and install it.
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.
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?
I'm using InstallJammer to create installers for my product. The source and binaries are located on SourceForge, but when I downloaded the latest (1.2.15) tar.gz file I found no executables. I tried running the .tcl files, but without success.
As it happens, I remembered I had an InstallJammer installer (.exe) that I had downloaded months ago for the same version (1.2.15). Once I ran that, InstallJammer was installed on my Windows machine and I had an "InstallJammer.exe" file in my Program Files directory that launched the GUI. Afterwards, I searched the web for this InstallJammer installer, but was unable to find it anywhere.
My issue is solved for now, but I'm posting in case anyone else has run into this. So my official question for the benefit of all is this: how do you get InstallJammer installed on a Windows machine using the sourceforge tar.gz file? Or, alternatively, where do you find the .exe installer for InstallJammer?
Thanks
As you've probably read on the InstallJammer website, active development of InstallJammer has been discontinued. The source files are still present, but the Windows installer for version 1.2.15 is no longer available on the Sourceforge site. However there still are some download sites that have the 1.2.15 installer,
e.g. this one
Also on the old InstallJammer site there still are 2 snapshot versions with Windows executable. I haven't tried them yet, as I am still using the 1.2.15 version myself.
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).