The comments contain this gold nugget: TaxiZaphod said: I'm not sure which is more newsworthy: that a Hisense TV borked a user's Windows PC, or that a thread on the Microsoft support forums actually contained useful information. Our Forgotten Astronomy | Object Oriented Programming with C++ | Wordle solver

Can it core a apple? (Chef of the future.) The difficult we do right away... ...the impossible takes slightly longer.

Soon? It already is.

I'd go so far as to say, not needed for any reason.

[sips beer] ...and you were expecting...? cheers Chris Maunder

I seem to remember this promise with XP SP3, Windows 7, and Windows 8. However, there really are fewer patches requiring a reboot each month. The problem is there is still one patch that requires it each month.

That was the original idea: a single centralized depository for all config info. So it grew and grew, and bloated massively, slowed down everything and became a source of problems because there was no defined (or enforceable) separation of App A info from App B, much less system related info. It also added a route by which trojans could inject themselves into other apps very simply by modifying the config info. So it became depreciated as a centralized store for new apps because of the problems it caused, and security features evolved as UAC was introduced which deliberately made it harder to use. Those continue to become more restrictive as the OS evolves - at some point it will probably become off limits to all non-admin apps (it's only not at present for backward compatibility with legacy applications). If it had been designed as a sandbox environment in the first place, it could have been a really useful secure store - but it never was and that lack of foresight shows in the zombie version we currently have! :D "I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!

Richard MacCutchan wrote: The problem is not due to Dave's comments, but rather the developers' failure (or is that refusal) to make use of official documentation. Or, the problem is that when some experienced programmer states "The limit IS 260 characters!" (and that is just a fact), the inexperienced programmer sees no need to go to the official documentation to learn that the experienced programmer had given him incorrect information 'just to be on the safe side'. I willingly admit that when a mate tells me how to do something, or how I can not do it (e.g. using longer paths), I frequently take that as a valid piece of information. I do not always verify against the official documentation every piece of information or every advise I receive. Maybe I should, but that would take a lot of time. I allow myself to learn from others. Religious freedom is the freedom to say that two plus two make five.

Not all projects, but I think that in average/median you are right. P.S. About the "edit"... sorry, it was me with lack of :java::java: clicking the wrong widget when answering back M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.

I still have an ME installer that I never used all legal OEM copy some where.

I might be one of the rare guys that has never used it (yet) M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.

power shell is an abort***. It's like they took ms-dos, smoked a crap load of crack and then came up with the "language". Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.

Not everybody wants to work with the cloud, a few of my customers ask to avoid it specifically in their contracts given the confidential nature of their software. I work for my customers since 1998, they are happy with what they get from me (which is an excellent service as they deserve). My customers have a weekly copy of their software (or in the worst case at the end of the project, because they decide to go this way). Copy #1. I have a NAS at the office (multiple disks with RAID 10). Copy #2. All is inside my laptop (of course fully encrypted). Copy #3. And of course, the backups are rotating monthly in different places. Copy #4 (which in fact is #4 and #5 as I rotate the building where those backups are placed every month). When I said I didn't know how to do it, I meant, I don't know how to send multiple GB of data daily to the cloud, just because it would not be enough time to send all that every single night. I can do incremental backups and... yes... maybe being older gives me the experience of having an incremental backup unusable because one of the tapes decided to fail, making it impossible to recover something. So no, thanks. If all my customers, my NAS my laptop, and the external location where the rotated HDD lays burns at the same time (or get a super-massive power surge), maybe we would be facing the WWIII and then I would not really be worried for that except to spend time with my wonderful wife (maybe in the cloud already / the real one). Hope it is clearer now, but in any case, I wanted help to choose a server... which maybe it won't be needed after all as it seems Odoo could work even in my NAS, let's cross fingers and hope this will work. Thanks for your post Bruno. www.robotecnik.com[^] - robots, CNC and PLC programming

The texture of open data, does commence, as dudgeon, of event driven.

It takes them this long to figure out how to upload all the secure passwords and keys using their security on every update... :-D