From the [windbg] list:
Scott Noone wrote:
1394 debugging has been removed from Windows, focus is switching over to
network debugging. You will eventually need to get the 1394 bits from the
SDK, current workaround is to find them elsewhere:
You know, I’ve always been pretty much of a Microsoft “fan boy”, as some
on this would list put it. Being an MVP for 22 consecutive years
attests to that. But I have to say, I’m really starting to develop an
attitude. Many of the decisions made during the short lifetime of
Windows 10 seem to be short-sighted and unnecessarily hostile towards
developers and users. Our big telemetry project is migrating its data
analysis engine from Windows to Linux, largely because we no longer feel
like we are in control of our own computers.
I don’t like the direction Windows is going.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
+1
About a third of my clients are seriously looking at ending Windows support
of their products before they are forced to go to Windows 10. If nothing
else the Windows Update cycle of four months makes it impossible for them to
get certification of their system (things like medical devices, telecom, and
casino gaming have longer cycles than Windows allows).
Don Burn
Windows Driver Consulting
Website: http://www.windrvr.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Tim Roberts
Sent: Wednesday, September 14, 2016 1:42 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Was: [windbg] 1394 on Win10
From the [windbg] list:
Scott Noone wrote:
> 1394 debugging has been removed from Windows, focus is switching over
> to network debugging. You will eventually need to get the 1394 bits
> from the SDK, current workaround is to find them elsewhere:
You know, I’ve always been pretty much of a Microsoft “fan boy”, as some on
this would list put it. Being an MVP for 22 consecutive years attests to
that. But I have to say, I’m really starting to develop an attitude. Many
of the decisions made during the short lifetime of Windows 10 seem to be
short-sighted and unnecessarily hostile towards developers and users. Our
big telemetry project is migrating its data analysis engine from Windows to
Linux, largely because we no longer feel like we are in control of our own
computers.
I don’t like the direction Windows is going.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
—
NTDEV is sponsored by OSR
Visit the list online at:
http:
MONTHLY seminars on crash dump analysis, WDF, Windows internals and software
drivers!
Details at http:
To unsubscribe, visit the List Server section of OSR Online at
http:</http:></http:></http:>
>I’ve always been pretty much of a Microsoft “fan boy”, as some on this would list put it.
It looks like now we have not only “Windows fanboy” but “Windows fan boy” as well
(i.e. pretty much the same way we have both “MM” and "m m " posters on this list)…
BTW, once we are at it, I just wonder what happened to Max( a.k.a “Windows fanboy”) - incredibly enough, he has not posted for almost two months(!!!). To be honest, I miss his posts quite a lot - after all, where else would I find out about the “right-wing liberals” with Pat Buchanan in a lead, about Stalin having had been sort of a good bloke, about MSFT Exchange being the best software title anywhere in the observable universe, about the “tame calve sucking from two mothers”, and many other"exciting" things. Where are you,Max?
Anton Bassov
If this is what they believe, somebody should explain to them how the Windows 10 servicing plan works.
I’m not saying it’s simple, but I’m saying that there are CBB and Enterprise LTSB branches for a reason. Enterprise LTSB has support for at least 10 years after release. For embedded systems (like on medical devices) Enterprise IoT allows you to control (and effectively disable) the delivery of updates.
Enterprise LTSB is really the answer to a lot of “I don’t want all the churn, I want something that’ll work virtually forever, I don’t want stupid shit like Microsoft Sports and News on my user’s PCs, and Cortana is an absolute no-go.”
In my experience, one of the biggest problems with Windows 10 is the extent of the changes (in everything from UI to release strategy) coupled with the serious lack of clear, concise, communication about some of these changes from Redmond.
For anyone who’s sufficiently motivated, there’s a good (if very long) write-up of the Windows 10 Servicing options at:
https:
Peter
OSR
@OSRDrivers</https:>