UPDATE
Just speaking to the two devs in question now and they both said they are running Win XP 2002 SP3. This could well be an issue to. Damn that's old.
All, I'm not sure the best way to describe this problem, but here goes.
Most of the devs in my team are using Windows boxes. A couple of experiencing the following problem...
When running commands from the command prompt nothing happens. By nothing I mean, the command prompt returns immediately, no error, no nothing. This does not happen every time but on average you need to run the same command about 5 times before it actually 'sticks' and the command executes.
This is compounded by the fact that if the command being executed in turn also calls other commands, these may fail too.
The net effect of this is a very frustrating time trying to run things like cucumber tests from the command line.
Specifically, these guys have been trying to run cucumber tests but I witnessed this when trying to add a new box via Vagrant this morning. Both these things are Ruby based so maybe there is something there.
Anyway, my questions to you are:
With the above information in mind, have you experienced the windows command line not executing commands randomly and if so, how have you fixed it?
Are there any logs I can look at to see why the command line commands may be failing?
cmd.exe
.