Big Booger
December 4th, 2005, 14:15 PM
Written by Kristan Kenney (Nighthawk), Last Updated on December 2nd, 2005.
Introduction
With every new build, there are bugs fixed, and more bugs introduced. If you are looking to run Windows Vista 5231 on a production machine for a temporary period of time (which I do NOT recommend), or you are just looking to play around with it, this guide will show you a few simple steps to make your life easier, and even make Build 5231 a bit more stable than what it is out of the box.
Build 5231 is known as an “interim” or an “in between” build; these builds do not show the quality, performance, or stability of a Beta product. If you are looking to run Windows Vista (for fun or otherwise), I’d personally recommend at the time of writing to install Beta 1 (Build 5112). While Beta 1 may not have some of the new bells and whistles, it does perform better when using Windows Vista’s new features, such as search capabilities.
Part One – Driver Issues
When you first install this build, you will be prompted to install any supplemental drivers. Just follow through the wizard and let it detect you hardware and install any necessary drivers.
For some users with NVIDIA graphics cards, this build may randomly restart, blue screen, or bring up a black screen on you. The easiest and most reliable way to fix this is to install the Windows XP compatible ForceWare driver package from the NVIDIA website (http://www.nvidia.com).
For the most part, users with ATI graphics cards have not experienced this issue, but should it occur, I recommend that you install the latest ATI Catalyst drivers. (http://www.ati.com).
There is a consequence of doing this – some applications with transparency features, such as Miranda, or the Office Language Bar, causes the system to throw a STOP error (or BSOD). Try to avoid applications like this. For the Office Language Bar, deselect any “Alternative User Input” or “Microsoft Handwriting Capability” items in Office setup.
:view: View: The Full Optimization Guide (http://digitalfive.org/?page_id=8)
Introduction
With every new build, there are bugs fixed, and more bugs introduced. If you are looking to run Windows Vista 5231 on a production machine for a temporary period of time (which I do NOT recommend), or you are just looking to play around with it, this guide will show you a few simple steps to make your life easier, and even make Build 5231 a bit more stable than what it is out of the box.
Build 5231 is known as an “interim” or an “in between” build; these builds do not show the quality, performance, or stability of a Beta product. If you are looking to run Windows Vista (for fun or otherwise), I’d personally recommend at the time of writing to install Beta 1 (Build 5112). While Beta 1 may not have some of the new bells and whistles, it does perform better when using Windows Vista’s new features, such as search capabilities.
Part One – Driver Issues
When you first install this build, you will be prompted to install any supplemental drivers. Just follow through the wizard and let it detect you hardware and install any necessary drivers.
For some users with NVIDIA graphics cards, this build may randomly restart, blue screen, or bring up a black screen on you. The easiest and most reliable way to fix this is to install the Windows XP compatible ForceWare driver package from the NVIDIA website (http://www.nvidia.com).
For the most part, users with ATI graphics cards have not experienced this issue, but should it occur, I recommend that you install the latest ATI Catalyst drivers. (http://www.ati.com).
There is a consequence of doing this – some applications with transparency features, such as Miranda, or the Office Language Bar, causes the system to throw a STOP error (or BSOD). Try to avoid applications like this. For the Office Language Bar, deselect any “Alternative User Input” or “Microsoft Handwriting Capability” items in Office setup.
:view: View: The Full Optimization Guide (http://digitalfive.org/?page_id=8)