One workaround is to plug the Kindle into the machine ... while the computer is sleeping.
I don’t know. My first wife hated that.
Rejected your download, did she? 
Posted on 08/25/2016 10:23:42 AM PDT by dayglored
BINGO
Thank You, VDK!!
One workaround is to plug the Kindle into the machine ... while the computer is sleeping.
I don’t know. My first wife hated that.
Rejected your download, did she?
I’ve got a USB equipped pet rock.
And still MS wonders why so many refuse to upgrade to Win10.
FWIW, my own Win10 machines haven't had the opportunity to get "Kindled", and won't, but I appreciate your info nonetheless for my users' sake.
Ummm, no they aren't.
Meltdowns aside, these sorts of errors show that responsible, effective Quality Assurance at Microsoft is a lost art.
In my opinion, the technical people were forced to keep to a release schedule for Anniversary because it had to come out on.... wait for it.... THE ANNIVERSARY. Marketing and upper management decreed it so, I'm certain.
Never mind that it wasn't ready.
THAT is why Microsoft deserves every bit of crap being thrown at them about Anniversary. It's a shambles and a travesty.
Microsoft used to be real good. I've used their products since the late 1970's continuously, and for the most part with satisfaction and good results. They used to be REALLY good. But they lost their mojo and this is no way to regain it.
I’m reading that Calibre syncs with Kindle Paper-White readers.
Well ok.
The expectation is that these companies can release complex software to run on thousands of brands and allow you to connect thousand more things to it without a single issue ever.
That is an utterly absurd expectation.
Every platform has had issues like this. People need to get a grip and stop pretending like MS has wronged them personally. Both the issues with Powershell and the Kindels, according to stories, are being addressed by MS, so people can stop overreacting like their lives are coming to an end.
Big difference.
I Use a paper White to duplicate non fiction books as reference, that don't need highlighter and/or marginal notes.
No.
That only works with Apple products
LOL!
Dear publius,
mazel tov! on your electronic achievements.
1. How good is the battery in that thing?
2. wha’ hoppen when dah lights get out fer daze? Kin y’all fill d’at back up agin?
3. How much did they soak you for that thing?
4. How much do you pay for particular services?
5. What happens if you drop it?
dear axe,
A person with a heart like mine.
That’s total crap.
There will ALWAYS be issues, in every piece of software and every operating system.
This is true for Linux, Apple and Microsoft.
I can’t even begin to tell you all the problems I have had to get a new Linux variant/release to accept hardware. Or maybe I’m making up the thousands of forums and user communities out there just for this purpose?
Microsoft, like Linux, has the same problem. These operating systems run on other people’s hardware, and just about any vendor’s hardware is different from the other. That’s 10s of thousands of hardware combinations. Some stuff will just never be pre-tested before deployment.
You work in IT and you know this. If deployment was easy (in both Linux and Microsoft realms), then many of us would be out of a job!
Bottom line, Microsoft’s “woes” with these issues in Windows 10 are NOTHING new. It happened in Windows 8.1, Windows Server 2012 and R2, Windows 8, Windows Server 2008 and R2, Windows 7, Windows Vista, Windows Server 2003, Windows XP, Windows 2000 Server and Professional, Windows Millennium Edition, Windows NT 4.0, Windows 98, Windows 95, Windows NT 3.5/1, and the Windows For Workgroups 3.11, 3.1, 3.0 2.0 and MS-DOS. I’ve been down this road on EVERY one of these operating systems.
Additionally, I’ve been working with Red Hat Linux since it was a baby, using RH 3.0. I’ve been using every version of RH Enterprise since that came out in 2002. On every occasion, I’ve had various issues to contend with, including kernel upgrades that “broke” them. It’s what we do for a living.
And Apple? Well, if you are the sole maker of both the hardware and the software, you can test the heck out of them. Then they “just work”, right?
Still, when Apple release a new version, there are tons of support issues getting that release to deploy properly then, with some folks finding older hardware or software not working, etc., and this is on the approved, made by Apple only hardware.
Bottom line here, Dayglored, is that New Microsoft OSs are always like this, and it is nothing new in Microsoft management like you claim. They’ve always been dollar driven A’Holes!
BTW, the PC came out in 1981. Unless you’re talking about BASIC (written for Altair’s), most folks wouldn’t have worked with Microsoft before IBM came out with the PC.
Well, good morning to you, too! :-)
> There will ALWAYS be issues, in every piece of software and every operating system. This is true for Linux, Apple and Microsoft.
Of course it is. No argument there. But that wasn't my point; you appear to have missed it, so I'll try to explain here, bear with me...
> I can’t even begin to tell you all the problems I have had to get a new Linux variant/release to accept hardware. Or maybe I’m making up the thousands of forums and user communities out there just for this purpose?
There are such forums and communities for all OSes and nearly all applications.
You might be interested to know that I've participated in such communities since 1976, first was the KIM-1 User Group. I helped answer folks' questions, traded hints, and had some of my early software applications published in the Newsletter. That was, ummm, 40 years ago -- you needn't attempt to lecture me on this topic. Instead I suggest you take a look at my FR Profile Page section which contains a brief timeline of my involvement with computers.
> Microsoft, like Linux, has the same problem. These operating systems run on other people’s hardware, and just about any vendor’s hardware is different from the other. That’s 10s of thousands of hardware combinations. Some stuff will just never be pre-tested before deployment. You work in IT and you know this. If deployment was easy (in both Linux and Microsoft realms), then many of us would be out of a job!
That's correct, to a degree. But I wasn't talking about the acknowledged difficulty of testing every single possible combination of S/w and H/W. I was speaking of these problems as being indicative of an attitude, common in upper management, of setting and holding to arbitrary release schedules, regardless of whether proper QA has been done on the product.
> Bottom line, Microsoft’s “woes” with these issues in Windows 10 are NOTHING new. It happened in Windows 8.1, Windows Server 2012 and R2, Windows 8, Windows Server 2008 and R2, Windows 7, Windows Vista, Windows Server 2003, Windows XP, Windows 2000 Server and Professional, Windows Millennium Edition, Windows NT 4.0, Windows 98, Windows 95, Windows NT 3.5/1, and the Windows For Workgroups 3.11, 3.1, 3.0 2.0 and MS-DOS. I’ve been down this road on EVERY one of these operating systems.
No argument, but since you're familiar with the whole line, I'll ask you to recall that a few times (notably in mid-late 90's) Microsoft has had to lay out and enforce a set of standards for what types of hardware and architectures Windows would run on -- and they were entirely correct to do so, because it had gotten so crazy. That was 20 years ago, vendors are used to the idea that they need to stick within guidelines to have Windows work on their systems.
My point was that those vendors made systems that ran Windows and worked with Windows -- and then Microsoft CHANGED the rules and BROKE things. That was my point. They screwed up on some very visible things, and they didn't catch their own mistakes. It had nothing to do with other vendors' systems being out of compliance.
> Additionally, I’ve been working with Red Hat Linux since it was a baby, using RH 3.0. I’ve been using every version of RH Enterprise since that came out in 2002. On every occasion, I’ve had various issues to contend with, including kernel upgrades that “broke” them. It’s what we do for a living.
Point granted, but RedHat (incidentally, my favorite Linux since about 2001) and Linux in general have taken a much looser approach by definition. They're a different sort of "product", indeed, with a few exceptions Linux wasn't even what I'd call a "product" (in the sense of a carefully defined and delineated offering) until only a few years ago.
In recent years, Canonical notwithstanding, Ubuntu has gone off the rails in this regard. Each new release makes changes for the sake of changes, breaking stuff, and it's driving me crazy because my main shop includes a few hundred Ubuntu "development" and "test/QA" systems, and keeping them from falling over after upgrades is a chore. They get no flowers from me.
> And Apple? Well, if you are the sole maker of both the hardware and the software, you can test the heck out of them. Then they “just work”, right? Still, when Apple release a new version, there are tons of support issues getting that release to deploy properly then, with some folks finding older hardware or software not working, etc., and this is on the approved, made by Apple only hardware.
Apple has NO excuse whatsoever, in my opinion, for such errors. As you say, they control the environment with an iron fist. Yet they still screw up occasionally, miss something in QA, and they have to fix things. I take Apple to task for that just like I do with Microsoft. It just happens that since I run the Windows Ping List here, my comments about MS are much more visible than my occasional comments on the Apple threads.
> Bottom line here, Dayglored, is that New Microsoft OSs are always like this, and it is nothing new in Microsoft management like you claim. They’ve always been dollar driven A’Holes!
Well, I'll agree up to a point... but then, they're supposedly a capitalist business, and their responsibilities include their stockholders. They have to be that way, to some degree.
> BTW, the PC came out in 1981. Unless you’re talking about BASIC (written for Altair’s), most folks wouldn’t have worked with Microsoft before IBM came out with the PC.
That's correct. A buddy of mine got a copy of MS BASIC for the 8080 and I was intrigued, so when I got my KIM-1, I got a copy of MS BASIC for the 6502 and with a bit of assembler for the I/O drivers, got it running in 1977. Again, my FR Profile has the timeline.
Thanks for the comments and chance for a bit of conversation -- I have to run now but I'll be back online tonight. Cheers!
If you'll allow me, I think your original rant was that Microsoft has taken a turn for the worse on Windows 10. My point is that it really hasn't. And, if you'll allow me, people SAY that about every major release, and then, when the NEXT release comes out they suddenly LOVE the earlier release and express disgust at Microsoft for "getting"--meaning NOW--shoddy, profit oriented, etc.
In other words, I'm saying I've heard this My point was that those vendors made systems that ran Windows and worked with Windows -- and then Microsoft CHANGED the rules and BROKE things. every single time.
The two biggest debacles, and these REALLY hurt when they occurred:
First occurrence was when Windows NT 4.0 Service Pack 2 came out--upon deploying, it is estimated that 25% of Windows NT 4.0 servers went belly up...
The second major occurrence was in 2006, when Microsoft came out with Windows Longhorn Beta 3 (soon to be Windows Vista), and they introduced the "Elevation of Privilege" concept that User Account Control uses in the new kernel, and the requirement that all 64 bit drivers had to be digitally signed. They introduced this in July 2006, with the RTM scheduled for October. That meant that manufactures had to, in many cases, completely rewrite their drivers in less then 3 months. Many, many were never done, and Microsoft's answer (from Ballmer) to this dilemma was to have the manufacturer tell users to get "newer" equipment that would work with Vista. Not that they'd fix Vista to make it work with everyone's equipment.
I'm still shaky from that one. These were much worse than a Kindle causing a blue screen, IMHO. They affected millions more people and thousands of enterprise-level businesses.
Now, you know I am a Microsoft MVP, but I am still ashamed of them over these types of issues, including Windows 10. One advantage I have though is I can speak directly to the product groups and let them know people are pissed and they've screwed up. Believe me, I have done a lot of that this year. I don't renew until next year, but at the rate I'm going, they probably WON'T renew me! ;-)
> I think your original rant was that Microsoft has taken a turn for the worse on Windows 10. My point is that it really hasn't.
Actually, my rant was that their QA -- testing prior to release -- had taken a turn for the worse on Windows 10. Not the underlying product itself; Win10 is actually pretty good.
This Ars Technica I ran across this morning seems to say it well: http://arstechnica.com/information-technology/2016/08/kindle-crashes-and-broken-powershell-something-isnt-right-with-windows-10-testing/
I agree that every version / release of Windows has has problems (like every OS) and that your observation that "people SAY that about every major release, and then, when the NEXT release comes out they suddenly LOVE the earlier release and express disgust at Microsoft for "getting"--meaning NOW--shoddy, profit oriented, etc." is likewise accurate.
My rant was directed at what I perceive as a repeat of an unfortunate occurrence that was manifest in the past mainly in WinME (and to a lesser extent in Vista) where the incompatibilities and instabilities were SO bad it was like they did it on purpose. [tinfoil_hat] Incidentally I actually DO believe they intentionally broke WinME, so that as the last of the DOS-based Windows, users would be more inclined to try out and switch over to the NT-based Win2K. [/tinfoil_hat]
Longhorn/Vista was so many years late, so it's unfathomable that they wanted to break it, and I cut them slack for intentions there. OTOH, Vista was not well suited to the existing hardware of the times and was a considerable overreach in terms of the UI (Aero, etc.). Win7 fixed all that, extremely well IMO. Your description of the troubles caused by UAC and digital signing is right on.
So, I don't disagree with most of what you wrote, and I appreciate your in-depth explication. Let's hope that MS can rapidly tune up their processes and keep the Win10 ball rolling. There's a changing marketplace out there and they need to stay relevant to survive.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.