Slashdot Log In
Windows Vista Annoyances
Posted by
samzenpus
on Wednesday January 30, @02:14PM
from the that's-a-big-list dept.
from the that's-a-big-list dept.
stoolpigeon writes "It has been well documented that the reception for Microsoft's Windows Vista has not been all that warm. Yet, visiting the web site of many PC manufacturers or visiting a retail outlet selling computers will show that most new hardware is being offered with Vista as the primary if not only option. O'Reilly's newest in their Annoyances series, "Windows Vista Annoyances", by David A. Karp, seeks to alleviate some of the pain for new Vista users. For the Vista owner who is able to put the book's suggestion into place, the edge should be taken off. For the individual considering a purchase of Vista and wondering if it can really be that bad, this book seems to indicate that yes, it is that bad." Read below for the rest of JR's review.
| Windows Vista Annoyances | |
| author | David A. Karp |
| pages | 641 |
| publisher | O'Reilly Media, Inc. |
| rating | 8 |
| reviewer | JR Peck |
| ISBN | 0-596-52762-4 |
| summary | Tips, Secrets and Solutions. |
I've read a decent number of O'Reilly titles over the years. My bookshelf for technical books is a rainbow of the various volumes, each with their wood carving style cover. I don't think in all those years I've ever read an introduction like the one in annoyances. O'Reilly authors tend to be enthusiastic about their topic and are often well known proponents of the technology discussed. I can only guess that Karp is not a huge fan of Vista. The preface begins with a section labeled "Why am I annoyed?" and that section concludes with the question, "Would Microsoft be making decisions like these if it had to compete fairly for your business?" The first sentence of the first chapter is, "Windows Vista is like a papaya: sleek on the outside, but a big mess on the inside." And Karp never lets up. Throughout the book, from start to finish, he never tries to gloss over the ugliness of Vista. This book may be hazardous to the health of Microsoft fanboys. I would imagine that too much time reading would lead to high blood pressure at the very least.
In view of the mess that is Vista, Karp informs the reader that, "Whether it goes down smoothly or gives you heartburn is up to you." The point of the book is to give the reader the information that they need to make Vista palatable. This may sound simple but it brings up what I thought was the most difficult issue for Karp. Vista Annoyances is written with a level of detail and explanation that marks it clearly for the user with casual knowledge of personal computers and how they work. Karp takes the time to explain things like what it means to zip a file, what happens when defrag is run on a hard drive, networking basics and so on. This is great for someone like me, who is sure to start getting a slew of calls from friends and family as some of them move to Vista. The problem is, many of the solutions revolve around steps that are not necessarily a good idea for the pc novice. A large portion of the solutions revolve around editing the registry. The third chapter of the book deals solely with the registry. How it works, how to navigate within it and how to alter it. For some people this could be a great route to take, for many it could lead to much more serious problems than they had in the first place.
For the technically proficient, this book will seem a bit bloated. They don't need all the explanation given for the beginner. Many of the books solutions are not just Vista specific. They give information and work arounds for Windows issues that have existed in XP and possibly back to 98. The saving grace is a thorough index. The person who buys this as a reference to help out others, or deal with some specific issue will find that the extensive index helps to not waste time working through what could feel like a lot of extra material.
I don't think this issue of complexity is necessarily the author's fault. Many of the changes users will want to make to Vista just can't be made any other way than through the registry. Where it is possible to use a programitic interface (gui or command line) Karp gives thorough and detailed instructions, with screen shots on how to do so. But for many options those tools don't exist or have been removed, leaving direct editing of the registry as the only solution left. Another issue, that is somewhat similar, is that for most home users, some of the better solutions wont be available as they wont have access to tools available in Vista Ultimate and Business editions. This isn't Karps fault again, but it means for many the book will have a lot of information that they just can't use.
Dealing with the various editions and their features is handled immediately in the first chapter. That chapter, "Get Started with Windows Vista", also covers installation. Karp goes over the various types of installs and gives tips on how to deal with failed installs, how to best set up prior to an install and how to deal with licensing. Throughout the book, Karp makes note when he is talking about a feature, choice or tool that is limited to a subset of the Vista family. Keeping track of it all can be a bit confusing. Once again, I don't really see this as a shortcoming on the part of the author. It's just the nature of the beast.
The title of the second chapter threw me at first. It is, "Shell Tweaks." When I hear the word shell my mind immediately brings up bash or ksh. In this case Karp is talking about Windows Explorer. As this is the primary interface for users working with the Vista file system, the chapter holds some vital information for attaining a sane and consistent user experience. Karp points out that many of the defaults are not going to endear themselves to many users and in many cases do not make much sense. When Karp discusses explorer he explains how to modify it when opened to various folders and also in the context of the desktop and taskbar.
Karp points out many third party tools that he feels will help the user. Many are free, some are not. The tools mentioned more than any other are Creative Element's Powertools. Powertools can be downloaded for a free 45 day trial period but costs $18 to license beyond that time frame. This is important as many of Karps solutions can be managed without this software but would be very cumbersome. This is especially true of all the editing done in the registry.
The registry chapter is thorough and offers a detailed explanation of what the registry is and how it works. This material could be useful for anyone using any version of windows. The issue of trying to make Vista useful for non-technical users rears its head here quite a bit, as I mentioned. I found myself reading explanations of hex and binary as well as reading how to create a patch file for the registry. This could be useful information for me, in helping others with Windows issues. But when I consider my parents, there is no way I would want them trying out half of what is in this chapter. They would in all likelihood need a complete reinstall in no time. What reading this said to me, more than anything was that most people are going to just have to settle for Vista the way Microsoft gives it to them.
The chapter on dealing with multimedia was interesting and could prove helpful for users with less experience. There are solid explanations on codecs, players and how to get the most out of media, especially video. There is very little said about Vista and DRM. There is no mention of possible problems with hardware due to DRM. In fact the discussion on DRM was primarily limited to a short mention of Tunebite and MyFair Tunes for DRM removal. I assume that this is because finding and explaining such issues would have required a lot more time, research and hardware. Vista annoyances pretty much sticks to the basics of media use.
I had to chuckle a bit as I read the chapter on performance as many of the recommendations involve turning off much of what differentiates Vista from XP. It is useful though, as Karp explains what the configurable options are and how much one can expect in gains. He does make it clear that the initial defaults are less than ideal and it is worth the time to dig in and make adjustments. The same can be said for security and in that regard the chapters on networking and users are indispensable. Once again, getting all the tools will involve having Ultimate/Business and installing third party tools to bring Vista into line.
I've rated the book 8 out of 10. This is due to two issues. The first negative I have explained quite a bit and that is the book speaks to the novice but requires someone with more experience in many cases. While this is may not be the fault of the author and a necessity brought on by the subject matter, it still makes the book less useful. The second is that quite often I found the author bringing up points only to say that he would explain more later in the same chapter or in another chapter. This is because the chapters themselves are built around topics like performance and troubleshooting. But when Karp is working his way through each option of a menu it branches out into other topics, as many options in Vista are spread all over the place. Once again, this seems to be more of a Vista issue, but hinders learning none the less.
After finishing this book, my first thought was that I am going to do all I can to make sure that no family or friends buy a machine with Vista if possible. Service Pack 1 will address just a few of the issues that Vista brings to the table. From what I've read about it fixing activation 'loopholes' it could make some things worse. Should I find myself approached by someone who already has Vista and wants help, I would recommend this book if they have some idea of what they are doing or can learn without getting into too much trouble. For that classic parent or grandparent always brought up as an example, I think I would just tell them Visa is the way it is and hope that they adjust. If I like them enough, I'll pull this book off the shelf and head on over to help them out.
You can purchase Windows Vista Annoyances from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
In view of the mess that is Vista, Karp informs the reader that, "Whether it goes down smoothly or gives you heartburn is up to you." The point of the book is to give the reader the information that they need to make Vista palatable. This may sound simple but it brings up what I thought was the most difficult issue for Karp. Vista Annoyances is written with a level of detail and explanation that marks it clearly for the user with casual knowledge of personal computers and how they work. Karp takes the time to explain things like what it means to zip a file, what happens when defrag is run on a hard drive, networking basics and so on. This is great for someone like me, who is sure to start getting a slew of calls from friends and family as some of them move to Vista. The problem is, many of the solutions revolve around steps that are not necessarily a good idea for the pc novice. A large portion of the solutions revolve around editing the registry. The third chapter of the book deals solely with the registry. How it works, how to navigate within it and how to alter it. For some people this could be a great route to take, for many it could lead to much more serious problems than they had in the first place.
For the technically proficient, this book will seem a bit bloated. They don't need all the explanation given for the beginner. Many of the books solutions are not just Vista specific. They give information and work arounds for Windows issues that have existed in XP and possibly back to 98. The saving grace is a thorough index. The person who buys this as a reference to help out others, or deal with some specific issue will find that the extensive index helps to not waste time working through what could feel like a lot of extra material.
I don't think this issue of complexity is necessarily the author's fault. Many of the changes users will want to make to Vista just can't be made any other way than through the registry. Where it is possible to use a programitic interface (gui or command line) Karp gives thorough and detailed instructions, with screen shots on how to do so. But for many options those tools don't exist or have been removed, leaving direct editing of the registry as the only solution left. Another issue, that is somewhat similar, is that for most home users, some of the better solutions wont be available as they wont have access to tools available in Vista Ultimate and Business editions. This isn't Karps fault again, but it means for many the book will have a lot of information that they just can't use.
Dealing with the various editions and their features is handled immediately in the first chapter. That chapter, "Get Started with Windows Vista", also covers installation. Karp goes over the various types of installs and gives tips on how to deal with failed installs, how to best set up prior to an install and how to deal with licensing. Throughout the book, Karp makes note when he is talking about a feature, choice or tool that is limited to a subset of the Vista family. Keeping track of it all can be a bit confusing. Once again, I don't really see this as a shortcoming on the part of the author. It's just the nature of the beast.
The title of the second chapter threw me at first. It is, "Shell Tweaks." When I hear the word shell my mind immediately brings up bash or ksh. In this case Karp is talking about Windows Explorer. As this is the primary interface for users working with the Vista file system, the chapter holds some vital information for attaining a sane and consistent user experience. Karp points out that many of the defaults are not going to endear themselves to many users and in many cases do not make much sense. When Karp discusses explorer he explains how to modify it when opened to various folders and also in the context of the desktop and taskbar.
Karp points out many third party tools that he feels will help the user. Many are free, some are not. The tools mentioned more than any other are Creative Element's Powertools. Powertools can be downloaded for a free 45 day trial period but costs $18 to license beyond that time frame. This is important as many of Karps solutions can be managed without this software but would be very cumbersome. This is especially true of all the editing done in the registry.
The registry chapter is thorough and offers a detailed explanation of what the registry is and how it works. This material could be useful for anyone using any version of windows. The issue of trying to make Vista useful for non-technical users rears its head here quite a bit, as I mentioned. I found myself reading explanations of hex and binary as well as reading how to create a patch file for the registry. This could be useful information for me, in helping others with Windows issues. But when I consider my parents, there is no way I would want them trying out half of what is in this chapter. They would in all likelihood need a complete reinstall in no time. What reading this said to me, more than anything was that most people are going to just have to settle for Vista the way Microsoft gives it to them.
The chapter on dealing with multimedia was interesting and could prove helpful for users with less experience. There are solid explanations on codecs, players and how to get the most out of media, especially video. There is very little said about Vista and DRM. There is no mention of possible problems with hardware due to DRM. In fact the discussion on DRM was primarily limited to a short mention of Tunebite and MyFair Tunes for DRM removal. I assume that this is because finding and explaining such issues would have required a lot more time, research and hardware. Vista annoyances pretty much sticks to the basics of media use.
I had to chuckle a bit as I read the chapter on performance as many of the recommendations involve turning off much of what differentiates Vista from XP. It is useful though, as Karp explains what the configurable options are and how much one can expect in gains. He does make it clear that the initial defaults are less than ideal and it is worth the time to dig in and make adjustments. The same can be said for security and in that regard the chapters on networking and users are indispensable. Once again, getting all the tools will involve having Ultimate/Business and installing third party tools to bring Vista into line.
I've rated the book 8 out of 10. This is due to two issues. The first negative I have explained quite a bit and that is the book speaks to the novice but requires someone with more experience in many cases. While this is may not be the fault of the author and a necessity brought on by the subject matter, it still makes the book less useful. The second is that quite often I found the author bringing up points only to say that he would explain more later in the same chapter or in another chapter. This is because the chapters themselves are built around topics like performance and troubleshooting. But when Karp is working his way through each option of a menu it branches out into other topics, as many options in Vista are spread all over the place. Once again, this seems to be more of a Vista issue, but hinders learning none the less.
After finishing this book, my first thought was that I am going to do all I can to make sure that no family or friends buy a machine with Vista if possible. Service Pack 1 will address just a few of the issues that Vista brings to the table. From what I've read about it fixing activation 'loopholes' it could make some things worse. Should I find myself approached by someone who already has Vista and wants help, I would recommend this book if they have some idea of what they are doing or can learn without getting into too much trouble. For that classic parent or grandparent always brought up as an example, I think I would just tell them Visa is the way it is and hope that they adjust. If I like them enough, I'll pull this book off the shelf and head on over to help them out.
You can purchase Windows Vista Annoyances from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Meh (Score:5, Informative)
Re:Meh (Score:5, Informative)
Unfortunatelly that is not possible, nor it was ever expected to be because Service Pack is meant to update the whole installation, if it detects that something is missing it aborts.
So the only way to use vLite on SP1 is to use it on the preintegrated version, meaning you can configure the Vista DVD or ISO which already has SP1 in it.
Until Microsoft releases one you can try making your own by following this guide.
But be careful, it's not official nor easy method so it is recommended only for the experienced users.
My Only Vista Complaint (Score:5, Interesting)
Other than that, there are a few things that annoy me but nothing that royally ticks me off like the printer issue. I should say, i'm a casual user. I use the system to read email, browse the web, play around with a few vmware images and burn home videos. Since I got my xbox 360 at xmas, I rarely play games, so even tho vista is a resource hog, I haven't noticed much.
Vista Annoyances- it is like they read my mind (Score:5, Interesting)
So, now my wife and I both say "I hate this f*cking computer" on a daily basis. First boot of the day often takes 5-10 minutes to simply stabilize and remain consistantly responsive with nothing but Firefox running. I am completely clueless as to what the hell this machine is doing on it's own that takes up all of its processing power that it can't handle simultaneously opening perezhilton.com. Additionally, the security package keeps annoying me over and over that my computer is not fully protected!!! because I turned off features that don't apply to our usage of it.
I would love to know a good resource to consult on how to tune the OS to get better performance w/o having to get into non-novice registry tweaks. I doubt this book could help me. Can anyone recommend a good resource for some more basic level Vista tweak advice?
Two things (Score:4, Insightful)
The two things I find annoying are UAC and enforced DRM. Yes, you can be affected by DRM even without buying any DRMed media--just try to load an unsigned driver in 64-bit.
Everything else is more disappointment than annoyance. With how much time they had to bake it, Vista could have come out amazing and full of great features. It was disappointing that it didn't live up to the hype.
It may not have been revolutionary, but it is still a solid improvement on XP. In my opinion.
Re:Two things (Score:5, Informative)
I mostly disagree with this on a number of points.
(1) Every other remotely common OS -- the various Unixes, Linux, OS X -- is just as susceptible as Windows is. They all use the same architecture: the driver runs in the kernel. Once you have that, an unstable driver can easily crash the system. Guess what: there are rootkits for Linux too, and they use the exact same principles as Windows ones: once you are installed as a driver, you are God.
(2) The main reason that this has been done is that it's hard to do well another way. Until relatively recently, the only mechanism that provided protection against a badly behaved driver was to run it in its own protection domain. This means a context switch whenever the kernel wants to call the driver, and a system call when the driver wants to call the kernel or return. For many drivers, the overhead here has been unacceptable. In the last several years there have been a couple new ideas for how to provide protection with lower overhead, but (1) they remain in the research state and haven't made it to real-world products, and (2) they too have overheads that are not trivial.
(3) MS is actually doing MORE to move drivers out of the kernel than the other mainstream OSes. Linux has some examples, for instance FUSE, but Vista introduces a new driver model that strongly encourages user mode drivers. (For instance, sound drivers are often written with the UMDF.) Performance critical drivers, such as parts of video card drivers, still run in the kernel.
Only 641 pages? (Score:5, Funny)
Vista is the ultimate Apple marketing program (Score:5, Insightful)
I mention all of this because the Apple store was PACKED. I had never even visited an Apple store, but in past years I would walk by and see lots of empty space. Not anymore. When I see the pain of Vista (not even our MS-loving IT dept. will touch it), I can't imagine Steve Jobs scripting it any better. "Gee, I would like the market leader to squander their advantage by breaking compatibility with old hardware and software. Make things more complicated, add in some DRM, slow it all down, and let the poor customer sort out the mess." MS strategy with Vista is beyond Steve Jobs' wildest dreams.
If Linux can't make serious progress on desktop market share in this market, then it will never happen. Opportunities like Vista don't come along every day of the week.
My top annoyance with Vista? It ain't in the OS... (Score:5, Interesting)
Seriously - did I get the magic copy of Vista that works just fine or something? It runs smooth, starts up OK, I like the default sleep feature, the added security (oh no - i get a popup everytime I install something - the horror), the photo gallery, the built in firewall, etc.
Its not a giant leap forward or anything - but then again - I didn't think XP was a big advance over Win2K client either. Just another incremental advance of the NT Client OS.
Being Constructive. (Score:5, Insightful)
Re:Seriously? (Score:5, Insightful)
Re:Seriously? (Score:5, Funny)
Did you mean: would be slashdot?
Re:Seriously? (Score:5, Insightful)
It's not the books fault if the solution to a particular problem is perhaps too sophisticated for some users. Unless there's an obvious simpler answer that the book overlooks, then this is simply a fact of life. The whole point is that they're trying to help out with an annoying piece of software they didn't write. What else could they do? Do what you originally said and just list the annoyance and show no solution? Or even worse -- list the annoyance, say that there's a solution, but then don't say what it is on the basis that it's too hard?
If the book can help users get over some of their problems, then it isn't a moot point at all. If by providing solutions that may be beyond the average reader, they encourage some of those readers to push their limits and become more comfortable, then that's even better.
That issue aside, when it comes to making changes that you're not entirely comfortable with (which presumably you wouldn't be if you needed a book to tell you how)
Some people are a lot more comfortable doing things if they have a book to tell them how. E.g. I'm no tool maven, and I would be terrified of actually trying to fix any of my plumbing if left to my own devices, but I am confident enough with tools that given an appropriate book explaining what to do that I could do it.
I get your point about a static book not necessarily being the best companion to a dynamic piece of software, but for some people especially beginners a book they can easily refer to and work through at their own pace is a better starting point than a web forum where they have to deal with human factors of entering some geek forum as well (e.g. the way I'd feel walking up to a group of contractors and plumbers and going "Der, how do I stop my faucet from leaking?" and then being confused by their answer).
Re:Seriously? (Score:5, Insightful)
Maybe, but newbies are also the ones who aren't particularly comfortable with asking questions, often can't completely explain the issues they're having (It don't do nothin'), and might have screwed something up which would prevent them from accessing the Internet.
A book, which can be propped open next to the keyboard and monitor, can be followed like a cookbook, minimizing the headaches of searching forums (and then trying to find those forums again after Windows asks you to reboot for whatever reason).
This sounds trivial to everyone here at /., but it's not for us.
Re:Seriously? (Score:5, Funny)
Oblig. Douglas Adams (Score:5, Funny)
This was the first thing I thought of:
The reason why it [the Hitchhiker's Guide] was published in the form of a micro sub meson electronic component is that if it were printed in normal book form, an interstellar hitchhiker would require several inconveniently large buildings to carry it around in.
Re:Seriously? (Score:5, Funny)
Re:Seriously? (Score:5, Informative)
Re:Seriously? (Score:5, Funny)
The publisher told him the trilogy probably wouldn't sell as well.
Re:Shock Horror (Score:5, Informative)
To summarize:
Re:Shock Horror (Score:5, Informative)
If Vista is so terrible, how come every single retail shop sells it first and foremost?
Umm, pretty much because Microsoft is forcing them to. And, yes, Microsoft does get to say when you can or can't sell something.
OEMs don't get forced into buying Vista after all, and it's not like Macs aren't selling either so it's clearly not just a Windows thing.
You have no idea of what an OEM agreement is, do you? Yes, OEMs are forced into buying Vista. Either that, or they forfeit all the nice marketing support, pricing, and other goodies that Microsoft gives - and that amounts to a lot of money. Think I'm kidding? Just try to buy an XP computer from Dell or HP after June 30'th. That's the cut-off date set by Microsoft for OEM sales.
Re:More Evidence Vista == Windows Me (Score:5, Informative)
Re:More Evidence Vista == Windows Me (Score:5, Interesting)
At the time, when Windows ME was a product being sold, I admit, it was garbage. They removed access to underlying DOS, compatibility issues arose where they absolutely shouldn't have, and honestly, it didn't offer me anything over Windows 98.
As a programmer, I do, however, have a handful of clients that use win9x, for whatever exotic reason, so I dug up my install CDs, found an unused Pentium III 800, and made a tri-boot system, with Windows 95C, Windows 98SE, and Windows ME, all with whatever updates were available.
This is, of course, years after 9x was dead, and probably no one cared, but seeing all three of these OS's run on the exact same machine, I have to say, I prefer Windows ME out of all of them. I will give you a few reasons why:
People seem to have forgotten how readily Win9x bluescreened. Sure, we all still joke about it, but there is a slight amnesia to how it really was. Windows 95 most specifically would bluescreen out of nowhere... just sitting there, doing nothing. And every so many bluescreens, something in the system directory would get corrupted, and you would have to reinstall... and did you ever notice that bringing up a DOS window, or running a native DOS app started your system on the downward spiral to hell? I have. But really, I am just talking about Windows 95 and 98... not ME. I have yet to have ME bluescreen on the described system. And if something happened to your system files? There was the Windows File Protection people now take for granted in Windows, so reinstalling wasn't necessary like it was on ME as it was with it's older brothers
Nextly, something you can only notice in the kind of setup I have... the GUI was flat out more responsive... both under load and not. I know that sounds kind of funny, but on Windows 98 especially, clicking a button took about 100ms to register... something you don't really notice, until you use Windows ME and see that clicking on everything causes a reaction more readily. Also, for whatever reason, my network throughput when booted into Windows ME is much much better. Under Windows 95/98, playing Quake2 over a cable modem, my lowest ping was practically the same as Windows ME, but the consistency on Windows ME was so prevalent, that if I play such on that machine, it HAS to be booted into Windows ME.
Honestly, I could drum up a multitude of things that I see NOW, that make ME better... but then, I agree, it wasn't. It is almost like it hit its peak abilities well after the market was gone.
Re:You forgot one (Score:5, Funny)
That's not a drawback, it's a feature.
Re:You forgot one (Score:5, Funny)