Great job everyone. We had a great go around with this contest and lot of participants. With over 2000 posts during the contest period there were plenty of questions and answers about Windows 8. For more stats, Bob put together a stats web app where you can compare contest stats and even personalize it! Go give it a check out for more details on the contest as a whole.
All winners will receive an email from the Stack Exchange team with instructions on how to get your prize. (Note: the T-Shirt emails have already been sent, so if you achieved Level 1 and didn’t get the email, check you spam folders and make sure you weren’t suspended for cheating.)
October 26th is coming fast. Are you ready for Windows 8? Super User is!
We’re having a party and you’re invited. Ask and answer questions to complete the challenge levels, and complete different tasks like editing, voting, and blogging to win the eight tile challenges. Each level you beat and each tile you finish enters you for sweet prizes, including the grand prize of a Microsoft Surface RT! more »
Windows 8 is out for MSDN account holders (including students with MSDN-AA access)! And it’s set to release on October 26th. With that there are bound to be tons of questions in regards to Windows 8. This post is meant to be a collection awesome questions/answers found on Super User that are tagged Windows 8. This is what we’ve got so far:
The New Modern Apps
As time goes on, and more questions/answers come along, we’ll update this help all you Super Users out there with the new Windows 8.
Yesterday, after two of my family members in turns tried to fix a video card driver installation error for 2 – 3 hours, they couldn’t get it to work. Trying it over and over, each time it stopped the progress bar somewhere before the middle, to finally throw up this screen:
Yeah, this is exactly the moment where you would freak and pull out your hair; especially to plan on finishing the day with some casual gaming. So, their next step was to fire up the device manager in an attempt to manually update the drivers by feeding the devices with the directory full of INF files. But apparently, the devices weren’t so hungry:
If you haven’t been living under a rock for the last few months, you probably know all of the following:
- Windows 8 is the name of Microsoft’s new version of the operating system.
- Windows 8 sports Metro, an attempt to introduce touch interactions as a first class citizen in Windows without crippling mouse and keyboard interaction.
- Windows 8 is different. If you’re stuck in 2001 with Windows XP, or GNOME 2 and/or KDE 3, obviously you also aren’t going to like Windows 8. Also I have a few dancing bunnies for you to look at.
This is the most important thing to realize: Windows 8 is different. Different in huge, important ways: It marks the transition to a brave new world in ways similar to what Windows 95 did. To do so, it abandons UI conventions that have been around us since then. The Start button? Gone. The Start menu? Gone. Pressing Start to shut down the computer? No more. Menus (and ribbons)? A thing of the past. Titlebars? Oh, please.
I have been using the Windows 8 Developer Preview for about 5 months or so and in order to install it on my PC, I had to create a rather small partition on my primary hard drive consisting of only about 16GB. Thankfully, a clean install of Windows 8 will fit comfortably within that space and still provide enough room for some basic utilities and drivers (of course, I do have other secondary partitions that I use for installing applications).
During the installation of a particular application, the free disk space on the partition dropped to about 28MB. One of the users over in the Root Access chat room suggested that I try filling the disk until it is completely full and then blogging about what happens – hence this article. I was a bit reluctant at first since I didn’t want the hassle of reinstalling anything if it became corrupted somehow, but since I have up to date backups of everything, I decided to proceed anyway.
Super Users often find ourselves installing operating systems. Whether you run your own computer shop, manage an army of thousands of corporate workstations, or are just the tech-savvy friend everyone you know calls for help, you’ve probably had to install various flavors of Windows over and over again. Most of us have also spent a fair amount of time installing different Linux distros, running data recovery disks, and using various live CDs.
The problem that presents itself is managing all of the required disks. There are at least 6 common flavors of Windows 7 alone (Home Premium, Professional, and Ultimate for both x86 and x64, plus Enterprise for you corporate types). Add in various distros of Linux and you start to see why some computer techs carry around whole folders of CDs.
I’ve been aware of Pendrive Linux for a while, which lets you setup a flash drive with multiboot Linux software, and can add a single Windows installation. But what if you wanted to have a single flash drive with all versions of Windows 7, as well as all the standard Linux boot disks? It took some work, but I decided to do this and the final result is impressive.
Ask some Windows users why they aren’t using Linux and chances are you will hear “because [program] doesn’t have a Linux version.” Although cross-platform software is popping up all over the place, there are still a number of applications that are restricted to a single platform – and for a lot of software, that platform is Microsoft Windows.
However, all is not lost. Although Linux has its own executable format and set of system libraries, a tool exists that will allows us to run a good portion of our Windows applications directly in Linux. This tool is of course, Wine. Wine initially began as a small project that was designed to run simple 16-bit Windows applications. As time went on, the target shifted to 32-bit applications and the long and hard process of rewriting Windows’ user-mode libraries began.
This week’s Question of the Week comes from MaxMaxie, and is about command line usage in Linux:
I’ve found myself using the
-vflag for lots of applications less and less (especially for trivial stuff like
cp). However, when I did and I was, say, unzipping a large file, it would take longer than when I didn’t use the
-vflag. I assume this is because the terminal has to process the text and I’m filling up whatever buffer it might have. But my question is, does this make the application actually run slower or does it complete in the same amount of time and what I’m seeing is the terminal trying to catch up?
According to Matt Jenkins, it does indeed. His explanation of why is an interesting read, but the question remains: exactly how much does it slow things down? I decided to find out – read on to see just how much of a difference verbose flags can make.
Have you ever been connecting to a new wireless network and seen the following pop-up balloon?
Whenever I connect to a WiFi network which requires in-browser authentication, such as university networks and hotel access points, Windows somehow magically knows. Windows also knows when your internet connection isn’t working, and can differentiate between having local LAN access, no network access at all, or full internet access. But how?
This week’s question of the week is one I myself asked about this very topic. I guessed that there must be some online Microsoft site that Windows is checking to determine the state of the connection, but I wanted proof, not just speculation.