Hi Darik > On Dec 15, 2021, at 5:11 PM, Darik Horn <dajh...@gmail.com> wrote: > > Hi, > > In FreeDOS 1.3 RC5, the new slicer handles file overwrites inconsistently in > interactive mode. Reproduce the bug by doing this: > > C:\> SLICER /x /f \SLICES\FREEDOS.SAF /g * /O OUT > ... > Overwrite BIN\FDINST.EXE, (N)o/(Y)es? N > > gzip: EGA\BIN\ID583S8Q.GZ: not in gzip format > FATAL ERROR: error code #2, unspecified error with "EGA\BIN\ID583S8Q.GZ" > > Expected behavior is that SLICER skips the current file and finishes the > extraction. > > SLICER behaves as expected on a "Y" input, or in non-interactive mode with > the /o switch. > > The given glob expresses the bug on the first call. If slicer is invoked > with a smaller category like "/g Network", then the bug happens on the second > call. > > On FreeDOS 1.3 RC5, slicer will always return error code #2 in the same place.
Error 2, means file not found. I think I may know what is happening. The addition of pass-thru compression support for gzip was added a couple days prior to release of RC5. And was only tested in automatic overwrite mode. What I think is probably happening is that after you tell it no, it still is trying to pass a non-extracted file to gzip which reports an error and extraction stops. I’ll need to look into it. Please post a bug report at https://gitlab.com/DOSx86/slicer <https://gitlab.com/DOSx86/slicer> or on the FreeDOS GitLab Archive at https://gitlab.com/FreeDOS/archiver/slicer <https://gitlab.com/FreeDOS/archiver/slicer> . That way I don’t forget to take care of the issue. > On DOSBox-X, slicer will fail on random files in a way that looks like a race > condition. Under the same situation? Jerome
_______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
