gonnalearn.com

Workaround: DaVinci Control Panels App crashing

Under DaVinci Resolve 19.0, not only does the DaVinci Resolve Control Panels app crash immediately when I try to start it, but Resolve itself also refuses to start as long as the app is installed. In both cases, the Windows Event Viewer displays exception code 0xc0000409:

Fortunately, uninstalling just the Control Panels app allowed me to work with Resolve again. However, whenever there’s an update available for my Speed Editor, I need to find a workaround. Previously, I installed the Control Panels app on a different computer, but this time it was even more frustrating, as it also crashed on that second machine.

What eventually worked for me was temporarily disabling all other startup applications. A simple way to do this is by pressing the Windows key + R, typing “msconfig,” and then selecting “Selective startup,” leaving only system services checked (unchecking “Load startup items”):

After restarting with this selection, DaVinci Resolve Panels ran just fine and updated my Speed Editor:

Once done, I set the selection back to “Normal startup”. I did not have the patience and time to go through the startup apps and disable them one by one to find which one was causing the conflict. You could do this in the “Startup” section of the Windows Task Manager or with other applications like Autoruns.

Solution: Can’t find Bluetooth devices on Win 11?

If the Bluetooth device you want to connect to does not appear on Windows 11, try the following.

Go to Bluetooth and other device settings:

Bluetooth and other devices settings in Windows 11

Scroll down to the “Device settings” section and set “Bluetooth devices discovery” to “Advanced”:

Bluetooth devices discovery: Default and Advanced

If you now try to add a Bluetooth device again, you should see all available devices.

Explanation

Discovery involves scanning for devices that are broadcasting their availability to pair. The “Default” mode uses predefined filters to reduce the devices the system displays to common ones, such as keyboards, mice, and headsets. Presumably this was done to reduce clutter.

When “Advanced” is selected, this filter is removed, allowing the system to list all devices that are discoverable in the vicinity.

While I wasn’t able to find a comprehensive list of devices that Microsoft considers to be uncommon, the following ones only showed up after I changed the setting:

Adafruit EZ-Link (discontinued)
Aranet4 Home CO2 monitor
Ohaus Defender 5000 weighing scale with Bluetooth dongle
Zebra label printer

Improvements in Windows 11 version 24H2

It looks like the upcoming version will offer to “show all devices” when Bluetooth devices have been detected but filtered out.

Note for Windows 10 Users

The setting discussed here is specific to Windows 11 and does not exist on Windows 10. This can make it look as if Windows 10 had better Bluetooth discovery capabilities, when the actual cause is the filter in Windows 11.

Zeef.com is shutting down?

Zeef.com is (was?) a curated directory where users could create organized lists of links. I used it to make pages about video management software and RS-232:

If you visit zeef.com right now (February 29, 2024), you’ll see a popup announcing that the site will be shut down:

Although I wasn’t notified by email, the shutdown didn’t come as a complete surprise to me. Zeef apparently struggled to attract a large user base. Moreover, it suffered from frequent outages recently. Still, it’s sad to see it go.

I will be uploading my pages to this blog. If you’ve missed the chance to download your pages, you can probably still find them on the Wayback Machine (Internet Archive).

How to temporarily turn SQL strict mode off in phpMyAdmin

Pre-pending the query with SET SESSION sql_mode = ”; worked for me:

Note that executing multiple queries separately did not work. Here I ran SET SESSION sql_mode =” first and then SELECT @@SESSION.sql_mode, which showed that strict mode was still active:

Example

After the update of a MySQL server on a shared hosting account, strict mode was enabled with the NO_ZERO_DATE option and there was no way to change this. This meant that – among other things – I had to remove a default timestamp value of “0000-00-00 00:00:00” from multiple columns:

However this failed with error #1067 as other columns still used this invalid default. In other words, altering column A to make it compliant failed as column B was not compliant yet: