It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 10 years ago.
It won't start the virtual device. Why can't things just work??
I'd rather not reinstall everything outside Program Files directory and I don't know and don't care what Eclipse is.
Its because of the spaces in "Program Files (x86)".
From the eclipse menu bar do this
Go to Window > Preferences
Click Android
At the "SDK Location bar" change it from C:\Program Files (x86)\Android\android-sdk to C:\Progra~2\Android\android-sdk
It should work perfectly now. (However if you're using a 32bit system then you'd have to change it to 'Progra~1' not 2.)
My guess is that you installed the SDK in a path with a space in it. Try uninstalling and installing to C:\Android or something.
Source: http://ideanotion.net/android-sdk-invalid-command-line-parameter-files-error/
Assuming Windows install:
Create an AVD with the Android SDK and AVD Manager, remember what AVD name you used.
Start Command Prompt, go to the SDK Tools folder (e.g. C:\Program Files (x86)\Android\android-sdk\tools.
Type emulator.exe -avd "avd_name, (e.g. emulator.exe -avd AVD_1.5).
Related
Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed last month.
Improve this question
I want to get the windows system directory(i,e C:\Windows\System32) where windows native files(like cmd.exe, xcopy.exe, reg.exe, etc..) are available to prevent Process Hijacking in the batch file by adding an absolute path of .exe in batch file.
I can get this C:\Windows\System32 by using the below command,
%systemroot%\System32\
But I'm afraid that what if all windows don't have their native files always in the "System32".
So my questions are,
Can windows' default system directory will vary depending on windows versions or something?
Can we modify the default system directory ourselves?
These native files(.exe) are always been into the "System32"?
Can windows' default system directory will vary depending on windows versions or something?
Yes. The 32 suffix was only added to the System folder when 64bit versions of Windows started existing. Previously it was just C:\Windows\System
Can we modify the default system directory ourselves?
The name of the folder is hardcoded into the operating system and cannot be changed
These native files(.exe) are always been into the "System32"?
Taking the cmd.exe file as an example, it has had the same location since Windows XP, but in Windows 95/98 it used to be located directly in C:\Windows directory
Extra note inspired by comment from cup
64-bit versions of Windows has a SysWOW64 folder in C:\Windows which (confusingly enough) contains 32bit utilities to support execution of 32-bit applications on a 64-bit system.
But these are not the commands you're referring to, which will always be found as explained above.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
The community reviewed whether to reopen this question last year and left it closed:
Original close reason(s) were not resolved
Improve this question
What is the name of the exe file for windows terminal preview,
its path and command to open it?
Like for windows terminal it is wt.exe
Check in AppData\Local\Microsoft\WindowsApps
Look for wt.exe or the "WindowsTerminalPreview" directory for the preview edition.
A more generic path is:
%LocalAppData%\Microsoft\WindowsApps\wt.exe
Open start menu and open Windows Terminal.
Click ctrl + alt + delete to open tasks manager.
Look for Windows Terminal task and unfold it.
Find Windows Terminal, click your right mouse button, click open file location. It will navigate WindowsTerminal.exe automatically.
That's it.
On my computer WindowsTerminal is installed at C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.9.1942.0_x64__8wekyb3d8bbwe. Note that WindowsApps may be hidden and restricted, you should make sure it is visible and accessable.
Try using where command in cmd. Like this where wt.exe, you should get full path (mine C:\Users\{user-name}\AppData\Local\Microsoft\WindowsApps\wt.exe
Usually I'd recommend that this question be moved to Super User, since it isn't programming related. However, it's too old for that at this point.
wt.exe is what's known as an "Execution Alias", a "fake exe" method to open a Windows Store app (a.k.a. Metro, a.k.a. Universal, a.k.a. Modern, or whatever it's called today).
Both "Windows Terminal" and "Windows Terminal Preview" use the same wt.exe execution alias, since Preview is just a pre-release of the final version.
If you have both versions installed, you'll need to choose which one runs with wt.exe by going to "Manage App Execution Aliases" in the settings (just search for it in the Start menu). Switch off the one you don't want to be using; switch on the one you do.
I was able to execute wt.exe previously.
Now "%LocalAppData%\Microsoft\WindowsApps\wt.exe" returns the following. The system cannot find the file XXXX\Microsoft\WindowsApps\wt.exe.
The wt.exe is in this directory as expected.
However, when I search for "Windows Terminal" and open it from the start menu it opens.
I believe this behavior is due to a change in my companies security GPO governing the execution of scripts. I am not certain of this yet.
I do not yet have more details but I am digging to find out more.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 2 years ago.
Improve this question
Trying to install git version 2.27.0 and installation stuck on 100%( full green bar).
I tried all the possible way like changing the install location path and with all the drive i have.but nothing worked.
When I asked my computer to restart and then canceling that....it takes me to the finish window but it worthless I could not run the git bash terminal.while trying to open git bash a file formed,named mintty.exe.stackdump
Please somebody help me to fix the issue....
System: windows7 32bit
Logging: This appears to be an INNO setup. Try to log it with:
Git-2.27.0-32-bit.exe /LOG
Then find the log file in the TEMP folder (sort it by modify time until you find the log file at the top).
Updated: "Short" list of things to check for a failing setup.exe
I have a generic check list / ideas list for failing setups here. Check the "Generic Tricks" section for some suggestions. Here are some of the points as recommendations:
Re-download the setup and virus check it. Quick malware scan of problem box.
Verify disk space and check for disk errors on problem box.
Temporarily disable your anti-virus during installation.
Now try to log your setup as described above - on the problem box - and check for errors.
Further alternatives:
Try to create a new admin account on problem box and install with a freshly downloaded and verified installer.
Install on a virtual to make sure the install can succeed in your environment.
First, as a workaround, you can at least simply uncompress PortableGit-2.27.0-64-bit.7z.exe, anywhere you want, and set your PATH:
set PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\
set GH=C:\path\to\git
set PATH=%GH%\bin;%GH%\usr\bin;%GH%\mingw64\bin;%PATH%
The other test you can do is simply to check if the issue persists with previous version of Git for Windows.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I had a directory 'c:\windows.old\ leftover from upgrading Windows 8 to 8.1. I wanted to delete the directory and could kill most of it using Windows Explorer shift+delete (delete no undelete).
However there were a few tricks left in there from good old MSFT themselves. For some odd reason they decided that having really long names (RLNs) for the cache entries was a Good Idea. Most Windows utilities (Del/Dir/PowerShell get-children) just die a stinking death when they see a file with a RLN.
So off on the hunt for something to put them out of their too-long misery.
I found this PowerShell add-on module at http://poshcode.org/2488. Joel's ps module adds several commands to ps, including get-longpath and remove-longpath.
Download the zip from his site and unzip it to C:\windows\system32\WindowsPowerShell\1.0\modules. You should now have an Experimental.IO folder in the ps modules directory.
Crank up PowerShell ISE (windows key+x, select Windows
PowerShell ISE) or open the PowerShell command windows (Windows key+x,
Windows PowerShell).
Navigate to the directory with the offending RLN files (e.g. 'c:\Windows.old\users{{username}}\Appdata\Local\Microsoft\Windows Store\Cache\0'. Your ps prompt should now be:
Now on to more productive work.
PS C:\Windows.old\users{{username}}\AppData\Local\Microsoft\Windows Store\Cache\0>
Enter this command: Get-LongPath | Remove-LongPath
This will pipe the RLN filenames to Remove-LongPath. PowerShell just returns to the command prompt, but you verify there are no long files by entering Get-Longpath (or its alias glp) and Dir to see there are no long any RLN files in the directory.
As a last note, if you want to save yourself about an hour, refer to this SO post to ask Windows to delete the Windows.old folder on your behalf from the Disk Cleanup utility.
1) Put Linux on a thumb drive. Ubuntu will be fine.
2) Boot to the thumb drive.
3) Delete the files in question from the UI or from the command line:
rm /path/to/file/that/you're/deleting/42915u02u51...24521.doc
Honestly deleting it wth a Linux thumb drive is far simpler and more reliable than hoping Windows utilities and workarounds won't muck it up.
Is is possible to install a gadget to a user's desktop somehow? I believe I need to copy all the files to a the user's gadget folder, e.g.
C:\Users\curusername\AppData\Local\Microsoft\Windows Sidebar\Gadgets\test.gadget
But copying the files here doesn't run the gadget. How can I register/activate it?
Is it enough to shell execute test.gadget?
Late answer, I know, but the other answer is talking about Windows Sideshow Gadgets, and your question is related to Windows Desktop Gadgets.
It's possible to run the gadget on Windows 7 without shell executing the archive, you need to use the IDesktopGadget interface method RunGadget. Call RunGadget on a folder containing your gadget's files and it will appear on the user's desktop.
A description of the RunGadget method and sample code for C++ is offered here:
http://msdn.microsoft.com/en-us/library/dd378390(VS.85).aspx
If you're using .NET, refer to a previous question I asked for how to implement the IDesktopGadget interface:
Stack Overflow - C#: Referencing a windows shell interface
For backwards compatibility (Vista), I would recommend you fall back to the shell execute method.
The following MSDN Article covers this:
http://msdn.microsoft.com/en-us/library/cc982277(VS.85).aspx