OK morning rant from yesterday.

Get into the venue, connect my surface to the dock, keyboard won't work.
Try more USB ports, try another machine, keyboard (corsair k70) is totally broken.

Ugh.
Fine.

Disassemble keyboard, someone asks me a question, turn around and knock full coffee cup over my surface book.

Fuck sake.
Now I need a new laptop.

How the hell can people actually WORK with these ultra slim ultrabooks with no ports?? My laptop is getting used like a cheap whore at a bachelors party...

Sometimes, I really fucking hate Windows.

Having trialled Linux for a week on a spare HDD, I wanted to move to a proper dual boot with Windows on my SSD, and I decided I may as well downgrade to Windows 7 at the same time (10 had started to really annoy me).

Booting into the initial USB yielded an unresponsive mouse and keyboard. Hmm, not a great start. Turns out the Windows install USB doesn't like the rear USB ports or the wireless mouse. Strange but plugged in a spare USB mouse into the front and could install Windows.

This install was very unhappy about not having SP1 - to the point where I couldn't even install the network drivers so I could download SP1. Fine, I just downloaded an ISO with SP1 on my Mac.

Then I discovered that you can only really make a Windows USB with Windows. But I've just removed both my Windows and Linux partitions so I can reinstall them ...

After hours of searching and trying to create a bootable USB on my Mac, I finally give up and install a trial of Parallels. So I ended up using the same ISO to install a VM of Windows on my Mac, so I can create a bootable USB, so I can install Windows on my desktop. Well done Microsoft ...

And then I needed to install various drivers for the install to be even remotely useable.

To top it all off: Linux just worked. The keyboard and wireless mouse worked when installing. I didn't need to do any additional set up to be able to use it all. It can even use all 3 monitors, rather than just the 2 that Windows recognises for some bizarre reason.

Thanks to Windows being special, I've lost a day of productivity 😡

Built a C#/.NET application with support for a serial device. Tested it on systems A, B, C initially, all Windows system, same .NET version, same targeting, same build tool version, same initial connection configuration etc, etc.

Testing - works on A and C, B nopes.
...
OK, let's check the source, is there something about B that makes it impossible to execute that bit? - No, there is not, you checked that already, stop poking around, it definitively should work on B.
...
OK, maybe admin privileges, there is I/O involved, didn't need that on A and C, but who knows - nope, doesn't work on B.
...
OK, maybe something wrong with the connection settings? First try at reinstalling driver - but no, it doesn't work on B.
...
OK let's try with another device - more/less devices on B. Other USB ports. No. Still does not work on B.
...
OK, this is stupid, but, is the cabling alright? It is, of course it is, stupid - but it still does not work on B.
...
OK, at that point I'm just gonna ask a colleague, GrumpySoftwareDev whether he has any clue why it doesn't work on B. GrumpySoftwareDev knows nothing, but discovers that one of his applications doesn't work on Windows 10. You know nothing, Jon Snow, but it doesn't work on B.
...
OK, now I'm just going to ask another colleague TheLastOfHisKind who handed B down to me somewhat bluntly if he ever experienced problems when working with B and its serial configuration. TheLastOfHisKind tells me he does not and kindly offers me some input on the situation. Still no progress to get it working on B but he hinted he might have fucked up B's driver. I already reinstalled the driver but didn't reboot, which comes after reinstall.
...
OK, I'm just gonna remove and re-install the driver, then restart. Hu! Now the UI is gone but another serial device reacted on a general call. Not fully working on B but we're getting there.
...
OK, I don't know, I'm getting frustrated, let's borrow another system D - which has roughly the same configuration as B - from my colleague StrongCurrentGuy. StrongCurrentGuy borrows me his system and cautions me not to break it. I install the driver, plug the device and copy the application from B. It just works on D. Not on B though.
...
OK, you know what. I'm done. For shits and giggles I'm gonna remove that driver again, reinstall it and restart, maybe it'll magically work afterwar- WHAT THE HELL, I JUST OPENED IT AFTER RESTARTING, IT JUST WORKS - ON B!

