Some of you really don't want Windows 10's April 2018 update on your rigs

Re: Not my fault you can't use it right.

@Updraft102 said:

Worst. Pop. Culture. Reference. Ever.

LOL, I thought that might sting a bit, but in your case it really really shows.

It's still true though, no matter how much you don't like to hear it.

Re: Not my fault you can't use it right.

the really REALLY annoying thing about MS is that they already offer decent versions of their OS. Remeber Vista and the shitness? Look at server 2008, server 2008 was awesome. It had a start menu, proper search, no telemetry. And its still supported now. 2008r2 (windows 7) just just 2008 with more goodies.

windows 8? Apart from the stupid way to reboot or search from rdp server 2012 just worked. It had a fully functional and working backup, desktop and control panel.

8.1 made 2012r2: gone was the silly rdp swipe to edges andnit booted to desktop. yey.

come windows 10, server 2016 is perfectly usable. Sure the start menu is a bit 'flat' but thats the only real gripe. It is similar to LTSB in a way.

The server iterations show what CAN be done with the OS. MS choose not to offer those "skins" though.

Re: Not my fault you can't use it right.

If they're trying Linux for the first time, and Linux doesn't yet support their hardware,

Then get them to email me their time machine. its not 1999 any more.

These days its far more likely Windows doesn't support their hardware.

Re: Not my fault you can't use it right.

@ Esme

I work in IT as a systems analyst and do a bit of 1st line/3rd line support as needed.

I can see you are not really recently experienced with the true state of hardware found INSIDE laptops these days.

After reinstalling windows via the method of the manufacturer (not necessarily talking about big guys like Dell etc) you find that half the hardware wont work because the stuff they put inside is non-standard enough for windows (8.1 and 10 are used) to not locate a driver automatically via windows update.

So, you go and try to use the vendors driver disc that has ancient and possibly buggy drivers that caused you to reinstall in the first place as recommended you do so by kind windowsy support peeps you found in the internet. This disc, hopefully you did not throw away. Hopefully the vendor provided you with the disc and you dont need to download it.

Hopefully the disc contains just the drivers you need, and not ones for other laptops that throw up errors when you try to install them causing you to talk to the same nice windowsy peeps who will tell you to either reinstall/refresh windows again or to open up device manager (good luck finding that) and googling the PCI hardware ID of the device to locate a device driver.

A device driver that is not provided from the original manufacturer because they are chinese and only make the chip, not the PCB and rely of the laptop vendor to provide drivers, which they may not do so without proof of purchase (pc specialist, I'm looking at you) which you dont have any more leaving you t wonder why you didnt just buy that ASUS machine, as they have a driver for the same PCI hardware ID but it wont install because you are not using an ASUS.

If hardware dont work in Linux, its so much simpler! Its either not going to work for a while or never will. None of this faffing about trying to get something working again only to discover that it having worked at all the first time round was simply a miracle.

Imagine if your TV remote stopped working due to dead batteries. You go and get batteries for it to find that it uses a non-standard size that nobody stocks but some guy from china on ebay can get you one for more than the cost of a universal remote that stakes standard AA's. So you get the universal remote to find that it wont work with your TV but only with the previous model as the codes changed.

You discover that the codes were added later and can be uploaded to your remote!

So you download the update, run it to be told that there is an error. You google the error to find you need to install .Net 3.5 whoch requires running DISM from the command line and having a valid windows install disc...

I think I've made my point about the state of windows driver support vs linux. It can be a load of shit no matter which OS you are using. Your point is moot.

Re: Not my fault you can't use it right.

(Shrugs) if you want to use brand new hardware that doesn't yet have Linux drivers, yes, you;re going to be better off using it with Windows. And this is a surprise because..?

Define "brand new" though.

AMD's recent graphics cards (and by "recent" I mean "two years since launch" - to be specific I have a Polaris 10 card) still don't have HDMI audio in most Linux distributions, because AMD only managed to get that included in kernel 4.13 and many distributions, including the very latest OpenSuse, released at the end of May this year, are still using older kernels.

For that reason my machine which has the Polaris card in it had to be migrated from the pretty rock solid "Leap" distributions of OpenSuse to the usually ok, but when it occasionally breaks it's a biggie, "Tumbleweed" distribution, which keeps fairly up-to-date with the kernels.

In theory I could have installed the proprietary AMDGPU-PRO, but I tried that and failed several times. In Windows? Download the driver and run it. Job done.

M.