It logs into the drives and lists (empty) directory.
Well, kinda "empty" -
Here's proof it works on real hardware 
And, you did it with which version of BEER firmware, may I ask? 1.8 or 1.9?
Thank you.
Firmware version on my interface is 1.9
Here's proof it works on real hardware
Very well! Congratulations buddy.
And, you did it with which version of BEER firmware, may I ask? 1.8 or 1.9?
Thank you.
Firmware version on my interface is 1.9
Got it, thanks.
So far, we are here:
CP/M 3 interoperates with Beer ROM kernel well.
But the disk parameters, hardcoded into CP/M, do not correspond with the geometry of drives itself. (That's the reason, in my opinion).
It looks like format didn't complete because Beer IDE requires HPREP to be used instead.
Yes, format definitely didn't complete. It was a dummy code from BEER, that had worked.
Same thing happens prior to file system initialization during Uzix installation.
Interesting.
Assuming drive A is already formatted, there's also the problem COPYSYS raises that error.
If copysys is the equivalent of old dos "sys" command, maybe try copying manually from an existing installation on diskette for example?
Ideally, I thought COPYSYS transfers system-reserved boot tracks to another disk, not files. But here it doesn't seem to be exactly the case, as it creates a file cpm3.sys on a target disk...
