Hi Lorenzo, I just checked your last post (2020-05-10): c:\freedos\nls\htmlhelp.es does not work, but it is not necessary to execute it this way. In the latest freedos test version, look for FDT24xx live CD https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/ you can install the most actual version and you will see, if you install it in spanish, it should work by typing "help" or "htmlhelp" now. Ifyou add one of the options "/F1 or /F2" you even get another colour scheme....
Hi Lorenzo, I just checked your last post (2020-05-10): c:\freedos\nls\htmlhelp.es does not work, but it is not necessary to execute it this way. In the latest freedos test version, look for FDT24xx live CD https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/ you can install the most actual version and you will see, if you install it in spanish, it should work by typing "help" or "htmlhelp" now. Ifyou add one of the options "/F1 or /F2" you even get another colour scheme....
This is simple, goto: https://gitlab.com/FreeDOS , editors, then mined, then appinfo and mined.lsm.
OK, after a few minutes of work here is a summary now: We talk about the codepages 862 (Isr), 856 (Isr) and 864 (Egypt and others) as well as about xkeyb, mkeyb and keyb and config.sys (here: country and country.sys). Country.sys does not support 864 and 856, there is a short message while booting. see also https://bootablecd.de/FreeDOS-Internet-version/help110/en/hhstndrd/cnfigsys/country.htm, 856 is not mentioned here and 862 seems to work. But this setting is not really needed. If you think you...
as FDT2408 says it supports is keyboard (is=israel) mkeyb is stable, I know that there are three different keyboards. But the latest version only installs "mkeyb is" without any other country related settings. The result was that virtualbox was unable to support right CTRL button and mined did not work with bidi. So I simply want to test all combinations with the different keyboards, codepages and country settings to be sure which combinaions really work. And this will last a while. I have no plans...
Hallo Klaus, Ich bin leider etwas spät dran. Versuch doch mal FD 1.3 bzw. die aktuellere Testversion FDT240x (live CD) unter: https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/ Das Problem, dass ich in deiner Beschreibung sehe, ist, daß die FreeDOS ISO oft zweimal gebootet werden muß, einmal um die Festplatte zu partitionieren (fdisk) - das erfordert zwingend einen Neustart, beim zweiten Mal sieht der Bildschirm ähnlich aus, führt aber dann weiter (Tastaturauswahl, einfache...
Hallo Klaus, Ich bin leider etwas spät dran. Versuch doch mal FD 1.3 bzw. die aktuellere Testversion FDT240x (live CD) unter: https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/ Das Problem, dass ich in deiner Beschreibung sehe, ist, daß die FreeDOS ISO oft zweimal gebootet werden muß, einmal um die Festplatte zu partitionieren (fdisk) - das erfordert zwingend einen Neustart, beim zweiten Mal sieht der Bildschirm ähnlich aus, führt aber dann weiter (Tastaturauswahl, einfache...
FD has an updated format command 0.92. I know that this question is extremely late, but can the bug be reproduced with a newer FD version - if possible, could you try the latest version at: https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/ (actual FDT2408, FDT2409 should come out in 09/2024)? Was it a built-in diskette drive?
FD has an updated format command 0.92. I know that this question is extremely late, but can the bug be reproduced with a newer FD version - if possible, could you try the latest version at: https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/ (actual FDT2408, FDT2409 should come out in 09/2024)?
Should be solved with FD 1.3 and/or actual FDT versions. I think this ticket can be closed.
No, it doesnt. It works as follows (tested): KEYB TR,857,C:\FREEDOS\BIN\keybrd2.sys /ID:440 (different syntax) see htmlhelp https://www.bootablecd.de/FreeDOS-Internet-version/help110/en/hhstndrd/base/keyb.htm section examples. I think this ticket can be closed.
I feel this is getting much more complicated than it is: Just for info: It is becoming more complicated as FDT2408 says it supports is keyboard, but I noticed that it uses mkeyb which requires the right CTRL (Strg) button - and virtualbox uses this for other purposes. So I will have to run tests on bare metal to see what really happens. This may last a while.
Okay, it is now sure that it is not the debt of FD when VGACopy does not work. I just tested it with two diskettes, one of them booted FD and started vgacopy on pure metal, the second was formatted (1,7 MB) and works fine! It can even be made bootable! If you have a closer look at VGACopy05.png you may see that there were problems with the oversize (marked in yellow) in virtualbox in combination with USB diskette drive. As this ticket is related to VGACopy I think it can be closed.
Okay, it is now sure that it is not the debt of FD when VGACopy does not work. I just tested it with two diskettes, one of them booted FD and started vgacopy on pure metal, the second was formatted (1,7 MB) and works fine! If you have a closer look at VGACopy05.png you may see that there were problems with the oversize (marked in yellow) in virtualbox in combination with USB diskette drive. As this ticket is related to VGACopy I think it can be closed.
Okay, I am a little bit further now: I was able to create high formatted floppy disks with vgacopy under Win XP on bare metal and a real diskette drive - and FreeDOS was able to read them (even from an USB disk) in virtualbox, see enclosed picures. But the same diskette drive had problems with creating disks in virtual box and an USB drive. So it seems to me that virtualbox refuses to write more than 1,4 MB. I will try to run some more tests with bare metal.
Okay, I am a little bit further now: I was able to create high formatted floppy disks with vgacopy under Win XP on bare metal and a real diskette drive - and FreeDOS was able to read them (even from an USB disk) in virtualbox, see enclosed picures. But the same diskette drive had problems with creating disks in virtual box and an USB drive. So it seems to me that virtualbox refuses to write more than 1,4 MB. I will try to run some more tests with bare metal.
He talked only about Mönkemeiers VGAcopy that is still available for download (as freeware). https://archive.org/details/vgacp625 I remember it. I know that there were several tools for creating oversizes, 2.8 MB diskette drives were very expensive. At the moment my USB diskette drive tries to format a diskette to 1,785 kB, after felt 15 minutes it is at sector 46. I will report later about the result. This were the good old times where you needed a lot of time for formatting one diskette!
He talked only about Mönkemeiers VGAcopy that is still available for download (as freeware). https://archive.org/details/vgacp625 I remember it. I know that there were several compressing tools - one of the best unusable was PTS-DOS format with different oversizes. At the moment my USB diskette drive tries to format a diskette to 1,785 kB, after felt 15 minutes it is at sector 46. I will report later about the result. This were the good old times where you needed a lot of time for formatting one...
He talked only about Mönkemeiers VGAcopy that is still available for download (as freeware). I remember it. I know that there were several compressing tools - one of the best unusable was PTS-DOS format. At the moment my USB diskette drive tries to format a diskette to 1,785 kB, after felt 15 minutes it is at sector 46. I will report later about the result. This were the good old times where you needed a lot of time for formatting one diskette!
What about this text, it is not country specific, and says everything that people that use bidi need. Other people will be not interested in it. More information about mined is the job of mined help. I think this enough. (13) FreeDOS supports these codepages, but it does NOT support bidi, means, it cannot write from right to left as it is done in parts of the world ("Something like this" will have to be typed "siht ekil gnihtemoS" in FreeDOS. For proper bidi support, a third party program is required,...
Is for https://github.com/FDOS/freecom/blob/master/utils/mkinfres.c Maybe this ticket can be closed?
The bugs were fixed. I think this ticket can be closed.
The actual version is at: https://github.com/shidel/fd-nls/blob/master/mem/nls/mem.it and shows a lot of FIXME text. So this ticket is still open.
It seems to work now with FDT2408 - with the exception that not everything is translated. Jerome Shidel has written a program that makes it easier to create the text for fdimples. I think this ticket can be closed.
@E.C.Masloch: Can this ticket be closed?
Hi Jerome, can you check if this still happens with format 0.9.2?
more /? offers "Qq" to quit the program. But it does not work when you are at "more"- nothing else. So it would be fine if Qq would work too. Additional STRG-Z could also be mentioned at the /? help. And a hint that you have to use the correct keyboard driver for "Z".
more /? offers "Qq" to quit the program. But it does not work when you are at "more"- nothing else. So it would be fine if Qq would work too. Additional STRG-Z could also be mentioned at the /? help.
The bugs were fixed. I think this thread can be closed.
Hmmm, hard to say 11 years later what is the reason for this. And with no information if there was another system on your computer etc. I assume "unknown filesystem" means that there was either no filesystem on your computer or another one (e.g. Windows with NTFS filesystem or a Linux filesystem). The only thing I can recommend is to try FD 1.3 or, even better one of the FDT24xx CDs.
From my side there are some questions too: a) You wrote "script"? Does this NOT affect all texts, e.g. documents etc? b) "(i.e. this gets reversed to siht)" I think this is a bad to understand example. I didn't at the beginning. Something like: To be able to read: "This is a text." in bidi (from right to left) you have to type: ".txet a si sihT" in standard DOS editors. As this is almost unduable you need special editors like mined? What happens if you type: ".txet a si sihT" into a standard editor...
I ran an additional test with 4 virtual 500 MB HDs - and there were entries in Sector 0 of all other HDs. The entries in HD001 - HD003 were identical. So I assume this seems to be correct.
I ran an additional test with 4 virtual 500 MB HDs - and there were entries in Sector 0 of all other HDs. So I assume this seems to be correct. I assume it is correct.
I had the following effect with 2 absolutely new virtual HDs and I only executed latest fdisk 1.3.15. Fdisk really wrote on the second HD, as you can see on the screenshots.
As I am only the translator of the help (actual version kpdos 3.1) see my other website: https://www.bootablecd.de/FreeDOS-Internet-version/help110/en/hhstndrd/other/kpdos.htm I will have to ask if this comment is correct (I think it is, but I have to ask). If yes, I will try to correct it. Only a question for security: What do you mean with "siht"? Is it a typo? Do you mean "sight"?
Hi, great! Do you have the permission to close threads? Then it would be great if you could close 29, 178 and 346.
See: https://bootablecd.de/FreeDOS-Internet-version/help110/en/hhstndrd/util/flashrom.htm Be happy that it did not work for you! @Jim and Jerome: Are you SURE that this file should be on FD or FDT24xx?
Hi tizizi, hi Lorenzo, at least Berki should know that all this help bugs have gone with the new htmlhelp.exe version. Thanks, Bernd! So could you please confirm, that the thread can be closed. Thx.
I think this thread can be closed.
I have seen a lot of problems with BIOS updates. Sometimes the producer of the computer added a not working batch file (wrong options, wrong name of flash tool etc!). At a DELL Latitude D531 the latest BIOS (A12) exe version did not work at all (all others before had no problems), I just tried to enter the service tag for this older laptop (ca. 2010) and the service assist says that it does not find the tag, but A12 can be downloaded from another DELL subsite, two years ago it said that it is out...
Hi, it seems it was overlooked to close this thread.
I think this thread can be closed.
Just for info: ReactOS seems to have fixed this. https://jira.reactos.org/browse/CORE-10495
I assume she wanted to backup files from a Win system with NTFS which did no longer boot up. In such cases I recommend the usage of a Linux live CD, especially Knoppix (there exists an english version) as you can add external HDs for backing up - and the NTFS file system of the internal HD is mounted as read/write, so you simply can boot up and backup. Of course read/write is a little bit dangerous, but I know, that mounting HDs with Linux boot CDs can be very tricky for newbies, e.g. Caine live...
There were many changes on Mined since 2012, see: https://mined.github.io/ If necessary, could you report it there? Could you please tell us if this thread can be closed? Thx.
I just tested it: "find fdauto.bat" really works forever. But according to the /? this is the wrong usage: FIND displays lines in one or more text files that contain a string. See examples at FD Help, https://bootablecd.de/FreeDOS-Internet-version/help110/en/hhstndrd/base/find.htm find /C "set" c:\fdauto.bat finds results for "set" find /C "SET" c:\fdauto.bat finds NO results for "SET" find /C /I "sEt" c:\fdauto.bat finds results for "set" and "SET". And this works fast. So I am not sure if this...
As newer FD versions use the bugfixed fdisk -and the maintainer stopped development in 2001 - could this thread be closed?
As newer FD versions use the bugfixed fdisk - could this thread be closed?
This should be fixed with FD 1.3 and the most actual version FDT24xx that can be downloaded here: https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/ In some special cases you have to add a /e when invoking mkeyb in fdauto.bat. I think this thread can be closed.
The actual FD version is 1.3; there are monthly trial versions that improved a lot of things, you can download it at: https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/ I think this report is outdated, so it could be closed.
The last version of XFDisk 0.93 is from 2001 see: https://www.mecronome.de/xfdisk/index.php - it is no longer maintained - whereas fdisk got a lot of updates in the last year, see https://github.com/FDOS/fdisk . So I would recommend fdisk which is actually used and distributed with the FreeDOS trial versions see: https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/ I think with this information in background this thread can be closed.
In difference to actual Win11 (tested) FD remdir has no options /s and /q. So you have to delete each empty folder step by step. Please use deltree instead. I think this thread can be closed.
It seems that a lot of bugs were fixed with version 1.0.8 So I think the thread can be closed.
I assume that in the meantime the usage of these special formats goes only to zero. For using diskettes in virtual machines you can create virtual 2,8 MB diskette images (supported by kernel and by format) and use it. Additional you have more free space. Enclosed an empty image that only contains kernel, command.com and mkeyb. I think the thread can be closed.
Should hopefully solved with version 1.6, see changelog: https://gitlab.com/FreeDOS/base/xcopy/-/blob/master/DOC/XCOPY/history.txt?ref_type=heads I think this thread can be closed now.
I assume this can be done with the actual FreeDOS diskettes. I think this thread can be closed.
I tried to find bsplash.bat at the installed versio of FD 1.2 and FDT2408 - and found nothing. So it is hard which program "MegaBrutal" spoke about. As the name of the program / game is unknown I recommend to close the thread.
As there was no more interest from users side I think this thread could be closed.
I just ran a test: a) it really supports only 2 GB file size. b) when the file is bigger than 2 GB it reports: "[insufficient disk space in destination path]" although there is enought space on the HD.
In the meantime FreeDOS supports files up to 4 GB on FAT32. I tested this by creating files a.txt, b.txt etc, each of them has 1.6 GB size and contains only "AAAAA", "BBBB" etc to find out where the content comes from. Then I ran "copy a.txt + b.txt + c.txt + d.txt + e.txt SUMMARY.txt. It creates a file of 4 GB. The only problem where I am not sure if it works correct is: a) should FD test if it can create a 6 x 1,6 GB file and abort when it sees that this cannot be done? b) should it stop when the...
I think this thread can be closed.
Thank you very much! Seems to be fixed now! From my side the thread can be closed!
dosshell seems to work in FDT2407, but not DOSZIP. It opens the basic window but does not jump to the correct position. As mentioned above, doszip.txt at C:\freedos\bin will solve the problem.
As WIKI is offline for the moment, here another link for the country code: https://www.bootablecd.de/FreeDOS-Internet-version/help110/en/hhstndrd/cnfigsys/country.htm I noticed that several countries already have an updated country code. In case that this theme is already fixed I would propose to close the thread.
I remember this "y" and "z" mixture in virtualbox, as mkeyb history.txt says, it was fixed with version 0.45. FD12 used mkeyb 0.41 - and the thread talks about mkeyb 0.44. The actual version 0.52 sometimes requires the option /e to be able to handle "| \ [ ]" and some other characters (third keyboard layer). Just for info. I think this thread can be closed.
I remember this "y" and "z" mixture in virtualbox, as mkeyb history.txt says, it was fixed with version 0.45. FD12 used mkeyb 0.41 - and the thread talks about mkeyb 0.44. The actual version 0.52 sometimes requires the option /e to show "| \" and some other characters. Just for info. I think this thread can be closed.
I remember this "y" and "z" mixture in virtualbox, as mkeybhistory.txt says, it was fixed with version 0.45. FD12 used mkeyb 0.41 - and the thread talks about mkeyb 0.44. The actual version 0.52 sometimes requires the option /e to show "| \" and some other characters. Just for info. I think this thread can be closed.
No, it doesnt. It works as follows (tested): KEYB TR,857,C:\FREEDOS\BIN\keybrd2.sys /ID:440 (different syntax) see htmlhelp https://www.bootablecd.de/FreeDOS-Internet-version/help110/en/hhstndrd/base/keyb.htm section examples. I think you can close this thread.
Kc200x.zip and kc200s.zip are in an outdated subfolder fdkeyb-2.0 - meanwhile there exists a subfolder fdkeyb-2.11 So it would really be helpful to add them in Gitlab and to create an own folder at Ibiblio. Thx. On my website you can find where they are needed for: https://www.bootablecd.de/FreeDOS-Internet-version/help110/en/hhstndrd/base/keyb.htm
All this was fixed with the new htmlhelp version. When you set LANG=RU or another language and russian (or another) help does not exist, it jumps back to english. It also supports help text written in Unicode now (at least at most of the European countries, if the codepage is set correct). Crashes of older versions are fixed to, thanks Bernd Böckmann! So I think this thread can be closed too.
I just tested FD 1.2 on virtual machines. The ISO image works on vmware and qemu, but not on virtualbox. I never had problems with FD 1.3 or FDT versions. As version 1.2 is out of date I would recommend to set it to "wont fix" or "closed". Thx.
I just tested 1.2 on virtual machines. It works on vmware and qemu, but not on virtualbox. I never had problems with 1.3 or FDT versions. As version 1.2 is out of date I would recommend to set it to "wont fix" or "closed". Thx.
The word "Polieren" does no longer appear in FreeDOS 1.3 and FDT2407. So I think this report can be closed. As it looks like there is nobody who translated the setup text into polish till today. So it makes no sense to add polish during the setup routine.
This bug is fixed with version 1.3.15 of fdisk. So this thread can be closed. What is not yet fixed is, that the whole 2 TB can be formatted (as much as I know Bernd already fixed it, but it is not yet in FDT2407).
As the bugs were solved by newer versions of doszip, I think this thread can be closed.
I had the same problem with 0.52 with all characters on the third layer of a key on certain keyboards (mine had more than 81 or 82 keys). ²³{[]}\~|µ did not work e.g. on a real machine. Solved by mkeyb gr /? which gave the help that has starting with 0.49 (0.48?) a new option; /E was introduced. So if you boot up with mkeyb gr /e everything works fine. Maybe the definition in /? is not optimum explanained, but it helps. Please stop to ride on this theme (debug etc.)
I just tested it. This happens when mkeyb is not the last loaded resident driver. Change the order: ctmouse first, mkeyb last - and it should work.
I just tested it. This happens when mkeyb is not the last resident driver. Change the order: ctmouse first, mkeyb last - and it should work.
Hi, I know that I am more than 18 years too late for this question, but maybe you can help me. I am working on FreeDOS help and searching for newer program versions that are not yet published in the FDT24xx (FreeDOS test version 2024xx) . While doing so, I noticed that 2.09c has no source code available. For this reason still version 2.09 is available for download at FreeDOS.. In case that you get this message (my mail went back): Could you please (if possible) upload the source code for srdisk 2.09c?...
OK, so it is no hardware but a software problem. You should test the different options of jemmex or jemm386, see: https://www.bootablecd.de/FreeDOS-Internet-version/help110-no-fish/en/index.htm , look for jemmex or jemm386 or himemx there, or run "jemmex /? | more" for getting help. The latest executable version is available here: https://github.com/Baron-von-Riedesel/Jemm
Hi, first of all thanks for using FreeDOS. As I learned that it is always good to understand what you really did, some questions: You installed FreeDOS with a 720 kB diskette? Did you use something else than a diskette? The diskette booted up without any problems? You were able to install the whole diskette to the HD without any problems? Any strange messages (HD is full or something else?) Which version did you use (1.3 or FDT2402=most actual) (Sounds crazy why I ask this, but this is important...
Hi, first of all thanks for using FreeDOS. As I learned that it is always good to understand what you really did, some questions: You installed FreeDOS with a 720 kB diskette? Did you use something else than a diskette? The diskette booted up without any problems? You were able to install the whole diskette to the HD without any problems? Any strange messages (HD is full or something else?) Which version did you use (1.3 or FDT2402=most actual) (Sounds crazy why I ask this, but this is important...
Sorry for the following stupid questions, but I have not yet seen this model in real life, only in internet: a) As there is no diskette drive inside - how can you add / install software and the FD kernels? Via USB-stick? Can you boot from USB-stick? Or is there another way? Can the CF card be replaced by another one? b) Is this MS-DOS 6.22 an old official version or was it modified? Is Win 3.0 delivered with it or do you have to buy it yourself? c) Does the BIOS support different harddrive settings...
Sorry for the following stupid questions, but I have not yet seen this model in real life, only in internet: a) As there is no diskette drive inside - how can you add / install software and the FD kernels? Via USB-stick? Can you boot from USB-stick? Or is there another way? Can the CF card be replaced by another one? b) Is this MS-DOS 6.22 an old official version or was it modified? Is Win 3.0 delivered with it or do you have to buy it yourself? c) Does the BIOS support different harddrive settings...
This is a screenshot of the second warning
This is a screenshot of the second warning
While checking the link "cd.textfiles.com" (is not the whole link!) G-Data Internet security refused to go further with a big red message box. Maybe this was a failure, maybe someone now tries to attack the FD group from within the forum? I am not sure, but be warned!
Did you really try version 1.2 of FreeDOS installation CD? Or which version (you did not mention it) If yes, I can understand you a little. I also had to be tricky to make 1.2 work. But meanwhile FreeDOS test version FDT2311 (version 1.3 with a lot of updates) Live CD is out, https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/ and it should work much better (among others: NLS, national language support for many commands, new fdisk and several other tools were updated. As...
Sorry, but I seems that I cannot really help you. There are several reasons for this: I ran google for HP pavilion 6330 and found this: https://www.amazon.de/HP-Pavilion-a6330-F-Desktop-PC/dp/B0010DQFDW (german, but should not make big differences), was built in about 2008, so it should use SATA HDs, but you talk about IDE HDs. This makes the first difference. The computer should run on Vista (2008) or newer then. IDE supported max. 4 HDs/CDs, whereas SATA offers adding more devices. Vista works...
Hi, I beg your pardon if I have to say this. Jim, our FreeDOS Guru, asked for more details. I can understand and confirm him. You start a confusing story anywhere after the middle and expect that all others know and understand the whole story before. This is almost impossible to do. We need step by step. So could you answer some questions before: You have a laptop with solid state SATA. OK. Means, the computer was built after ca. 2005. But you did not tell us, which OS(es) are on it, is there a multiboot...
Hi, I beg your pardon if I have to say this. Jim, our FreeDOS Guru, asked for more details. I can understand and confirm him. You start a confusing story anywhere after the middle and expect that all others know and understand the whole story before. This is almost impossible to do. We need step by step. So could you answer some questions before: You have a laptop with solid state SATA. OK. Means, the computer was built after ca. 2005. But you did not tell us, which OS(es) are on it, is there a multiboot...
Hi, I just wanted to ask you if I can help you with tests etc. to make zerofill work with bigger file systems. Thx for response.
Hi, I just tested zerofill 1.05 and 1.09 today as 1.05 is part of the FreeDOS distribution. It works, I needed a while to see that it creates 4 x 500 MB files for a "shown" 2 GB file. While this is a good solution for the old FAT format, it is not usable for bigger FAT32 partitions that FreeDOS supports for a longer time now (max. 2 TB now!). As zerofill deletes the temporary files at the end (2GB) it is not usable for such big partitions as it would have to write more than 8.000 files with 500 MB...
Have a look at the link above. 2.65 supports both features now. Doubledot shows available drive letters and there is no error message when there is no file (or label) on it. Great!
There is a new DOS version available that fixes the doubledot bug, but not the problem of an error message when there is no file on the partition (label or another file).
https://github.com/nidud/doszip/issues/12
yes, you were right, I assume the problem is that the empty diskette only finds ".." and not an empty file with label name. So I will report two bugs.
yes, you were right, I assume the problem is that the empty diskette only finds ".." and not an empty file with folder name. So I will report two bugs.
Hi Oliver, could it be that the bug description is not exact? Reason: dz shows (in difference to FD "dir" or other commanders a ".." (also known as: "go back") in the root A:.. or C:.. When I click on this ".." I get the message: "Cannot open directory A:.. No such file or directory" - which is another bug. The label bug was not reproducable by me. So either your or my test was wrong - or there are two bugs. Please check.
unzip 6.0 is delivered with FDT2306 see screenshot