Windows Vista Annoyances
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.
It's actually a book about the annoyances, and how to fix them. Just listing annoyances would be stupid. Listing the annoyances, along with giving details of how to get around them, so they are no longer annoying, is actually quite useful.
Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
I dunno. Based on the comments here, a lot must have been cut out to make it FIT in only 641 pages. :)
Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
If you want to alleviate Vista annoyances, and you MUST use Vista, use vLite and make a custom Vista install image with ONLY the stuff you want on it. I just did this yesterday and it works wonders. Vista doesn't feel like a slug anymore.
There are really only two options.
#1. Run a utility that makes the Registry changes for you. Where are you going to find that?
#2. Edit the Registry by hand. At least the option is there.
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.
"Thanks to the remote control I have the attention span of a gerbil."
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?
Just listing annoyances would be stupid.
Did you mean: would be slashdot?
ccalam - acoustic versions of new songs.
Yeah, but anyone with half a brain can Google their Vista annoyance and find a FREE solution. Why would anyone waste money to read about some other guys annoyances and how to fix them? I personally use Vista Ultimate now, and for comparison I have also used Ubuntu for a while. In fact in my approx 6-7 months of using Ubuntu, I had plenty of annoyances. After I switched to Vista, I didn't have any problems or annoyances ay all.
That a book like this would be written and actually published seems more evidence that Windows Vista is the next incarnation of Windows Me which proved to be a nasty little speed bump on the way to the next "good" version of Windows. It's a real shame to do this to the users. Microsoft is full of talented, bright people to whom Vista is giving a bad name. It's almost never a good idea to push an incomplete product out into the market.
To the making of books there is no end, so let's get started
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.
Seriously, I'm surprised the book length is finite.
+0 Meh
O'Reilly publishes quite a few books in the "Annoyances" series (Windows XP Annoyances, Mac Annoyances, etc.) This is just the next one in the series.
TODO: Insert witty sig
I am a first time Mac buyer. I'm a big Linux fan, and use it for my home machine. At work, I'm stuck with Windows. My wife had a Windows XP box as well, but she wanted a laptop to use for scrapbooking. Over the years I have tried many times to deploy various Linux distros on laptops, with mixed results. I suppose I could lock down an exact configuration that someone else has already declared to be trouble-free and go buy the same thing. But as far as taking any old machine and putting Ubuntu on it, then educating my wife on the use of Linux, that's more time than I want to spend. Getting stuck with Vista is a non-option, so I bought her a Macbook.
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.
It sucks because it just fucking sucks big hairy donkey balls.
- None can love freedom heartily, but good men; the rest love not freedom, but license. -- John Milton
To summarize:
.sig
The publisher told him the trilogy probably wouldn't sell as well.
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.
Don't sell Windows at all, and make most Linux PCs? That's got to be the best possible license price, right?
throw new NoSignatureException();
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.
My biggest annoyance is the screen flickering when unlocking a laptop that has an external monitor plugged in. I found a way to get it to stop, but that disables the auto-detection of external monitors (http://comments.deviantart.com/18/976237/576101509).
If you do disable TMM, you will need to remember to disable the 2nd monitor before suspending your laptop to go somewhere. If you don't, you'll go to unlock your machine and be staring at a black screen. You'll then need to hit CTL-ALT-DEL, and select "Switch User", and re-login in order to use your machine again. Pretty freakin' annoying.
So, one of those Egg Council creeps got to you too, huh?
I will assume that you are new to this because things have been this way since the Pentiums first rolled out. There is nothing illegal, immoral or anything else wrong. It has nothing to do with liking or even if the OS is useful to their customers. It all comes down to availability and profit. It is not even limited to the computer industry as Games Workshop does the same thing.
Shops will sell what has the highest profit margin and what they can get their hands on. The two computer shops near my house could not get access to retail WinXP licenses after Vista shipped. There was nothing to be had as Microsoft stopped selling them through their channel. They had no choice but to put Vista on the shelves. The second company (much bigger than the first) actually got a nice sized "advertising" cost offset from Microsoft channels to display/sell Vista. The limitation was that they had to remove XP from the shelves and really push Vista to make up the numbers, thus giving them more offsets.
OEMs love it because they are paid to love it. For the same reason there is that the Intel Inside sticker was put on everything. Microsoft pays them in advertising dollars for each time they run something with the Vista logo.
Good or bad has nothing to do with why companies place Vista so highly. Companies could care less about Vista except that it has the capability to drive more expensive purchases. Its all about the money.
Programming: Its not just a job - its an indenture.
Ever heard of those "Anti Virus" that slow down your system by scanning everything you read or write, third-party "personal/desktop firewalls", and other spyware/malware cleaners? Products like "Norton 360" ?
DualBrain - Level Up Your Brain! - now available on your iPhone!
I'm addressing all the posts that go along the lines of "Windows Suxxors" here. Linux can be technically superior to Windows in every way and that is still not enough. It's a Windows world and it's going to stay that way for the forseeable future. The reason for this - and pointing out that comparing Windows to Linux alone is myopic - is that people don't really buy Windows, they buy compatibility with software. Or what Ballmer refers to as the "ecosystem". Linux is great but I can't walk into a BestBuy and buy anything software wise for it. How to go about getting around this feedback loop? Well, virtualization at the application level is the single approach that can actually break the loop. Things like Thinstall which was just purchased by VMWare or the ubiquitous Wine project. Weaning people off of the Windows dependence does not begin with Windows, it begins with it's applications.
Shh.
it's sad when an operating system is so horrible it severely hinders even writing about it.
VLC FOR MAC IS DYING! IF YOU DEVELOP, PLEASE SAVE IT!!
> It's actually a book about the annoyances, and how to fix them.
method #1: get a real OS.
If you have specific annoyances, you search for them on the Internet and find solutions. That's like having a giant constantly-updated index at your fingertips.
Microsoft will have released a new operating system, with new flaws and workarounds and fixes, before such a paper book becomes worn.
So why spend the money, unless you are a collector of books?
Joe Llywelyn Griffith Blakesley
[This post is in the public domain (copyright-free) unless otherwise stated]
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.
Weaselmancer
rediculous.
I dunno - there's at least three magic copies, then, because I'm running a pain-free one at home (Ultimate), and at work (Business), which I use heavily, and I haven't run into any big annoyances at all.
Oh, and to all you UAC haters, I actually like it. You all probably surfed the net with admin privileges on XP and thought you were secure because you use firefox. Not so, pineapple man! UAC works well, and is not intrusive. I only get prompts with (un)installs and serious configuration changes, but not in my daily use.
Just because I doubt myself does not mean I find your position compelling.
Yeah never mind the fact that Vista has only sold 100 million copies to the end of December and that Microsoft had it's best quarter in history.
Yeah, but how much did they pay the developers to write it? They released XP in October 25, 2001. They released Vista to the public January 30, 2007. That's over five years of paycheques to recoup before they actually start to turn a profit on this release.
Of course, it's the big media companies who paid for Vista. Microsoft saw the writing on the wall, and they sold out their install base. They didn't put the new features in for the benefit of the consumer, they put them in because they hope to get a few points on the dollar from the copyright industries once they've created an infrastructure for total information control. I imagine the US government threw a lot of money in the pot too.
Hopefully, this will all just collapse under its own weight. If it doesn't, eventually, it is going to be necessary to send ground troops after these people and force them to stop what they're doing.
-1 Uncomfortable Truth
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.
But as the review explains, many of the fixes probably aren't suitable for the intended audience of the book, which kind of makes that a moot point.
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).
The enemies of Democracy are
Luckily, if you happen to have a copy of Office, you can go to Help->About and click on the conveniently located link to read the EULA.
Upon reading the EULA for Office 2003, I can't find the clause you mention. It's a pretty standard EULA and is actually surprisingly generous in its licensing terms, especially with regards to clip art (which is more or less "don't use it to violate any depicted entity's trademark, and if you do, we're not liable"). There's nothing in there that I could find about not using Office to hurt Microsoft. Perhaps it's in the French translation?
The Freelance Wizard
The notion that Vista took ~5 years is a fallacy. During those first few years, much of the Windows team was focused on the security push and XP SP2. What few teams were left on Longhorn (as it was called at the time) were mostly without direction. Once XP SP2 shipped and teams started focusing back on Longhorn, it was clear that things had gotten out of hand and they implemented the famous Longhorn Reset. That brought the codebase back to Windows Server 2003 as the base and essentially started Vista over from scratch. That was in mid-2004, which means Vista actually only took 2.5-3 years to write and was definitely not a complete rewrite of the whole OS (though portions did get a full rewrite, like the driver model).
You don't think they didn't? It's been argued that Jim Allchin's departure from Microsoft was a direct consequence of the Vista debacle. Otherwise, the firing or re-purposing of lower level employees isn't something that really makes the news. From the external point of view, of course it looks like everything's the same.
I really don't think you understand what MinWin is. The ability to strip down the OS to its bare essentials has been available in various forms at least since Windows XP Embedded (if not earlier), and I'd be very surprised if MinWin is not working from that base. It's not a rewrite so much as it's a re-restructuring of the Windows architecture to facilitate more modular uses of the core platform.
And Apple's copied just as much from Microsoft. Many of the features in OS X were directly lifted from early plans and betas of Vista/Longhorn. The only difference was that Apple was able to execute quickly and ship product while Microsoft floundered. Only time will tell if the same will happen with Windows 7, but I think Microsoft may have learned its lesson the hard way this time around and will really surprise everybody with Win7.
Personally I've been an OS junkie since the DOS 6.0 days / slackware 1.0 (can't even remember how long ago that was) and I've more or less tried every OS for the x86 platform (hell I even tried OS/2 and BeOS!!)
The one thing about Vista that has been DRIVING ME INSANE, is the fact my vista clock keeps going forward by 4 - 6hrs (it's random but at a minimum of 4hrs). I've tried everything to correct this issue and have even come across users who have the same issue and still no avail. fix. I've tried new drivers, confirmed the time zone, checked in other OS's, etc etc but Vista will not remember the time for the life of it. It's a huge nuissance and is about to force me to go back to XP. I can't believe I've lived with Vista this long (bought it on the day it came out. . . yes I paid real $$$ for it). There is a bunch of other random issues but I won't bore anyone with the details as I'm sure it's already been beaten to death with the "I hate Vista stick"
When I find the time to reinstall all of the windows apps on XP I'm throwing Vista out.
When I bought my laptop last summer, I was dreading having to deal with Vista. To the point I was researching how to wipe Vista and install XP. (What I found is the newer hard drives do not have driver on XP natively so XP might not recognize the drive and so you have to load those first....) Anyway, I decided to try Vista first to see if it was really worth going through a major headache of wiping the drive and starting over.
I was, in fact, pleasantly surprised...mostly. I don't know if it was the manufacturer (HP) doing a great install configuration or the version (Home Premium) or the fact it was built for Vista vs. just slapping an upgrade on a current computer, but I've had very few problems. Only thing I've done was upgrade the memory from 1 to 2 GB. I also turned off UAC which I found beyond annoying. The computer is used mostly at home and behind a firewall--not to mention that UAC can be foiled--and chances are most people are going to automatically approve something when they're installing a program (which is usually when a person gets a virus), so the UAC becomes useless.
If you're into voice recognition, the voice recognition that comes with Vista works surprisingly well--better than Dragon Naturally Speaking and with less training. (Just be sure and have a good microphone.) However you won't be able to use it with Open Office--you'll have to stick with MS Office, notepad, etc. Also I'm able to play even ancient DOS games with DOSBox and I've found very few programs I've had a problem running. Networking with my wireless router was a breeze.
Vista IS a Mac rip-off with eye candy--stick a few new screensavers and Yahoo! Widgets on your XP and you're 2/3s there. The most annoying thing is once again having to FIND where they hid the settings again--almost none of it is helpful or makes things smoother--especially if you want to just view ALL the programs. It's not as great as the fan boys praise, but it's not as horrible as the nay Sayers make out either. Personally I wouldn't upgrade from XP as long as possible, but if you're getting a computer with it installed, you might find it isn't as bad as you think.
If you've never been modded as "flamebait" or "troll," you've never tried to argue a minority viewpoint here!
I accessed the EULA directly from my copy of Microsoft Office 2007. I saw no reference to the terms you specified. This smells like a misinformation.
Your courageous and selfless spelling corrections have made me a better person.
How much d'you think I can get for it on ebay? There's gotta be a ton of folks who want Vista with the hidden "Work OK" setting enabled by default.
Slashdot needs a moderating system to identify possible paid shills. This guy hits way too many marketing points to be a real user. Vista has SPEECH RECOGNITION? He must have gotten that from the glossy brochure. Nobody uses speech recognition but it's a great advertising gimmick.
See - thats EXACTLY why I must have the magic copy of Vista. I never get any popups - and I have UAC fully enabled. I run plenty of legacy software that predate XP, let alone Vista, so before I installed it I figured I'd see it all the time. About the only time I ever see the popup is when I launch Visual Studio...
Run a utility that makes the Registry changes for you. Where are you going to find that? [or] Edit the Registry by hand. At least the option is there.
Wow, thanks Microsfot for the great options. Somehow Apple, KDE, Gnome, BeOS, Windows pre registry all manage to provide a way for users to change settings on their computer without typing Hex into some crummy database manager that might brick the computer. I'll take a well commented text file over that mess. Text configuration files are the reasonable third option that's sadly missing in Windows.
The workrounds for Vista are actually considerably simpler.
From scarped cliff or quarried stone she cries "A thousand types are gone, I care for nothing, no not one."
Interestingly, there's none on Linux annoyances.
Good, inexpensive web hosting
I never get to see the damage. All I do is reinstall and take away their administrator privileges.
I'm aging rapidly, I bought a new game and had no idea if my machine was good for it.
About a week ago, I build a new pc and decided to give Vista (Ultimate x64) a try. I have been able to work through most of the problems/annoyances, such as disabling UAC and various other services that significantly slow the system down, but there is one small one that gets on my nerves that I can't find a fix for...
I like to use the 'Details' view when browsing folders in Windows Explorer - I'm not a fan of all those giant icons. Whenever I perform copy/move operations by dragging a file/folder into the detail view, the sorting gets removed. For instance, when I have the folder contents listed alphabetically (by the 'Name' column), if I drag a file into this view, it drops it exactly where I let off the mouse button and removes the 'Name' sorting instead of organizing that file to where it should be in the list. I have to click on the 'Name' column header to sort the contents again.
I have yet to find a way to disable this behavior and return it to the way every previous version of Windows worked. If anyone else has run into this and has a fix, I'd love to hear it!
I beg to differ. Symantec pcAnywhere seems to have no issues with allowing the remote user to "click through" the dialogue. I use it on a daily basis to provide support to my company's customers, and have decried the "security" of this feature ever since I clicked "Allow" on a system 220 miles from my physical location.
This work is licensed under a Creative Commons Attribution 3.0 Unported License.
thats because pcanywhere connects the user to the console and runs as a kernel mode process. It even replaces the gina.dll. Without all that pcanywhere couldn't do it. If you've allowed spyware/malware that does all that to be installed on your machine then you're already screwed and no amount of sas will protect you.
"In the end, there is simply no weapon more devastating than the truth, delivered in just the right way." - tnk1
You can instead type machinename_or_domain\username. Not the same thing but it's not as if you're blocked from logging in as a specific user. Depending on taste, it's nice to just having to type that instead of going "oups, I have the wrong dropdown." But totally a fair criticism.
As for 2, I'm not sure what you mean. They've moved some things out of My Documents but it's all still in the "documents and settings" (now Users) area. They've also exposed more of that to the user by a creating a link to your user's root folder from the start menu. Some of those folders are, such as AppData, are understandably set hidden so this scheme works well for the novice.
You can use UAC over an RDP or VNC connection. If vncserver can send the appropriate signals to the dialogue box, I would have thought anything could.
Why cant the double click on the Icon use that security level feature... I would understand if it was an autmated process of an open app but this is a double click on a provided icon. If Double Click from Actual mouse then open app with no questions...
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
Apparently you did. Not a single application compatibility problem? Lucky you. Lack of decent Anti-Virus/Firewall solutions available. Turn off a single "security" feature and the system nags you non-stop. UAC is retarded. I'm quite capable of using my system without it, but I can't turn it off without the nagging. It's simply not able to be configured at a fine-grained level, and the system complains if you turn it off outright.
It runs smooth,As does every other modern OS on the planet. This one will only run smoothly if you either a) have a very modern system, which many can't afford yet, or b) change back to the Windows 2000 look and turn off all the bells and whistles (why would you do that?)
starts up OK,Yeah, the hard drive only grinds needlessly for 5 minutes before allowing me to use it. This on a Core-Duo with SATA drives. What the hell is it doing?
I like the default sleep feature,...which some random update causes it to remain asleep. Again, no exotic hardware, just a standard ASUS motherboard with a Core-Duo.
the added securitywhich explains that even with AVG professional I got no less than 5 adware registry entries within 3 months? (no, not browsing pr0n) My Windows XP box has never received even 1 (same AV engine). Oh yes, and making you click "Confirm"/"Deny" is really security? Why the hell did you execute the program, etc. if you didn't intend to? Idiot-proofing != security. You're stuck with Windows Firewall (which sucks) as opposed to being able to install (say) AVG Professional Firewall, which works well. There's no default AV program, and no free solutions were/are available, so there's another $60 to the price tag.
the photo gallerySo you bought a $500 OS and a $60 Anti-Virus program to get a photo gallery? Either you've got money to burn or you just bought the most expensive slide-show program on Earth? Apparently you need Vista's idiot-proofing features...
Maybe the fact that you don't actually use your computer explains why it works for you. As a desktop ornament it's great and has lots of eye-candy. So does Ubuntu, and I can do stuff with it too.
"Please describe the scientific nature of the 'whammy'" - Agent Scully
O'Reilly has published _the_ authoritative books in so many software categories that it goes without saying that in this community (Slashdot) anybody who stumbles out of the woodwork attacking a book like this looks like, well, somebody stumbling out of the woodwork. O'Reilly is a traditional Unix book publisher. For instance, they published the X11 manual set. For Unix people trying to make sense out of the 'doze the O'Reilly books are often the first one to reach for. Further, the 'Annoyances' book series has been a cut-through-the-crap series for people forced to deal with Windows since the Windows 95 days. To me it goes without saying that anyone who would refuse to even question the usefulness of a book purely because they like the publisher behind it is someone who is not helping anyone or anything. Sadly, there are all too many people in this community who, like you, will refuse to even discuss certain things based on their own merits because they've already picked their "side" and decided that this thing or that thing is either with them or against them (Gee, where have I heard that before?) and will blissfully remain ignorant in favour of having their clearly defined lines of what is Good and what is Bad.
Does this book have a legitimate purpose? Maybe. Does it have a customer base? Probably, even if as others have stated it is more down to some people's own tendencies to prefer a non-judgemental block of paper than risk the chance of being thought stupid asking people online. Whatever the case, it would be nice if the book could be judged on its own instead of people throwing in the ridiculous notions that is must be good because it's from O'Reilly and declaring anyone who disagrees to not be part of the community.
Spelling mistakes, grammatical errors, and stupid comments are intentional.
...because I'm running Vista on 4 machines in my house and I have yet to come across any significant issues. Two of these installations are 64-bit. I've only gotten a BSOD once on any one of them and that was because my memory timings were a bit too tight.
Seriously. Am I God? Because according to all the PR out there, you have to be in order to get Vista to work.
If anyone remembers (and how quickly we tend to forget in the world of technology), much of the same thing happened when XP launched. People that were running 9x kernels absolutely hated XP at first. Why? Because it was different and required you to "relearn" some stuff, most of which ultimately will make you far more productive (which I think everyone can agree XP did over any 9x version).
Working in retail I hear it all the time: "I hate this new Vista." When I ask why, the reply is always the same, "It's too different from XP." Not "it crashes all the time" or "won't let me do anything." I even had one lady tell me she hated Vista because it automatically made her monitor's resolution 1280x1024 instead of 800x600 which she wasn't used to. You wouldn't believe how difficult it was to even explain what the heck resolution was to her.
There's this overwhelming impression out there that Vista is utter garbage. And while I won't doubt that some people are having massive issues with Vista, I would wager that, for the most part if 1) they actually did more than 5 minutes of research they'd realize that Vista isn't the culprit and stop assuming it is, or 2) stop being so computer illiterate and learn to adapt to the changing technology industry.
Oh how quickly we forget about how horrible Windows 95 or ME actually was. I can't even get ME running properly in a virtual machine. Windows 95 keeps barking about system files missing. Comparing Vista to THAT is completely and utterly uncalled for and absolute ignorance to the true situation.
I'm a Windows Vista x64 user. And I have been since Beta 2. And I've not had a single issue. Call me lucky or call me a God, but I'd rather call myself educated in technology.
The Computations of AdamR
http://www.adamreyher.com