• what's amylist.tic for?

    From Jeff Kocuipchyk@39:902/518 to All on Sat Jun 7 22:44:44 2025
    Hi all,

    I seem to be having an amibinkd issue. It seems to be hanging while executing my amiganet.scr at almost the end of the session there's a line that says
    1 FILES 1,260 BYTES
    Have 1,260 BYTE(S) of amylist.tic

    what's a .tic file used for? It's constantly doing this and it hangs the session and blows up my amiga.

    I don't recall seeing any .tic files in fidonet sessions?

    Thanks in advance
    J
    * C-Net/5
    * Origin: call.rofbbs.com ports 6800 6400 8502 / 423-541-8271 (39:902/518)
  • From Stephen Walsh@39:901/280 to Jeff Kocuipchyk on Sun Jun 8 19:15:54 2025

    Hello Jeff!

    07 Jun 25 22:44, you wrote to all:

    I seem to be having an amibinkd issue. It seems to be hanging while executing my amiganet.scr at almost the end of the session there's a
    line that says 1 FILES 1,260 BYTES Have 1,260 BYTE(S) of amylist.tic

    what is the content of your amiganet.scr file?

    what's a .tic file used for? It's constantly doing this and it hangs
    the session and blows up my amiga.

    *.tic files are sent along woth the other files in a file echo.

    The one in your message is for the Amiganet nodelist.




    Stephen


    --- GoldED+/LNX 1.1.5-b20240302
    * Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- Prt: 6800 (39:901/280)
  • From Nigel Reed@39:902/513 to All on Sun Jun 8 08:02:45 2025
    On Sat, 7 Jun 2025 22:44:44 +0000
    "Jeff Kocuipchyk" (39:902/518) <Jeff.Kocuipchyk@f518.n902.z39.fidonet>
    wrote:

    Hi all,

    I seem to be having an amibinkd issue. It seems to be hanging while
    executing my amiganet.scr at almost the end of the session there's a
    line that says 1 FILES 1,260 BYTES
    Have 1,260 BYTE(S) of amylist.tic

    what's a .tic file used for? It's constantly doing this and it hangs
    the session and blows up my amiga.

    I don't recall seeing any .tic files in fidonet sessions?

    Thanks in advance
    J
    * C-Net/5
    * Origin: call.rofbbs.com ports 6800 6400 8502 / 423-541-8271
    (39:902/518)

    tic files tells the tic processor how to deal with the associated file.
    It'll contain details such as which area the file belongs to, the file
    name, the source, the password, if there is one set, whether the new
    file replaces the old one, a crc32 checksum, and various other bits of information.

    Without the tic file, your system wouldn't know what to do with the
    file it accompanies.
    --
    End Of The Line BBS - Plano, TX
    telnet endofthelinebbs.com 23
    --- SBBSecho 3.27-Linux
    * Origin: End Of The Line BBS - endofthelinebbs.com (39:902/513)
  • From Jeff Kocuipchyk@39:902/518 to Stephen Walsh on Sun Jun 8 14:33:19 2025
    Thanks for the info, but what happens to them upon transfer? LIke I said, that message keeps appearing in the amibinkd log for amiganet but I haven't seen it in any fidonet log at all. And it hangs amibinkd when I run my amiganet script.

    Thanks
    J
    * C-Net/5
    * Origin: call.rofbbs.com ports 6800 6400 8502 / 423-541-8271 (39:902/518)
  • From Jeff Kocuipchyk@39:902/518 to Nigel Reed on Sun Jun 8 14:36:00 2025
    Thanks for the message. But what's supposed to happen to it once amibinkd finishes its processing? Does the Tosser get rid of that file afterwards (I'm assuming it gets transferred into Inbound: from the boss node).

    Thanks
    J
    * C-Net/5
    * Origin: call.rofbbs.com ports 6800 6400 8502 / 423-541-8271 (39:902/518)
  • From Nigel Reed@39:902/513 to Jeff Kocuipchyk on Sun Jun 8 15:50:00 2025
    Re: Re: what's amylist.tic for?
    By: Jeff Kocuipchyk to Nigel Reed on Sun Jun 08 2025 14:36:00

    Thanks for the message. But what's supposed to happen to it once amibinkd finishes its processing? Does the Tosser get rid of that file afterwards (I'm assuming it gets transferred into Inbound: from the boss node).

    Usually the tic and the file will be in your inbound directory and the tic processor, if it successfully completed, should delete the tic after moving the
    file to the correct directory.

    Unless there's an option to keep them, I guess. If it's not successful then it may keep the tic around so you can investigate. It's a regular text file you can look at.
    --- SBBSecho 3.27-Linux
    * Origin: End Of The Line BBS - endofthelinebbs.com (39:902/513)
  • From Stephen Walsh@39:901/281 to Jeff Kocuipchyk on Mon Jun 9 19:20:45 2025
    Hi Jeff,

    On Sunday June 08 2025, Jeff Kocuipchyk said to Stephen Walsh:

    Thanks for the info, but what happens to them upon transfer? LIke I
    said, that message keeps appearing in the amibinkd log for amiganet but
    I haven't seen it in any fidonet log at all. And it hangs amibinkd when
    I run my amiganet script.

    You should have a *.tic processor. They take the information in the *.tic
    file and move the relevant file to your file base, at the same time adding
    the file to your bbs.

    Post your amiganet script, so others can see it and point anything out.



    -- Stephen --

    Rocking Amiganet with an Amiga 4000 and Zeus BBS.


    --- Zeus BBS 1.5
    * Origin: -:-- Dragon's Lair --:- dragon.vk3heg.net Prt: 6800 (39:901/281.0)
  • From Wilfred van Velzen@39:150/200 to Jeff Kocuipchyk on Mon Jun 9 12:23:44 2025
    Hi Jeff,

    On 2025-06-07 22:44:44, you wrote to All:

    I seem to be having an amibinkd issue. It seems to be hanging while executing my amiganet.scr at almost the end of the session there's a
    line that says 1 FILES 1,260 BYTES Have 1,260 BYTE(S) of amylist.tic

    What I find very strange here is the file name.

    http://ftsc.org/docs/fts-5006.001 has this to say about the file name in paragraph 2.2:

    A TIC file is a text file with a name in 8.3 DOS format with the
    extension .TIC. The name of the TIC file should be unique enough
    to ensure that systems receiving TIC files never have two TIC
    files with the same name in their inbound. How this is done is
    left to the implementation.

    So every tic processor I know of, generates some random (kind of) file name for
    every .tic file it generates. I have never seen a .tic file with such an explicit name. So someone must be doing it wrong!

    Btw: This has probably nothing to do with the problem you are seeing!


    Bye, Wilfred.

    --- FMail-lnx64 2.3.2.4-B20240523
    * Origin: FMail development HQ (39:150/200)