I'll second GNU/Linux's suggestion.
Just FYI, no matter what distro you run, or which version of WINE you install, after installation you must run 'winecfg'. You can generally find this in /usr/bin (sometimes /usr/sbin, depending on the version of WINE and how your distro's package manager is set up to install it); it's an executable script, so simply clicking on it should run it. Or, as stated, simply run it from the terminal.
If you don't run it, the 'hidden' /.wine directory will not be created (I believe in Ubuntu it's found at /home/,wine. It's located at /root/.wine in my Puppies, since Pup always runs as root.) And as GNU/Linux states, it's also needed for downloading & installing 'Gecko' & 'Mono', which are required for WINE to work properly.
And if the /.wine directory isn't created, you won't be able to install or run anything, as it is from here that the 'emulated' Windows applications are run, in a simulated 'real-time' Windows environment.
Edited by Mike_Walsh, 20 August 2016 - 12:59 PM.
Distros:- Multiple 'Puppies'..... and Anti-X 16.1
My Puppy BLOG ~~~ My Puppy PACKAGES
Compaq Presario SR1916UK; Athlon64 X2 3800+, 3 GB RAM, WD 500GB Caviar 'Blue', 32GB Kingspec PATA SSD, Seagate 'Expansion' 3 TB USB 3.0 external HDD, ATI Radeon Xpress 200 graphics, Dell 15.1" pNp monitor (1024 x 768), TP-Link PCI-e USB 3.0 card, Belkin PCI USB 2.0 4-port card, self-powered 7-port USB 2.0 hub
Dell Inspiron 1100; 2.6 GHz P4, 1.5 GB DDR1, 64GB KingSpec IDE SSD, Intel 'Extreme' graphics, 1 TB Seagate 'Expansion' external storage, HP HD2300 webcam.