Posted by jpluimers on 2021/08/18
LOL: [WayBack] atx psu 24pin 24p power supply jumper jack adapter connector for btc – Google Search
Via [WayBack] Brad Smith a Twitter: “LOL I just wanted to buy the cheapest ATX socket on ebay to to make a little power jumper connector, and the cheapest one already has the wire stuck onto it. “…for BTC” 🤣… “
–jeroen
Posted in Development, Fun, Hardware, Hardware Development, Power User | Leave a Comment »
Posted by jpluimers on 2021/08/17
Not sure why, but Winbox 3.17 could not connect to out of the box blank MikroTik equipment at all.
Winbox 3.19 complains every now and than, but usually connects fine.
This was while configuring a bunch of [WayBack] MikroTik Routers and Wireless – Products: CRS305-1G-4S+IN.
Posted in Development, Internet, MikroTik, Power User, RouterOS, routers, Scripting, Software Development | Leave a Comment »
Posted by jpluimers on 2021/08/17
More sites seem to have a tendency of stealing keyboard shortcuts and violating the WCGA (Web Content Accessibility Guidelines), especially the (lowest!) conformance level A in [Wayback] WCAG version 2.1, section Success Criterion 2.1.4 Character Key Shortcuts
If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true:
- 1. Turn off
- A mechanism is available to turn the shortcut off;
- 2. Remap
- A mechanism is available to remap the shortcut to use one or more non-printable keyboard characters (e.g. Ctrl, Alt, etc);
- 3. Active only on focus
- The keyboard shortcut for a user interface component is only active when that component has focus.
Mind you, I’m a keyboard person, there is even a: Keyboards and Keyboard Shortcuts category, but they always need to be configurable, anything else is a sin.
And GitHub did it again: [Archive.is] GitHub on Twitter: “🤫 New shortcut: Press . on any GitHub repo.… “.
So I’m totally with these:
Now they have started to steal the dot (.) keyboard to (in-place, with a fully new URL and no indication how to easily go back) start Visual Studio Code in the current repository.
Going back, though not documented, actually takes between one and three “back” movements in your web-browser history: utterly ridiculous for a key one can accidentally hit.
This behaviour violates all three above sub-criterions:
This is a very bad way to cope with accessibility, especially as conformance level A is yet again violated.
[Wayback] WCAG 2.1: section 5.2.1 Conformance Level:
One of the following levels of conformance is met in full.
- For Level A conformance (the minimum level of conformance), the Web page satisfies all the Level A Success Criteria, or a conforming alternate version is provided.
- For Level AA conformance, the Web page satisfies all the Level A and Level AA Success Criteria, or a Level AA conforming alternate version is provided.
- For Level AAA conformance, the Web page satisfies all the Level A, Level AA and Level AAA Success Criteria, or a Level AAA conforming alternate version is provided.
To me another cardinal sin is that they stole Ctrl-F / Command-F (depending if you use non-MacOS or MacOS) from the web browser. So now it does not find it in the full page, but only in the currently selected file. (You guessed it, I’m with [Archive.is] KewlCat on Twitter: “I hate it when they intercept “/” and even [Ctrl]-F… “ too)
More of those conformance violation sins are at [Wayback] Keyboard shortcuts – GitHub Docs.
It isn’t hard to prevent this kind of thinking: it’s a mind set as described by [Archive.is] Patrick Joannisse on Twitter: “I don’t know if you are expecting a real answer but here goes: it starts with the mindset. In my training they had us wear goggles to block our vision and made us use a screen reader for a while. We met people with disabilities and they would show us how they work.… “
github1s ft. netcon, @xcv58… “
–jeroen
Posted in accessibility (a11y), Development, GitHub, Keyboards and Keyboard Shortcuts, Power User, Software Development, Source Code Management | Leave a Comment »
Posted by jpluimers on 2021/08/16
If you own a Mikrotik CCR device based on NAND memory, then be prepared that it will die.
I had this on a (now discontinued [WayBack] MikroTik Routers and Wireless – Products: CCR1009-8G-1S-1S+PC, superseded by the less functional [WayBack] MikroTik Routers and Wireless – Products: CCR1009-7G-1C-1S+PC, which is also NAND based).
Many more people had this or very similar problems:
It also happens due to bad capacitors on the (also discontinued) [WayBack] MikroTik Routers and Wireless – Products: RB1200:
There have been quite a few NAND related changes to the firmware over the years that have to do with handling corruption:
If you are really lucky (I was not), then it is a bad power supply: [WayBack] bootloop on CCR1036-12g-4s (almost 5 years old) [SOLVED] – MikroTik.
Sometimes you can partially recover using the Console port or NetInstall, but eventually you will trip another part of the faulty NAND storage and it will die again, until it has spent all its lives.
Unlike a cat, those are usually far less than 9 lives.
If you do need to recover, the links might help you:
–jeroen
Posted in Internet, MikroTik, Power User, routers | Leave a Comment »
Posted by jpluimers on 2021/08/16
Steps to convert PDF to OCR on all pages in Acrobat XI Standard (STD) via [WayBack] PDF to text, how to convert a PDF to text | Adobe Acrobat DC:
- Open a PDF file containing a scanned image in Acrobat.
- Click on the Edit PDF tool in the right pane. Acrobat automatically applies optical character recognition (OCR) to your document and converts it to a fully editable copy of your PDF.
- …
- Choose File > Save As and type a new name for your editable document.
Screenshots:
You can select from many OCR languages:
On pages without bitmap content, you see this message:
Note that Acrobat XI was the last version where this was possible in the Standard edition.
More recent versions of Acrobat, need the Pro version for OCR:
Posted in Adobe, Adobe Acrobat, Fujitsu ScanSnap, Hardware, ix100, Power User, Scanners | Leave a Comment »
Posted by jpluimers on 2021/08/13
Otherwise SuperMicro devices might not get a DHCP address on the IPMI (BMC) interface, despite the tooling like [WayBack] ipmicfg indicating getting DHCP was succesful.
This especially holds for X9 boards, likely for newer boards as well.
Personally I never had the 4. and up above, but I bumped into 1. and 2. with SuperMicro boards and 3. with other devices.
Posted in Hardware, Mainboards, Power User, SuperMicro, X9SRi-3F, X9SRi-F | Leave a Comment »
Posted by jpluimers on 2021/08/13
For my screenshot archive:
A retry with about 5 gigabyte of free space went further:
Posted in Fujitsu ScanSnap, Hardware, ix1500, Power User, Scanners, Windows, Windows 8.1 | Leave a Comment »
Posted by jpluimers on 2021/08/13
This works only for PDF files originally created by ScanSnap (otherwise “Unsuccessful” with “Non-ScanSnap PDF”: [WayBack] ScanSnap Advanced Operation Guide (Mac OS) Creating Searchable PDF Files
ATTENTION
- Vertical text can be searched with Adobe Acrobat, but not with Spotlight or Preview.
HINT
The [Searchable PDF Converter] icon
appears in the status menu of the menu bar while Searchable PDF Converter is running. For details, refer to the ScanSnap Manager Help.
- Click the [Searchable PDF Converter] icon
in the Quick Menu.
- The [Searchable PDF Converter – PDF Conversion List] window appears, and conversion starts.
HINT
On a window that appears when [Searchable PDF Converter] is started for the first time, click the [OK] button to open the [Searchable PDF Converter – Initial Settings] window. In the [Searchable PDF Converter – Initial Settings] window, specify the processes that are to be performed, the conversion timing, and the folder to which the converted files are saved while conversion into searchable PDF files is being performed.
When using different kinds of PDFs, you get this error:
I have not figured out yet how it recognises ScanSnap generated PDF files.
–jeroen
Posted in Fujitsu ScanSnap, Hardware, ix500, Power User, Scanners | Leave a Comment »
Posted by jpluimers on 2021/08/12
It was fun while it lasted, and puts other operating systems at an advantage.
[Wayback] Jeroen Wiert Pluimers on Twitter: “Bye bye printer Plug & Play on Windows for end-users: … Though MacOS has its share of printer driving issues (like only printing monochrome to colour printers), this is a serious step back on Windows compared to MacOS.”
More on the MacOS printer woes in a later blog post.
Web related:
Have they forgotten SysAdmin Appreciation Day so soon?
Today, we are addressing this risk by changing the default Point and Print driver installation and update behavior to require administrator privileges. The installation of this update with default settings will mitigate the publicly documented vulnerabilities in the Windows Print Spooler service. This change will take effect with the installation of the security updates released on August 10, 2021 for all supported versions of Windows, and is documented as CVE-2021-34481.
Twitter related:
–jeroen
Posted in Hardware, Power User, Printer drivers, Printers, Windows, Windows 10, Windows 7, Windows 8, Windows 8.1 | Leave a Comment »
Posted by jpluimers on 2021/08/09
The chocolatey package for OpenVPN has not been updated for quite a while. It looks like it has to do with the current dependency to verify the OpenVPN signature.
The current [Wayback] Chocolatey Software | OpenVPN 2.4.7 version is both outdated on the major version number ([Wayback/Archive.is] Release OpenVPN v2.5.3 release · OpenVPN/openvpn) and minor version ([Wayback/Archive.is] Release OpenVPN v2.4.11 release · OpenVPN/openvpn). The version 2.4 Windows installers are now called “Legacy Windows Installers”.
Luckily less than a day after the start of the [Wayback/Archive.is] RFM – openvpn · Issue #1024 · chocolatey-community/chocolatey-package-requests, a volunteer stepped forward.
Hopefully by now the package is being maintained again.
–jeroen
Posted in Network-and-equipment, OpenVPN, Power User, VPN | Leave a Comment »
The Wiert Corner - irregular stream of stuff 