Re: Samba can disable SMB1 as well
" but the loyalty that XP still seems to have (especially seen as though XP was a pain in the arse) baffles me."
Time to do some hard thinking.
Imagine you have some extremely expensive piece of kit, say a million or so of your favoured currency units. When bought it had a projected life of 20 years. A replacement would cost at least 50% more than the original, isn't in your budget and not likely to be within the next few years.
This very expensive item is working hard. You can't afford not to have it. But it's controlled by software written for XP. It's proprietary code and you don't have source. The company that wrote it is long gone. There's a regulatory requirement that the entire installation have a specific certification which the original installation has.
Do you
(a) kill the PC because it's running XP, scrap the kit which is no longer able to work because you can't run the S/W, close down the service you were providing with it and sit on you backside doing nothing for several years until you can afford to replace it?
(b) reverse engineer the S/W kill the PC, get the program rewritten for a different OS and in the meantime close down the service you were providing and sit on your backside soing nothing whilst the program is rewritten and recertified at considerable expense over the course of a year or so?
(c) protect the PC from the net and carry on?
Are you still baffled?