I fail to see how an alleged forced reboot that was probably not even the fault of Windows directly is somehow breaking medical software on a remote computer. But this is a nice case of the LYSE way again. Blame Windows for the crash of some crap software that isn’t even related at all to MS.
ChristX: yes, indeed. I’m usually quite verbose. In this case, I just felt like dunking my head in a bucket of ice water and driving up to Manchester to practice my l33t nuclear wedgie skillz.
Comments
Unbelievable. I like how he neglects to to mention the millions of lives that are saved on those same machines people depend on.
If Linux had 95% of the market, you can bet there’d be identical issues.
Convenient how he doesn’t think to blame the hospital IT staff for not taking measures to prevent the virus.
Oh wow. Missed this one. Good catch.
Well, that’s it. I’m never gonna submit another FUD article again. This one just can’t be topped!
I fail to see how an alleged forced reboot that was probably not even the fault of Windows directly is somehow breaking medical software on a remote computer. But this is a nice case of the LYSE way again. Blame Windows for the crash of some crap software that isn’t even related at all to MS.
Freetard logic:
I forgot to tell the people at the drive-through that I don’t want mayo, so they put it on. They’re after ma freedomz!!
ChristX: yes, indeed. I’m usually quite verbose. In this case, I just felt like dunking my head in a bucket of ice water and driving up to Manchester to practice my l33t nuclear wedgie skillz.
You must be signed in to leave comments.