I'm trying to install IIS on the Windows 2003 Datacenter x64 edition AMI on aws, however, it complains that it can't find the installation media "C:\WINDOWS\INSTALLATION\i386\amd64"? What am I doing wrong?
I'm answering my own question, because I couldn't find an answer anywhere else.. the hint as in the path it was asking for "C:\WINDOWS\INSTALLATION\i386\amd64" .. if you look at the directory on the drive, it lists 2 folders under "C:\WINDOWS\INSTALLATION\": "i386" and "amd64". The trick seems to be to change the path to the real folder.. in my case (installing 64bit), it was to make the path: "C:\WINDOWS\INSTALLATION\amd64". Note, it may ask for this path 2-3 times.. but it worked.
Related
I'm struggling to understand how exactly WSL works.
The training that I'm doing requires nvm so I can manage my node versions in my project, located in my hard drive that is running with Windows.
So, in order to use nvm I need WSL, but I cannot comprehend where it is located. As far as I understood (and I'm pretty sure that I'm wrong) the WSL that I installed is like a Linux VM, completely independent from my Windows, and I operate it through the Ubuntu Terminal that came with WSL. If that's the case, how can nvm in WSL be useful if my project is in my Windows directory and the WSL controls node versions from my Linux VM?
How do I make nvm useful for my project running from my C:\ drive and how does WSL work with nvm in my Windows?
Thank you!
A few options, but each has advantages and disadvantages:
If your Node/JavaScript files are on your Windows C:\ drive, then you do have the ability to access that from WSL. Windows paths are automatically mounted and accessible in WSL via /mnt/c, /mnt/d, etc.
So if you have your JS source in, for example:
C:\Users\<myusername>\Documents\Projects\JS_class\project1\
Then that would be accessible under Ubuntu in WSL via:
/mnt/Users/<myusername>/Documents/Projects/JS_class/project1/
The disadvantage here is performance, as mentioned in this question.
Alternatively, you can store your project files inside WSL. You can access the WSL path from Windows by using \\wsl$\Ubuntu\home\<yourusername>\ (or similar). You can use this to copy from your existing Windows drive to your WSL distribution.
Advantage: Faster. Disadvantage: Unknown -- You seem to want the files to be in Windows, but I'm not sure why.
Or you can use WSL1 for most Node/JS tasks. See the previously mentioned answer for details on how to convert.
Advantage: Speed
Disadvantage: WSL1 hasn't been updated in a while, and is started to run into some compatibility issues. It's still popular enough and stable enough at the moment for me to continue to recommend it, though.
There's also a Windows version of nvm as well as a replacement project that the repo there mentions. I cannot personally speak for the quality of it, but it does have 23k stars on Github. Note that it is not affiliated with the original (Linux-based) nvm project.
I was trying to install Node.js node-v14.15.1-x64 on PC with Windows 10 Pro 64-bit OS, but then I found that the problem appears with any .exe and .msi
If I'm trying to run installer with/without administrator, I got only endless blue loading circle icon on my screen without any error report or process in Task manager:
Hanged icon with cursor arrow does not disappears, even if I will wait for a hour, to stop it, I've to restart computer
I've followed Stein Åsmul answer, which I'm forced keep unmarked, because it seems like nothing helps yet:
I've re-download installation media but now I see that this happens happens to all installers.
I've tried turn off Windows Defender Firewall and Security Antivirus.
with C:\WINDOWS\system32>sfc /scannow Windows Resource Protection did not find any integrity violations.
HKEY_CLASSES_ROOT/.exe value is exefile, and exefile folder value is Application, I have tried to change it with "%1"%*
in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion in ProgrmFilesDir value is C:\Program Files and in ProgramFiles Dir (x86) is C:\Program Files (x86)
With attempt to C:\WINDOWS\system32>assoc .exe=exefile something also went wrong here, because OS freeze, and I was forced to reboot
C:\WINDOWS\system32>msiexec.exe /i :\Users\User\Desktop\New folder (1)\pycharm-community-2020.2.3.exe /L*v C:\Your.log opens Windows Installers, which describes Display, Install, Restart and Logging Options, but I'm not sure, how to use it, to find out with this issue
Solution:
After removing AVScanner.ini form C:\ directory problem disappeared and installation works fine
Also I have to note, that I will mark answer by Stein Åsmul because I found it useful in similar possible situation, even if it was not solution in this particular case
Any advice, guide or example would be helpful
Overall: Do you have a screenshot? That almost sounds like a Windows Smartscreen issue?
Here are some generic setup.exe debugging suggestions:
Shortened setup.exe problem list
Long setup.exe problem list.
Specific Suggestions: 1) Re-download the installation media first of all. 2) Then reboot and disable anti-virus scanners and try to install. 3) You should also enable logging and look at the log for clues. 4) Try to install as a different admin users. 5) Finally test on a virtual or another machine to verify the integrity of the setup file.
Quick Logging:
msiexec.exe /i C:\Path\Your.msi /L*v C:\Your.log
General WiX and setup links (section: "Generic Tricks? - Consumer issues")
Smartscreen issues
Node.js - Cannot Install it is showing an error because of .msi
recently I started to use WSL & vcpkg, but it has some problems when mixing windows + linux development.
It seems like that installing Linux packages or Windows packages with vcpkg, mutually damage the vcpkg configuration and then vcpkg roughly says: "the package you want to install doesn't exist". (I know for sure that it exist)
If it matters, the project is located in the windows "world" so the WSL directing to it with /mnt/c/Users//workspace/proj1
but it really doesn't matter.
Does Anyone already encountered this problem?
Am I doing something wrong?
Is there a better way to develop a cross-platform project?
Thanks
So I post it to help anyone who have doubts about it:
Don't mix WSL project with windows project because it will force you to work on the windows filesystem from WSL. (WSL can work on the windows filesystem with /mnt/)
anyway, It will both corrupt the vcpkg and the overall compile times will be horribly slow from linux filesystem (usually ext4) to the windows filesystem (NTFS).
this is my original post in the Github:
https://github.com/microsoft/vcpkg/issues/13948#issuecomment-706625438
I'm trying to download the Debian Neo4j version from a Window 7 machine. I'm not managing to find the URL in order to download the package/file . I have installed the GOW software for some linux commands.
Any assistance would be appreciated.
Update
I found this link - https://neo4j.com/download/other-releases/ . Know I need to figure out what is the best file to download in order to install it on an Ubuntu Machine
You've got two options :
If you've got access to the package repository (from your Ubuntu machine), follow the information in https://neo4j.com/docs/operations-manual/current/installation/linux/debian/ to install it as a package. That's the best option which also provides start/stop scripts, a user that runs Neo4j (neo4j) and also allows for easier upgrades.
If you can not reach the internet from your Ubuntu machine (as could be deduced from the way you're trying to do it, the zip (or tar.gz for Linux) download is the way to go. You can find that at http://info.neo4j.com/download-thanks.html?edition=community&release=3.2.3&flavour=unix
Hope this helps.
Regards,
Tom
I'm setting up an Ubuntu guest under Windows using VirtualBox for a colleague to provide him with a Linux-based development environment for a node.js application.
This colleague of mine can't or doesn't want to SSH into the VM and work in emacs or vim; he's a Sublime Text guy. So I have set up the project tree in a VirtualBox shared folder so he can access it from Windows (to edit) and the Linux VM (to build/test).
Unfortunately, npm install fails with file system errors. The problem seems to be extremely long path names resulting from deeply nested node_modules dependencies. I'm guessing we're hitting a Windows limit on filename length. The npm install works just fine in a regular (non-shared) directory in the VM.
Does anyone have ideas about how to deal with this problem? One idea I had was to somehow alias or link $MY_PROJECT/node_modules to another, non-shared location, but I can't figure out how to do that.
Update: I'm going to try this hack: https://www.virtualbox.org/ticket/11976.
Update 2: Ended up using samba, which is probably what I should have done in the first place.
One option is to use one of the multiple ways for sublime to edit remote files over ssh, covered in some detail here
How to use Sublime over SSH
Another is try using the native windows version of node and have your colleague develop locally directly under windows.