Re: I Just Don't Understand
Nope. I'm so sorry that it bothers you that I refuse to piss and moan about problems I'm not having.
81 posts • joined 20 Sep 2015
Features and functions reported as being "broken" in the 1809 update work properly on my Windows 10 x64 install.* I'm following the steps people claim to fail or break, and there's just no problem. There hasn't been any problem with updates/patches since I installed Windows 10 on three computers (a desktop, laptop, and tablet) the first or second day it was released. As I've said before, I'm using the same bits as other people so I cannot for the life of me understand why failures are being reported when I never see them.
I am NOT saying this in an effort to refute the claims, but rather to suggest that perhaps some other fault may be involved.
*I want to note that I do not use some of the software said to be experiencing problems, such as iCloud or Windows Media Player. However, I can associate file extensions with any Windows app that I want all day long and it works as it is supposed to work (as one example.)
Windows users will put up with *anything* and they simply don't believe that other systems can run for multiple years without a single problem.
I haven't had an issue on a Windows machine since 1998 that wasn't caused by a hardware problem. That was the last time I got a BSOD, which is why the date stands out. So I have no idea what you are going on about.
I've been using Windows 10 since the day after it's initial release. The problems I've experienced have been:
1. None at all.
2. See 1.
Please don't bother to tell me how "lucky" I am. I'm using the same bits as everyone else. NO broken updates, NO update interruptions (I tell Windows to perform the updates in the middle of the night when I'm sleeping), NO issues with application software, NO BSODs, a faster UI, and frankly, I couldn't care less concerning someone else's opinion of what the interface should look like. Every piece of hardware I use has worked flawlessly with Windows 10.
If the above offends you, tough.
I was visited by a couple of ATT representatives who informed me that fiber was available for my home (ATT had been digging and burying fiber lines for about three months). I asked a few questions: Was it fiber all the way to the modem, and what were the upload/download speeds I could expect, and what was the cost. I was told that it was fiber to copper at the "box" on the outside of my house but I could expect gigabit speed down and about 750Mbs up. The cost would be the same as my current service.
The actual installation was all fiber to the modem and gig down and gig up, which I verified using a wired connection to a computer. The installation was free, the connection is unlimited, and costs the same as my previous 45Mbs, including five static IP addresses. I'm not complaining.
@ Christian Berger:
Your description of the halting problem didn't sound right to me...
"The halting problem is the problem of determining, from a description of an arbitrary computer program and an input, whether the program will finish running or continue to run forever."
"I regarded Win9x and ME as game consoles. Never sold or installed them for business."
All I have to say about it is this: Back in the 90's I was a support tech for Windows at Microsoft, first-line support as it's called. I "graduated" to the Premier Support group after awhile, meaning that my team provided phone support for customers paying for it. Fortune 500 companies, smaller-but-still-quite-large companies, occasionally a rich person who was showing-off. I took thousands of calls from businesses. I supported Windows 95, 98, 98SE, and ME. All business, all the time. And I will just mention that the vast majority of calls were exactly the same kind as for free support, and most of the rest were just barely more challenging.
This dredged-up an old memory of mine: Back in the late '70s I was seated at a private dinner with a guest who a missile officer on a US ballistic-missile submarine. I tried to question him about nukes, the ONLY thing he would confirm for me was that the Little Boy bomb functioned by jamming two masses of uranium-235 together. I was disappointed (physics major in college) but I understood that he was sworn to secrecy. Imagine my surprise when, in reply to someone else's question about politics and nukes, he said, "We all know that maybe one in ten H-bombs will go off." I have no reason to think that he made a deliberate mis-statment, because there would be no point in doing so. He said no further word that evening concerning anything other than sports. He did take me to one side as he was leaving and said, sotto vocce, "We never had that conversation. Right?"
MSGrrrrl: I saw this when I Googled it: "It's thus worth adding that the Windows 10 technical preview has these requirements". The articles below this say that the Windows Acccount and Internet Connection were not required in the release version of Windows 10.
Slight confusion, perhaps not really Microsoft's fault, but the user's for not reading the first article properly or completely.
Amazingly enough, I've actually built a paintball Gatling gun. It's not belt-fed, but feeds from a "powered magazine" to keep stuffing paintballs into the gun as fast as it can fire. Got it up to 6000 paintballs/minute but then realized just how many paintballs I was going through--it gets expensive after a few minutes.
It's been so long since I've seen a BSOD on a Windows box that it took me a few seconds to remember what a BSOD is. The last time I had one was when I installed some defective "brand new" memory--around about 1999, or maybe 2000 (memtest confirmed the problem for me). After that happened, I kept a small spare machine around just for testing new hardware of any kind, or for testing older hardware that seemed to have failed.
The closest I've come to such a problem was a few months ago, after updating my video driver. A resizing operation inside of Photoshop suddenly starting failing, but at least I got a nice clear message that the problem was, in fact, in the video driver. Not really a crash, more of an inability to perform the operation. Rolled-back the driver and was fine.
When I worked for Microsoft years ago, I had several occasions to meet Bill Gates at after-presentation lunches, and such. At one lunch, I saw him standing in the middle of a circle of middle-management-to-peon (like me) people, answering questions, all of which were tech or tech industry related. I walked through the circle--no one was closer than about six feet to him--shook hands with Bill, and asked him how he was doing. We chatted for a moment, then I asked how his wife was doing (pregnant with his first), if they knew the sex of the baby, and that sort of thing. I could see him switch gears, and he smiled as he answered my admittedly-personal questions.
When I left him, I was inwardly pleased by the looks I got from the other people. Perhaps, like many others, they didn't really believe that Bill was human, with human feelings. Of course, they hadn't made much effort to find out...
Well, maybe you're right. But why aren't the hundreds of millions of Linux and other non-Windows operating systems users not purchasing printers? The sales of printers fell even further than that of PCs in percentage terms. Are Linux, etc., users not buying printers either?
Or are people buying other brands of printers, just not HP printers, perhaps? I don't know... it's a question, not a comment.
Curiously enough, from reading about this event on several blogs, the Linux Mint website was hacked, restored, and then hacked again. The website is offline as I write, while the Mint people work on the server.
I downloaded the KDE 17.3 version of Mint because the 17.3 Cinnamon package wasn't ready at the time, but I couldn't make it work. I was thinking about downloading Cinnamon yesterday but didn't get around to it, and for once my laziness paid off. Although I'm still planning to get Mint and try again.
What's that? you say.
It's somewhat surprising that everyone (I think) has missed the obvious. The UK government doesn't expect this plan to work and never did. What they do expect is that that they will pick up goodwill points for being anti-pornography and for saving-the-children, plus maybe some extra shine by successfully prosecuting a few sites. These are the things that matter to career politicians.
could have written this article after being told nothing more than the name of the department in charge of the firewall, although he/she might not have gotten the statistics exactly right.* That would apply to a British version as well.
*The only surprising information is that the firewall caught as much as 29% of the intrusions. I'd have guessed somewhere in the 6-9% range.
Richard, perhaps I wasn't clear in my post: I was not saying that there ought to be some way of making the detachable cabin idea work. What I was trying to say is that there might be some other way of saving the passengers that would work. Especially for controlled flight into terrain--whatever happened to things like avoidance radar, and so forth, to force the aircraft to avoid flying into a mountain or the ground? It doesn't/won't work? Too expensive? I don't know. The basic construction of an airliner doesn't seem to be much different now than it was 50 years ago, but I'm not an aeronautical engineer and I may be very mistaken.
Having been a passenger on an aircraft that came 'way too close to crashing, and having talked with a couple of people who survived an air crash (Eastern Air Lines Flight 401), I can tell you that the last thing passengers consider as the end approaches is "Wow, this doesn't happen very often!"
The basic objection to any kind of bulk rescue is cost. The article makes this point many times. It would be nice, if, rather than throwing out the entire concept, someone with the know-how came up with some way of doing it that would be acceptable.
Years ago, the company I worked-for had a microcomputer (16-bit, though) running Xenix and a package of Business BASIC applications. The system ran nicely but one day we got a warning that the disk drive was nearly full. Business being good, too much of the drive was active to be backed to tape, and the computer itself could not handle a larger drive. Sooo... we bought a new computer with a larger drive, and I committed myself to transfer the data from the old drive to the new one. The only good way to do it was to write programs to dump the data over an RS-232 connection, accept it, and write it to the new drive. In itself, not too big a deal. We set the transfer date to a holiday, July 4th, when I would come in, finish the programs, and start the transfer.
Came July 4 and I was feeling awful... just terrible. I dragged myself to the office anyway and worked on the "acceptor" code until I simply couldn't do it any longer, but I thought I had finished it and the transfer wouldn't take more than a few hours. I went home, then dragged myself back into the office the next day with a temperature of 104F and tried to start the transfer. The data was making it's way down the RS-232 line but was being scrambled on the disk, so I started going through the "acceptor" code. I found things like:
IT (blijk(i) <+ feemble} TENH GOOT ++++;
Utter gibberish. The second half of the program was ALL gibberish. Apparently I wasn't able to write comprehensible code with a temperature of 104 or higher. I finally gave up trying to fix it, bailed out of the office until my fever went down, then returned to write the code properly and run the transfer--which worked fine afterwards.
Biting the hand that feeds IT © 1998–2019