Kloetzl, thanks. I don't know whether it's forward slash or backward slash (one website says forward slash), so I will try both. Thanks again. Jack
Command name namd2 is not being accepted
I am using a Windows 10 platform to perform simulation of ubiquitin. In the MS-DOS command window, I type ./namd2 ubq_wb_eq.conf > ubq_wb_eq.log & but I keep getting the error message invalid command name "./namd2". The weird thing is that just a week ago, this command was working. Does anyone have any suggestions?
• 5,071 views
•
link
1 answer
./namd2 is the unix way of saying “look for namd2 in the current directory”. Windows does that anyway so just namd2 ubq_… should be sufficient. (In technical terms: . is part of the PATH on windows by default.)
Also, an windows it should be .\namd2, amyrite?
• 1 views
•
link
• 1 views
•
link
Log in to answer this question.
Obvious thing to check is are you in the directory where the namd2 executable is present? If not you would need to provide the full path like
c:\program files\some_dir\namd2 ubq_wb_eq.conf > ubq_wb_eq.log &in your command.Genomax2, thank you -- I did not know about putting the whole path directory. Jack
Are you using
cygwin(unix like environment for windows) or are you using a virtual machine?Hello, Genomax2. No, I'm not using any Linux like environment for Windows. I'm using command line on actual Windows, which accounts for the fact that some of the Linux commands are giving errors.