• Long FileNames :( :(

    From Janis Kracht@1:261/38 to All on Tue Jun 23 14:52:44 2009
    Hello Folks!

    So sorry.. It was brought to my attention this morning that I cannot count.. at
    least first thing in the morning before coffee Lol..

    These files will be re-released tomorrow with 8X3 file names in Fernwood

    agena0221.zip Missing Area: FWPROG Origin: 1:261/38
    Agena, a procedural programming language.


    sdlmam132.zip Missing Area: FWPROG Origin: 1:261/38
    SDLMAME v0.132 for OS/2


    Sorry for the inconvenience!


    Take care,
    Janis

    --- BBBS/LiI v4.01 Flag
    * Origin: Prism bbs (1:261/38)
  • From Benny Pedersen@2:237/53 to Janis Kracht on Wed Jun 24 22:58:18 2009
    Hello Janis!

    23 Jun 09 14:52, Janis Kracht wrote to All:

    So sorry.. It was brought to my attention this morning that I cannot count.. at least first thing in the morning before coffee Lol..

    hatch files at the night solves it nicely :)

    These files will be re-released tomorrow with 8X3 file names in
    Fernwood Sorry for the inconvenience!

    bbbs should have spotted the problem for you before any other noticed it


    Regards Benny

    ... there can only be one way of life, and it works :)

    --- Msged/LNX 6.2.0 (Linux/2.6.29-gentoo-r5 (i686))
    * Origin: http://www.facebook.com/xpoint (2:237/53)
  • From mark lewis@1:3634/12 to Benny Pedersen on Sun Jun 28 22:09:31 2009

    These files will be re-released tomorrow with 8X3 file names in
    Fernwood Sorry for the inconvenience!

    bbbs should have spotted the problem for you before any other
    noticed it

    why? IIRC bbbs does LFNs with no problem... it is the other systems that cannot
    where the problem arises... it is they who need to do the footwork to adjust the filename for their local filesystem... no only the file processors but the mailers as well ;)

    )\/(ark


    * Origin: (1:3634/12)
  • From Benny Pedersen@2:237/53 to mark lewis on Sat Jul 4 15:29:52 2009
    Hello mark!

    28 Jun 09 22:09, mark lewis wrote to Benny Pedersen:

    These files will be re-released tomorrow with 8X3 file names in
    Fernwood Sorry for the inconvenience!

    thanks janis, you do a great job in fidonet, i may just say girl power now :)

    bbbs should have spotted the problem for you before any other
    noticed it
    why?

    i belive software that accept errors is basicly bad writed in the first place

    IIRC bbbs does LFNs with no problem...

    janis just tested it for us above :)

    it is the other systems that cannot where the problem arises...

    as always, its not my fault :)

    it is they who need to do the footwork to adjust the filename for their local filesystem... no only the file processors but the mailers as well ;)

    mailers dont care about lfn or not, but bso does, aso have lfn as default



    Regards Benny

    ... there can only be one way of life, and it works :)

    --- Msged/LNX 6.2.0 (Linux/2.6.29-gentoo-r5 (i686))
    * Origin: http://www.facebook.com/xpoint (2:237/53)
  • From mark lewis@1:3634/12 to Benny Pedersen on Mon Jul 6 15:23:46 2009

    bbbs should have spotted the problem for you before any other
    noticed it
    why?

    i belive software that accept errors is basicly bad writed in the
    first place

    this is true but one must also fully understand all the aspects of the technologies involved...

    IIRC bbbs does LFNs with no problem...

    janis just tested it for us above :)

    incorrect... i'm am very aware of numerous systems that transfer LFN files over
    8.3 connections without any problems... there are several factors involved... one being that the mailer receiving the file can handle LFN->8.3 conversion on the fly AND that the inbound TIC file accompanying the file also understand the
    name conversion...

    it is the other systems that cannot where the problem arises...

    as always, its not my fault :)

    no, i'm saying that (part of) the problem is on the receiving systems...

    it is they who need to do the footwork to adjust the filename for their local filesystem... no only the file processors but the mailers as well ;)

    mailers dont care about lfn or not, but bso does, aso have lfn as
    default

    mailers SHOULD care about their local file system's capabilities and also make allowances for other mailers they connect with that cannot handle LFNs...

    this discussion was done a long time ago when the major developers of fidonet software were still active... some of those capabilities were implemented and some were not... then some devs drifted away and others arose and the main fidonet development echo, NET_DEV, got broken somehow and folk today still don't know about it or try to find it...

    )\/(ark


    * Origin: (1:3634/12)