I have a neo4j folder (all of it) in /home/me/Downloads, which is bad. I want to move it to /usr/lib where I'll think it is, but I was wondering if moving the folder after it's installed (and working properly) will cause any of those weird, explainable errors from things installed automatically in bashrc or whatnot. I just unzipped it to Downloads and it's there and working
I also want to rename it. Can this be done safely?
Thank you
You can move it, as long as you stop neo4j running before you move.
You can also rename the folder, no problem.
Related
I was running some code on SAS that was generating data and for some reason, it froze. I quit the program and relaunched SAS, but noticed it didn't clear the memory. It's a lot of data, about 20 gigs, so losing that much space is more than I'm willing to give up. Normally, when I close and relaunch SAS it clears that memory, but this time it didn't, even after restarting the desktop (it's a Windows PC on Windows 10). Any suggestions or ideas?
Sometimes runaway processes that do not end gracefully will leave their temporary data in your WORK directory. Here are two ways to do it:
Use cleanwork.exe
Run the following in an elevated command prompt, where C: is the drive SAS is installed and your SAS WORK directory resides.
"C:\Program Files\SASHome\SASFoundation\9.4\cleanwork.exe" /v C:
This will search your entire volume for temporary SAS files and it could take a while. If you want to only clean your WORK directory and make it run faster, you can find it in sas9.cfg file. For example:
"C:\Program Files\SASHome\SASFoundation\9.4\cleanwork.exe" /d "%TEMP%\SAS Temporary Files"
Documentation
Delete it manually from WORK
To get to your WORK directory:
Open SAS
Type the following code:
%put %sysfunc(getoption(work));
Check your log. You'll see something like this:
C:\Path\_TD_<numbers and letters>\<id>
Go to the directory that the _TD is in.
Delete all files/folders in this directory that start with:
#TD
_TD
SAS_util
NOTE: If you are using Enterprise Guide, you can delete everything in the "EGTEMP" folder. If you're having issues deleting temporary files in it, check out Unlocker. It's a bit oldschool but still works on Windows 10! Great little tool.
I have a large desktop application with 178 project in it.
I switched the domain on my PC and did a get from TFS to a different root path but most of the references are now broken.
They have a yellow warning next to them and no path.
The problem seems to be with both Nuget packages and system references. Strangely it seems to be intermittent, some package references and some system references are okay. The Dot Net Framework I am using is still in the same location
I have tried a package reinstall but that didn't work.
Has anyone come across this problem before who knows of any easy way to fix this that doesn’t involve deleting and adding them all again? Which does not work anyway.
Thanks in advance
Total red herring.
Turned out to be, I had not included the .nuget folder.
I'm having some kind of problem with my project that me and my friend is working on. When I try to open the project that I've been working on it gives me an error message saying that "one or more lines were too long and have been truncated" and thus I can't see my code or GUI. When my friend opens the project on his computer (The project is on dropbox so it's the same file) there's no problem at all. I've googled but couldn't find anything. I just did a repair of RAD Studio but no luck. We have 2 forms and a unit that we use, the unit and the mainform isn't working for me but the second form is no problem.
Thanks!
Make a copy of your project directory.
Search your harddisk for XXXX.pas and XXXX.dfm
Hopefully there will be some temperary files that match - like "mylostform.dfm.~1307~" . copy the newest to your project directory, and rename them to "mylostform.dfm" and "mylostform.pas".
Kind regards,
Geir Bratlie
From the comments, you have Dropbox, and the Restore functionality is available, but using it would cost you a week's worth of work.
If I was in that situation, here's what I would do:
Copy the current file to somewhere else (My Documents, for example).
Use Dropbox Restore to get the old version that works.
Make a copy of this, because you're going to be modifying it
Ensure that you can open it in the IDE.
Use Beyond Compare to open the two files side-by-side. (If you don't have this, you really should!)
If they're completely different from each other, you have a serious problem. If not, you'll see the changes you've made. Start copying changes one at a time, and after each change, save and try to open it in the IDE.
At some point, you won't be able to. That's where your problem lies. Now you can fix it!
I have pointed/opened dart folder, so. that, where Darteditors own program-files are, in Darteditors File window and begin to create one web program there. Clever? Is'nt it?:)
I wanted to test one of my own programs there, for using pub packages.
Now editor seems stucked, nothing works, can open FEEDBACK window only for 2 seconds and i can close Editor only with Windows Operations control.
Might there be some kind of recursion going?
New install is quick, but finding the course of this would be useful..
So how can I clean this DartEditors Files-directory without starting DartEditor?
And should I avoid putting my own program files in dart folder?
I have latest Darteditor, 19425, in Windows7. Thanks!
You should avoid putting any of your own code into the Editor's directory; that directory is managed by our auto-update process and you could potentially loose that code.
To get your Editor back to a happy state, you'll have to delete its workspace metadata folder. On windows, that should be in c:\Users\yourname\DartEditor. Just delete it (or rename it) and the Editor should be able to start back up again.
Going forward, you'll want to locate your code outside the Editor's directory; we default to c:\Users\username\dart. Hope this helps!
After many months of postponing it, this week, I finally started using a new Windows 7 Professional PC for actual development (which is 90% still done in Delphi 7 with some of these programs still using the Borland IDAPI to access Paradox files). The previous development pc was still an XP-one.
Every thing works except for one thing: somehow the settings of the IDAPI and BdeAdmin configuration files are messed up or they are read/written in different locations. To be more precise, it looks like two configuration files are active.
It must have something to do with rights or settings being read/written in the wrong folder or registry setting, but after searching for it for a couple of hours, I give up.
Anyone had any problems with this, before ? And if so, hopefully, has any one solved this problem ?
Thx for any thoughts/solutions ...
My guess is it has something to do with the fact that Vista and Windows 7 don't allow programs to change files under the C:\Program Files folder. They create a copy of those changed files in a virtual store, the process is known as virtualization. The copies end up in the hidden appdata folder of the user account and can be found in the Local\VirtualStore\Program Files folder. The structure in that folder reflects the one in the actual Program Files folder.
Programs that access their files in the Program Files folder using a "hardcoded" path, will always get the original - unchanged - file contents.
Solution: running the apps in a virtual XP system or upgrading the apps is probably your best bet.
You could try to run the apps elevated. That is: right click them and choose Run as Administrator. Please note that it isn't enough to be logged in as an administrator. Even administrators run all processes unelevated by default. Instead of right-clicking, you can also create a shortcut and set the Run as administrator for the shortcut - the checkbox for this is on the compatibility tab of the properties dialog. No guarantees though that this will alleviate the problem.
Since IIRC D7 setup allows you to configure paths in multiple ways, maybe simply do a reinstall outside "program files"?
Afaik this solves several vista/w7 problems.