I formatted my hard drive, and saved the full folder of my WAMP (c:\wamp).
I then reinstalled Windows and the installed the exact same WAMP server, and then just replaced all the contents in c:\wamp with my previous version.
I was hoping this would work.
But the wamp indicator just stays yellow now, and when I try to run localhost it just says,
Could not execute menu (internal error).
[Exception] Could not execute run action. The directory name is
invalid.
Can someone tell me how best to get my previous WAMP version up and running??
Thank you.
I realised when I reinstalled WAMP I had a slightly different version. When I made certain that the new WAMP version was idential the previous WAMP version, I could easily replace the new install content with all my previous content.
Related
I installed node.js to work on a discord bot with VSCode but it didn't work.
I reinstalled it but ticked the 'install chocolatey' box this time, halfway through the installation I got 3 trojan alerts from my AV, and cancelled the installation.
Since then, I have been unable to uninstall, repair or reinstall Node.JS, through the Windows 10 uninstall function or from the Node.JS .msi file.
Each time I try, I get the same error message:
"The Windows Installer Service could not be accessed. This can occur if you are running Windows in safe mode, or if the Windows Installer is not correctly installed."
I've removed all instances of Node.JS from my program files and %appdata%, I've ensure the Installer Service is running, and yet the Node.JS application still shows in the Uninstall Tool and when I try to uninstall / modify / reinstall, it shows the same error, and seems to think it's still installed on my system! Not even Node.JS commands work in my CMD!
I've got no idea how to fix this, and I don't want to use glitch anymore to write my bot, so please help- or it seem's I'll have to factory reset my PC and hope that resolves the issue.
Thanks in advance, guys.
Godspeed.
EDIT: I tried installing a newer version hoping it would overwrite old Node.JS files. Didn't work. Issue still occurring.
Do these:
Open command prompt as Administrator and run /sfc scannow. It will scan and replace corrupted files.
Restart your PC when the scan is done.
I had installed nodejs on Windows 10 Pro PC. The drive it was installed in failed and is no longer accessible. I sent it away for data recovery attempt, but it's now gone, not even connected.
I created a restore point and went to NodeJS site, downloaded the installer anew, and tried to re-install it.
The installer looks for that original installation and immediately responds: "Invalid Drive: O:" (the old location). It then immediately quits.
What can I do to re-install it? I can't uninstall it or do anything else (change, or repair). They all give the same message and quit.
Can I uninstall it from the command prompt? Or do a new installation that way?
You can try by editing the following registry value
HKEY_LOCAL_MACHINE\SOFTWARE\Node.js
There you will find an InstallPath property. Rename the drive to a valid one and then try to install node again.
Also remove Node from your PATH variable
would anybody happen to know the latest versions that work together on Windows Vista? I've been back and forth trying to get the right combination together but ng new never works for some reason or another.
(this is the older post showing what I already tried)
I'm having a bit of a problem here. I attempted to update angular/cli and I got errors telling me I need to update my version of node. I have windows vista so I'm pretty much stuck with node 5.7 and npm 3.6 until I can afford a new computer.
I tried uninstalling angular and clearing the cache and installing angular-cli#1.0.0-beta.14 and it installs. I can create a new project with it though it takes a long time to create it, and it also throws an error with node-pre-gyp. I came across an article on Github that said it's meant to be installed locally in the project and not globally. So I tried uninstalling, clearing cache and installing without -g to make it local within my project folder and it still has errors installing and I still can't serve my project.
How can I clear this all up and just start back with a clean slate of Angular2? I've looked around and everything I find leads me to the docs which are now updated to something beyond what my computer can handle.
I have windows vista so I'm pretty much stuck with node 5.7 and npm 3.6 until I can afford a new computer.
Have you considered running Linux? There are many versions with a lightweight GUI that runs well on older hardware. Ubuntu Mate is an example. It's harder to run node on Windows because of symlinks.
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.
I recently had to reinstall Windows and had several working copies checked out. I copied these to a network share, reinstalled Windows and copied the working copy folders back to the HDD.
They are now no longer recognised by TorroiseSVN as being a working copy - no overlay icons are present and the right-click menu shows SVN Checkout instead of SVN Commit and SVN Update
All _svn directories where backed up and restored.
What has gone wrong and how can I fix it without having to checkout fresh copies? (each one is nearly 1GB)
Edit 1 Current installed TortoiseSVN is 1.7.4. The working copies would have been generated by 1.6.x and upgraded to 1.7.x. I think this is why they have _svn not .svn folders.
Edit 2 These are definitely 1.7.x working copies as there is only a single _svn folder in the root and none in sub directories
First: if you're not still using VS.NET (no, not VS2002: the version before that), then do yourself a favor and do a fresh checkout. Even if each working copy is around 1GB, believe me: it's worth it!
Otherwise, if your really don't want a fresh checkout:
You reinstalled windows, which means you lost the SVN_ASP_DOT_NET_HACK environment variable. You can manually set that env variable and set it to 1. After a reboot, your working copies with the _svn folders instead of the .svn folders will be recognized by any svn client.
Does the right-click show an "upgrade local copy" option? If so, you have installed a 1.7 TortoiseSVN client, and you were on 1.6 or earlier before the machine swap. perform the upgrade and you should be ok.
The _svn instead of .svn is used when you're working with .NET Framework solution/project. Why don't you first try to use the exact same TortoiseSVN version wich you worked with before the reinstall?