 | Mike Verhagen on geerlingguy/my-backup-plan: Ho… |
 | Attila Kovacs on docs.embarcadero.com unreachab… |
 | David Blue on MacOS: converting a man page t… |
 | jpluimers on How do I pretty-print JSON in… |
| jpluimers on Delphi 10.2 Tokyo Godzilla ISO… |
Posted by jpluimers on 2021/12/28
Via https://twitter.com/locuta/status/1475849029376516098
LET OP: We hebben een telefoonnummer gevonden dat je vanuit het buitenland kunt bellen om een boosterafspraak te maken: +31851124970. Deze lijkt nog wél te werken!
prikdoor
Draadje met extra informatie:
Posted in Uncategorized | Leave a Comment »
Posted by jpluimers on 2021/12/28
MSTSC.exe helptext
I created this small batch file:
:: start last RDP session (or new one with command-line parameters) full-screen :: see https://interworks.com/blog/ijahanshahi/2012/01/02/mstsc-commands-and-creating-custom-remote-desktop-shortcut/ mstsc /f %*
It is based on [Wayback] MSTSC Commands and Creating a Custom Remote Desktop Shortcut | InterWorks, which has the helptext for MSTSC.exe (which stands for MicroSoft Terminal Services).
Later I found out a way easier method to get that helptext is to run MSTSC.exe /?, which shows a nice dialog:
[Window Title] Remote Desktop Connection Usage [Content] MSTSC [] [/v:<server[:port]>] [/g:] [/admin] [/f[ullscreen]] [/w: /h:] [/public] | [/span] [/multimon] [/edit "connection file"] [/restrictedAdmin] [/remoteGuard] [/prompt] [/shadow: [/control] [/noConsentPrompt]] "connection file" -- Specifies the name of an .RDP file for the connection. /v:<server[:port]> -- Specifies the remote PC to which you want to connect. /g: -- Specifies the RD Gateway server to use for the connection. This parameter is only read if the endpoint remote PC is specified with /v. /admin -- Connects you to the session for administering a remote PC. /f -- Starts Remote Desktop in full-screen mode. /w: -- Specifies the width of the Remote Desktop window. /h: -- Specifies the height of the Remote Desktop window. /public -- Runs Remote Desktop in public mode. /span -- Matches the remote desktop width and height with the local virtual desktop, spanning across multiple monitors, if necessary. To span across monitors, the monitors must be arranged to form a rectangle. /multimon -- Configures the Remote Desktop Services session monitor layout to be identical to the current client-side configuration. /edit -- Opens the specified .RDP connection file for editing. /restrictedAdmin -- Connects you to the remote PC in Restricted Administration mode. In this mode, credentials won't be sent to the remote PC, which can protect you if you connect to a PC that has been compromised. However, connections made from the remote PC might not be authenticated by other PCs, which might impact application functionality and compatibility. This parameter implies /admin. /remoteGuard -- Connects your device to a remote device using Remote Guard. Remote Guard prevents credentials from being sent to the remote PC, which can help protect your credentials if you connect to a remote PC that has been compromised. Unlike Restricted Administration mode, Remote Guard also supports connections made from the remote PC by redirecting all requests back to your device. /prompt -- Prompts you for your credentials when you connect to the remote PC. /shadow: -- Specifies the ID of the session to shadow. /control -- Allows control of the session when shadowing. /noConsentPrompt -- Allows shadowing without user consent. [OK]
–jeroen
Posted in Batch-Files, Development, Power User, Remote Desktop Protocol/MSTSC/Terminal Services, Scripting, Software Development, Windows | Leave a Comment »
Posted by jpluimers on 2021/12/28
It still seems that WMIC is the quickest way to get CPU information on the console:
T510-PSO C:\bin\rdp> wmic cpu get name,CurrentClockSpeed,MaxClockSpeed CurrentClockSpeed MaxClockSpeed Name 2667 2667 Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz T510-PSO C:\bin\rdp> wmic path win32_Processor get Name,NumberOfCores,NumberOfLogicalProcessors Name NumberOfCores NumberOfLogicalProcessors Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz 2 4
Actually, wmic cpu is shorthand for wmic path win32_Processor, so this works fine:
T510-PSO C:\bin\rdp> wmic cpu get name,CurrentClockSpeed,MaxClockSpeed,NumberOfCores,NumberOfLogicalProcessors CurrentClockSpeed MaxClockSpeed Name NumberOfCores NumberOfLogicalProcessors 2667 2667 Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz 2 4
The reason is that cpu is an alias:
T510-PSO C:\bin\rdp> wmic alias cpu list brief FriendlyName PWhere Target CPU Where DeviceID='#' Select * from WIN32_PROCESSOR
Via:
–jeroen
Posted in Batch-Files, Console (command prompt window), Development, Power User, Scripting, Software Development, T510, ThinkPad, Windows | Leave a Comment »
Posted by jpluimers on 2021/12/28
People around me often wonder why things that seem so obvious does not work, and ask me if I bump into similar things.
I do, and often wonder why banks do not pay users to do testing for them instead of the other way around.
Below the fold a few Twitter threads. They might be mainly involving ING, but that’s just because I use their business and consumer portals more than those of other banks.
Here are the summaries:
account number and account statement date from the download files:
; DROP TABLE "COMPANIES";-- LTD – Overview (free company information from Companies House).–jeroen
Posted in Development, Software Development, Web Development | Leave a Comment »
The Wiert Corner - irregular stream of stuff 