Hi Jim, > On Oct 1, 2023, at 7:05 PM, Jim Hall via Freedos-user > <freedos-user@lists.sourceforge.net> wrote: > > Eric wrote: >> You can also find updates for JEMM and HIMEMX on Japheth's GitHub "Baron von >> Riedesel", even his HIMEMSX to use more than 4 GB RAM :-) > > Mercury Thirteen wrote: > [..] >> Looks like I fell behind on keeping up with all of Japheth's updates! The >> downloads section at MercuryCoding.com has been updated with new versions of >> HiMemX and JWasm as well. Thanks, Eric, for (indirectly) pointing this out >> to me! :) >> > > I didn't have the latest HIMEMX mirrored on Ibiblio, so I just grabbed > the copies you have. I checked the file contents, and they have been > touched since the original. For example, 3.38 > (https://github.com/Baron-von-Riedesel/HimemX/releases) was released > Nov 21, 2022 and has file contents like this: > > $ unzip -l HimemX338.zip > Archive: HimemX338.zip > Length Date Time Name > --------- ---------- ----- ---- > 6056 11-21-2022 13:01 HimemX.exe > 6056 11-21-2022 13:01 HimemX2.exe > 1954 04-16-2020 06:38 Readme.txt > 4871 11-21-2022 13:01 History.txt > 81855 11-21-2022 13:01 HimemX.asm > 296 03-24-2020 01:56 Make.bat > 529 03-24-2020 01:58 Makefile > --------- ------- > 101617 7 files > > > It looks like you modify the zip files when you mirror them. Your > version looks like this: > > $ unzip -l 3.38/himemx338.zip > Archive: 3.38/himemx338.zip > Length Date Time Name > --------- ---------- ----- ---- > 0 09-23-2023 03:38 APPINFO/ > 568 09-23-2023 03:38 APPINFO/HIMEMX.LSM > 0 09-23-2023 03:38 BIN/ > 6056 09-23-2023 03:38 BIN/HIMEMX.EXE > 2168 09-23-2023 03:38 BIN/UMBM.EXE > 6056 09-23-2023 03:38 BIN/HIMEMX2.EXE > 0 09-23-2023 03:38 DOC/ > 0 09-23-2023 03:38 DOC/HIMEMX/ > 1954 09-23-2023 03:38 DOC/HIMEMX/README.TXT > 4871 09-23-2023 03:38 DOC/HIMEMX/HISTORY.TXT > 0 09-23-2023 03:38 SOURCE/ > 0 09-23-2023 03:38 SOURCE/UMBM/ > 296 09-23-2023 03:38 SOURCE/UMBM/MAKE.BAT > 12147 09-23-2023 03:38 SOURCE/UMBM/UMBM.ASM > 0 09-23-2023 03:38 SOURCE/HIMEMX/ > 296 09-23-2023 03:38 SOURCE/HIMEMX/MAKE.BAT > 81855 09-23-2023 03:38 SOURCE/HIMEMX/HIMEMX.ASM > 529 09-23-2023 03:38 SOURCE/HIMEMX/MAKEFILE > --------- ------- > 116796 18 files > > > (You sent your message on 9/23, so that explains the dates.) > > Are you folding the source code into the "exe" zip file to create a package? > > > At least for the mirrored files on Ibiblio, I prefer to keep the files > as provided by the developer (Jerome creates packages, but the Files > Archive section is a straight mirror.) So I'll re-mirror the original > releases from GitHub. >
Unfortunately, GitHub and GitLab do not preserve timestamps on their own. When you checkout a project, the files get stamped with current time. The same thing happens when they create a release. The files in the zip have a timestamp based on the release creation and not when the file was last modified. This was one of the primary reasons I wrote the FDVCS.SH script. It maintains a simple hash based timestamp data file. Which is updated and managed automatically through the script during commits and checkouts to preserve correct timestamps. The script also handles several other issues and annoyances when using Git. Side note, The RBE pulls the project from the GitLab archive and uses that utility to adjust file timestamps before building the packages that get included on the release media. Anyhow, simply refetching the release zips from Git* won’t correct the timestamp issue with the mirrored archives. Jerome > > _______________________________________________ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
