On 22/11/2015 20:39, Jerome E. Shidel Jr. wrote:
> I’ve tried recompressing them multiple ways, but that either
> causes  FDINST to choke on all of the files. Or, just fail at the
> same point.

In fact, the problem is not about compression, but the lack of it.
I introduced a 1-byte bug in v0.99.2 that causes uncompressed files to 
fail being extracted from the zip file.

FDNPKG v0.99.3 fixes this issue.

> 2) Although, when 1st problem is corrected this won’t matter.
> But, it does not generate an exitcode errorlevel when this happens.
> Basically, it prints an error and continues on as if nothing went wrong.

This is part of the design. A single file failing to be extracted is not 
considered a fatal error, it only gets reported at the end of 
installation in a summary. I did it this way for packages that have 
failing files because of LFN/SFN incompatibilities. Such files are 
usually non-critial, most often located in soruces, so marking the whole 
package as 'failed' wouldn't be user-friendly in most cases.

Mateusz


------------------------------------------------------------------------------
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to