|
|
|
|
— |
blog:pushbx:2024:0129_late_january_work [2024-01-29 18:08:56 +0100 Jan Mon] (current)
ecm created |
| | ====== Late January work ====== |
| | |
| | **2024-01-28** |
| | |
| | Here's this week's work. |
| | |
| | |
| | ===== lDebug ===== |
| | |
| | ==== dpb.eld ==== |
| | |
| | * [[https://hg.pushbx.org/ecm/ldebug/rev/2fc6be2c34ef|Add ADDRESS mode]] to specify address to read DPB from instead of a drive |
| | * [[https://hg.pushbx.org/ecm/ldebug/rev/40c90d3aa601|Add EXTENDED= mode]] with FREEDOS, MSDOS, [[https://hg.pushbx.org/ecm/ldebug/rev/7a8632be6633|and EDRDOS keywords]] to select format |
| | * [[https://hg.pushbx.org/ecm/ldebug/rev/f8ab95430062|Add ONLY keyword]] to skip base DPB |
| | * [[https://hg.pushbx.org/ecm/ldebug/rev/f919a916ad7b|Add LIST SKIP number]] and [[https://hg.pushbx.org/ecm/ldebug/rev/3642560db852|LIST DRIVE drive modes]] to use DPB pointer chain from the DOS List of Lists |
| | * [[https://hg.pushbx.org/ecm/ldebug/rev/7632f946e120|Add LIST AT mode]] to specify address of the DOS List of Lists |
| | |
| | This last point [[https://hg.pushbx.org/ecm/ldebug/rev/cb7a0a1d450c#l1.34|is interesting]] because it uses the debugger's ''getaddrX'' function with a 86 Mode segmented address, even in Protected Mode. This appears to have no ill effect. The default segment for the LIST AT address is read from the 86 Mode interrupt vector 31h's segment which will address the DOS data segment in FreeDOS and EDR-DOS. Therefore, a command like ''ext dpb.eld list at 26 drive C:'' is sufficient to access a DPB without using DOS at all, but not needing to find the exact address of the DPB either. |
| | |
| | |
| | ==== Other ==== |
| | |
| | * [[https://hg.pushbx.org/ecm/ldebug/rev/2639075fad77|Disable reclaim.eld hint]] by default |
| | * boot.asm: [[https://hg.pushbx.org/ecm/ldebug/rev/3b26a6d6dafa|Allow trailing blanks]] after BOOT PROTOCOL= filenames even with CMDLINE=0 |
| | |
| | |
| | ===== inicomp ===== |
| | |
| | [[https://hg.pushbx.org/ecm/inicomp/rev/ebc8a12f4841|Add the C mode test to display the number of dots]] that would be displayed during a full depack run. This is not used yet, but will allow to display a more useful progress indicator later. |
| | |
| | |
| | ===== bootimg ===== |
| | |
| | [[https://hg.pushbx.org/ecm/bootimg/rev/e1e9e530b4a2|Display how many bytes are missing]] when the image becomes too full. |
| | |
| | |
| | ===== FreeDOS kernel ===== |
| | |
| | I [[https://github.com/FDOS/kernel/issues/121|submitted a bug report to the kernel]] on what happens when the fdconfig.sys SHELL= line has a leading digit at the beginning of the specified filename. This was reported to one of the mailing lists earlier. Todo: Note that inserting a backslash should work around the problem. |
| | |
| | I also want [[https://github.com/FDOS/kernel/pull/120|to push the ecm-boot32-dl branch]] to merge it into the main kernel branch soon. Its Pull Request has been sitting for more than a week without any reactions. |
| | |
| | Finally, I want to change the boot, boot32, and boot32lb loaders to move their buffer uses up to linear 22000h (or segmented 1FE0h:2200h) in order to allow loading with 128 KiB/cluster if the kernel file fits within 128 KiB, and with an /L parameter between ''60'' and ''200'' to SYS. With the FAT32 loaders this is probably not possible yet, and with the FAT12/FAT16 loaders it may depend on the trail of the file cluster data being padded with zeroes. |
| | |
| | {{tag>ldebug edrdos freedos inicomp bootimg}} |
| | |
| | |
| | ~~DISCUSSION~~ |
| |
