tkchia

Hello @tsupplis, > None of the cp/m-86 emulators work decently. and in some cases where there is no dos equivalent, I need to use a CP/M 8080/Z80 binary with a...

Hello @ivan-avalos, What information exactly, regarding memory, would you like to be able to log? Thank you!

Hello @tfarina , The makefile should still work (and it does work on my Linux box). Many versions of `make` have built-in "implicit rules" for building `.o` files from corresponding...

Hello @ghaerr, hello @Mellvik, > You may be on to something here: lets take a closer look at the probing routines used by bioshd.c for the devices, in particular bioshd_gethdinfo...

Hello @Mellvik, > I don’t know what to look for yet, but I’ll compare the values on floppy booted and HD booted systems. > Here’s the HD booted: > elks17#...

Hello @ghaerr, Hmm... is the bug what I suspect it is? If my surmise is correct: * The BIOS did set `int 0x1e` to point to the "standard", IBM-compatible DDPT...

Hello @ghaerr, hello @Mellvik, Thanks for the heads-up! > What I don't yet understand is how this only fails on HD boots and never FD, but I suppose that all...

Hello @Mellvik, Thanks! This MBR code is highly interesting, but also a bit worrying. I hope this particular MBR is not malware (and I am not kidding). More on that...

Hello @Mellvik, hello @ghaerr, Some quick observations: * Yes, it turns out that the MBR does transfer control to the boot partition's bootloader through `0x7c0:0`. For some reason, the MBR...

Hello @ghaerr, > can you post the binary boot block? @Mellvik had provided a link: https://github.com/jbruchon/elks/files/9331781/SX-MBR.bin.gz . It goes without saying, but anyway: treat with extreme care. :astonished: > Still...