Hi everybody, I am in the process of developing an application and I use Megaspeedy in various drive emulation modes to test my application. Recently i came up with two issues and I am not sure whether they are bugs in the firmware or I am doing something wrong.

1. When MegaSpeedy is in US Doubler mode GET PERCOM BLOCK command ($4E) always returns a sector size of 128 bytes even if the disk is double density. When I switch the mode to Speedy or Happy it returns the correct size of 256 bytes. The rest of the Percom info seems to be correct.

2. When MegaSpeedy is in HAPPY mode I issue a command ($48) to put the drive in UNHAPPY mode, the drive reports a speed index of $0A, then I change the baud rate from 19200 to 52640 In this mode the drive is supposed to act like a US Doubler 1050, however when i issue a read sector command ($52) the drive returns the data frame with an extra checksum byte For example a 128 byte sector is returned as "4143.....sector data......9898". The first 98 is the correct checksum, but the second one is extra, so it looks like the drive is returning a 129 byte sector instead of 128, this of course upsets the application which expects 128 bytes.

I found a workaround for problem 1, but no luck with problem 2 so far.