MartyMcNuts wrote: Wed Feb 11, 2026 4:16 am
1. No. Most people have 2+ drives. Very nitpicky! So what if you have to select your single drive...
Some people have multiple drives, including myself, but most of these people have only one drive connected at a time -- especially if they are actually updating the firmware for a drive. Standard software behavior is to select a default if it is obvious; like the first item in an enumerated list. The first and only drive in a list of optical drives would be a simple thing to default to. And what else could or would be selected if there is only one?
MartyMcNuts wrote: Wed Feb 11, 2026 4:16 am
2. No you don't. Read the first post as it explains you just edit the DPI settings of the exe.
I did exactly that before posting my previous message. The point is that it did not work. Specifically: in the properties for SDFTool 1.3.6 running on up-to-date Windows 10, on the "Compatibility" tab -> Button "Change high DPI settings" -> Section "High DPI scaling override": select "Override high DPI scaling behavior -> Scaling performed by: "System (enhanced)". This did not solve the problem, and made no visual difference. After testing several combinations of compatibility settings including the one described in the first post, I concluded that if the operating system's scaling is something greater than 100%, the SDFTool GUI is malformed no matter what the compatibility settings. The checkbox for "Encrypted" is absent or cut off; a button is labeled "STAR" instead of "START", etc. So changing the override for high DPI scaling to "System (Enhanced)" makes no difference. The only solution is in the system's advanced scaling settings, changing custom scaling to 100%, which requires signing out/in again to apply; it also might not be what the user wants to do for the entire OS appearance. Then SDFTool runs with the GUI properly formed; and SDFTool still is unaffected by what the compatibility settings for it are set to. So SDFTool looks correct only if the OS scaling is 100%, no matter what the compatibility settings are, and looks incorrect if OS scaling is >100%, no matter what the compatibility settings are. This is what I wrote in my previous message.
MartyMcNuts wrote: Wed Feb 11, 2026 4:16 am
3. It is explained in detailed english. The gif explains it even more. The recover from firmware isn't used for anything other than to obtain a 16 byte string for use in the recover command. There is no need for it to be displayed anywhere. No one needs to know any more than the instruction text each firmware file selection window provides.
Yes, it is explained, and I did work through the quirky GUI to flash BU40N firmware to a BP50NB40 unit with SVC code NB52 successfully on my first attempt. But confusion over several years among other people, evident from many forum posts, stems partly from odd behavior of the software in recovery mode. The process is not complicated, but the software's behavior is strange. Therefore, yes, there is a need to display what recover-from firmware is currently selected. In order for a write command using recover-from firmware to execute correctly, the correct recover-from firmware needs to be selected. So the current selection of the recover-from firmware should be displayed, just like the correct drive choice and firmware to write should be displayed. All three need to be selected correctly. If any of those selections are wrong, then obviously there will be a problem in the procedure. Why hide the current choice of recover-from firmware? To summarize, the recovery mode requires three correct settings, which should all be shown from top to bottom in the UI:
1. Optical drive
2. Recover-from firmware
3. Firmware to write.
#1 and #3 are displayed. #2 is hidden. All three matter.
