Re: [Freedos-devel] FreeDOS 1.4 known issues

[Wilhelm Spiegl via Freedos-devel]

Okay,

here is a first list of known bugs (this list is not complete):

 

a) shsufdrv: mounting a diskette image does not work. There is an error message:
   U<EFRDOS5.1 failed to open.
   Tested with VirtualBox.
   This is known by the programmer, he told me that it works on other DOSes, but not with FreeDOS.
   There exists a working version (which is not published) - but no source code for it was published,

   although Berki and I already asked for it.
   shsuRdrv works fine.

 

b) chkdsk: most of them are reported at: https://sourceforge.net/p/freedos/bugs/search/?q=chkdsk
   and still existent.
   aa) #380 serial number is printed in "bbbb-aaaa" instead of "aaaa-bbbb".
   bb) #16 message: Assertion failed: 0, file blkcache.c, line 322 when running chkdsk /r
       This message only appears when using a real diskette drive and starting FD from VirtualBox
       (maybe others too), but NOT if i use an image of this diskette.
   cc) #382, 383: serial number is only printed when label exists, works on MS-DOS
   dd)  chkdsk c: /d seems not to work, I only get the message: /d

 

c) edit: there are so many bugs reported at gitlab (one a small part of it see:)
https://gitlab.com/groups/FreeDOS/-/issues/?sort=updated_desc&state=opened&search=edit&first_page_size=20&show=eyJpaWQiOiI2IiwiZnVsbF9wYXRoIjoiRnJlZURPUy9PUy9mZC1ubHMiLCJpZCI6MTAwOTc2ODQzfQ%3D%3D
There are also several at sourceforge.net (02/96/112/120/214/264/350/366)
(96 seems to be the bug reported several times in combination with not working \}][{ etc.)
that it would make sense to create a new editor. But anyhow it works.

 

d) swsubst (replaces subst and join): the "subst" part of swsubst works, whereas:
   swsubsst /j d: c:\test does not work. The folder C:\test is empty and d: (which contained
   files) is unvalid after executing the command. Tested with diskette drive and FAT16 and FAT32.
   Please check if I handled it wrong.

 

e) NO bug, but files missing in FD 1.4 and earlier: KC200x.zip and KC200s.zip,see: https://sourceforge.net/p/freedos/bugs/181/
you can find them at: http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/keyb/fdkeyb-2.0/
As this folder is outdated it should be copied to the actual folder too. Thx.

 

f) bolitare still has "bg = blue_angle.jpg" in config.txt instead of blue_ang.jpg. Causes a hang.

 

g) flashrom (not part of FD1.4, but can be downloaded via fdnpkg) without a given file reports:
   command or filename not found. - "dmidecode".

Sent: Sunday, April 27, 2025 at 1:41 AM
From: "Jim Hall via Freedos-devel" <freedos-devel@lists.sourceforge.net>
To: "Technical discussion and questions for FreeDOS developers." <freedos-devel@lists.sourceforge.net>
Cc: "Jim Hall" <jh...@freedos.org>
Subject: Re: [Freedos-devel] FreeDOS 1.4 known issues

On Sat, Apr 26, 2025 at 4:08 PM Jerome Shidel via Freedos-devel
<freedos-devel@lists.sourceforge.net> wrote:
[..]
> Just my thoughts on such a list.
>
> I think this might be something to create in the Documentation project on the in the FreeDOS Archive on GitLab.
>
> https://gitlab.com/FreeDOS/docs
>
> Maybe a “known_issues” subdirectory, with files for current and future releases.
>
> Then like other such documents, Jim could pull a copy to place on the FreeDOS.org site whenever it is updated.


I like this idea!

And it looks like I need to finally get off my butt and actually set
up the process that pulls documents from GitLab into the new
Documentation website. (Once that's there, it's probably just one step
to copy the "known issues" file onto the www.freedos.org/downloads
directory so we can reference it there.)


_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel