The problem is that these are small vendors they don’t even want to deal
with Microsoft on this stuff, and the few that have get quotes for deals
involving buying orders of magnitudes more licenses than they want. They
need a full PC, and in many cases their customer is the one who is buying
it. I have one client who is trying Windows 10, but finds that many of
updates break their software (then fix it with the next update) of course
the problem is that when the software breaks their clients mess up parts
that easily cost of $100,000 a piece,
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 Scott Noone
Sent: Wednesday, September 14, 2016 2:57 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] [windbg] 1394 on Win10
While it might seem counter intuitive, network is simply less convenient for
us . I don’t want my test system on my private LAN and I usually don’t even
want it connected to the internet (especially when I don’t want to fight
with WU running while I’m trying to get my code working). The only saving
grace is that the 1394 bits (will eventually) still be available, which just
means an extra step when configuring test machines.
Shouldn’t they be on an LTSB? IoT Enterprise should have a much longer
update cycle.
-scott
OSR
@OSRDrivers
“Don Burn” wrote in message news:xxxxx@ntdev…
+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:
—
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:></http:></http:></http:>