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 1,878 other followers

Archive for January 27th, 2020

How to run Troubleshooter in Windows 10 from the command line

Posted by jpluimers on 2020/01/27

Learn how to run Hardware, Audio, Power Network, Windows Update, System Maintenance, App, Sound, etc, Troubleshooters in Windows 10/8/7 from the command line using MSDT.exe.

From:

Summary:

To invoke built-in Troubleshooters, use this command:

msdt.exe /id <diagnostic_id>

To run a custom-built troubleshooter stored locally use this command line:

msdt.exe /path <path_to_troubleshooter>

To run a troubleshooter which is in a .diagcab file format, use this:

msdt.exe /cab <path_to_diagcab>

List of diagnostic IDs:

Troubleshooting Pack ID Description Application or Feature Dependency
AeroDiagnostic Troubleshoots problems displaying Aero effects like transparency. Aero Display Theme installed
NetworkDiagnosticsDA Troubleshoots problems connecting to a workplace network over the Internet using Direct Access. Direct Access installed
DeviceDiagnostic Troubleshoots problems using hardware and access devices connected to the computer.
HomeGroupDiagnostic Troubleshoots problems viewing computers or shared files in a homegroup. HomeGroup installed
NetworkDiagnosticsInbound Troubleshoots problems with allowing other computers to communicate with the target computer through Windows Firewall.
NetworkDiagnosticsWeb Troubleshoots problems connecting to the Internet or to a specific Web site.
IEDiagnostic Helps the user prevent add-on problems and optimize temporary files and connections. Internet Explorer installed
IESecurityDiagnostic Helps the user prevent malware, pop-ups, and online attacks. Internet Explorer installed
NetworkDiagnosticsNetworkAdapter Troubleshoots problems with Ethernet, wireless, or other network adapters.
PerformanceDiagnostic Helps the user adjust settings to improve operating system speed and performance.
AudioPlaybackDiagnostic Troubleshoots problems playing sounds and other audio files. Audio output device installed
PowerDiagnostic Helps the user adjust power settings to improve battery life and reduce power consumption.
PrinterDiagnostic Troubleshoots problems printing.
PCWDiagnostic Helps the user configure older programs so that they can run in the current version of Windows.
AudioRecordingDiagnostic Troubleshoots problems recording audio from a microphone or other input source. Audio input device installed
SearchDiagnostic Troubleshoots problems with search and indexing using Windows Search. Search enabled
NetworkDiagnosticsFileShare Troubleshoots problems accessing shared files and folders on other computers over the network.
MaintenanceDiagnostic Helps the user clean up unused files and shortcuts and perform other maintenance tasks.
WindowsMediaPlayerDVDDiagnostic Troubleshoots problems playing a DVD using Windows Media Player. Windows Media Player installed
WindowsMediaPlayerLibraryDiagnostic Troubleshoots problems with adding media files to the Windows Media Player library. Windows Media Player installed
WindowsMediaPlayerConfigurationDiagnostic Helps the user reset Windows Media Player settings to the default configuration. Windows Media Player installed
WindowsUpdateDiagnostic Troubleshoots problems that prevent Windows Update from performing update tasks.

–jeroen

Posted in Power User, Windows | Leave a Comment »

Hamburger menu character on unicode: use U+2261 instead of U+2630

Posted by jpluimers on 2020/01/27

Not all fonts have Unicode character ☰ [WayBack] Unicode Character ‘TRIGRAM FOR HEAVEN’ (U+2630) as it is in a less common block.

More fonts have Unicode character ≡ [WayBack] Unicode Character ‘IDENTICAL TO’ (U+2261)

The latter is slightly shorter and slightly narrower than the former, but works in way more places.

Via [WayBack] html – Unicode ☰ hamburger not displaying in Android & Chrome – Stack Overflow

I’ve worked around this problem by using the UNICODE character UNICODE U+2261 (8801), ≡ IDENTICAL TO as illustrated below rather than the UNICODE U+2630 (9776) ☰ TRIGRAM FOR HEAVEN which

–jeroen

Posted in Development, Encoding, LifeHacker, Power User, Software Development, Unicode | Leave a Comment »

GitHub – Nike-Inc/gimme-aws-creds: A CLI that utilizes Okta IdP via SAML to acquire temporary AWS credentials

Posted by jpluimers on 2020/01/27

Since I will likely need something like this one day: [WayBackGitHub – Nike-Inc/gimme-aws-creds: A CLI that utilizes Okta IdP via SAML to acquire temporary AWS credentials

I think I got this via Kristian Köhntopp a while ago.

–jeroen

Posted in Amazon.com/.de/.fr/.uk/..., Cloud, Cloud Development, Infrastructure, Power User, Software Development | Leave a Comment »

Mapping US-English Keyboard keys to Turkish

Posted by jpluimers on 2020/01/27

I wrote about Delphi, IBX and the Turkish I problem about a year and a half ago. Back then, I could use a US-English system to reproduce the problem. This time, I had a problem on a Turkish system running an embedded version of Windows with hardly any UI tools available (especially no Windows Explorer).

Luckily, I had the command prompt, but it looked like this:

X:\>mode con codepage

Status for device CON:
----------------------
    Code page:      857

X:\>mode con codepage select 437
Invalid parameter - select

X:\>mode con codepage select=437
Invalid parameter - select

Status for device CON:
----------------------
    Lines:          300
    Columns:        120
    Keyboard rate:  31
    Keyboard delay: 1
    Code page:      437

X:\>

I tried the [WayBack] modecommand to change from [WayBack] code page 857(Turkish) to [WayBack] code page 437(IBM PC or OEM-US) which is the default on US-English systems, but that did not change the keyboard locale, not even for the command prompt.

Read the rest of this entry »

Posted in Development, internatiolanization (i18n) and localization (l10), Power User, Software Development | Leave a Comment »

 
%d bloggers like this: