> On Oct 2, 2024, at 6:23 AM, Paul Dufresne via Freedos-devel > <freedos-devel@lists.sourceforge.net> wrote: > > I already knew about rcal link that is still broken (my fault, not fixed yet, > expect to fix it soon).
:-) > > But I thought I would go through all the links in C:\FreeDOS\Links to see > which one seems to not work (return to DOS prompt doing nothing): > Gopherus, lame, rcal, > why tcedit.dst file is in links? > utf8tocp I’ve already updated the packages for Gopherus, Lame and UTF8TOCP. So, just rcal needs fixed. I just did a fresh install of T2410. I don’t see a tcedit.dst file under links. > Unsure if I am supposed to file a bug for each of those... I feel this is > what I should do. > > On the subject, I wonder if the installer could test the links to see if they > reach installed files? > I believe it is the installer that transform the .bat links into .com > links... so my guess is that it knows > already those pretty well. During installation, the installer uses FDINST to install the packages. While FDINST is installing the package, it converts any batch files in the LINKS path of the archive into COM files. There are many benefits that doing so provides. However, there can be some issues. For example, It can be difficult to see where those links point or for a user to change them. The configuration file for FDINST during installation maps the LINKS directory to %DOSDIR%\LINKS (aka FreeDOS\LINKS). However, a fixed link COM file may not be desired. For example, if some additional action needs performed in the BATCH (like chasing between two programs), then the conversion used would break things. Therefore, there is also an additional mapping configured in the settings. Files placed in the ZIP archive directory BATLINKS are copied as-is to the LINKS directory without being converted. _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
