Hi, On Wed, Dec 2, 2015 at 2:28 AM, Mateusz Viste <[email protected]> wrote: > > Joe Forster kindly hinted off-list that open watcom comes with a > 'doslfnX.lib' library that can be used to transparently enable LFN > support within the compiled application. Since the required effort is > more than reasonable, I linked FDINST to it, so hopefully (?) FDINST > should now support LFN files, and therefore it might solve all the -2 > errors that were popping up when trying to unpack LFN files from packages.
IIRC, the LFN support in OW 1.9 was half-baked, at best. For instance, even the DOS compiler itself didn't support LFNs for compiling sources. So it only sometimes worked, and only (IIRC) if you defined __WATCOM_LFN__. OW 2.0-pre (which hasn't been rebuilt since April) supposedly has better support, but I haven't bothered tested that, so no guarantee that it's really a quick fix. Honestly, there's not much to do about it. If you see that a file uses invalid chars or is longer than 8.3, just either ignore it or rename it. If you're that worried, do something like DJGPP's DJTAR does, write the name changes to "tarchang.lst" (or "descript.ion" or whatever). At least then the end user can figure it out and adjust later, if needed. ------------------------------------------------------------------------------ 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=254741911&iu=/4140 _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
