I was wondering if any fur here has tried either the Developer Preview, Consumer Preview, or any other leaked or officially released beta version of Microsoft Windows 8 on any of their computers or in a virtual machine. For the last several days I have been messing around with the 32-bit Consumer Preview beta-version of Windows 8 on a brand new netbook PC, and I have become curious as to whether or not anyone else here has taken the plunge into the brave new world that is the Metro user-interface as well.
While I bear no official allegiance to any particular computer software vendor's ecosystem or any particular software community (well, with maybe the exception of the Commodore 64 programming community that's still out there), Microsoft has a small office facility only a few miles from my house so I attend 4 local Microsoft-centric user groups that have their monthly meetings either based at or around that office due to the sheer convenience of them. So to say that Microsoft has some influence over what technologies that I have some exposure to is an understatement to say the least. While I have been hearing about the wonders of Windows 8 being extolled by the Microsofties ever since the Developer Preview of it was released last September, I never got around to trying out a version of it for myself until last week. What sparked me to finally try it was because I received a brand new Acer Aspire one D255E-13695 netbook last week, and since the netbook is brand new I have no work-critical functions invested in it yet. As a result, there was nothing for me to disrupt if I formatted it and threw Windows 8 on there. That of course is when I learned my very first lesson about Windows 8:
The first rule of Windows 8: Don't try installing it on a netbook, even a brand new netbook, unless you want to subject yourself to workarounds and trouble.When I was deciding on a candidate machine to test Windows 8 on, the minimum system requirements for the beta-OS that I was primarily focusing on were its minimum processor and RAM requirements, which for the 32-bit version is a 1GHz processor and 1GB of RAM respectively. My shiny new Acer Aspire one had a 1.6GHz Intel Atom N455 and 1GB of DDR3 RAM, so I figured that it would work out alright. However, there was one minimum system requirement for Windows 8 that I didn't pay any attention to and I should have-- apparently Windows 8 has a minimum screen resolution requirement of 1024x768 pixels. Windows 8 will still install and the desktop side of the operating system will still run if you have a screen resolution that is less than that, but unless you have a screen resolution of 1024x768 or larger
you won't be able to get any Metro apps to run. Period. My Acer Aspire one, like most modern netbooks, has a widescreen format screen with a native resolution of 1024x
600-pixels, which meant that when I tried to launch some Metro apps I quickly realized that they weren't going to load and that I was out of luck.
Now, for those of you paying attention to the development of Windows 8, it is a cobbled-together Frankenstein of an operating system with a split-personality disorder. There are two "sides" to it, a desktop side, which is essentially the Windows 7 desktop environment with the "Start" button removed for your inconvenience, and a brand new "Metro" environment side, which is where all of the new work and development in the OS has really taken place. The operating system does as much as it can to force Metro into your face as much as possible (such as replacing the "Start Menu" that has been a staple of Windows since Windows 95 with a new Metro "Start Screen"), so if you find yourself suddenly unable to launch Metro apps like I did it is a real deal-breaker. So just like that all of a sudden instead of having Windows 8 on my machine all I had available to me was "Windows 7 Extremely Annoying Start Menu-less Edition" because my widescreen-format screen was 168-pixels too short in the vertical dimension. Not good. Not good at all.
Feeling extremely irate by this, I quickly joined the Microsoft TechNet Windows 8 discussion forums and started
a new topic in their "Windows 8 Hardware Compatibility" section to complain about how wrong it was that they chose an unreasonable standard-ratio screen resolution as a minimum requirement when nearly every laptop, netbook, and desktop monitor has been using widescreen ratios for the last several years. In my opinion, it made much more sense to use the 1024x600 widescreen format as the minimum resolution, as it wouldn't be *that* different from their current minimum and it wouldn't leave millions of netbook owners, whose machines can otherwise run Windows 8 just fine, out in the cold. After all, Microsoft wanted to hear my feedback about Windows 8, so I gave it to them. The first reply that I received from my post was unfortunately an unhelpful remark from some Microsoft "Partner MVP" about how analysts are predicting the death of the netbook to the hands of tablets, and therefore Microsoft shouldn't care about my predicament. (For those of you who are wondering, yes, netbook sales are dropping each year, and many media outlets are
very quick to report that statistic with glee. What they don't bother to tell you however, and I looked up sales figures to be sure, is that there were still over 4-million netbooks sold
in the U.S. alone last year. So are netbook sales declining from year to year? Yes. But there are
still a lot of netbooks being sold each year, and too many of them for Microsoft to be ignoring them with Windows 8 in my opinion!)
In any case, later posts made to the thread by more helpful people revealed that there is a change that you can make to the Windows registry on many netbooks that will allow them to use screen-resolution down scaling to project a higher resolution image onto a smaller resolution-capable screen. This registry change allowed me to project a 1024x768 image on my Acer Aspire one's 1024x600-native resolution screen. And while that made the picture "squished" a bit in the vertical and made the picture much fuzzier due to the scaling, the screen-image was still usable and it does allow me to run the Metro apps on my netbook. So while it is definitely not an ideal solution due to the loss of image sharpness, through the use of down scaling you can indeed run Windows 8's new Metro apps on a netbook PC. If you find yourself in a similar predicament when trying to run Windows 8 on your own netbook,
I have posted the instructions on how to enable down scaling at the bottom of my Microsoft TechNet Windows 8 forum thread.The next major issue that I immediately had with Windows 8 while first playing around with it was the networking settings. As I mentioned above, Windows 8 is an operating system with a split personality, and this split cuts straight through the middle of more than just radically differing graphical user-interface paradigms. On one hand, it seems like Microsoft wants to cram absolutely everything that they can into the Metro-side of things to force you into using Metro as much as possible, but on the other hand it seems like either they haven't had enough time to cram everything into the Metro side of things yet or they realize that they really can't which forces you to have to do some things on the Metro-side of the operating system and some things on the Windows Desktop side. Unfortunately, much to Windows 8's detriment, this also applies to settings that once were all conveniently found within the Windows Control Panel. My case in point is for the wi-fi and other networking settings. You see, Windows 8 tries to be really smart, probably too smart in fact, and automatically assumes that you want to use Wi-Fi and that you will receive all of your networking settings automatically, from your IP address all the way down to your DNS servers' IP addresses, automatically through DHCP. This probably would work fine for most consumers out there, but I am not like most consumers. I have an entire evil warfleet of over 90 sinister Solaris, IRIX, OpenVMS, and Linux servers and workstations sprawled around my house (including filling two tall server racks in my basement). My current networking setup involves a full-blown Cisco router running Cisco IOS, a 40-port Cisco Catalyst Switch, and various Cisco and Linksys Wireless Access Points, Wireless Bridges, and switches arrayed throughout the house. Across this runs one large statically-addressed network, controlled by a "hosts" file located on each machine, in the 10.0.0.x IP address space. That means that under normal everyday operating situations
I am not running DHCP. Windows 8's clever little default behavior of searching for a wi-fi network running DHCP naturally then doesn't find my network, and thus Windows 8 decides that it can't connect to any networks.
In previous versions of Windows this wasn't a very big issue. To fix it, you would just click on the Windows "Start" menu, mouse over to "Settings," and then click on "Control Panel." Every setting that you needed to change to setup your Windows PC to use a statically addressed network was right there. In Windows 8, however, there is a Metro-based "More Settings" app. In that app there is a section for Wi-Fi settings. When you select it you get two settings listed that you can change: Turn the "Airplane Mode" on or off, and turn the "Wi-fi Device" on or off. That's it. And there are no other sections dealing with networking in this settings Metro app either. That truly is it. Luckily, the old faithful Windows Control Panel desktop application is still around. Since troubleshooting my network connection issue was one of the first things that I tasked myself with doing in Windows 8, I wasn't very familiar with the Metro side of things yet and as a result I finally found the old desktop Control Panel application by doing a search for "Control Panel" in the desktop-mode version of Windows Explorer. That is a ridiculous way to go about doing things I know, but what can I say, I was frustrated and desperate! Since then I have discovered that there is a much easier way to find the old desktop-mode Control Panel through Metro:
1. Go to the Metro "Start" Screen.
2. Right click your mouse on a blank area of the "Start" screen to have its "command bar" float up from the bottom. Choose the option, "All apps". (In my case it was the only option.)
3. Scroll through the list of apps to your right until you see a heading that says "Windows System." Click on the "Control Panel" app listed underneath "Windows System."
In the Control Panel you can still set all of your more advanced Networking settings for both wired and wireless networks pretty much how you are used to doing. This isn't where the story quite ends however-- as I said, some of your PC's settings and even some administrative functions such as adding new users have been pushed over to the Metro "More Settings" app. In some cases it seems, when a setting has been moved to the Metro settings app it has also been
removed from the traditional desktop-mode Control Panel, so you often find yourself having to check both places to be able to do what you want. Lame. Seriously, I haven't had
this much fun since I found myself often switching between the Gnome-based "Java Desktop System (JDS)" and the UNIX "Common Desktop Environment (CDE)" on my Solaris 10 machines because while I liked the JDS much better over all, the CDE had the better system administration tools. But at least in that case both of those rival desktops used the same graphical user-interface paradigm, i.e. "WIMP" or "Window, Icon, Menu, Pointer." In Windows 8 the situation is even more disjointing because the Windows desktop/Metro GUI paradigms are different.
Speaking of different graphical user-interface paradigms, getting used to Windows Metro itself was also the cause for a lot of pain, suffering, frustration, and confusion. Let me tell you this now:
If you are using a mouse with Metro instead of your fingers on a touchscreen, *and* you are familiar with how previous versions of Windows worked, you are going to find yourself absolutely hating Metro... at first. When you are using a mouse, Metro behaves completely differently from any other Windows technology that you have used before. If you are a long-time Windows user and you are trying out Windows 8 for the first time,
for the first one or 2 hours you will be completely lost and wandering around the operating system aimlessly like a chicken with its head cut off. Little of the Metro side of things will be intuitive to you, and even less will be obvious. The loss of the "Start" menu that has been a fixture since the days of Windows 95 will leave you screaming out loud "why?", and make you wonder why you ever decided to subject yourself to this torture to begin with. I have been reading a lot of IT Professionals' reactions to trying out Windows 8, and I remember reading how one IT Pro couldn't even figure out how to
shut down his PC in Windows 8 Metro until after 30-minutes of searching! I myself had a miserable time finding the Control Panel as I mentioned above, and I didn't learn how to "properly" close a Metro app until day 2 of my own testing! Sure, I did find "a" way to close Metro apps early on (by revealing the "previously used app list" by holding my mouse in a certain unmarked corner of the screen, right clicking on the running app that I wanted, and then selecting "close"), but the easier and more "correct" way that I only discovered later is to move your mouse-pointer to the top of the screen, wait until the mouse-pointer transforms into a little hand-shape, click the left-mouse button, and then drag downwards to close the app. All of this probably makes real sense when using your fingers on a touch screen, but it makes little to no sense at all when you are stuck using a mouse.
That brings me to my final thoughts on Windows 8 up until this point. Windows 8 would be fine if you could set it to primarily use the Metro touch screen interface when you are running it on a touch screen tablet or touch screen monitor, and set it to primarily use the Windows desktop environment when you are running it on a netbook, laptop, or desktop.
But it doesn't let you do that. When you are in the desktop environment and you want to select a new desktop-mode program to run, instead of having a Start menu right there you are forcibly kicked out into the new Metro-based "Start Screen," only to get kicked back into the desktop environment again once you have clicked on the desktop-mode program's Metro tile. You also completely lose the old Start menu's ability to organize lists of program icons into various folders. When you install a desktop software application onto Windows 8 it ends up throwing all of its newly-installed icons into the Metro "All apps" screen, including the icons for the uninstallers for that program and other such garbage icons, which you then have to go and spend time to sort and clean-up. And while I find myself getting better and more familiar with navigating through the new Metro interface all of the time, I definitely don't see any real benefit to being forced into it from the desktop mode every time I want to select another program to run. In other words, it is not helping my productivity or ease-of-use at all. Instead, only the amount that it is
hurting my productivity is only slightly lessening over time, and that is only because I am getting better and more familiar with using it so the amount that it is holding me back and inconveniencing me is dropping. So I am actually getting better at using Windows 8
despite Metro,
not because of it. With that said, I do have to say that some of the Metro apps that I have played around with, especially the "Weather" app, are some of the most beautiful-looking things that I have ever seen. But at the end of the day computers are made for doing work on, and while running a smart-phone-esque full-screen one-app-at-a-time user-interface on a tablet makes sense, also being forced to run it on a powerful quad-or-more-core desktop machine, no matter how pretty those full-screen apps might be, just seems like a horrible waste of good computing resources and productivity to me.
In any case, I am going to try to tough it out and keep Windows 8 Consumer Preview running on my netbook for as long as I can stomach it, or until it expires, which ever comes first. As a computer programmer, I have come up with some great ideas for some Windows 8 Metro apps that I would like to try and develop, and since Microsoft has also made available a beta-version of Visual Studio 2012 for Windows 8 Consumer Preview that allows you to create your own Metro apps, I am going to try to get some apps written and placed into the Windows app store before the final release of Windows 8 launches. Luckily, the Consumer Preview of Windows 8 doesn't expire until
January 15th, 2013, so I have some time to accomplish this yet!

