Bernie wrote:
> Sergei wrote:
> >> > Maybe Arachne should understood long filenames when launched
> >> > under Windows 95, same as FAR do ?
> >> > Michael ? In future v. 1.70 ?
> >>
> >> Maybe longfilenames should go away ? <My wish>
> >
> >Then any UNIX, Amiga, BeOS, other with long filenames should go away
> >with their long filenames ? And how about CDROM's filesystems ? Go away
> >too ?
>
> There's a small diffrence. FAT16 doesn't have LFN - it's a work around that
> M$ has invented. And IIRC the filenames on CDs are 8.3. But that's beside
> the point.
>
> >Thats not a solution.
>
> You are one of the few who thinks that would be usefull. To get the LFN all
> someone (probably me in this case <g>) have to do is to recompile wwwman
> under DJGPP (which also makes it useless for people running anything less
> than a 386). There are of course a few problems with this (IMO the LFN
> should be shown but not used - mostly since otherwise DJPEG and other
> programs would need to be recompiled under DJGPP (still no luck with that
> btw)). And there is another issue as well, the current code is written for
> Borland C/C++ not GNU C/C++.
> //Bernie
Maybe you right. But do not forget, Windows is mainstream
for now.
And i do not like to use files with ~ inside of the name.
But also i think that few different Arachne versions for
different versions of DOS is not good idea.
Maybe wwwman can check the OS before starting and work with
different portions of code ? Or this can be done during
installation.
Lot of folks here work with Windows, and they do not need
compatibility with 8086 processor.
It depends from Michael's priorities to do it or not.
Sergei
--
