Volkert de Buisonjé

@crazii Alright, I ran into something weird. Building without `DEBUG=1` works fine both on my current development machine (using [act](https://github.com/nektos/act) to test the GitHub Actions Workflow locally), but [fails in...

Thanks, I'll try that. In the meantime, I created a separate issue (#7) for that AMD system that I just tried to test USBDDOS on. I also uploaded a video...

I just tried `-mxgot` locally, but DJGPP didn't support it. Apparently, this option is available only when compiling for `M680x0`, `ColdFire` and `MIPS` architectures: https://man7.org/linux/man-pages/man1/gcc.1.html

@Torinde That makes sense, but I'll wait for USBDDOS to mature a bit first, since right now it's hanging on the two different machines that I tried it on. Have...

With a debug-enabled build that I built locally, I recorded a video of the output, since a lot of debug logging scrolled past the screen before it ultimately failed in...

Also, here is the output of `lsusb -t` for this same motherboard: ``` /: Bus 09.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M /: Bus 08.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p,...

[As I mentioned here](https://github.com/crazii/USBDDOS/issues/5#issuecomment-1872072221), the same problem occurred when I tried to load `USBDDOS` without having `SBEMU` loaded.

Trying both `/HID` and `/DISK` (so `LH D:\USBDDOSP.EXE /HID /DISK`) instead of just `/HID` got the same result. The C: drive couldn't be accessed anymore. I'm now going to try...

I just tried it with only `/DISK` (without `/HID`), and I got the exact same result, and C: wasn't accessible anymore either. I'm now going to try it without `HDPMI32i`...

Okay, that was pretty pointless, since it just resulted in `Load error: no DPMI - Get csdpmi*b.zip`. Even just running `USBDDOSP.EXE /?` to get the help info would result in...