Evidence that Windows NT is in fact, the most annoying operating system when it comes to USB, or that me, USB, and Microsoft just don't mix well += 1.

So, for the day I've been rather perturbed that about every ten minutes or so, Rimuru makes the USB enumeration sounds.

Running Device Manager in "Devices by connection" mode allows me to obtain a decent tree view of USB things. Fucking with cables like a mad man allows using the process of elimination to determine what the actual fuck device or port causes this.

Interesting to me, after process of elimination across all ports on my motherboard's Intel controller and the twin ports on my ASMedia controller, I've figured out something interesting about my new Anker hub.

When connected to the ASMedia (directly or extension) the onboard network port shows up as Unknown USB Device (Device Descriptor Request Failed). Likewise, if you insert a memory card into either card slot, no driver letter appears, and it starts making USB enumeration sounds like a mother fucker. Looks like two ports on an NS1081 USB flash card controller judging by the device manager but doesn't work. Connect something to the Gigabit port and it does not even light up past the hubs power up cycle. This is true even if nothing is connected to the hub's USB ports, so that it's a straight shot to the controller's C port and as minimal a downstream power draw as physically possible (i.e., only the hub's power LED, network port or sd port).

By contrast, connect the hub to my motherboard's front USB-C port and instead of Unknown USB Device (Device Descriptor Request Failed) that entry becomes a typical AIX based USB Ethernet port. Didn't try the card slots when connected to the Intel controller, but I imagine they would work in that configuration.

So, this boils down to when connected to the Intel controller the hub works just fine and when connected to the ASMedia controller, the bridge chips on the hub don't work.

Also, by contrast if I swap in one of the HooToo USB-C hubs that are so ubiquitous on Amazon, it just works fine regardless of which USB controller it is connected to.

Yeah. Pretty much by down, I don't really care which vendor is the problem child here. Fuck'em all.

Windows: oh, so poorly defined

Wondering what the heck Rimuru is so lethargic at I/O, to the point that programs take minutes to launch from the start menu and Explorer instances minutes to refresh.

Task Manager reports that my NVMe drive is at locked on 100% but only registers tens of MB/s in I/O. That's kind of silly in more ways than one.

Running perfmon /res from PowerShell, imagine my greater surprise when the Resource Monitor paints the finger at PID 4, SYSTEM and shows executable files from the new XBox advanced management feature.

Now here's the real kicker! Of the top three entries two are for a file that no longer exists on disk because I uninstalled the game a few weeks ago. Both marked at roughly 10~11 MB/s reads if you translate the B/s into reality. The third is installed but is registering ~4.5 MB/s reads for a file that is 600 something KB in size.

But I suspect that this non-sense is also a red herring, as system performance has leveled off despite the silly entries in the monitor. Whatever really sledgehammered the drive at startup is likely long since gone by the time I could get the monitors up and running.

That said, I kind of have to wonder what kind of I/O pattern could possibly register tens of megabytes of reads on a file that does not exist for thirty plus minutes and going, and if it did exist, would probably fit on a floppy diskette with plenty of room to spare.

A Visual History of Windows Icons: From Windows 1 to 11

While somewhat a reminder of how old I’m getting, I found this a refreshing and well executed trip down visual memory lane.

Tastes and styles pretty much change as fashions come and go. But system icon themes tend to be long lived.

Little Smiles

One of the things I've generally adapted to is using a local mail client again at home. Something, I sort of blame on a mixture of work and my tablet-first life style. As such, given my deep annoyance for most mail clients above the scope of mailx and mutt, I've mostly suffered the native Windows mail app. In particular because such applications are about the only good way to integrate my contacts and calendar accounts with the modern desktop. For me it's worked out, since I also hate clients like Thunderbird and Outlook but suffer them just the same.

Something that has long irked me is how Windows Mail defaults to showing a couple folders (inbox, drafts, sent) and none of the many folders my mail accounts are organized into. Thus, I get a little smile when I realize the fancy spancy modern looking menu supports right clicks and defines this ridiculously short list as "Favorites".

That's at least one less annoyance :).

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:\Users\Terry> gci C:\Windows\System32\*.msc


    Directory: C:\Windows\System32


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: Here's the real reason Edge crashed when Google was the default search engine

Things that happen all too often when two pieces of gorilla gonads interface with one another over a network

An update to my previous post, but dropping priority to "Normal" mode.

General system responsiveness is normal. Handbrake's average frames per second county thingy now goes to ~8.1 on average with extremes being more like 7.7~9.3, but it pretty well hovers at 8.1.

By contrast, applications like writing this post in a browser are now normal performance. It's even possible to watch previous encode without glitches and artifacts in the decode. But things like writing this post cause more dips in Handbrake's frame rate.

Overall, it seems fair to say "High" -> "Above Normal" priority loses 5% if you want a nice round number instead of a range for the average. "High" -> "Normal" priority loses 15% by the same method.

Where "High" = cripples the desktop session, "Above Normal" = makes the desktop session feel a few hardware generations behind, and "Normal" = makes it just another process.

I guess that solves that, lol.

A while back, I remember tuning the default priority in HandBrake's preferences, back when I made the leap over to HEVC. Mainly because the encode times are so long on my old Core i5-3570K, and because I tend to leave such jobs running overnight.

Well, for curiosity sake I've decided to see how monkeying with this changes things a bit.

In my experience, nicing processes on my unix systems is rarely worth the bother. That is to say, a nice system like Linux this side of multi-core processors tends to remain pretty responsive, and most people I encounter screwing with niceness tend to be pissing down the wrong problems to start with. But NT is not unix, nor Linux, so who knows.

Looks like the default priority I had configured was "High". Task Manager also shows a "Real Time" but that isn't in the GUI.

Net result is Handbrake proceeds at a pace of roughly 8.9 ~ 9.5 frames per second. Which works out to being closer to 9 than 10. Set to high priority also means that while the encode is running my desktop session is virtually useless, as things like updating UI state takes a back seat to next Tuesday.

After the first item in my queue finished, and the next began: I lowered the priority to "Above Normal". Impact on encode is roughly 8.9 ~ 8.3 frames per second on the average county thingy. So that's a performance loss of about 3 ~ 6 percent, but my desktop session is actually usable. UI updates like the process table in task manager now update in something closer to real time than melting an Titanic sized iceberg with a zippo lighter, and general productivity is passable. Typing this post is about on par with running a web browser on an older computer. Small price to pay.

That roughly equates to the encode takes less than five minutes less, if I render my desktop useless until the task finishes. Provided current pace keeps. When the entire encode takes a bit more than an hour per episode, it's kinda a meh perspective. Also a little nicer seeing my processor bouncing between ~70% and 99% in task manager instead of 97 ~ 99 %, lol.

I'm kind of reminded of XP, and my opinion that it could be very stable if you didn't do nasty things (or need shit drivers) to it, but being user responsive when under heavy loads it was not. As beautifully as the NT desktop has evolved since then, I still don't think melting a Windows box is as smart an idea as melting a Linux box, if you've really got to melt your system's load.

When the third file starts encoding, I'll probably try dropping the priority to normal and see what happens.

First impression of Edge 80, based on Chromium:

"Holy fuck that's fast"
"Is this powered by nitromethane or something?"

The main reason that I had converted my games machine back to Chrome was thanks to Edge being flaky release to release about my tab change / load habits, which could vary from smoother to an effect like watching the GUI thread block for background tab loads or something. Moving it back to Chrome was mostly to get performance that was consistent.

In the time that I used Edge on that machine, I was otherwise very happy with it as a browser. In fact if they had been more consistent, I probably would not have bothered to change things around.

With the move to a Chromium base, I doubt that there's much reason to care anymore. The only reason that I'm actually left to care about is the bookmark and history syncs with my Debian machine, and I don't really do that much with bookmarks anymore. Most interesting history bits can probably be solved by Google's activity page, since doing anything in Chrome's history usually rolls as "Gah, crap, I'll just type a search term", lol.

Windows 10X: Everything you need to know about the foldable PC OS
https://flip.it/tk_HYE

I for one, am more interested in foldable devices like these than ones we see harped on in phone space.

For me, there’s only two points of interest in a foldable phone. Either one that “Pops” open into a tablet, around the size of a Nexus 7 or iPad Mini; or something very compact ala the old Motorola Razrs. That’s about it. I don’t really want or care about most of the other things that have come up in phones, nor about a seamless display.

Now when we move into the size of a tablet or laptop: my tune changes! A device that can be the size of one, or two iPads; a device that can be a massive tablet or a dual screen book, that’s something I could use. I’m less interested in a seamlessly folded one piece screen than I am a layout more like a notebook with a thin bezel at the spine. See, PC operating systems like NT have better handling of multiple displays than contemporaries like Android and iOS. It’s a faster leap to abusing two screens if your starting point is something like Windows 10 than Android.

I want to see productivity gains from having two related, but not unified displays. It’s less about having a 14” tablet that can fold in half, and more about how two monitors that can interact—touch screen monitors, running mature software.

Microsoft shows off how containerized apps will work in Windows 10X

My interest in dual screen productivity to go, aside, I’m kind of interested to see where this goes. Most of the experiences I’ve had with containers in Linux, be out Docker, or building on top of chroot, have been a largely positive experience. Combine that container concept with the stability of the Win32 ABI, and there’s some viable good sides to this.

As software becomes increasingly long lived, the need to support software no one is ever going to recompile: keeps going up. Not to mention software that no one is ever going to port forward to more modern APIs and tool chains.

Microsoft is updating one of Windows 10’s oldest apps – but you won’t like the change

When you consider that Office is one of Microsoft’s big money makers for client side, and the main competition in browser space is an advertising company (Google), I’m not inclined to hold it against them very much. You can always install Libre Office or  Abiword if you really want free.

Rather: I’m just glad that Notepad gained support for Unix style end line markers. Most use I’ve had for Word Pad since the fall of 32-bit Windows has been to view text files that aren’t in DOS format, on machines that aren’t mine, or are in the process of setup. Prior to 64-bit Windows becoming the norm for NT based systems, I’d usually use edit.com for that purpose: but support for 16-bit DOS applications aren’t included in Windows x64.

To PowerShell or not to PowerShell

For the most part, I’ve found it very hard to care about PowerShell. But as time goes on, I mostly look at it with the thought, “Wish I had more use for that”.

Things that I do that require some scripting, and that run on more than unix systems, usually resort to creating .cmd or .bat files to handle the Windows systems. There’s mostly two reasons for that: execution policies and portability.

I don’t really like scripting cmd.exe. As an interactive shell, it’s barely livable but gets the job done. The focus on interactive mode, and the nature of DOS, show through in what can be done in cmd.exe. NT’s modern extensions and so on make it a lot better than COMMAND.COM but cmd.exe is not a good scripting environment, nor a great interactive shell: it just sucks less than its predecessors.

PowerShell on the other hand took some good ideas and largely addressed much of the suck. Exposing .NET even offers the opportunity to solve problems that would call for writing a solution in something beyond bash/ksh, or finding dedicated utilities for. It is really neat the amount of shit you can do in a PowerShell script.

But in the end, the default execution policy is what really keeps me away. Open sourcing and cross platformyness stuff in Core 6.x resolved most of my negative feelings for PowerShell, but it doesn’t suit my scripting needs.

By default: client systems reject running PowerShell scripts, and so monkeying with execution policy is needed. Either to unrestrict it for the current  session or my user. Which makes using it for projects less useful than using the older comspec. Because while cmd.exe is very meh, it doesn’t require any extra monkeying after I’ve git cloned my repo. Yet another thing to do when setting up a system, or document about a code base, that I don’t need.