As it turns out, Veewee on Windows needs the PowerShell Community Extensions (PSCX) installed before you can actually export the Vagrant VirtualBox box you just created. So now the Veewee folks have corrected documentation in the form of a Github pull request.

While I am at it -- please use CMD or PowerShell when working with Veewee on Windows, rather than a Cygwin shell (Bash, etc.) You will thank me.

("In the form..." -- is this the right phrase?)

With a little Win32::FileOp magic, it is easy to whip up a simple (minded?) Windows sudo(1) substitute for Cygwin:

#!/usr/bin/env perl

# ------ pragmas

use strict;

use warnings;

use Win32::FileOp;

Win32::FileOp::ShellExecute( runas => "cmd.exe", "/k " . join(' ', @ARGV) );

Apart from how you start it, a similar approach should work for Strawberry Perl once Win32::FileOp is installed.

The underlying idea is that usually (at least for *me*) I don't care w…

The Key to Database Normalization, in one phrase:
  "If you have more than one of them, it probably needs its own table."

(Inspired by Ovid's How to Fake a Database Design and Robin Smidsrød's comment thereupon at 2013-07-25T09:46:25+00:00.)