1. The baloon that says 'click this baloon to fix this problem'
2. The big button marked recommendations that includes the option to not monitor.
3. The menu that includes the option not to monitor.
Those are your choices, after clicking 1, you can follow 2 or 3.
Seriously, how do you make it simpler? It's already popping something up to tell you how to change it, do you need some kind of loud alarm and flashing lights to go with it?
I don't see how you can blame the vendors for this. Fact is, the reason that software breaks in unpredictable ways is because windows closed API's act unpredictably. The full details are never published, so therefore incompatibilities for future versions can be very difficult to predict.
Um, that's why they are closed? There's a perfectly good list of API's you are supposed to use. Quick tip, they are not the ones you are have to reverse engineer.
Ready or not, patch your fucking computer, you incompetent nimrod.
It's a service pack, it fixes bugs, its a required update if you want support in the future.
If it breaks a program or driver, guess what, I'm going to bet someone didn't follow the programming guidelines for the OS.
The blame should be placed on the developer of the app and the end-user for using uncertified software, not Microsoft. MS put a program in place to avoid this (Windows certification), the end-user ignores it, and then it's someone else's fault when it breaks.
A well regulated militia, being necessary to the security of a free state, the right of the people to keep and bear arms, shall not be infringed.
Reads to me like you have the right to join a well regulated militia. Not the right for any yahoo to amass a stockpile of weapons and go on a shooting spree.
You can't watch you kids every single second of every day.
I'm a parent, and I CAN and WILL watch my kid every single second while on the Internet.
So don't tell me I suddenly need a new law that involves tearing up the constitution, just because you are incapable of installing your own blocking software.
Or google's never expiring tracking cookie. It aint there just for your "prefs."
Actually, I think it is. I ran an online service that required cookies. A cookie was set to expire one day after being set. So, what happened was a good 10% of the users had their clocks set wrong and would usually expire the cookie immediately, resulting in calls to customer service.
I tried setting it a day, week, month and year in the future, still had about 7%.
At that point, I just set it to 30 years in the future, that cut it to about 2 calls a month.
By the way, the average person who had their clock set wrong was off by YEARS. Think 2011 instead of 2001.
Now that people are upgrading to operating systems that auto set the time, this has become much less of a problem. If I were still running the system, I would go back to the 1 week timeframe in about a year or so.
Version 5.1 actually, if you want to be technical. Personally, I would have called it 5.5, but that's just me, some of the improvements in XP are pretty nice. I love the faster bootup time, for example.
Win98SE to ME was also a point release, but not a well thought out one. The biggest mistake was closing the 98 shell team at Microsoft and using the 2000 shell on 98 giving you Windows Me.
Technically Google wouldn't be Google if it didn't use web-bots. There is no way they could maintain their current system manually and stay in business.
While practicality might not be a good excuse, running Google out of business would be a better one.
Why not just have all doctors work 20 hours a day 7 days a week? Even better yet, have YOUR doctor follow that schedule.
I like mine to have time off.
The on-call system is to allow doctors to work only when needed all hours of the day and night. That way they can get some time to themselves AFTER they work about 10 to 12 hours straight.
I have no major problems with XP themes on a Dell Inspiron 7000. 500Mhz P3, 384MB RAM and ATI Rage mobility card. It works fine for web browsing, remote access and the occasional DVD movie playing.
DOS left Windows a while ago. NT on the business side and XP Home for the average Joe User.
No, your response was just 1 step away from the typical "OMG M$ IS TEH GHAY!!!".
Simply put, you couldn't resist taking a swipe at Microsoft, which leads back to the entire point of this article. That point being, not will Linux ever mature, but will Linux advocates ever mature.
Originally, the Southern State and the Southern Parkway were two different parkways. The state parkways were the Southern State Parkway, Northern State Parkway, Meadowbrook State Parkway, Wantagh state parkway, Bethpage State Parkway, Heckscher State Parkway, Sagtikos State Parkway and Sunken Meadow State Parkway.
People started dropping the 'state' name from the
parkway names in the early 60's. The signs started changing in the 80's and 90's to reflect the new names, but on paper, they remain the State Parkways.
The whole mess leads back to Robert Moses, who designed these parkways, again, just for park traffic. The original Meadowbrook and Wantagh didn't go past Sunrise highway. They were eventually extended to the Southern State and later the Northern State, to reduce traffic on local streets, but NEVER to the Long Island Expressway, as that would make the road a commuter road.
Robert Moses was in some ways a genius, and in other ways a total maniac.
The Windows NT (2k/xp) kernel has the ability to use multiple APIs out of the box, with WIN32/Posix/OS2 1.x support built in..NET will most likely wind up in this group with the longhorn release.
This will allow.NET apps to run about as fast as current Win32 apps. The average joe user won't know or care what API the software was designed for.
It would, but that's not what I wanted. All errors were fatal, including informative errors, it made EH inside the procedures impossible.
A simple example.
Insert record If duplicate record error then update record instead if other error throw exception
Now, a duplicate record would throw a fatal error to coldfusion. I could then catch that error in CF, but now I have to code for 2 possible outcomes, a fatal error that isn't fatal, and a fatal error that is fatal. At that point, you might as well split it into individual statements.
Not quite on topic, but, I once tried writing code in SQL (in this case for ColdFusion) by using stored procedures and exception handling.
What a nightmare.
Many people code unique inserts like this.
Check for duplicate record. if not found, then insert. else, prompt user.
Using exception handling, you code like this.
insert. if error thrown, prompt user.
One less query, lots less code.
One problem, the web application language treated all db errors as fatal. When asked, I was told this was by design.
Thinking about it, I feel that Macromedia didn't want me to code efficiently. You don't sell extra ColdFusion servers if you can offload all your data logic to the SQL server. (Where it belongs)
Slashdot Mirror
Yay, you win, you have a program that is messing up your security center settings.
Now take the 15 seconds to disable the service.
Wow, that was tough.
How do you make this simpler?
1. The baloon that says 'click this baloon to fix this problem'
2. The big button marked recommendations that includes the option to not monitor.
3. The menu that includes the option not to monitor.
Those are your choices, after clicking 1, you can follow 2 or 3.
Seriously, how do you make it simpler? It's already popping something up to tell you how to change it, do you need some kind of loud alarm and flashing lights to go with it?
I don't see how you can blame the vendors for this. Fact is, the reason that software breaks in unpredictable ways is because windows closed API's act unpredictably. The full details are never published, so therefore incompatibilities for future versions can be very difficult to predict.
Um, that's why they are closed? There's a perfectly good list of API's you are supposed to use. Quick tip, they are not the ones you are have to reverse engineer.
That is/was some kind of generic catch-all response that can't/wont be able to be proven/disproven, and is therefore full of crap.
Show me a KB article on this bug.
Suggested New Title for this article:
Ready or not, patch your fucking computer, you incompetent nimrod.
It's a service pack, it fixes bugs, its a required update if you want support in the future.
If it breaks a program or driver, guess what, I'm going to bet someone didn't follow the programming guidelines for the OS.
The blame should be placed on the developer of the app and the end-user for using uncertified software, not Microsoft. MS put a program in place to avoid this (Windows certification), the end-user ignores it, and then it's someone else's fault when it breaks.
Yeah, I know, clicking 'do not monitor firewall' was real tough, took 6 clicks total.
I should go put ice on my mousing finger, so many clicks.
I mean, 6, wow, it like took forever.
Get a starbucks card and go crazy.
$100, that's like 15 cups of coffee now?
A well regulated militia, being necessary to the security of a free state, the right of the people to keep and bear arms, shall not be infringed.
Reads to me like you have the right to join a well regulated militia. Not the right for any yahoo to amass a stockpile of weapons and go on a shooting spree.
You can't watch you kids every single second of every day.
I'm a parent, and I CAN and WILL watch my kid every single second while on the Internet.
So don't tell me I suddenly need a new law that involves tearing up the constitution, just because you are incapable of installing your own blocking software.
Or google's never expiring tracking cookie. It aint there just for your "prefs."
Actually, I think it is. I ran an online service that required cookies. A cookie was set to expire one day after being set. So, what happened was a good 10% of the users had their clocks set wrong and would usually expire the cookie immediately, resulting in calls to customer service.
I tried setting it a day, week, month and year in the future, still had about 7%.
At that point, I just set it to 30 years in the future, that cut it to about 2 calls a month.
By the way, the average person who had their clock set wrong was off by YEARS. Think 2011 instead of 2001.
Now that people are upgrading to operating systems that auto set the time, this has become much less of a problem. If I were still running the system, I would go back to the 1 week timeframe in about a year or so.
XP is a point release, plain and simple.
Version 5.1 actually, if you want to be technical. Personally, I would have called it 5.5, but that's just me, some of the improvements in XP are pretty nice. I love the faster bootup time, for example.
Win98SE to ME was also a point release, but not a well thought out one. The biggest mistake was closing the 98 shell team at Microsoft and using the 2000 shell on 98 giving you Windows Me.
FYI: Project "Longhorn" should be Windows 6.0.
When using Windows you should always be behind a firewall
When shouldn't you be behind a firewall? With the exception of say, a WebTV, ALL operating systems should be behind a firewall.
Mac included.
Technically Google wouldn't be Google if it didn't use web-bots. There is no way they could maintain their current system manually and stay in business.
While practicality might not be a good excuse, running Google out of business would be a better one.
Under the DMCA, Google is protected, as long as they remove the offending data when asked to.
Why not just have all doctors work 20 hours a day 7 days a week? Even better yet, have YOUR doctor follow that schedule.
I like mine to have time off.
The on-call system is to allow doctors to work only when needed all hours of the day and night. That way they can get some time to themselves AFTER they work about 10 to 12 hours straight.
Your computer is broken.
I have no major problems with XP themes on a Dell Inspiron 7000. 500Mhz P3, 384MB RAM and ATI Rage mobility card. It works fine for web browsing, remote access and the occasional DVD movie playing.
Full disclosure of what?
DOS left Windows a while ago. NT on the business side and XP Home for the average Joe User.
No, your response was just 1 step away from the typical "OMG M$ IS TEH GHAY!!!".
Simply put, you couldn't resist taking a swipe at Microsoft, which leads back to the entire point of this article. That point being, not will Linux ever mature, but will Linux advocates ever mature.
Originally, the Southern State and the Southern Parkway were two different parkways. The state parkways were the Southern State Parkway, Northern State Parkway, Meadowbrook State Parkway, Wantagh state parkway, Bethpage State Parkway, Heckscher State Parkway, Sagtikos State Parkway and Sunken Meadow State Parkway.
People started dropping the 'state' name from the
parkway names in the early 60's. The signs started changing in the 80's and 90's to reflect the new names, but on paper, they remain the State Parkways.
The whole mess leads back to Robert Moses, who designed these parkways, again, just for park traffic. The original Meadowbrook and Wantagh didn't go past Sunrise highway. They were eventually extended to the Southern State and later the Northern State, to reduce traffic on local streets, but NEVER to the Long Island Expressway, as that would make the road a commuter road.
Robert Moses was in some ways a genius, and in other ways a total maniac.
The guy that made the original comment is just so full of himself.
Yeah, and typing WinDOS is a REAL mature response.
Windows doesn't really have a default API.
.NET will most likely wind up in this group with the longhorn release.
.NET apps to run about as fast as current Win32 apps. The average joe user won't know or care what API the software was designed for.
The Windows NT (2k/xp) kernel has the ability to use multiple APIs out of the box, with WIN32/Posix/OS2 1.x support built in.
This will allow
Amtrak has the same thing on most northeast corridor trains. The front cars are 'quiet cars'.
Personally, I want a cell jammer, a good 20 square foot 'cone of silence' would be great.
Windows2k uses the exact same drivers as XP yet is stable!
No, it doesn't. XP can use Windows 2000 drivers. 2000 can not use XP drivers.
Granted, there are not a lot of XP only drivers.
It's possible it was added in in later versions.
I have not used it much since 4.5. cfstoredprocedure never really worked well for me.
It would, but that's not what I wanted. All errors were fatal, including informative errors, it made EH inside the procedures impossible.
A simple example.
Insert record
If duplicate record error then update record instead
if other error throw exception
Now, a duplicate record would throw a fatal error to coldfusion. I could then catch that error in CF, but now I have to code for 2 possible outcomes, a fatal error that isn't fatal, and a fatal error that is fatal. At that point, you might as well split it into individual statements.
Not quite on topic, but, I once tried writing code in SQL (in this case for ColdFusion) by using stored procedures and exception handling.
What a nightmare.
Many people code unique inserts like this.
Check for duplicate record.
if not found, then insert.
else, prompt user.
Using exception handling, you code like this.
insert.
if error thrown, prompt user.
One less query, lots less code.
One problem, the web application language treated all db errors as fatal. When asked, I was told this was by design.
Thinking about it, I feel that Macromedia didn't want me to code efficiently. You don't sell extra ColdFusion servers if you can offload all your data logic to the SQL server. (Where it belongs)