I have to wonder, though: Why "hack" TOS 2.06, when there is EmuTOS? Imho, a modern, advanced hardware platform should be supported by a modern OS.

Meanwhile, HDDRIVER 11.14 was released today with the fix that Frank had already successfully tested: https://www.hddriver.net/en/news.html.

I still find it deeply unfair to attack someone in a forum where they won't present their side of the story. I still think any grudges, misunderstandings and such are best settled in private. But I don’t mind at all publicly standing by what I wrote you some weeks ago: Personally, I have nothing but...

I decided not to go down the rabbit hole of why it hangs within a Windows DLL. After all, there are other things to do on Christmas Eve :D . Instead, using a hex editor, I patched Xilinx's libPortability.dll to cause the network share enumeration always to fail, without even calling the function tha...

I had to rename the file libPortabilityNOSH.dll to libPortability.dll SmartHeap disabled (aka NOSH) https://support.xilinx.com/s/article/62380?language=en_US But that was a long time ago, not recently. Yes, I also had to do that when I installed Xilinx ISE on Windows 10 way back ago. In other words...

I rolled back the last 2 updates and it started working again. Do you have Windows Subsystem for Linux (WSL) installed? Initial debugging shows that Xilinx software hangs at startup while trying to enumerate network shares. In particular, in my case, it hangs while enumerating the pretended \\wsl s...

Same for me. The program just hangs and needs to be terminated from the task manager. It does not only affect iMPACT but also other programs from the Xilinx ISE suite, as well. I intend to do some debugging after Christmas.

Perhaps the bombs are due to the absence of a boot device. (No floppy drive configured, maybe?) EDIT: Then again, Hatari has a built-in debugger, so it should be easy to find out where and why it bombs. Hmm... If only there was an open-source, actively developed OS written in a higher level language...

My only thought is simply that EMUTOS has a faster keyboard repeat rate than TOS404 making it unusable in FF mode. And I was only saying that to me it is equally "borderline" usable, i.e., it get repeated key press events with both TOS 4 and EmuTOS: https://www.youtube.com/watch?v=hnPqqv9...

So are you suggesting EMUTOS doesn't work with ACC or CPX then ? As the setup is identical other than changing the ROM image. If a CPX for example caused the keyboard repeat rate to change, then why wouldn't it also do the same for EMUTOS ? Of course, EmuTOS works with ACCs and CPXes that set keybo...