Tech things that mildly worry me

I find it just a bit worrisome how often I remember shortcuts for running the MMC‘s various faces.

PS C:UsersTerry> gci C:WindowsSystem32*.msc


Directory: C:WindowsSystem32


Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---- 2019-12-07 04:09 41587 azman.msc
-a---- 2019-12-07 04:09 63081 certlm.msc
-a---- 2019-12-07 04:09 63070 certmgr.msc
-a---- 2019-12-07 04:08 124118 comexp.msc
-a---- 2019-12-07 04:09 113256 compmgmt.msc
-a---- 2019-12-07 04:09 145622 devmgmt.msc
-a---- 2019-12-07 04:09 13091 DevModeRunAsUserConfig.msc
-a---- 2019-12-07 04:08 47682 diskmgmt.msc
-a---- 2019-12-07 04:09 145127 eventvwr.msc
-a---- 2019-12-07 04:09 144909 fsmgmt.msc
-a---- 2019-12-07 04:53 147439 gpedit.msc
-a---- 2019-12-07 04:08 144998 lusrmgr.msc
-a---- 2019-12-07 04:09 145519 perfmon.msc
-a---- 2019-10-15 09:53 146389 printmanagement.msc
-a---- 2019-12-07 04:53 43566 rsop.msc
-a---- 2019-12-07 04:53 120458 secpol.msc
-a---- 2019-12-07 04:09 92746 services.msc
-a---- 2019-12-07 04:09 145059 taskschd.msc
-a---- 2019-12-07 04:08 144862 tpm.msc
-a---- 2019-12-07 06:19 144967 virtmgmt.msc
-a---- 2019-12-07 04:08 115109 WF.msc
-a---- 2019-12-07 04:08 144673 WmiMgmt.msc

In most cases I’m more likely to do foo.msc from a command prompt than go hunt down what I want through the start menu or other methods. Despite my background having focused heavily on unix systems, I’ve actually have learned a fair bit of NT over the past 15~20 years. Don’t think I’ll ever enjoy the care and feeding of Windows systems but it does come with the computer nerd territory, I suppose.

When you consider that for much of the past fifteen or so, the main reason I’ve kept Windows around has been for video games it may be kind of sad and worrisome, lol.

 So of the various ways that Windows NT pisses me off, one is networking.

Years of roaming between my home and work networks never made my Debian partition miss a beat. But with the Windows partition, it often decides to give me the finger.

Home/DHCP and Work/Static shouldn’t be an issue, but however I’ve managed to achieve the state (more than once) it decides that Work/DNS servers should be used in place of Home/DHCP lease. Which of course means pain in my arse.

The various methods of stabbing NT’s network stack with a spork through netsh and ipconfig didn’t help me, or I’ve never learned more useful pressure points. Regardless the applied settings don’t match what I’ve tried to configure on the connection nor the adapter through both the modern and old interface.

What finally works is this: https://superuser.com/a/1464468/295120

Hunted down the entry that corresponds to my pain woe and purged the value of ProfileNameServer for both tcpip and tcpip6. Vola the mother fucker switches back to the DNS in my DHCP lease.

Sigh.

Windows Me, 20 Years Later: Was It Really That Bad?

While Millennium Edition is mostly remembered as a disastrous hell pit: it did try to roll up quite a few odds and ends. That’s probably part of why it was so buggy, and XP had more time.
To be fair the Windows 9x line probably brought their operating system as far forward as it could really go without dropping the relationship to MS-DOS. A compatibility issue of decreasing importance by the time 98 SE reached customers, and more and more software came to expect a 32-bit Windows and modern memory management units.
XP is itself long post it’s throw out date: but was definitely a step in the right direction. Part of me remembers it fondly because it was the first time we really had a computing environment that could play games, and want e limited by outdated hardware. At the same time the shiny of business as usual left me ready for a unix environment long beds XP itself became outdated.
Part of me rather wonders what the modern desktop might look like if Microsoft would of had as much ownership of Xenix as they ended up with NT. At least few of us really need MS-DOS or 286 compatibility today as much as we may want Windows 98 or XP compatibility.

Thinking over my experiment, I think I can principally call it a success. Over the past ~three weeks, I’ve managed to not go out of my cottin pickin’ mind and want to flip my NT partition out a window. 

As someone that’s principally had a FreeBSD or Debian setup on hand for the past fifteen years, I’m going to call that signs of progress on Microsoft’s part. Because while there are worts here and there using a X session: traditionally they piss me off less than Windows.