... seriously, what the fuck. But yeah, at least it works now.

The recent USB C/ no headphone-jack rant inspired me a bit and I noticed that two USB C ports might be a solution for me in regards to the headphone debate.
I'd still need a dongle for my headphones, but I can still charge.
Maybe I could get a audiophile grade dongle make myself def, that be great.

It would also be kind of useful for other stuff, you can't have enough usb ports on any device.

And then I started looking into that topic.

WTF one plus! Why did you make my op 3T USB 2.0 in type C !!!????

I'm not that stupid though. I know there are reasons, but this just upsets me, 3.0 at least please!

What is missing for you that you could use your phone instead of a PC for the most workloads of use-cases?

For me it's two high speed usb C ports with display connect capabilities + periferals.

I currently think that it would be a great thing to move most Noob users off their pcs onto their smartphones for that purpose.

So as a personal project for work I decided to start data logging facility variables, it's something that we might need to pickup at some point in the future so decided to take the initiative since I'm the new guy.
I setup some basic current loop sensors are things like gas line pressures for bulk nitrogen and compressed air but decided to go with a more advanced system for logging the temperature and humidity in the labs. These sensors come with 'software' it's a web site you host internally. Cool so I just need to build a simple web server to run these PoE sensors. No big deal right, it's just an IIS service. Months after ordering Server 2019 though SSC I get 4 activation codes 2 MAK and 2 KMS. I won the lottery now i just have to download the server 2019 retail ISO and... Won't take the keys. Back to purchasing, "oh I can download that for you, what key is yours". Um... I dunno you sent me 4 Can I just get the link, "well you have to have a login". Ok what building are you in I'll drive over with a USB key (hoping there on the same campus), "the download keeps stopping, I'll contact the IT service in your building". a week later I get an install ISO and still no one knows that key is mine. Local IT service suggests it's probably a MAK key since I originally got a quote for a retail copy and we don't run a KMS server on the network I'm using for testing. We'll doesn't windows reject all 4 keys then proceed to register with a non-existent KMS server on the network I'm using for testing. Great so now this server that is supposed to connected to a private network for the sensors and use the second NIC for an internet connection has to be connected to the old network that I'm using for testing because that's where the KMS server seems to be. Ok no big deal the old network has internet except the powers that be want to migrate everything to the new more secure network but I still need to be connected to the KMS server because they sent me the wrong key. So I'm up to three network cards and some of my basic sensors are running on yet another network and I want to migrate the management software to this hardware to have all my data logging in one system. I had to label the Ethernet ports so I could hand over the hardware for certification and security scans.

So at this point I have my system running with a couple sensors setup with static IP's because I haven't had time to setup the DNS for the private network the sensors run on. Local IT goes to install McAfee and can't because it isn't compatible with anything after 1809 or later, I get a message back that " we only support up to 1709" I point out that it's server 2019, "Oh yeah, let me ask about that" a bunch of back and forth ensues and finally Local IT get's a version of McAfee that will install, runs security scan again i get a message back. " There are two high risk issues on your server", my blood pressure is getting high as well. The risks there looking at McAfee versions are out of date and windows Defender is disabled (because of McAfee).

There's a low risk issue as well, something relating to the DNS service I didn't fully setup. I tell local IT just disable it for now, then think we'll heck I'll remote in and do it. Nope can't remote into my server, oh they renamed it well that's lot going to stay that way but whatever oh here's the IP they assigned it, nope cant remote in no privileges. Ok so I run up three flights of stairs to local IT before they leave for the day log into my server yup RDP is enabled, odd but whatever let's delete the DNS role for now, nope you don't have admin privileges. Now I'm really getting displeased, I can;t have admin privileges on the network you want me to use to support the service on a system you can't support and I'm supposed to believe you can migrate the life safety systems you want us to move. I'm using my system to prove that the 2FA system works, at this rate I'm going to have 2FA access to a completely worthless broken system in a few years. good thing I rebuilt the whole server in a VM I'm planning to deploy before I get the official one back. I'm skipping a lot of the ridiculous back and forth conversations because the more I think about it the more irritated I get.