Reputation
533
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
1 4 12
Newest
 Good Answer
Impact
~75k people reached

  • 0 posts edited
  • 0 helpful flags
  • 14 votes cast
Mar
4
awarded  Good Answer
Feb
25
awarded  Yearling
Aug
29
awarded  Nice Question
May
29
awarded  Nice Answer
May
28
awarded  Yearling
Nov
28
revised Vagrant VirtualBox VM is initializing new instead of loading the existing VM after VagrantFile change
Added my VagrantFile for fun and giggles.
Nov
28
comment Vagrant VirtualBox VM is initializing new instead of loading the existing VM after VagrantFile change
No, I only have one Vagrant machine on my computer (my first to be exact). The box I'm using is precise32 from the vagrant website. I'll update the question with a bit of information and my VagrantFile.
Nov
27
awarded  Promoter
Nov
27
awarded  Famous Question
Nov
22
asked Vagrant VirtualBox VM is initializing new instead of loading the existing VM after VagrantFile change
Oct
8
awarded  Self-Learner
Aug
12
awarded  Student
Jul
8
awarded  Notable Question
Apr
22
accepted Using robocopy and excluding multiple directories
Mar
21
awarded  Popular Question
Jan
26
awarded  Tumbleweed
Oct
1
revised Using robocopy and excluding multiple directories
improved my answer with some extra options I ended up using
Oct
1
comment Using robocopy and excluding multiple directories
Hey, thanks for the comment. I thought there was a help command, but it doesn't seem to be active in the Windows Recovery Environment (I received an error like "No command 'help' found"). Robocopy is a windows default command that replaced xcopy and is not 3rd-party.
Oct
1
answered Using robocopy and excluding multiple directories
Oct
1
revised Using robocopy and excluding multiple directories
Added note about the /create option to clarify my question