Since the experiment began I’ve made numerous changes, but mostly small ones.

The freaky SD card freezes Explorer thing hasn’t happened in ages, so I can probably thank updates for that. Likewise I find turning my keyboard off before power down seems to result in less having to repair the damned thing. Pretty stable for the most part.

IIS is definitely slow as dog poop compared to lighttpd, but given how easy it is to lock it down to a specific network, I’ll forgive that.

The thing I miss the most is how copy/paste works in X. The whole thing about ^C/^V versus the mouse selection and clicking the middle mouse button is really helpful when you’re copying between a terminal and a note editor. The select / right click thing with modern Windows terminal emulators and console things, not so much. But that was also something I disliked about using Android and a monitor anyway.

Since modern Linux tends to treat otherwise available memory like a ramdisk, and buffers the crap out of it for faster file I/O, I’ve made a small tweak to WSL2 setup:

PS > type ..wslconfig
[wsl2]
# default is 80%, or about 12.8 if you’ve got 16GB.
memory=8GB
# Default is 25%, or about 4GB if you’ve got 16GB
# It’s a VHDX file used as swap: not system virtual memory.
#swap=?

Effectively limiting WSL2 to half my system’s physical memory. Otherwise I’ll find myself with 300~400 MB free in task manager. Some of the projects I work on generate ~20 GB of files and general nut punches memory.

That my desktop sessions on W10 usually burn up to 3.5 ~ 6.5 GB according to Task Manager, this further increments my desire that my next machine offer at least 32 GB of RAM. Because 640 KB isn’t enough for anything anymore 🤣.

As most of my interests revolve around an xterm session, WSL works pretty damned good for me. Enough so that using Xfce4 and Thunar vs NT’s DWM and Explorer aren’t as large an impact as the change from Davmail + Thunderbird to ActiveSync and Windows Mail.

Much to my amusement if I do the old “Send to” -> “Mail recipient” trick, I get an error message that there is no program for that. Actually, I can’t remember what decade I last actually tried that. But I’m pretty sure that XP or ’98 was still sexy at the time.

I’ve been happy to see that Windows Terminal has come along nicely. When I tried it very early on, I found it annoying because I abuse bash’s classic line editing instead of using notepad like shortcuts. No frustrations or interference with a release version of Windows Terminal; in fact my only negative comment is the fancy pane split stuff isn’t the same as tmux or screen, hehe.

Spending more time on Windows 10 than normal, I find myself reminded that it’s been about a decade since I figured I should learn how to use PowerShell. While I mostly skipped having to care about batch files in command.com, I have had no such luck avoiding cmd.exe in my life. And PowerShell frequently reminds me how nicer it is–if only I’d have the time to learn it as well as I do bash and general Bourne Shell voodoo.

My little experiment of using Windows 10 Pro instead of Debian Buster was meant to answer the question “Can I” use NT as my main development and work platform. The question of “Should I” however is a different one. That I haven’t gone insane is a positive. That I’ve tried at all of course indicates that I may be a tad more insane than normal.

But hey, I spent many years using Android as a desktop replacement, so I’m obviously crazy to begin with ^_^.

 Various sad and comical things.

Decided to try an old SSD in my spare enclosure. But I found while my Linux machine blows away just fine on I/O performance: my NT partition maxes out at about 30 MB/s on Crystal Disk Mark and 11 MB/s on Windows time.

In fact every fracken’ thing I plug into my USB 3.0 port maxes out at that speed.

So decided to do a little poking around. My NT install comes from Microsoft, not from Dell, so there’s a minimal of their things tacked on. Looking for updated drivers, I was kind of just glad to see W10 well represented given the age of my Latitude.

Found a BIOS update and dared to do it. Going from A00 to A20 (2018) was a lot of versions.A001 I think was dated 2012, and the oldest available. Mostly it’s fixes and security updates. But low and behold upgrading my BIOS a terrifying number of versions forward: my USB 3.0 is working right.

That is to say, Crystal Disk Mark basically jumps from ~30 MB/s to 250 MB/s, and Explorer reports much more appropriate speeds itself.

