Trying to build emerge(http://techbase.kde.org/Getting_Started/Build/Windows/emerge) with vc2008 expression, when I type "kdeenv.bat", the command prompt tell me that
'"C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bin\SetEnv.cmd"' is not recognized as an internal or external command,
operable program or batch file.
call "C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bin\SetEnv.cmd" /x86
After I navigate to the folder(C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bin), I find out that there is no "setenv.cmd". Where could I get this file?
PS: what I really need is the library of openldap; this post suggests emerge
Check this link.
Or you can write your own version of SetEnv.cmd and save it at C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bin\SetEnv.cmd. You can google for SetEnv.cmd script.
Related
I am unable to add an assembly into GAC. Please assist in getting it work. I ran following command in VisualStudio13 CMD
gacutil /i “<C:\Program Files\ibm\IBM DATA SERVER DRIVER>\bin\netf40_32\IBM.Data.DB2.Entity.dll”
Error Message:
Command "gacutil" is not valid.
Also, i checked there is also no gacutil.exe file on path
C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin\NETFX 4.0
Tools
But when i access the path there is no gacutil file as shown:
The issue was Windows Explorer path(C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin\NETFX 4.0 Tools\gacutil.exe) had no "gacutil.exe". Accessing the same path through cmd listed down "gacutil.exe" as present.
Thus, instead of just giving command gacutil-i to add an assembly in cache, i gave full path
C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin\NETFX 4.0Tools\gacutil.exe -i
Don't trust windows explorer. Trust command credits# Sir Conrad Frix-Comments
You can either drag-drop the .dll into c:\windows\assembly folder or check C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6 Tools\x64 for gacutil as its part of .net framework, not your IDE. Hope it helps!
After installing VB6 successfully on my Windows 8.1 64bit pc, whenever i am trying to open my .vbp project file it gives me an error can't find DAO350.dll file. Googled for every possible solution but couldn't find one.
Please help me.
[UPDATE]
[UPDATE1]: It looks something like this
The DA0350.dll must be registered.
Try this:
On the Visual Basic 6.0 CD (or whatever your installation source is), locate the Dao350.dll file, and then copy it to the directory c:\program files\common files\microsoft shared\DAO. (The Dao350.dll file is located in the \os\system folder on the Visual Basic 6.0 CD.)
To register this file, click Start, click Run, and then type or paste the following line:
Regsvr32 "c:\program files (x86)\common files\microsoft shared\DAO\Dao350.dll"
Update:
The VB6TMPL.TLB is probably not installed for your current user.
Try to run Visual Basic as administrator and/or try this: http://support.microsoft.com/kb/262976/en-us
To solve about "Can't find file DAO350.DLL"
Download DAO350.DLL file from https://www.dll-files.com/dao350.dll.html
Extract file DLL, then copy file DAO350.DLL to C:\Program Files (x86)\Microsoft Visual Studio\VB98 or any other place you install VB 6
Try open your VB 6
Work for me.
From the command prompt, execute the following commands:
cd C:\Program Files (x86)\Common Files\Microsoft Shared\DAO
regsvr32 dao350.dll
This should do it.
On the Visual Basic 6.0 CD (or whatever your installation source is), locate the Dao350.dll file, and then copy it to the directory C:\Program Files\Microsoft Visual Studio\VB98.
After applying this fix. The Visual Basic 6 can now run successfully on your Computer.
NOTE: The Dao350.dll file is located in the \os\system folder on the Visual Basic 6.0 CD.
I have a stupid question to ask. I have just started learning F#, and I am trying to compile some basics examples (such as HelloWorld.fs).
I created a simple F# file whose path is: C:\FSharp\HelloWorld.fs.
In order to compile it, I used the full path of the F# compiler as follows:
C:\FSharp>"C:\Program Files\Microsoft F#\v4.0\fsc.exe" HelloWorld.fs
It worked perfectly.
However, I do not want to keep writing the full path of the complier: C:\Program Files\Microsoft F#\v4.0\fsc.exe. I tried to add it to Windows path,but I keep getting the error fsc is not recognized as internal or external command.
How can I create a shortcut word for F# compiler so that I don't have to use the full path everytime I need to compile a program?
For those arriving here in 2019 having received F# as a component of Visual Studio 2017. The location of the F# compiler is as follows:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\CommonExtensions\Microsoft\FSharp\fsc.exe
Take careful note of the Version Type (Community in this case) and adjust yours accordingly.
You don't really need to create a shortcut for this, you just need to add the folder containing fsc.exe to your PATH variable.
When you open the command prompt, run this:
set PATH=%PATH%;"C:\Program Files\Microsoft F#\v4.0\"
or, if you're using a 64-bit version of Windows:
set PATH=%PATH%;"C:\Program Files (x86)\Microsoft F#\v4.0\"
The most recent version of fsc.exe can be found in these locations :
"C:\Program Files (x86)\Microsoft SDKs\F#\3.1\Framework\v4.0" // as of Aug 2014
"C:\Program Files (x86)\Microsoft SDKs\F#\3.0\Framework\v4.0" // 2013
I tried setting it to my path, but unfortunately it did not work. Tried logging off/restarting etc. I believe it is because of security measures in place on my work computer.
For other people having similar issues, I found that setting the alias not only worked but was more preferable over other methods.
set-alias fsi "C:\Program Files (x86)\Microsoft SDKs\F#\3.1\Framework\v4.0\fsi.exe"
set-alias fsc "C:\Program Files (x86)\Microsoft SDKs\F#\3.1\Framework\v4.0\fsc.exe"
Now the commands don't have the annoying .exe file extension.
Helpful in getting setup was this article on creating persistent aliasing for powershell.
http://www.powershellpro.com/powershell-tutorial-introduction/tutorial-powershell-aliases/
I can confirm that adding the directory to your PATH variable should do the trick (works on my machine!) Note that you may need to restart any opened command line (or, just to make sure, the system) until the change is taken into account if you change the PATH variable in system properties.
You could also create a bat file with something like:
echo off
"C:\Program Files (x86)\Microsoft F#\v4.0\fsc.exe" %*
And then make sure the bat file is somewhere in your PATH. But the bat file can have a different name (say fsharpc.bat), in case there is some name clash between the standard name fsc and something else on your system...
I've looked in numerous threads here and on Google and cannot find a solution.
I've installed the latest version of Java JDK (1.6.0_26) on my 64-bit Windows 7. I've added the file path "C:\Program Files (x86)\Java\jdk1.6.0_26" to JAVA_HOME, and added "C:\Program Files (x86)\Java\jdk1.6.0_26\bin" to the CLASSPATH and PATH variables. I've restarted my machine. But, I when I go to to run javac -version from the command line, I receive the error
'javac' is not recognized as an internal or external command, operable program or batch file.
Please let me know what I should do! I'm attempting to use Appcelerator's Titanium but it requires a valid path for javac. Thanks!
For reference, here is my PATH variable.
C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x8
6)\Common Files\Microsoft Shared\Windows Live;C:\Windows\system32;C:\Windows;C:\
Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Fil
es\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\Progra
m Files (x86)\Windows Live\Shared;C:\Program Files (x86)\Common Files\Roxio Shar
ed\DLLShared\;C:\Program Files (x86)\Common Files\Roxio Shared\OEM\DLLShared\;C:
\Program Files (x86)\Common Files\Roxio Shared\OEM\DLLShared\;C:\Program Files (
x86)\Common Files\Roxio Shared\OEM\12.0\DLLShared\;C:\Program Files (x86)\Roxio\
OEM\AudioCore\;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files\WIDCO
MM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\syswow64; C:\
Program Files (x86)\Java\jdk1.6.0_26\bin;
The error is just what it says. javac is not found on the path. (This issue has nothing to do with Java, rather windows cannot find the unqualified executable in the current path or search "PATH" paths.)
Locate the javac file manually. Verify it can be run with the found path.
Ensure the path is put in PATH environment variable correctly (it must be separated from other entries with a semi-colon (;)). The CLASSPATH is not relevant here. Depending on how PATH is set, it may require restarting the windows shell (e.g. log out and log back in). Verify the new PATH is correct with echo %PATH% from a console.
Run javac and verify it is executed.
Happy coding.
I was facing the same problem, I set the path in command line:
set path = "c:/...."
but it was not recognized as path, than I checked my Windows type (x64) and Java type (x64). Then I set the path manually in system variables in the properties of My computer and re-opened the cmd prompt, it worked.
Hi I am running following command from my post build event:
C:\Program Files\Microsoft SDKs\Windows\v7.0A\bin\mt.exe -manifest "$(ProjectDir)$(TargetName).exe.manifest" -updateresource:"$(TargetDir)$(TargetName).exe;#1"
It is failing with Exited with code 9009... I don't understand why this happens; any suggestions?
Try adding quotes around the mt.exe path, e.g.:
"C:\Program Files\Microsoft SDKs\Windows\v7.0A\bin\mt.exe"
Also, make sure that path is valid.
Hope this helps. I've been beating my head against code 9009 all day and a full quoted path seem to make it work.
Exit code 9009 is a file not found error. The spaces that exist in your path to the post build command cause errors in a command prompt unless you include quotes around the entire path and executable name. Essentially, in your post-build command, it is trying to execute C:\Program with the arguments:
Files\Microsoft
SDKs\Windows\v7.0A\bin\mt.exe
-manifest "$(ProjectDir)$(TargetName).exe.manifest"
-updateresource:"$(TargetDir)$(TargetName).exe;#1"
Since obviously you don't have a file called Program residing in your root directory, this entire command fails. Encapsulating the path and executable in quotes will cause the entire expression to be evaluated as a single command, so everything should work fine if you change the post-build command to:
"C:\Program Files\Microsoft SDKs\Windows\v7.0A\bin\mt.exe" -manifest "$(ProjectDir)$(TargetName).exe.manifest" -updateresource:"$(TargetDir)$(TargetName).exe;#1"
Or use for VisualStudio x86 in Windows x64
"C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\bin\mt.exe"
Here is a potential solution:
You can use the Post build event
functionality of Visual Studio to do
this typing the command above: mt.exe
-manifest app.manifest -outputresource:myapplication.exe;#1. This probably won't work and Visual
Studio will give you an error like
"...exited with code 9009...".
You have to edit the csproj file using
for example the notepad and uncomment
the XML tags related to the Target
Name="AfterBuild" (you can find them
at the end of the file usually). Then,
place the tags related to the
PostBuildEvent within the tags related
to the AfterBuild and then, reload the
project and compile. It will produce a
.exe file that needes to be execute
with Administrator permissions.
Until reading this thread, I foolishly assumed VS would know where mt.exe lives. +1 to #james
Since there's no built-in macro for the current SDK, I relied on the system envar, windowssdkdir
"%windowssdkdir%\bin\mt.exe"