If serial hardware flow control is enabled, but not working, then a system will appear dead because it won't send any data to the host computer. This change suppresses hardware flow control during boot just to ensure that boot messages can make it to the serial console. This will only be effective for serial interfaces that support dynamic management of HFC.
Edge case where the CPU speed detection routine would overflow in a fast emulator and return a speed of 0.000 MHz. Modified to fail back to the default CPU speed from the config file if an overflow occurs.
- Revamped CTC detection algorithm hoping to handle problem XRBR is having
- Fixed typo in dynamic CPU speed test that caused it to not be properly recorded/reported (credit XRBR)
- Allow use of DEL/RUBOUT keys as backspace in ROM Loader and Debug Monitor
- Set the default CPUOSC to 8MHz (default value in the project's
documentation), updated the User Guide
- Set the FDD controller to ZETA2 - regression introduced in bd664c3
cp/m fails to boot with the dma driver included but no dma hardware installed. This is because the default "dma_fail_flag" indicates that the dma is good to go. But in safe mode the dma initialization never takes place to find no dma and set this flag, so the memory driver hangs. This change is to make the default status of the flag the failed state so the memory driver will fallback to software in recovery mode.
CBIOS reports *** HBIOS Heap Overflow, when the HBIOS is big (i.e. lots of included drivers)
Trigger build failure when CCP will not fit in heap.
Slightly more informative CBIOS error message
- Tweaks to SURVEY and PORTSWP to improve port detection accuracy and handle Z280 better
- Recover a **lot** of wasted space in dbgmon using a few built-in utility routines instead of entire util.asm
- Improve the (D)evice command in romldr to use the HBIOS routine which is much more complete and saves space
In the IDE and PPIDE drivers, a CF Card is differentiated from a Hard Disk using the first word of the result of the IDENTIFY DEVICE command. The value 0x045A was recently added because it was seen from a CF<->SD Card adapter. However, the value has now been seen from a spinning hard disk. Since the value is ambiguous and not defined in the CF Card specs, I am removing it from the list of CF Card signatures.
Credit to Mark Elkin for identifying this and helping me track it down.
Added configuration setting VDAEMU_SERKBD which can be used to specify any serial unit # to be used as the keyboard for the video terminal. Default value is $FF which means to use the default hardware keyboard. All other values mean that terminal input is to come from corresponding serial unit #.
Also a couple more tweaks to the p-System boot volume.
