So, for the nth time, I found myself wondering “what name did I use to map this network drive” in Windows Explorer…
A quick Google search dug this up, so, just to document it for my own (future) reference:
wmic netuse where LocalName="Z:" get UserName /value
Where “Z” is the mapped drive letter in question…
So my Silverstone DS-380 casing’s power LED seems to have bought it… In an attempt to try fix it (or at least test it), I had to get to the motherboard and that meant I had to remove all the drives, drive cage, etc… Since piecing everything back together again was a pain, I left the 3.5″ spinning media drives out to boot the system several times during testing.
After giving up on the power LED, I re-plugged in everything + the drives… Only to find that, of some 11 different ZFS sub pools, 10 were missing…
My heart stopped and the universe whirled around me…
zpool status showed the drives were all present and accounted for…
Thankfully, zfs list showed all my ZFS sub pools/”partitions” were still there… So, what gives?
Recently, I had to capture screen clips and decided to utilise Techsmith’s Snagit, which worked wonderfully in the past…
However, try as I might, it now hung on my PC whenever I stopped the capture (and it tried to save the clip), showing me a spinner that sat there forever (till its process was killed).
Scrounging around the ‘net provided little clue, but seemed that quite a few people had run up against it also. Then, after weeks of on-and-off searching, I finally ran across this little answer hidden in the corner of the ‘net…
Check the simple fix (if you had not already clicked through the linked solution from above)…
I absolutely abhor applications that infest your machine in the C:\Users\<blah>\AppData\<blahblah> folder, needlessly littering their “little pebbles of rabbit droppings” all over your hard drive (similar to Mac OS’s ._crap). I have administrator access and don’t want multiple copies of your program, thank you – much less mis-matched, outdated versions.
It’s hard enough to explain software interfaces to my elderly parents without having to also waste time explaining why their applications have different buttons due to different versions due to these “profile-local” installs, or why their C:\ boot drive, running on that small, purposely designated PCIe 4.0 NVMe SSD, was running out of disk space with multiple copies of the same files…
Spotify and Zoom are prime examples, particularly Spotify – at least Zoom provides an offline MSI installer (which then properly installs into C:\Program Files (x86)\)…
But… although there’s a desktop x64/64-bit installer (which infests individual profile’s personal directories), there’s no x64/64-bit version of said MSI installer… But is there?
So, I finally got sick of typing my root user password in my Windows Subsystem for Linux (WSL), *nix Docker containers and Linux servers…
The answer (for some flavours of *nux): just create an addendum to /etc/sudoers by creating any new file in the /etc/sudoers.d/ directory!
