Hi, I just wanted "to add my mustard" (=denglish, =german english) to make this FD update discussion a little
useful for end users (for improved files) by adding the "to-do-list" and "plans for the future" that I found at the
FD base section while working on help 1.1.0 (will surely not be published before update/upgrade/whatever 2023-12 version)
and some bug report links for checking.
useful for end users (for improved files) by adding the "to-do-list" and "plans for the future" that I found at the
FD base section while working on help 1.1.0 (will surely not be published before update/upgrade/whatever 2023-12 version)
and some bug report links for checking.
I know that some of these commands are outdated, but my idea was to remember you what still
could / has to be done. You can find the whole text / documentation files at:
https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/1.3/base/
at the related files. Please do not oversee position 18).
0001) fdisk: (actual: 1.3.4)
Future changes planned for Version 2.0.0:
-----------------------------------------------------------------------------
TO-DO: Complete addition of international language support.
-----------------------------------------------------------------------------
TO-DO: Complete addition of international language support.
Future changes planned for Version 1.8.0:
-----------------------------------------------------------------------------
TO-DO:
-----------------------------------------------------------------------------
TO-DO:
Future changes planned for Version 1.6.0:
-----------------------------------------------------------------------------
TO-DO: Increased the extended partition buffer size by 1 to support
24 extended partitions.
-----------------------------------------------------------------------------
TO-DO: Increased the extended partition buffer size by 1 to support
24 extended partitions.
Future changes planned for Version 1.4.0:
-----------------------------------------------------------------------------
TO-DO: Investigate the possibility of resetting the boot sector
bytes 510 and 511 to 0x00 instead of filling the boot
boot sector(s) with 0xf6 when creating a partition. This
would make a file system easier to repair if a drive was
accidentally fdisked.
-----------------------------------------------------------------------------
TO-DO: Investigate the possibility of resetting the boot sector
bytes 510 and 511 to 0x00 instead of filling the boot
boot sector(s) with 0xf6 when creating a partition. This
would make a file system easier to repair if a drive was
accidentally fdisked.
TO-DO: Fixed a bug that prevented option 5 from being displayed,
????? on the main menu, when more than one physical drive exists.
????? on the main menu, when more than one physical drive exists.
TO-DO: Continued adding support for international languages.
TO-DO: Check for fdisk functionality if the only hard disk is on
the second IDE controller.
the second IDE controller.
TO-DO Fixed the ported BootEasy code.
TO-DO: Regression Testing
1. Maxtor 245MB hard disk (7245AT)
2. Fujitsu 20GB hard disk (MPF3204AT)
3. Western Digital 180GB hard disk (WD1800JB)
1. Maxtor 245MB hard disk (7245AT)
2. Fujitsu 20GB hard disk (MPF3204AT)
3. Western Digital 180GB hard disk (WD1800JB)
TO-DO: Fix drive label modification issues.
TO-DO Fix partition start and end corruption problems with
some non-dos partition types.
some non-dos partition types.
0002) format (0.91w) - todo.txt:
TO-DO Add international language support (e.g. with KITTEN library).
TO-DO Debug FAT32 support. Debug all mirror / unformat data writes.
FAT32 mirror data partially done in 0.91k - depends on your
UNFORMAT whether more mirroring is required. To make things
easier, 0.91l now contains a builtin UNFORMAT. Improved FAT32
MIRROR and Win9x compatibility in 0.91p and 0.91q (again).
FAT32 mirror data partially done in 0.91k - depends on your
UNFORMAT whether more mirroring is required. To make things
easier, 0.91l now contains a builtin UNFORMAT. Improved FAT32
MIRROR and Win9x compatibility in 0.91p and 0.91q (again).
TO-DO Fix any other bugs (see bugs.txt).
TO-DO Clean up the source code, for example: Remove duplicate
duplicate sanity checks. Maybe add checks for division by 0:
0 sec/fat, 0 sec/clust, 0 sec/disk, too few sec/disk...
duplicate sanity checks. Maybe add checks for division by 0:
0 sec/fat, 0 sec/clust, 0 sec/disk, too few sec/disk...
TO-DO (half) Release filesystem locks (Win9x) when FORMAT has to give up
before completing the format process. Otherwise, the system
could be left in a "dangling" state, esp. for 0.91q / newer.
(half-done: ctrl-c handler missing, otherwise done, 0.91r)
TO-DO (half) Modify safe formatting such that it avoids overwriting data.
(e.g. create a mirror.fil before deleting the file system...)
(for now, 0.91r+: mirroring just fails if it would o/w data.)
(e.g. create a mirror.fil before deleting the file system...)
(for now, 0.91r+: mirroring just fails if it would o/w data.)
TO-DO (maybe) Support sector sizes other than 512 bytes (64, 128, 256...).
TO-DO (maybe) SET 40:[9x] values to use all drives on all (even XT) BIOSes?
Optimize non-standard floppy format settings? (...)
Optimize non-standard floppy format settings? (...)
TO-DO (maybe) Use bigger and aligned buffers for harddisk surface scan.
Is a WRITE ONLY scan enough (HARDDISK has to detect errors)?
Is a WRITE ONLY scan enough (HARDDISK has to detect errors)?
TO-DO (maybe) When system files are written, the summary must subtract the
amount of space they take up from the total disk space.
(We just call the SYS tool to write the system files...)
amount of space they take up from the total disk space.
(We just call the SYS tool to write the system files...)
format - bugs.txt:
Known bugs and problems (in 0.91k / known by Brian or Eric):
*** = bug which is definitely still an issue in 0.91t...
Please test and tell if the non-*** problems are REALLY fixed now!
*** = bug which is definitely still an issue in 0.91t...
Please test and tell if the non-*** problems are REALLY fixed now!
*** There should be error handling that allows you to retry when format or
disk read / write errors happen (beyond the default "try N times").
Partially fixed in 0.91n by allowing noncritical disk I/O to fail.
disk read / write errors happen (beyond the default "try N times").
Partially fixed in 0.91n by allowing noncritical disk I/O to fail.
*** Could use separate error messages for CD-ROM, remote, SUBST...
Will, under some circumstances, fail to format due to dma overruns.
Fixed in 0.91?
Fixed in 0.91?
The FAT32 format may not be compatible with MS's operating systems.
Fixed in 0.91i? When running FORMAT itself under MS operating systems,
things are more complicated. Should be fixed in 0.91q (not o), though.
Fixed in 0.91i? When running FORMAT itself under MS operating systems,
things are more complicated. Should be fixed in 0.91q (not o), though.
Floppy format to smaller sizes than the drive default sometimes fails.
(seems to work much better in 0.91c??) 720k are most tricky here.
Formats with more than standard TRACKS only work on "generous" drives!
However, both 1440k and 1680k work fine in 1440k drives :-).
Even 720k support to work now in 0.91o, finally, but you have to use
real DD diskettes for that. USB floppy ONLY supports exact 1440k size.
(seems to work much better in 0.91c??) 720k are most tricky here.
Formats with more than standard TRACKS only work on "generous" drives!
However, both 1440k and 1680k work fine in 1440k drives :-).
Even 720k support to work now in 0.91o, finally, but you have to use
real DD diskettes for that. USB floppy ONLY supports exact 1440k size.
Format after FDISK screwed up (uformat mode active here)...
Fixed in 0.91d?
Looks as if sometimes the kernel (int 21.440d.?860) returns 0 cluster
size while other BPB values are all okay, e.g. on some SCSI systems!?
Possible background: FreeDOS kernel 2035 and older use wrong subunit
number for user block device drivers for IOCTL. Fixed in 2035-devel.
Fixed in 0.91d?
Looks as if sometimes the kernel (int 21.440d.?860) returns 0 cluster
size while other BPB values are all okay, e.g. on some SCSI systems!?
Possible background: FreeDOS kernel 2035 and older use wrong subunit
number for user block device drivers for IOCTL. Fixed in 2035-devel.
0003) attrib:
Call to strupr() should be replaced by call to function, which will
provide support for national characters through DOS NLS. This function
will not affect interface with DOS (it uppercases file names inside), but
affect error messages. Example (if T and S are national characters):
provide support for national characters through DOS NLS. This function
will not affect interface with DOS (it uppercases file names inside), but
affect error messages. Example (if T and S are national characters):
C>attrib dir\nametns.ext
ATTRIB: no targets: DIR\NAMEtNs.EXt
ATTRIB: no targets: DIR\NAMEtNs.EXt
0004) pgme - blablah:
** QCNFTOOL.EXE **
Basic usage of QCNFTOOL. First, please note that if you
do not issue a /W or /X (/WRITE or /EXPORT) command, no
changes or files will be written to disk.
Basic usage of QCNFTOOL. First, please note that if you
do not issue a /W or /X (/WRITE or /EXPORT) command, no
changes or files will be written to disk.
The output file. When this utility starts, the output
filename is unassigned and if a /W or /X comand is
issued the "NONAME.CFG" filename will be used. However,
the first file you /READ will set the output name
to the same filename that is read. Any future changes to
the output filename will reguire setting it using the
/OUTPUT switch.
filename is unassigned and if a /W or /X comand is
issued the "NONAME.CFG" filename will be used. However,
the first file you /READ will set the output name
to the same filename that is read. Any future changes to
the output filename will reguire setting it using the
/OUTPUT switch.
Also to issue many or extremely long commands, us the
/FILE option. The file will be process the same as one
single set of commands. See the incleuded KIOSK.OFF and
KIOSK.ON files for an example.
/FILE option. The file will be process the same as one
single set of commands. See the incleuded KIOSK.OFF and
KIOSK.ON files for an example.
0005) jemm / jemmex - readme: REMOVED from list
0006) ctmouse - ctmouse.txt
Option /S, whose syntax is described in the help screen, disables PS/2
support and can specify the COM port to be checked for a mouse connection
and its IRQ line; option /P disables serial protocols. If option /S is
present in the command line, but PS/2 support is also required, then
option /P must also be present.
support and can specify the COM port to be checked for a mouse connection
and its IRQ line; option /P disables serial protocols. If option /S is
present in the command line, but PS/2 support is also required, then
option /P must also be present.
If a COM port number is not specified with the /S option, then CTMOUSE
searches all COM ports. If an IRQ line is not specified with the /S
option, then the default IRQ line value is IRQ4 for COM1/3 and IRQ3
for COM2/4. In the future IRQ autodetection will be added.
searches all COM ports. If an IRQ line is not specified with the /S
option, then the default IRQ line value is IRQ4 for COM1/3 and IRQ3
for COM2/4. In the future IRQ autodetection will be added.
0007) display - readme
1.6.- Future wishes
In a nearby future, I'll be considering these tasks:
(1) Turn the files into proper device drivers (expect by 1.00)
Here I show a list of wishes that I'd leave for other contributors:
- load CPI files in several chunks (as MS-DISPLAY does)
- configure more than one device at a time. E.g.:
DEVICE=PRINTER.SYS LPT1=... LPT2=...
- (DISPLAY.SYS) communicate with ANSI.SYS via IOCTL calls
- (PRINTER.SYS) enable the Privileged Lock Codepage Switching feature
- load CPI files in several chunks (as MS-DISPLAY does)
- configure more than one device at a time. E.g.:
DEVICE=PRINTER.SYS LPT1=... LPT2=...
- (DISPLAY.SYS) communicate with ANSI.SYS via IOCTL calls
- (PRINTER.SYS) enable the Privileged Lock Codepage Switching feature
0008) fdapm - fdapm.txt:
... and this is the TODO LIST ...
handlers.asm some POWER API "set" functions are only dummies, you
may want to change that.
Hooked interrupts are roughly complete, the main work
should be done in "working" and "idling".
UNIDLECHECK if you want to define this (activate it at compile
time), you must fill in: 1. i08: timer tick handler,
count down and call idling if zero reached.
2. working: count up general busy-ness count which
i08 counts down - the rest is there since Nov 2003.
(in handlers.asm and hooktsr.asm)...
time), you must fill in: 1. i08: timer tick handler,
count down and call idling if zero reached.
2. working: count up general busy-ness count which
i08 counts down - the rest is there since Nov 2003.
(in handlers.asm and hooktsr.asm)...
UNLOAD add a way to remove FDAPM from memory (no need to be
compatible to MS POWER - you cannot remove that one).
compatible to MS POWER - you cannot remove that one).
... last but not least, this is the KNOWN COMPATIBILITY RISK LIST ...
APM BIOSes Some APM BIOSes have bugs like spinning up the disks
at the moment when they cut power or not being able
to enter sleep / standby mode properly. Hints for
workarounds are always welcome. For now, use PUREOFF
instead of POWEROFF to avoid the problem.
Connect bug If your software fails to DISconnect from the protected
mode APM BIOS interface, weird things can happen when
FDAPM connects the interface in real / v86 mode later.
mode APM BIOS interface, weird things can happen when
FDAPM connects the interface in real / v86 mode later.
QEMM Some EMM386 drivers like some QEMM versions do not allow
DOS to halt the CPU. In that case, APMDOS mode has little
or no energy saving effect.
DOS to halt the CPU. In that case, APMDOS mode has little
or no energy saving effect.
EMM386 Some EMM386 drivers only allow int 15.87 access to normal
memory. The ACPI tables, however, are not "normal" - for
some computers, they are at the end of the 4 GB address
space (some EMM386 always allow access there, as VGA RAM
framebuffers etc are in that area, too), but for other
computers, the tables are at the end of your real RAM,
yet (of course) excluded from use for EMS / XMS / other.
memory. The ACPI tables, however, are not "normal" - for
some computers, they are at the end of the 4 GB address
space (some EMM386 always allow access there, as VGA RAM
framebuffers etc are in that area, too), but for other
computers, the tables are at the end of your real RAM,
yet (of course) excluded from use for EMS / XMS / other.
HIMEM Some versions of HIMEM have broken int 15.87 wrappers to
manage A20 state during access to RAM outside the first
1 MB. If FDAPM ACPI functions fail, add EMM386 (which
will override the HIMEM int 15 handler) or use another
version of HIMEM or try without HIMEM loaded at all.
manage A20 state during access to RAM outside the first
1 MB. If FDAPM ACPI functions fail, add EMM386 (which
will override the HIMEM int 15 handler) or use another
version of HIMEM or try without HIMEM loaded at all.
SSHDOS The DOS SSH client (compiled with DJGPP) never seems to
be idle enough for APMDOS. Let me know your ideas about
saving energy while SSHDOS is running... Thanks.
be idle enough for APMDOS. Let me know your ideas about
saving energy while SSHDOS is running... Thanks.
0009) pdtree - changes.txt:
Future Plans: When time permits. KJD
I would like to get it to compile using other
compilers, such as DJGPP, Dunfield's Micro C,
and Borland's TC++ v1.01
Update cats library (use cats v4 aka kitten
for DOS and cats v3.97 for Windows)
Update DOS version to detect screen size and
if output redirected or not.
I would like to get it to compile using other
compilers, such as DJGPP, Dunfield's Micro C,
and Borland's TC++ v1.01
Update cats library (use cats v4 aka kitten
for DOS and cats v3.97 for Windows)
Update DOS version to detect screen size and
if output redirected or not.
0010) unformat - readme.txt:
Future Plans:
1. Add more functionality as per the spec on unformat.
2. Add a warning before the program starts any drive activity
to warn the user of the possibly destructive nature of this
program if used on a drive that does not need unformatted.
3. Fix any encountered bugs.
1. Add more functionality as per the spec on unformat.
2. Add a warning before the program starts any drive activity
to warn the user of the possibly destructive nature of this
program if used on a drive that does not need unformatted.
3. Fix any encountered bugs.
0011) fdxms286 - todo.txt
* Is there a race while allocating a handle? Like this: a call to
xms_alloc_xms, interrupt occurs giving control to interrupt
routine that calls xms_alloc_xms -> bang!
xms_alloc_xms, interrupt occurs giving control to interrupt
routine that calls xms_alloc_xms -> bang!
For much later:
* Somebody (I've forgotten whom, sorry) suggested to show the trace
lines on a monocrome grafics adapter if installed. While I
think it's a good idea, I'm not inclined to do it as I don't
have the necessary hardware.
lines on a monocrome grafics adapter if installed. While I
think it's a good idea, I'm not inclined to do it as I don't
have the necessary hardware.
0012) fdxms - todo.txt
* Is there a race while allocating a handle? Like this: a call to
xms_alloc_xms, interrupt occurs giving control to interrupt
routine that calls xms_alloc_xms -> bang!
xms_alloc_xms, interrupt occurs giving control to interrupt
routine that calls xms_alloc_xms -> bang!
For much later:
* Somebody (I've forgotten whom, sorry) suggested to show the trace
lines on a monocrome grafics adapter if installed. While I
think it's a good idea, I'm not inclined to do it as I don't
have the necessary hardware.
lines on a monocrome grafics adapter if installed. While I
think it's a good idea, I'm not inclined to do it as I don't
have the necessary hardware.
0013) mirror - bugs.txt:
BUGS.TXT
Bugs:
Bugs:
1. Will destroy any data at the end of the disk when the mirror image is
written. (Probably only occurs on floppy disks at this time.)
written. (Probably only occurs on floppy disks at this time.)
0014) pdtree - changes.txt:
Future Plans: When time permits. KJD
I would like to get it to compile using other
compilers, such as DJGPP, Dunfield's Micro C,
and Borland's TC++ v1.01
Update cats library (use cats v4 aka kitten
for DOS and cats v3.97 for Windows)
Update DOS version to detect screen size and
if output redirected or not.
I would like to get it to compile using other
compilers, such as DJGPP, Dunfield's Micro C,
and Borland's TC++ v1.01
Update cats library (use cats v4 aka kitten
for DOS and cats v3.97 for Windows)
Update DOS version to detect screen size and
if output redirected or not.
0015) zip - bugs:
- zip sometimes crashes on some versions of NetBSD (0.8, 0.9 and early
0.9-current), FreeBSD (<= 1.1) and BSDI (< 1.1) . This is due to a
bug in stdio.
Upgrading the stdio package in /usr/src/lib/libc/stdio should
fix the problem. See *BSD mirrors in src/lib/libc/stdio
You must at least replace setvbuf.o in all the libc's with a newer version.
0.9-current), FreeBSD (<= 1.1) and BSDI (< 1.1) . This is due to a
bug in stdio.
Upgrading the stdio package in /usr/src/lib/libc/stdio should
fix the problem. See *BSD mirrors in src/lib/libc/stdio
You must at least replace setvbuf.o in all the libc's with a newer version.
0016) assign - bugs:
Known bugs:
+ When starting ASSIGN from a secondary shell some shells don't let ASSIGN
find its resident copy. It will then load itself more than once into
memory or complains about that it is not loaded.
+ When starting ASSIGN from a secondary shell some shells don't let ASSIGN
find its resident copy. It will then load itself more than once into
memory or complains about that it is not loaded.
0017) htmlhelp - reported by W. Spiegl
a) links break out of file, means: if you go to the bottom with arrow down, suddenly other
links are shown, sometimes bad links, if you press enter, it may crash
b) it does not like going back from one command to another, after a while
there maybe a crash,
c) see a), there are sometimes more free lines shown than there should exist,
links are shown, sometimes bad links, if you press enter, it may crash
b) it does not like going back from one command to another, after a while
there maybe a crash,
c) see a), there are sometimes more free lines shown than there should exist,
0018) some more bugs reported by me at:
https://github.com/FDOS/freecom/issues OR:
https://sourceforge.net/p/freedos/bugs/ OR:
https://gitlab.com/groups/FreeDOS/-/issues
https://sourceforge.net/p/freedos/bugs/ OR:
https://gitlab.com/groups/FreeDOS/-/issues
What about backup / restore that was announced for this year?
Thanks for reading.
_______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
