Message from @Eccles

Discord ID: 679342134175727626


2020-02-18 14:50:47 UTC  

How have the poor spec. What you mean is you ran the Compatibility software and it said you could you did and it broke

2020-02-18 14:52:13 UTC  

Sorry bad sentence cba re writing

2020-02-18 14:52:27 UTC  

Yes, on 3 of 5 devices I have at home, and at work, about 30% of their entire PC fleet is manually limited to 1709 because 1803+ won't work

2020-02-18 14:53:45 UTC  

I don't know what 1709 and 1803+ are I assume sockets?

2020-02-18 14:53:56 UTC  

no, versions of windows 10

2020-02-18 14:54:41 UTC  

Oh Are they mobile devices arm devices, or intel amd devices

2020-02-18 14:55:19 UTC  

work devices are all intel bog standard platforms from dell

2020-02-18 14:55:27 UTC  

home devices are a mix of intel and amd

2020-02-18 14:56:08 UTC  

I update windows whenever it wants, I had an issue once in 4 years of using windows 10

2020-02-18 14:56:31 UTC  

well like i said, this is an issue for legacy hardware

2020-02-18 14:58:03 UTC  

I don't think that's microsoft's fault though, they provide a greater freedom to the user in terms of hardware they can't compatibility check every piece of hardware

2020-02-18 14:58:05 UTC  

Lol, we still have Window 7 on some machines

2020-02-18 14:58:15 UTC  

Let alone versions of WX

2020-02-18 15:00:24 UTC  

I am arguing from a personal consumer point not an enterprise consumer point of view. Microsoft's business model is an improvement, since going to Windows 10, but that is my personal opinion unfortunately.

2020-02-18 15:00:47 UTC  

yes they can, farrongoth, they can run your hardware id's against their database and see if they're compatible - it would be trivial

2020-02-18 15:01:13 UTC  

it's different

2020-02-18 15:01:20 UTC  

Yeah but they have to have tested that hardware.

2020-02-18 15:01:46 UTC  

it only has to be in their driver db

2020-02-18 15:02:23 UTC  

The compitability checks CPU architecture ram and storage I'm pretty sure it doesn't check hardware at all

2020-02-18 15:03:01 UTC  

it doesn't, but it needs to

2020-02-18 15:03:06 UTC  

it'd solve all the remaining problems

2020-02-18 15:03:21 UTC  

You are right they could if they wanted to. They do to some degree because it installs drivers for most things automatically although you can almost always install better drivers

2020-02-18 15:03:46 UTC  

That's been true since XP tho

2020-02-18 15:04:24 UTC  

difference being service packs for xp didn't remove hardware support and therefore break existing installs

2020-02-18 15:04:49 UTC  

which is my contention with windows 10 🙂

2020-02-18 15:05:10 UTC  

I don't think windows 10 does, tbh but I cba scouring the internet to find out if it is the case

2020-02-18 15:05:47 UTC  

it is the case

2020-02-18 15:07:18 UTC  

Manufacturers tend to provide drivers not microsoft themself I'm pretty sure.

2020-02-18 15:07:53 UTC  

not on legacy hardware they don't

2020-02-18 15:08:14 UTC  

and it wouldn't be much help if the feature update physically cannot install

2020-02-18 15:08:36 UTC  

Okay

2020-02-18 15:10:06 UTC  

like i said, they can fix this by creating a much better compatibility checker tool - one that actually -checks- compatibility of hardware rather than just checking free disk space, cpu speed, and ram size, and then not forcing incompatible feature updates on people that don't work

2020-02-18 15:10:35 UTC  

I agree with the first part.

2020-02-18 15:10:41 UTC  

Pretty sure the second part isn't true

2020-02-18 15:10:45 UTC  

xp was probably the best OS from Windows

2020-02-18 15:11:14 UTC  

That's an easy stance to take

2020-02-18 15:11:15 UTC  

last of the 'small' OS'

2020-02-18 15:11:29 UTC  

wasnt a resorce whore

2020-02-18 15:11:44 UTC  

and Vista came next which made it look epic 😂

2020-02-18 15:11:47 UTC  

It definitely is true 🙂

2020-02-18 15:12:16 UTC  

the RAM jump alone was crippling for a lot of people