• logon.js won't show logonXX.seq files

    From Fernando Toledo@1:103/705 to GitLab issue in main/sbbs on Fri Jan 21 14:53:44 2022
    open https://gitlab.synchro.net/main/sbbs/-/issues/325

    I create a logon1.seq logon2.seq etc to show petscii logon screens (also test with logonX.40col.seq)I also have the current logon1.asc,logon2.asc etc..that work fine.I noteice that at logon procedure always show these .asc files instead of the .seq files for 40 columns connections (Pet40port)''' // Print successively numbered logon screens (logon, logon1, logon2, etc.) var highest_printed_logon_screen=-1; for(var i=0;;i++) { var fname="logon"; if(i) fname+=i; if(!bbs.menu_exists(fname)) { if(i>1) break; continue; } bbs.menu(fname); highest_printed_logon_screen = i; }'''bbs.menu() works at main menu prompt, it show the main.40col.seq file whitout problem
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Fri Jan 21 15:11:40 2022
    https://gitlab.synchro.net/main/sbbs/-/issues/325#note_2208

    Works for me. I created logon.seq and it displays during logon (instead of logon.asc or logon.msg or logon.ans)
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Fri Jan 21 15:12:36 2022
    https://gitlab.synchro.net/main/sbbs/-/issues/325#note_2209

    ```Logging on to Vertrauen as Digital Man ...THIS IS LOGON.SEQ ```
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Fri Jan 21 15:13:34 2022
    https://gitlab.synchro.net/main/sbbs/-/issues/325#note_2210

    I did notice that it's not auto-screen pausing after display logon*.seq however. I'll look into that.
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Fernando Toledo@1:103/705 to GitLab note in main/sbbs on Tue Jan 25 14:38:46 2022
    https://gitlab.synchro.net/main/sbbs/-/issues/325#note_2229

    i Have this setup:```root@scarlet:/sbbs/text.docksud# ll menu/log*-rw-r--r-- 1 root root 511 feb 28 2010 menu/login.wip-rw-r--r-- 1 root root 371 feb 28 2010 menu/logoff.asclrwxrwxrwx 1 root root 17 oct 1 02:14 menu/logon1.asc -> /sbbs/ans/lmn.anslrwxrwxrwx 1 root root 15 mar 18 2020 menu/logon2.asc -> /sbbs/ans/1.anslrwxrwxrwx 1 root root 22 mar 30 2020 menu/logon3.asc -> /sbbs/ans/micronet.anslrwxrwxrwx 1 root root 17 jul 9 2019 menu/logon4.asc -> /sbbs/ans/pvm.anslrwxrwxrwx 1 root root 20 ene 31 2021 menu/logon5.asc -> /sbbs/ans/separa.anslrwxrwxrwx 1 root root 20 jun 8 2021 menu/logon6.asc -> /sbbs/ans/zudaka.ans-rw-r--r-- 1 root root 2619 feb 9 2020 menu/logon.asc-rw-r--r-- 1 root root 1642 ene 21 19:27 menu/logon.seq```The logonX files are symlinks to some ansi files.When I connect on port 64 I don't see the logon.seq file. but the logon.asc ![image](/uploads/a4c9b0a5d5d0fb39269106fdee1d3469/image.png)I try to copy logon.seq to severals logonX.seq with no luck```root@scarlet:/sbbs/text.docksud/menu# root@scarlet:/sbbs/text.docksud/menu# ls -l log*-rw-r--r-- 1 root root 511 feb 28 2010 login.wip-rw-r--r-- 1 root root 371 feb 28 2010 logoff.asclrwxrwxrwx 1 root root 17 oct 1 02:14 logon1.asc -> /sbbs/ans/lmn.ans-rw-r--r-- 1 root root 1642 ene 25 19:28 logon1.seqlrwxrwxrwx 1 root root 15 mar 18 2020 logon2.asc -> /sbbs/ans/1.ans-rw-r--r-- 1 root root 1642 ene 25 19:28 logon2.seqlrwxrwxrwx 1 root root 22 mar 30 2020 logon3.asc -> /sbbs/ans/micronet.anslrwxrwxrwx 1 root root 17 jul 9 2019 logon4.asc -> /sbbs/ans/pvm.anslrwxrwxrwx 1 root root 20 ene 31 2021 logon5.asc -> /sbbs/ans/separa.anslrwxrwxrwx 1 root root 20 jun 8 2021 logon6.asc -> /sbbs/ans/zudaka.ans-rw-r--r-- 1 root root 2619 feb 9 2020 logon.asc-rw-r--r-- 1 root root 1642 ene 21 19:27 logon.seq```only the logons screen part fail, then onliners, sbbslist and main menu is fine:![vokoscreen-2022-01-25_19-36-23](/uploads/c9db05cec093b7eb05bc39948aeaa0d7/vokoscreen-2022-01-25_19-36-23.mp4)
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Tue Jan 25 15:58:14 2022
    https://gitlab.synchro.net/main/sbbs/-/issues/325#note_2230

    1. You should not symlink .asc (ASCII) files to .ans (ANSI) files. That is not going to produce the expected results. Either convert those .ans files to .msg or .asc and use those instead or have a separate version for non-ANSI terminals (named either .msg or .asc).2. You don't have a .seq files for every .asc file, so I would expect the logon3 through logon6.asc files (which are actually symlinks to ANSI files) to be sent to a PETSCII terminal. That's how you have it setup.I would expect the logon1.seq and logon2.seq files to be displayed however. Did you check your scroll-back?
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Fernando Toledo@1:103/705 to GitLab note in main/sbbs on Wed Jan 26 11:17:16 2022
    https://gitlab.synchro.net/main/sbbs/-/issues/325#note_2234

    thanks!! i will fix the mixed filenames. For now, I can see the logon.seq on port 64 connect =)![image](/uploads/4f831613426e81029ca879dedf17dcc4/image.png)
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Fernando Toledo@1:103/705 to GitLab issue in main/sbbs on Wed Jan 26 11:17:58 2022
    close https://gitlab.synchro.net/main/sbbs/-/issues/325
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)