Unable to download Disk Images from LIB: to PC

[pfcushing]

I recently noticed that I can no longer download a disk image from the LIB: window to my web-attached PC. I can't remember when it was the last time that I could do this. I am running firmware 1.12.0 and have tried using Windows 7, Windows 10 and Windows 11 so I don't think the issue is related to the PC in use. I also noticed that when I mouse-click on a disk image, it does not appear to select that disk and neither the Refresh or Download via the widgets on the header of the LIB: window do anything. I have not tried the Delete widget because I am afraid it might work. The other devices all seem to work correctly. I noticed in the Release documentation for firmware 1.12.0 that changes were made to the LIB: to allow renaming disks. I assume that also does not work given that I cannot select a disk with a mouse-click..

I am reluctant to try going back to maybe firmware 1.10.0 for fear of breaking my working machine so I have not moved in that direction yet.

Paul Cushing

[BraerFox]

Hey Paul,
same issue. did you ever get it to work?

[ElectricDream]

Hello, I can still download any DSK file from LIB to my PC. My IMSAI 8080 ESP is up to date with the latest firmware version.

My setup :

• IMSAI : Firmware Build Version: V1.14.0 + GUI Version: webfrontend-v1.15.0
• OS : Windows 11 Build 26200.8655 version 25H2
• Chrome build 149.0.7827.104

Just a reminder (it may sound silly to repeat this, but you never know): in the LIB UI, click the DSK icon for the file you want to download, then drag and drop it onto the Download icon located at the top-right corner of the LIB window. This will trigger the download.

Also, be aware that Chrome blocks downloads from websites without a valid HTTPS certificate by default (sometimes without making it very obvious). In my case, after starting the download from the WebUI, I have to manually allow it from Chrome’s download manager before the file is actually downloaded.

That said, I have to admit that I rarely use this feature, so I can't say whether this potential bug was already present in versions prior to 1.14.0.

[pfcushing]

well, you hit it on the head but this is not how I remember it worked. Could be just be my memory, but your method works fine. I did get am pop-up with "insecure download blocked" and had to click on "keep" for it to continue. That is probably Chrome security.

Thank You

[BraerFox]

Hey Electric Dream,I do have the latest update.It looks like i hit the snag in Chrome. I closed out, and reopened it and it seemed to take -but I don't get the inconsistency (whatever, when and if it works, I'll take it unless it's a recurring problem). I finally got the COMMS disk to mount in the B: drive. Ran Kermit just fine, but am still waiting for the IMSAI clone to connect even though it's showing a proper handshake at pins 4 and 5 (green) 3 is red. The BBS host at the other end saw that I was timing out while trying Bell103 (it's a 300bd modem). Tried V21 but no avail either. So I'm stuck in the Authenticating -phase.  On Sunday, June 28, 2026 at 02:49:33 PM CDT, Electric Dream ***@***.***> wrote: Hello, I can still download any DSK file from LIB to my PC. My IMSAI 8080 ESP is up to date with the latest firmware version. My setup : - IMSAI : Firmware Build Version: V1.14.0 + GUI Version: webfrontend-v1.15.0 - OS : Windows 11 Build 26200.8655 version 25H2 - Chrome build 149.0.7827.104 Just a reminder (it may sound silly to repeat this, but you never know): in the LIB UI, click the DSK icon for the file you want to download, then drag and drop it onto the Download icon located at the top-right corner of the LIB window. This will trigger the download. Also, be aware that Chrome blocks downloads from websites without a valid HTTPS certificate by default (sometimes without making it very obvious). In my case, after starting the download from the WebUI, I have to manually allow it from Chrome’s download manager before the file is actually downloaded. That said, I have to admit that I rarely use this feature, so I can't say whether this potential bug was already present in versions prior to 1.14.0. — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today! You are receiving this because you commented.Message ID: ***@***.***>