GaNFast, which appears to be a site intended to promote Gallium Nitride devices, happens to have one of the best charger + hub product lists out there. It gives power, type and number of prts, and overall size, all in one table:
After installing the Visual Studio Theme Pack from the Visual Studio Marketplace website, my installatio of Visual Studio 2022 was completely broken. The error messages I was getting included:
The 'MEF Service Broker Package' package did not load correctly. The 'Background long idle package' package did not load correctly.
I couldn't even open Tools | Manage Extensions. In fact, no menu items worked at all, only triggering an error message, "The operation could not be completed." Attempting to open a project resulted in an error "There is no editor available for..."
Even the close button resulted in an error dialog!
The fix was to uninstall the Visual Studio Theme Pack using this command:
C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\VSIXInstaller.exe /u:VisualStudioThemePack.453e3fa1-2e0e-467e-abbd-1d08fe6468d1
After some more monkeying around, I managed to get Visual Studio into an even worse condition. Ultimately, running these commands as an Administrator got Visual Studio working again:
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\Build\vcvars32.bat devenv /resetuserdata
Tired of the awful OEM screen on your T420? Want FHD (1920x1080) resolution with the full colors and deep blacks of IPS screens? Having a hard time deciding which to order? Then this page might help you.
There are several screens available for the non-S T420 laptop which have performance characteristics on par with true IPS screens. This page has a good explanation of how the various panel types differ.
This thread by RMSMajestic seems to be the origin of the screen upgrade for the non-S Thinkpad T420 and T430. The first post explains why flickering is a common problem.
There are several eBay sellers carrying FHD IPS controllers. The one sold by moe-tech, for example, supports the following screens:
1920x1080 (FHD) Screens
|B140HAN01.1||AHVA||Matte, hard||16.2m||300 cd/m^2||700:1||89/89/89/89|
|B140HAN01.2||AHVA||Matte, hard||16.2m||300 cd/m^2||700:1||89/89/89/89|
|B140HAN01.3||AHVA||Matte, hard||16.2m||300 cd/m^2||700:1||89/89/89/89|
|LP140WF1-SPK1||AH-IPS||Matte, hard||262k||300 cd/m^2||700:1||80/80/80/80|
|NV140fhm-n41||ADS||Matte, hard||262k||250 cd/m^2||800:1||85/85/85/85|
There are also 40-pin controllers that support 2560x1440, such as this one by e-qstore. It lists the following screens:
2560x1400 (WQHD) Screens
|AUO||B140QAN01.1||AHVA||Matte, hard||16.7m||340 cd/m^2||700:1||85/85/85/85|
I chose the AUO B140HAN01.3 from eBay seller neidersch, and the LCD controller from moe-tech. Why that particular screen? Because I wanted a matte finish, and it appears to be identical to the B140HAN01.1, aside from being 0.2mm shallower. Both have been working great for around nine months.
Since I always forget how to configure a symbol cache on a new machine, here's my configuration. Setting this environmental variable will download symbols from Microsoft's servers and cache them at E:\symbols:
I finished Far Cry 5's main story with only 32 hours of game play. I spent a fair amount of time doing side missions, too. I generally see 50 - 70 hours of game play in AAA titles, so I'd rate this a mediocre value. Still better than FC4, though.
Back in August of 2015, I wrote about how System Notifications in Windows 10 were deafening and ignored System Volume settings.
It's 2017, and the problem appears to still be there. In fact, it's even worse, since Dropbox has to notify me every time I take a screenshot (even though I turned off notifications), and Windows chooses to notify me when Windows Defender has not detected any threats.
One very ugly fix is to go into System Sounds and disable the Windows | Notification entry. But I actually want notification sounds, I just don't want them blasting at full volume.
So, here is my ugly hack: I loaded the "Windows Notify System Generic.wav" file into Audacity, dropped the volume 20dB, and set that as my notification sound.
Here is a link to a ZIP file containing -5dB, -10dB, and -20dB versions of the default system sound. To use them, download the file, extract its contents to C:\Windows\Media, then type "Change System Sounds" into the Start menu, scroll down to 'Notification' under 'Windows', 'Browse', and select the sound file you want:
I wanted to install an Intel 7260-N WiFi PCIe card into my T420. For this to work, I had to flash a modified BIOS that removes the hardware whitelist. Unfortunately, I had just upgraded to BIOS 1.49, which ostensibly cannot be downgraded.
The solution was to manually call winflash using the sv and sd flags:
winflash.exe /sv /sd 83ET76WW\$01C8000.FL1
The above command assumes that you're in the bios_mod folder, which is contained in the modified BIOS archive on ThinkWiki.
I was having problems getting PPTP to work with PureVPN on a Lubuntu VM. I followed PureVPN's directions, but only one of the four VPNs I created actually worked. The configuration appeared to be identical, based on what the user interface was telling me.
When I looked at the VPN configuration files in /etc/NetworkManager/system-connections, I found a discrepancy. The VPN that worked contained three entries under [vpn] that were missing from the other files:
[vpn] refuse-chap=yes refuse-eap=yes refuse-pap=yes
Once I added these entries, the PPTP connections worked as expected.
I was trying to install Electron on Ubuntu using this command:
npm install electron-prebuilt -g
It would run for awhile, then fail with this error:
sh: 1: node: not found
Several online sources said to install "node-legacy", but this never worked:
sudo apt-get install node-legacy
Reading package lists... Done
Building dependency tree Reading state information... Done
E: Unable to locate package node-legacy
Searching the apt cache revealed something:
sudo apt-cache search legacy | grep node
node-dompurify - XSS sanitizer for HTML, MathML and SVG - Node.js module
The package is nodejs-legacy, not node-legacy! Installing nodejs-legacy solved the problem, and Electron installed cleanly after that.
sudo apt-get install nodejs-legacy
After moving a Lubuntu virtual machine from VirtualBox to VMware Workstation and installing VMware Tools, I needed to clean out an old installation of Open-VM-Tools (OVT) and VirtualBox Guest Additions. Here are the steps I followed:
List installed dkms packages:
Remove open-vm-tools and vboxguest that were listed by the previous command (note that you'll need to provide the corresponding version numbers):
sudo dkms remove open-vm-tools/9.10.2 --all sudo dkms remove vboxguest/5.0.2 --all
List openbox related tools (note that this will list anything with 'open' in the title, you only want open-vm related items):
dpkg --get-selections | grep -v deinstall | grep -i open
sudo apt-get remove open-vm-tools-dkms