
One of the big barriers to upgrading to Windows 8 is that Windows 7 is so good. For keyboard-and-mouse users, Windows 8 isn’t a hugely compelling upgrade — and without judicious use of third-party apps tobring back the Start menu and other core Windows 7 features, Windows 8 can actually make the desktop experience worse.
But what if you want to try out Windows 8? What if you want to take the Metro Start screen for a spin? (Who knows, maybe you’ll like it.) What if you want to give Windows 8 a chance?
One method you could use is virtualization, where you quite literally have Windows 8 open in a window on your Windows 7 PC. Virtualization isn’t really viable if you’re looking to truly experience Windows 8 and everything that it entails, though. For that, you need to dual-boot.
How to dual-boot/multi-boot Windows 8 with Windows 7
This guide assumes that you already have Windows 7 (or XP or Vista) installed. If you’ve already got Windows 8 installed, and you want to install Windows 7 as an additional OS, this guide might still work — but no guarantees.
First things first, you should backup any important documents. You shouldn’t lose any files during this process, but it’s better to be safe than sorry. See our Backup Masterclass for tips on how to backup your data efficiently and securely.
With that out of the way, hit Start, typediskmgmt.msc, and press Enter. This will open the Disk Management console. You should see a big (or small) list of all the drives currently attached to your computer.
Find the drive that Windows 7 is installed on (it should be marked as “Boot” or “System”), right click it, and click Shrink Volume. In the window that pops up, you ideally need a figure that’s around 50,000MB (50GB). If your hard drive is very full, this might not be possible. In theory the minimum install size for Windows 8 is around 20GB, but I really wouldn’t proceed without at least 30-50GB. If Disk Management refuses to shrink your volumes, you may need to try a third-party tool such as Paragon’s Hard Disk Manager.
Once the volume has been shrunk, a black, “Unallocated” region will appear at the end of the drive. Right click this and select New Simple Volume. Click through the dialog windows and give the new volume a memorable name such as Windows 8. Don’t change any other settings. This process will format the new partition, which may take a little while.
Installing Windows 8
At this point, all you really need to do is install Windows 8. You might opt to install a full version of Windows 8, or you can grab a 90-day evaluation copy. Either way, you want to slot the DVD (or USB stick) into your computer, reboot, and begin the installation process. (You may need to change the boot priority of your DVD drive/USB stick, which can be done in the BIOS).
When given the option, select a Custom install (not Upgrade). On the next screen you’ll be shown a bunch of partitions/volumes. Select the one that’s labeled Windows 8 (or whatever you called it). Be absolutely certain that you’ve selected the right volume, then click Next.
The slick Windows 8 installer will now do its thing. It will reboot once or twice, but eventually you’ll be greeted with a multi-boot menu that allows you to select which OS you want to load (Windows 8, Windows 7, or any other OSes that’re installed). Windows 8 will load by default after a few seconds, but you can change it back to Windows 7 by clicking “Change defaults or choose other options” at the bottom of the screen. Voilà: You now have a PC that dual-boots Windows 8 and Windows 7.


A little snarky in his explanation, Molnar goes on to say: “Unfortunately there’s a nostalgic cost: your old original 386 DX33 system from early 1991 won’t be able to boot modern Linux kernels anymore. Sniff.” Torvalds followed Molnar’s remark with cold acceptance, stating “I’m not sentimental. Good riddance.”
Pixel bitmaps have their problems, though. As display (and camera and cinema) resolution increases, so does the number of pixels. The obvious problem with this is that larger bitmaps are computationally more expensive to process, resulting in a slower (or more expensive) workflow. Pixel bitmaps also don’t scale very gracefully; reduction is okay, but enlargement is a no-no. There is always the issue of a master format, too: With pixel bitmaps, conversions from one format to another, or changing frame rates, is messy, lossy business.








When an app is installed,
Google’s verification system relies almost entirely on SHA1 values and the package name to determine if something is malicious. This is a very limited approach because malware authors can easily change the checksums without making any other alterations. Google just isn’t acquiring enough information to do in-depth analysis.
Take the so-called DroidKungFu Trojans. These nasty little bits of code are intended to root a target device and give control of it to a remote server. Yeah, it sounds really terrible until you realize this malware relies on an OS exploit that was patched at the system level over two years ago. There is just no reason for Google to bother scanning for this. No phone with the app verification system will ever need to worry about any of the nearly 500 DroidKungFu samples tested.




