Posted by jpluimers on 2021/04/27
If you setup an empty test project, then DUnitX will throw an ENoTestsRegistered.
This exception is not handled, which results in two things:
So better catch the ENoTestsRegistered exception in your .dpr level: a caught exception will be destroyed by the exception handling mechanism.
–jeroen
Posted in Delphi, Development, Software Development | Leave a Comment »
Posted by jpluimers on 2021/04/26
In sommige gevallen wil je geld in kleinere coupures opnemen, bijvoorbeeld in biljetten van 5 of 10 euro.
Het is niet makkelijk om hier informatie over te vinden, maar gelukkig bood de web-care uitkomst:
ABN heeft hier op sommige kantoren een automaat voor die een “retail mix” uitgeeft. Sommige van die automaten zijn 24 uur per dag beschikbaar.
Er is geen kaartje, maar wel een lijst van die kantoren op [WayBack] Locatie Retailmix – Retailmix MKB – ABN AMRO
Via [WayBack] ABN AMRO on Twitter: “Hallo Jeroen. Er zijn een aantal automaten verspreid over Nederland waar ook nog briefjes van 5 euro te pinnen zijn. Hier https://t.co/iAquvwO2oX vind je daar een overzicht van. Op de geldautomaat zit een sticker met ‘Retailmix’. Werkt de link? ^Janwalter… https://t.co/IyOXUo9WLq”
Gerelateerd:
Er zijn 5 standaard samenstellingen van biljetten mogelijk:
- 40 x € 5,-
- 40 x € 10,-
- 40 x € 20,-
- 20 x € 5,- + 20 x € 10,-
- 20 x € 10,- + 20 x € 20,-
–jeroen
Posted in LifeHacker, Power User | Leave a Comment »
Posted by jpluimers on 2021/04/26
Just in case I get Finder at 100% of one CPU core again while Time Machine is performing “Preparing backup…” for > 6 hours, I might take another look at these links:
This did not reveal much interesting back then:
clear; printf '\e[3J' && log show --predicate 'subsystem == "com.apple.TimeMachine"' --info --last 24h | grep -F 'eMac' | grep -Fv 'etat' | awk -F']' '{print substr($0,1,19), $NF}'
I was at Mac OS 10.3 High Sierra back then with 4 TB external backup disks backing up from the internal 1TB PCIe NVMe.
–jeroen
Posted in Apple, Mac OS X / OS X / MacOS, macOS 10.13 High Sierra, Power User | Leave a Comment »
Posted by jpluimers on 2021/04/26
User Bmw e46 320d Touring mentions this:
For this to work the following is needed:
- Springs to lift the trunk.
- ncs-expert to code your car, this option “FUNKTIONEN_TOURING” should be set to “nicht_aktiv” on touring model.
Basically this “FUNKTIONEN_TOURING” is to open a tailgate glass lid on touring model with key fob trunk button. If set to “aktiv” it will unlock/open tailgate glass lid, if set to “nicht_aktiv” it will unlock trunk lid with key trunk button.
More on NCS-expert:
–jeroen
Posted in cars, E46 330xd touring BMW, LifeHacker, Power User | Leave a Comment »
Posted by jpluimers on 2021/04/23
I had a curious error despite the build not having any failures on VirusTotal:
You have nirlauncher v1.23.42 installed. Version 1.23.43 is available based on your source(s). nirlauncher not upgraded. An error occurred during installation: Operation did not complete successfully because the file contains a virus or potentially unwanted software. nirlauncher package files upgrade completed. Performing other installation steps. The upgrade of nirlauncher was NOT successful. nirlauncher not upgraded. An error occurred during installation: Operation did not complete successfully because the file contains a virus or potentially unwanted software.choco upgrade throwing virus error during nirsoft 1.23.43 update
When upgrading, this briefly is visible in the Windows Security view “Virus & thread protection”:
[Archive.is] “HackTool:Win32/Passview!MSR” threat explained very thinly by Microsoft as [Archive.is] HackTool:Win32/Passview!MSR.
So I need to figure out a few things before I can upgrade Nirsoft:
–jeroen
Posted in Chocolatey, Power User, Windows, Windows 10 | Leave a Comment »
Posted by jpluimers on 2021/04/23
This was a cool one a few years back: [WayBack] Certified Secure – XS4ALL Challenge
–jeroen
Posted in Fun, History, Power User, Security | Leave a Comment »
Posted by jpluimers on 2021/04/23
Got this a while ago with 5.10.17:
This might be a hardware issue with [Archive.is] Ubiquiti UniFi Cloud Key, UC-CK: AmazonSmile: Computer & Zubehör
Reading the 1-star reviews, SD-card problems seem paramount: [Archive.is] Amazon.de:Kundenrezensionen: Ubiquiti UniFi Cloud Key, UC-CK.
For me, most of the times this solved the problem:
Posted in Cloud Key, Hardware, Network-and-equipment, Power User, Unifi-Ubiquiti | Leave a Comment »
Posted by jpluimers on 2021/04/22
I think the easiest way to list all VMs is the vim-cmd vmsvc/getallvms command, but it has a big downside: the output is a mess.
The reason is that the output:
Vmid, Name, Datastore, File, Guest OS, Version, Annotation),Annotation is a free-text field that can have newlines.Example output on one of my machines:
| Vmid Name File Guest OS Version Annotation | |
| 10 X9SRI-3F-W10P-EN-MEDIA [EVO860_500GB] VM/X9SRI-3F-W10P-EN-MEDIA/X9SRI-3F-W10P-EN-MEDIA.vmx windows9_64Guest vmx-14 | |
| 5 PPB Local_Virtual Machine_v4.0 [EVO860_500GB] VM/PPB-Local_Virtual-Machine_v4.0/PPB Local_Virtual Machine_v4.0.vmx centos64Guest vmx-11 PowerPanel Business software(Local) provides the service which communicates | |
| with the UPS through USB or Serial cable and relays the UPS state to each Remote on other computers | |
| via a network. | |
| It also monitors and logs the UPS status. The computer which has been installed the Local provides | |
| graceful, | |
| unattended shutdown in the event of the power outage to protect the hosted computer. | |
| … |
As an alternative, you could use esxcli vm process list, but that gives IDs that are way harder to remember:
| PPB Local_Virtual Machine_v4.0 | |
| World ID: 2099719 | |
| Process ID: 0 | |
| VMX Cartel ID: 2099713 | |
| UUID: 56 4d 74 f8 c8 22 41 27-a3 88 49 df 8b dc d6 63 | |
| Display Name: PPB Local_Virtual Machine_v4.0 | |
| Config File: /vmfs/volumes/5d35e7d8-e8df636f-46b9-0025907d9d5c/VM/PPB-Local_Virtual-Machine_v4.0/PPB Local_Virtual Machine_v4.0.vmx | |
| X9SRI-3F-W10P-EN-MEDIA | |
| World ID: 2099728 | |
| Process ID: 0 | |
| VMX Cartel ID: 2099717 | |
| UUID: 56 4d 51 ac f6 cf e4 0b-b6 86 2f 53 a2 8a 4b ea | |
| Display Name: X9SRI-3F-W10P-EN-MEDIA | |
| Config File: /vmfs/volumes/5d35e7d8-e8df636f-46b9-0025907d9d5c/VM/X9SRI-3F-W10P-EN-MEDIA/X9SRI-3F-W10P-EN-MEDIA.vmx |
I got both of the above commands from [Wayback] VMware Knowledge Base: Performing common virtual machine-related tasks with command-line utilities (2012964).
Back to the columns that vim-cmd vmsvc/getallvms returns:
Vmid is an unsigned integerName can have spaces[ and ] around itFile can contain spacesGuest OS is an identifier without spaces (it is a value from [Wayback] the vSphere API VcVirtualMachineGuestOsIdentifierVersion looks like vmx-# where # is an unsigned integerAnnotation is multi-line free-form so potentially can have lines starting like being Vmid, but the chance that a line looks exactly like a non-annotated one is very lowSo let’s find a grep or sed filter to get just the lines without annotation continuations. Though in general I try to avoid regular expressions as they are hard to both write and read, but with Busybox there is no much choice.
I choose sed, just in case I wanted to do some manipulation in addition to matching.
Though the source code [Wayback] sed.c\editors – busybox – BusyBox: The Swiss Army Knife of Embedded Linux indicates sed.c - very minimalist version of sed, the implementation actually is reasonably feature rich, just not feature complete. That’s OK given the aim of Busybox to be small.
Luckily, deep in the busybox sed code, it indicates that extended regular expressions are supported (support is in [Wayback] /uClibc/plain/libc/misc/regex/regcomp.c (look for regcomp, do not get confused by xregcomp on call sites as that is [Wayback] just a tiny wrapper to call regcomp).
The support has become better over time, like [Wayback] gnu – sed Command on BusyBox expects different syntax? – Super User shows.
This means far less escaping than basic regular expressions, capture groups are supported as well as character classes (so [[:digit:]] is more readable than [0-9]), and the + is supported to match once or more (so [0-9]+ means one or more digits, as does [[:digit:]]+, but [d]+ or \d+ don’t ). Unfortunately named capture groups are not supported (so documenting parts of the regular expression like (?<Vmid>^[[:digit:]]+) is not possible, it will give you an error [Wayback] Invalid preceding regular expression).
But first a few of the sed commandline options and their order:
vim-cmd vmsvc/getallvms | sed -n -E -e '/(^[[:digit:]]+)/p'
-n outputs only matching lines that have a p print command.-E allows extended regular expressions (you can also use -r for that)-e adds a (in this case extended) regular expression'/(^[[:digit:]]+)/p' is the extended regular expression embedded in quotes
/ at the start indicates that sed should match the regular expression on each line it parses/p at the end indicates the matching line should be printed( and ) surround a capture group^[[:digit:]]+ matches 1 or more digits at the start of the lineThe grep command is indeed much shorter, but does not allow post-editing:
vim-cmd vmsvc/getallvms | grep -E '(^[[:digit:]]+)'
I came up with the below sed regular expression to filter out lines:
Vmid unsigned integer[Datastore] before the FileGuest OS identifier after FileVersion matching vmx-# after File where # is an unsigned integerVersionvim-cmd vmsvc/getallvms | sed -n -E -e "/^([[:digit:]]+)(\s+)((\S.+\S)?)(\s+)(\[\S+\])(\s+)(.+\.vmx)(\s+)(\S+)(\s+)(vmx-[[:digit:]] +)(\s*?)((\S.+)?)$/p"
A longer expression that I used to fiddle around with is at regex101.com/r/A7MfKu and contains named capture groups. I had to nest a few groups and use the ? non-greedy (or lazy) operator a few times to ensure the fields would not include the spaces between the columns.
Others use different expressions as for instance explained in [Wayback] Get all VMs with “vmware-vim-cmd vmsvc/getallvms” – VMware Technology Network VMTN:
Output from “
vim-cmd vmsvc/getallvms” is really challenging to process. Our normal approaches such as awk column indexes, character index, and regular expression are all error prone here. The character index of each column varies depending on maximum field length of, for example, VM name. And the presence of spaces in VM names throws off processing as awk columns. And VM name could contain almost any character, foiling regex’s.
The cool thing is that it is straightforward to modify the expression to print any of the capture groups in the order you wish: you convert the match expression (/match/p) into a replacement expression (s/match/replace/p) and print the required capture groups in the replace part. A short example is at [Wayback] regex – How to output only captured groups with sed? – Stack Overflow.
There is one gotcha though: Busybox sed only allows single-digit capture group numbers, and we have far more than 9 capture groups. This fails and prints 0 after the output of capture group 1 instead of printing capture group 10, similar for 2 after group 1 instead of printing group 12:
vim-cmd vmsvc/getallvms | sed -n -E -e "s/^([[:digit:]]+)(\s+)((\S.+\S)?)(\s+)(\[\S+\])(\s+)(.+\.vmx)(\s+)(\S+)(\s+)(vmx-[[:digit:]]+)(\s*?)((\S.+)?)$/Vmid:\1 Guest:\10 Version:\12 Name:\3 Datastore:\7 File:\8/p"
So we need to cut down on capture groups first by removing all capture groups around the \s white-space matching:
vim-cmd vmsvc/getallvms | sed -n -E -e "/^([[:digit:]]+)\s+((\S.+\S)?)\s+(\[\S+\])\s+(.+\.vmx)\s+(\S+)\s+(vmx-[[:digit:]]+)\s*?((\S.+)?)$/p"
Then we get this to print some of the capture groups:
vim-cmd vmsvc/getallvms | sed -n -E -e "s/^([[:digit:]]+)\s+((\S.+\S)?)\s+(\[\S+\])\s+(.+\.vmx)\s+(\S+)\s+(vmx-[[:digit:]]+)\s*?((\S.+)?)$/Vmid:\1 Guest:\6 Version:\7 Name:\3 Datastore:\4 File:\5 Annotation:\8/p"
With this output:
Vmid:10 Guest:windows9_64Guest Version:vmx-14 Name:X9SRI-3F-W10P-EN-MEDIA Datastore:[EVO860_500GB] File:VM/X9SRI-3F-W10P-EN-MEDIA/X9SRI-3F-W10P-EN-MEDIA.vmx Annotation: Vmid:5 Guest:centos64Guest Version:vmx-11 Name:PPB Local_Virtual Machine_v4.0 Datastore:[EVO860_500GB] File:VM/PPB-Local_Virtual-Machine_v4.0/PPB Local_Virtual Machine_v4.0.vmx Annotation:PowerPanel Business software(Local) provides the service which communicates
This will be in the next installment, as by now this already has become a big blog-post (:
–jeroen
Posted in *nix, *nix-tools, ash/dash, ash/dash development, Development, ESXi6, ESXi6.5, ESXi6.7, ESXi7, Power User, RegEx, Scripting, Software Development, Virtualization, VMware, VMware ESXi | Leave a Comment »
Posted by jpluimers on 2021/04/22
Notes to myself:
I bumped into some legacy code with a windows process and DLLs both using ShareMem (now System.ShareMem) so that strings could be shared between the instances.
There were lots of memory leaks, so migrating to FastMM was important.
I followed these steps to get rid of ShareMem:
FastMM4 at the top of the uses lists for both the application and DLL projectsShareMem from these uses lists (in fact from any unit used)ShareMM;ShareMMIfLibrary;AttemptToUseSharedMM in each project file or the below in a fork of the FastMM4 repository file FastMM4Options.inc{$define ShareMM} {$define ShareMMIfLibrary} {$define AttemptToUseSharedMM}
ShareMM, ShareMMIfLibrary and AttemptToUseSharedMM in FastMM4.pas and add FastMM4.pas to the top of the uses section of the .dpr for both the main application and the DLL.[dcc32 Error] E2201 Need imported data reference ($G) to access 'IsMultiThread' from unit 'FastMM4': in projects that depend on run-time packages. Luckily, how to do that is in the FAQ too:
$G) to access ‘IsMultiThread‘ from unit ‘FastMM4‘”. How do I get it to work?UseRuntimePackages” option in FastMM4Options.inc.Related:
Note:
SimpleShareMem (now System.SimpleShareMem) as the source of it did not tell me anything about FastMM4 compatibility.EnableBackwardCompatibleMMSharing from the old EnableSharingWithDefaultMM conditional define.–jeroen
Posted in Delphi, Development, FastMM, Software Development | Leave a Comment »
Posted by jpluimers on 2021/04/21
Every now and then it is useful to be able to do maintenance work from the ESXi console addition to the ESXi web-user interface.
I know there are many sites having this information, but many of them forgot to format the statements with code markup, so parameters with two dashes -- (each a Wayback Unicode Character ‘HYPHEN-MINUS’ (U+002D)) now have become an [Wayback] Unicode Character ‘EN DASH’ (U+2013) which is incompatible with most console programs, especially the ESXi ones (as they are Busybox based to minimise footprint).
Note you can use this small site (which runs in-browser, so does not phone home) to get the unicode code points for any string: [Wayback] What Unicode character is this ?.
Links like below (most on the vmware.com domain) have this EN DASH and make me document things on my blog instead of trying code directly from blogs or forum posts:
So below are three commands I use that have to do with the maintenance mode (the mode that for instance you can use to update an ESXi host to the latest patch level).
Enabled or Disabled):esxcli system maintenanceMode get
Maintenance mode is already enabled. when failed):esxcli system maintenanceMode set --enable true
Maintenance mode is already disabled. when failed):esxcli system maintenanceMode get
Some examples, especially an the various output possibilities (commands in bold, output in italic):
# esxcli system maintenanceMode get Disabled # esxcli system maintenanceMode set --enable false Maintenance mode is already disabled. # esxcli system maintenanceMode set --enable true # esxcli system maintenanceMode get Enabled # esxcli system maintenanceMode set --enable true Maintenance mode is already enabled. # esxcli system maintenanceMode set --enable false # esxcli system maintenanceMode get Disabled
I made these scripts for this:
esxcli-maintenanceMode-show.sh:#!/bin/sh esxcli system maintenanceMode get
esxcli-maintenanceMode-enter.sh:#!/bin/sh esxcli system maintenanceMode set --enable true
esxcli-maintenanceMode-exit.sh:#!/bin/sh esxcli system maintenanceMode set --enable false
Note I have not checked the exit codes for these esxcli commands yet, but did blog about how to do that: Busybox sh (actually ash derivative dash): checking exit codes.
–jeroen
Posted in BusyBox, Development, Encoding, ESXi6, ESXi6.5, ESXi6.7, ESXi7, Power User, Software Development, Unicode, Virtualization, VMware, VMware ESXi | Leave a Comment »
The Wiert Corner - irregular stream of stuff 