OK - but I am running this in windows command prompt. I am fairly sure I need to use the set command for VAGRANT_LOG.
When I run your suggested command I get: 'VAGRANT_LOG' is not recognised as an internal or external command, operable program or batch file.' Neil. On Tuesday, 4 November 2014 10:23:46 UTC, Alvaro Miranda Aguilera wrote: > > try > VAGRANT_LOG=debug vagrant up > > same line > > On Tue, Nov 4, 2014 at 9:39 PM, Neil Strange < > [email protected] <javascript:>> wrote: > >> I assume you mean: >> set VAGRANT_LOG=debug >> vagrant up >> >> It goes straight to the same error message in a pop up window. No debug >> trace is produced that I can see. >> >> Neil >> >> >> >> >> On Monday, 3 November 2014 22:09:17 UTC, Neil Strange wrote: >>> >>> No matter how I try I can't get Vagrant to run on my desktop (AMD >>> Opteron) under Windows 8.1. I have Vagrant 1.6.5 installed and Virtual Box >>> 4.3.18 (which runs quite fine on its own). The path looks OK too. >>> >>> When I run vagrant I get an error box popup saying Edit subject"vagrant.exe >>> has stopped working". >>> >>> I have tried uninstalling ruby, reinstalling Vagrant, etc. >>> >>> Any suggestions welcome! >>> >>> Neil. >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Vagrant" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
