The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 2,947 other followers

Archive for June 17th, 2019

Varios DELL machines having an unknown device ACPI\DELLABC6 – it is the WiFi switch support – via Dell Community

Posted by jpluimers on 2019/06/17

It looks like many Dell machines suffer from this: devmgmt.msc indicating an unknown device with identification ACPI\DELLABC6.

The odd thing is that the tool known for 10+ years as Dell Detect, but got renamed into SupportAssist does not detect that Windows needs drivers for it.

So a bunch of posts:

They lead to these download:

  1. [WayBack] Dell WLAN Radio Switch Driver | Dell US with [WayBackDell-WLAN-Radio-Switch-Driver_JK9WM_WIN_1.0.0.9_A05.EXE
  2. [WayBack] Dell Airplane Mode Switch Driver | Dell US with [WayBackFOLDER03137561M/1/Network_Driver_PX8MM_WN64_1.0.0_A00.EXE

The first of these works on a Dell Precision 7710 perfectly fine.

The odd thing: without the driver, pressing Fn+PrtScr (turn off/on WiFi radios) just works (for details on that key combination, see [WayBack] How to Turn the Wireless Devices on a Dell Notebook On and Off | Dell US or[WayBack] Dell Precision 7710 Mobile Workstation Keyboard Guide | Dell US)


Posted in Hardware, Power User | Leave a Comment »

I’ve given up on entering non-ASCII characters when entering data on-line

Posted by jpluimers on 2019/06/17

I live in a street that has a non-ASCII character in it: Pyreneeën.

I’ve reverted back to entering the street name as plain ASCII for a simple reason:

Too often the ë gets mangled into encoding gibberish, similar to the é example in [WayBackWhen Good Characters Go Bad: A Guide to Diagnosing Character Display Problems as these characters are very near both in UTF-8 and in the [WayBackUnicode Characters in the Latin-1 Supplement Block:

I’ve seen these encodings, where only the top encoding is correct; the degeneration gets worse moving downwards, a classic Mojibake:

# encoded UTF-8 (hex.)
0 ë 0xC3 0xAB
1 ë 0xC3 0x83 0xC2 0xAB
2 ë 0xC3 0x83 0xC2 0x83 0xC3 0x82 0xC2 0xAB
3 ë 0xC3 0x83 0xC2 0x83 0xC3 0x82 0xC2 0x83 0xC3 0x83 0xC2 0x82 0xC3 0x82 0xC2 0xAB
4 ë 0xC3 0x83 0xC2 0x83 0xC3 0x82 0xC2 0x83 0xC3 0x83 0xC2 0x82 0xC3 0x82 0xC2 0x83 0xC3 0x83 0xC2 0x83 0xC3 0x82 0xC2 0x82 0xC3 0x83 0xC2 0x82 0xC3 0x82 0xC2 0xAB
5 ë 0x26 0x65 0x75 0x6d 0x6c 0x3b

The last one seldomly happens, the first one relatively often, just like [] did a while on their finanancial pages.

These mistakes become sort of understandable (but not forgivable) when you look at the below table-fragment (the full table is at[WayBack] Unicode/UTF-8-character table – starting from code position 0080).

Read the rest of this entry »

Posted in Development, Encoding, Mojibake, Power User, Software Development, Unicode, Web Browsers | Leave a Comment »

syntax – Comments in Markdown – Stack Overflow

Posted by jpluimers on 2019/06/17

Comments that are not emitted to the output:

The most platform-independent syntax is

(empty line)
[comment]: # (This actually is the most platform independent comment)

Thanks nick-volynkin for answering this at [WayBack] syntax – Comments in Markdown – Stack Overflow.


Posted in Development, Lightweight markup language, MarkDown | Leave a Comment »

%d bloggers like this: