Why did you open bug report 402 instead of replying to 401? Please do not open a new bug report each time you want to comment or send a message. I already know about the ZIP that is included in ARACHNE. However, I have not looked at it to verify it is 8086 compatible and contains sources. If you read my reply, this is one of the "possible alternatives" to which I was referring. Out of projects I am responsible (Online Repositories, FreeDOS translations, Release Media Builder, and others) and numerous...
This is not an unknown issue and has not yet been resolved. See, the https://sourceforge.net/p/freedos/mailman/message/59222415/ thread. It discusses the problems with the current UNZIP which requires 386+CWSDPMI and possible alternatives. Those have not been fully investigated as of yet. A satisfactory solution will require a opensource UNZIP that does can run on a 8086 and will not automatically use a SWAP file on 386+ hardware.
At present, FDIMPLES has two different ways it displays the "File List". For packages that are installed but NOT available on the install Media, it displays the list of Files that were installed with their path information. These items get grouped into a "Installed!" group. The Second way is for packages that are available on the install Media. Regardless of whether or not they are installed, those show a simple list of contents of the zip file. This is not likely to change in the current Major version...
At present, FDIMPLES has two different ways it displays the "File List". For packages that are installed but NOT available on the install Media, it displays the list of Files that were installed with their path information. These items get grouped into a "Installed!" group. The Second way are for packages that are available on the install Media. Regardless of whether or not they are installed, the show a simple list of contents of the zip file. This is not likely to change in the current Major version...
Thank you
Patch to handle binary files correctly
Format Stack Overflow
I also posted this issue more recently on Github. Yes, this issue is now fixed as of FORMAT v0.92.