Amusing to me, one of the features I kind of missed was the option of Secure Boot. Which was added in one of the many updates. Ironically, a cyber security report from the NSA actually has better descriptions of the new UEFI settings on my system than Googling them ^_^.

 When I think back over the past fifteen years and the various systems I’ve used, I think a table of Bluetooth problems would look like this:

  • GNU/Linux on PC: 100% success, or no BT driver.
  • FreeBSD on PC: 100% success, or no BT driver.
  • Android on phone, tablet, television, and laptop: 90% success.
  • Windows NT on XP, 7, and 10: 25% success.
  • iOS on tablet: 100% success.
Actually, come to think of it, aside from the ruckus with Google changing BT stacks and a painful Nexus 7, I’m pretty sure the only operating systems that ever give me grief about Bluetooth are all ones baring the name NT!!!
I’d like to think it would suck less on a device with an integrated Wi-Fi/BT card. But applying USB BT to laptops and desktops has definitely been a painful experience over the past ~15 years.

 Well, that’s kind of neat. Windows Defender can run Edge in a Hyper-V session as part of “Application Guard.”

Considering that browsing the world wide web is pretty much a living definition of remote code execution, it’s probably about time someone tried to make a standard feature of isolating the browser. If WSL2 is any indication, Hyper-V also offers great performance if your machine doesn’t suck.

This long, tiresome week, I’ve opted to conduct an experiment: working out of my Windows partition. Since shoving my Chromebook in a closet ages ago, I’ve usually booted Stark  from my Debian partition. Well, this week I tried a little insanity.

So what worked? Well the important stuff. Namely WSL2 and Docker for Windows now enable me to do the things my Debian partition offers that actually matter. Yay for that. Being a busy week, I kind of put that part of the system through five hundred laps of abuse without a problem.

A very large part of my time revolves around command line environments one way or another, so a lot of my client machine’s job is being a glorified X-Terminal on steroids. Most GUI software I rely on is cross-platform within the desktop family trees, pardoning proprietary bits. Most parts I really care about are terminal friendly; most GUI parts involve interaction with others or specific tasks.

In particular I found it pleasant to have a Evernote’s desktop client. The web client’s not my cup of tea, beyond some of the editing shortcuts it shares with the Android and iOS clients. While most of what I do on my Linux partition was direct and to the point thanks to WSL, Evernote was a big shift.

What didn’t work so hot?

In a very unsurprising shortfall was Bluetooth. Twice I had to totally start from scratch pairing my Bluetooth keyboard and mouse. To be fair, W10 20H1 launched with problems that are supposedly resolved. To be honest I’ve always had trouble with NT and Bluetooth: going as far back as the XP era. By contrast in a decade of combing Bluetooth and Linux: the only issue I’ve had is changing batteries 🤣.

Another is the networking side. Seems like W10 is happy enough to use my static/dns setup for Wi-Fi at work, and DHCP for my Wi-Fi setup at home. It’ll even deal with the DNS suffix at home. But sometimes it thinks my home network has no Internet connectivity because it’s trying to use my work DNS servers with my home connection. I suppose, considering the era NT comes from: I should just be glad that W10 has a concept of different configurations for different wireless connections. But annoying.

Shifting from Davmail / Thunderbird to the various Microsoft things, I mostly have two comments. One: easier setup. Second: different quirks. On the flipside, Davmail has a spectacularly accurate manual. And Thunderbird probably has more bugs and quirks than it’s competition, lol. I could actually replicate my Linux setup on W10, but would rather not during the experiment.

Explorer is probably the gold standard of file managers. Compared to Thunar, it sure is. But I found it amusing how it was a sticking point. On occasion Explorer total death hangs until I eject my SD card. In the kill explorer from taskkill /f and then restart the damned thing just to get my panel back kind of hangs. Although, I’ve probably seen more crashes from X file managers than you can shake a stick at, it’s compensated by *nix having a far superior command line environment.

More minor were things like my internal web server. Easy enough to replicate my simple lighttpd setup in IIS, and to lock it to my connection at work. Most of my stuff is either static, Perl CGI, or bash based; so the only thing that’s not operational with trivial effort is a few CGI scripts done in bash.

And then there’s the part that should really scare me: I didn’t hate the experience. By comparison using Windows 7 and its predecessors generally lead to cursing and gnashing of teeth.

Microsoft’s Edge browser is crashing if you have Google set as default search – There’s a temporary workaround

Considering how much of Edge is Google, and both companies histories, I do find this kind of amusing. Given the isolation it almost makes me wonder if some Googly interface somewhere has changed its response in a funny way, or if a Microsoft change relative to Chromium induces a crashola.
In any case, looks like people using Edge should stop sending their address bar inputs to Google ala Chrome.