So now I ask all of you: Have any of you tried any of the pre-release versions of Windows 8 yet? What was your own personal experience like with it? Did you experience any hardware incompatibilities or any problems getting used to using it? What do you think of Windows 8 overall? Do you think that Microsoft has the right idea with where they are taking the Windows operating system, or do you think that Windows 8 and Metro will be their biggest blunder since
Microsoft Bob? I would be extremely interested to hear eveyones' thoughts, experiences, and impressions!
(With that said, I would like to institute one rule with replying to this thread if I can. It is well known that there are some furry Linux enthusiasts around that patrol this section of Furtopia. Don't get me wrong-- there is absolutely nothing wrong with both running and enjoying Linux-- I have Pardus, Scientific Linux 5 and 6, Ubuntu "Lucid Lynx" LTS, Puppy Linux, KNOPPIX, Wolvix, and Damn Small Linux running on various machines of my own. But what I don't want to see in this thread is any form of "Anything from Microsucks blows because it's from Microsucks, and anything from the FOSS community rulez because Richard Stallman said so" kind of trolling. If you want to have a civilized discussion over the new tablet-centric features being introduced these days in the many competing GUI's, such as Microsoft Metro, Ubuntu Unity, Gnome 3, and Mac OSX Lion, and how their various strengths and weaknesses differ from one another that is more than fine. In fact I actively encourage that sort of discussion here. The effects of Windows 8 taking advantage of UEFI's "Secure Boot" feature (which could potentially limit duel-booting into a second OS) could also be a valid point of discussion. But if all you want to contribute is something of negligible discussion value along the lines of "of course it sucks because it's from Microsoft! Linux rulez!" please take your thoughts somewhere else and start your own thread if you have to. I don't want a FOSS vs. Microsoft holy war to dominate this discussion. I just want to discuss what's new and different in Windows 8, if anyone has tried it for themselves, and what everyone thinks about it. So please stay on topic and thank you for your understanding!)