TicMover 1.10 was made by Pinkie Soft (c) Copyright 1995 by Pinkie Soft Nothing of this program may be altered changed or whatever that may change the status of this program. This program may NOT be used for commercial pur- poses without WRITTEN permission of the author. I am not responsible for any damages this program could do to your system. Don't worry, this is just here to clear my name :) Remember this is a BETA version. What does not work is the point/node support zo .TIC files are not yet exported to your points/nodes. What? ----- This program processes the .TIC files send to you through a fidonet-compatible mail network. TIC files are files created by Xareafix (for example) so that the BBS can store the attached files easily and put them in a file area. DayDream BBS does not have such a program like Xareafix so I decided to make something like it. It looks at the config file, it then inspects the .TIC file and looks for an area name configged in the config file. If the program finds a tagname, it will continue to process the file. The file is copied to de directory where you want the files to go to. Then the description is added to the Directory.xxx in the configged config directory and it will report al the actions in a logfile. If you did not config the Tagname, the program will report that to you and put it into the logfile. The program does NOT wait for a return so you can use it for automatic processing but since it is a beta version I don't recommend it. Not yet. If you find NO errors/bugs, then ... How? ---- How do you instal it? Simple. Put TicMover and TicConfig in the directory Util/ which should be in you DayDream directory. The program does not want this but I think it is easier. Then copy the library AGABBS_crew.library to your Libs: next copy the TicMover.cfg to your DayDream:Configs/ directory. Make sure the directory Logfiles/ exists in your DayDream:. These are the only two directories TicMover really NEEDS! Then you should edit the .cfg file. Here is the example: WATCH CAREFULLY!! THE CONFIG HAS BEEN CHANGED DRASTICALLY!!!!!!!!!!!!! TIC_INBOUND. BBS:Fidonet/Inbound/ Inbound directory TIC_OUTBOUND BBS:Fidonet/Outbound/ Outbound """"""" TIC_TEMP.... T: Temporary """""" TIC_POINTTIC Y Want TIC files sent to POINTS/NODES?Y/N TIC_FILETAG. ERO-X TAGS Stated in Fidonet tagname list TIC_FILETAG. ERO-ANI TIC_FILETAG. ERO-BIZA TIC_FILETAG. ERO-GAY TIC_FILETAG. ERO-LES TIC_FILETAG. ERO-PISS TIC_FILETAG. ERO-SHAV TIC_FILETAG. ERO-DIFF TIC_FILETAG. ERO-PRI TIC_FILETAG. ERO-TEEN TIC_FILETAG. ERO-THAI TIC_FILETAG. ERO-TRAN TIC_FILETAG. ERO-VAR TIC_FILETAG. ERO-WOM TIC_FILETAG. ERO-NODE TIC_FILETAG. AGA_FILESLISTS TIC_FILETAG. AGA_NODELIST TIC_FILETAG. LDY_NLIST TIC_FILETAG. LDY_SCREENS TIC_FILETAG. LDY_F_COMMS TIC_FILETAG. LDY_F_UTILS TIC_FILETAG. LDY_F_MUSIC TIC_FILETAG. LDY_F_PROG TIC_FILETAG. LDY_F_GAMES TIC_FILETAG. LDY_F_GDOCS TIC_FILETAG. ERO-POINT TIC_FILETAG. AGA_UPDATES TIC_FILETAG. PM_MUSIC_NLIST TIC_FILETAG. PM_MUSIC_PROBLEM_MODS TIC_FILETAG. PM_MUSIC_MISC TIC_FILETAG. PM_MUSIC_MIDIF TIC_FILETAG. PM_MUSIC_MODS TIC_AREA.... 014 Area to put them in...in which TIC_AREA.... 014 conference, will follow later in TIC_AREA.... 014 the config so don't worry TIC_AREA.... 014 TIC_AREA.... 014 TIC_AREA.... 014 TIC_AREA.... 014 TIC_AREA.... 001 TIC_AREA.... 014 TIC_AREA.... 014 TIC_AREA.... 014 TIC_AREA.... 014 TIC_AREA.... 014 TIC_AREA.... 014 TIC_AREA.... 001 TIC_AREA.... 044 TIC_AREA.... 001 TIC_AREA.... 001 TIC_AREA.... 001 TIC_AREA.... 001 TIC_AREA.... 001 TIC_AREA.... 001 TIC_AREA.... 001 TIC_AREA.... 001 TIC_AREA.... 001 TIC_AREA.... 001 TIC_AREA.... 034 TIC_AREA.... 001 TIC_AREA.... 008 TIC_AREA.... 008 TIC_AREA.... 026 TIC_AREA.... 008 TIC_CONFEREN BBS:Configs/1/ path of the conference where the TIC_CONFEREN BBS:Configs/1/ files should be put... TIC_CONFEREN BBS:Configs/1/ TIC_CONFEREN BBS:Configs/1/ TIC_CONFEREN BBS:Configs/1/ TIC_CONFEREN BBS:Configs/1/ TIC_CONFEREN BBS:Configs/1/ TIC_CONFEREN BBS:Configs/14/ TIC_CONFEREN BBS:Configs/1/ TIC_CONFEREN BBS:Configs/1/ TIC_CONFEREN BBS:Configs/1/ TIC_CONFEREN BBS:Configs/1/ TIC_CONFEREN BBS:Configs/1/ TIC_CONFEREN BBS:Configs/1/ TIC_CONFEREN BBS:Configs/14/ TIC_CONFEREN BBS:Configs/1/ TIC_CONFEREN BBS:Configs/4/ TIC_CONFEREN BBS:Configs/15/ TIC_CONFEREN BBS:Configs/15/ TIC_CONFEREN BBS:Configs/15/ TIC_CONFEREN BBS:Configs/15/ TIC_CONFEREN BBS:Configs/15/ TIC_CONFEREN BBS:Configs/15/ TIC_CONFEREN BBS:Configs/15/ TIC_CONFEREN BBS:Configs/15/ TIC_CONFEREN BBS:Configs/14/ TIC_CONFEREN BBS:Configs/1/ TIC_CONFEREN BBS:Configs/18/ TIC_CONFEREN BBS:Configs/1/ TIC_CONFEREN BBS:Configs/1/ TIC_CONFEREN BBS:Configs/1/ TIC_CONFEREN BBS:Configs/1/ TIC_PRESET.. -#2AKA002# Preset 2AKA002 TIC_PRESET.. -#2AKA002# ^^^^ ^^ TIC_PRESET.. -#2AKA002# || || TIC_PRESET.. -#2AKA002# || ``--AKA number format [XXX] TIC_PRESET.. -#2AKA002# ``---ALWAYS INCLUDE THIS! TIC_PRESET.. -#2AKA002# TIC_PRESET.. -#2AKA002# Last AKA is ALWAYS !ONE! 2AKA TIC_PRESET.. -#2AKA002# because this is your OWN node nr. TIC_PRESET.. -#2AKA002# the others are ALL AKAXXX presets TIC_PRESET.. -#2AKA002# so your first preset for a node TIC_PRESET.. -#2AKA002# would be AKA001 etc. TIC_PRESET.. -#2AKA002# NEVER use more then one 2AKA-tag TIC_PRESET.. -#2AKA002# on the same line. TIC_PRESET.. -#2AKA002# TIC_PRESET.. -#2AKA002# When you do not want to send TIC_PRESET.. AKA001#2AKA001# a TIC file to the users ONLY include TIC_PRESET.. AKA001#2AKA001# your nodenumber at the end (the preset) TIC_PRESET.. -#2AKA003# and put a - instead of a AKAXXX TIC_PRESET.. -#2AKA003# don't forget to put a # after EVERY TIC_PRESET.. -#2AKA003# AKA. (also 2AKAxxx and AKAxxx) TIC_PRESET.. -#2AKA003# TIC_PRESET.. -#2AKA003# TIC_PRESET.. -#2AKA003# TIC_PRESET.. -#2AKA003# TIC_PRESET.. -#2AKA003# TIC_PRESET.. -#2AKA002# TIC_PRESET.. AKA001#2AKA001# <-- Look here: AKA for a node/boss TIC_PRESET.. AKA002#2AKA004# and last on the line is my TIC_PRESET.. AKA002#2AKA004# nodenumber TIC_PRESET.. AKA002#2AKA004# TIC_PRESET.. AKA002#2AKA004# TIC_PRESET.. AKA002#2AKA004# TIC_2AKA001. 171:100/107.0 These are the presets for 2AKA TIC_2AKA002. 68:319/153.0 these are all YOUR nodenumbers TIC_2AKA003. 69:100/205.0 or pointnumbers (who knows what TIC_2AKA004. 17:100/206.0 nut wants to use this) TIC_AKA001.. 171:100/107.1#171:100/0.0# These are your points/nodes connected TIC_AKA002.. 17:100/206.1#17:100/200.0# to you. (I have also included my BOSS so that he will receive all TIC files send from other systems through me) When you have configured the config file to the max don't forget these important things: 1. Always put as much TIC_FILETAG, TIC_CONFEREN, TIC_AREA, TIC_PRESET 2. Make sure the directories DayDream:Logfiles/ and DayDream:Configs/ are present! 3. Only use ONE 2AKAxxx preset (where xxx is a number of three digits) on one and the same line/preset 4. Always put after every AKA and 2AKA a '#' or the program will bug. When you have configured the config file TicMover.cfg in the directory DayDream:Configs/ you then must run the program TicConfig. This program will lookup all you areas and paths.dat and will make a file containing the paths where your ticced files must go to. This program, in fact makes it easier for you to config the program. Ypu don't have to type big long directory names etc. and it makes the program a lot simpler to code. Ok, after you have done the ticconfig program, you can then wait for Tic files to arrive to your system. Just one tip: don't let the program be started automatically! Remember that this is just an BETA version, so it is NOT yet tested deeply. You are free to run it automatically, it might not even be a problem BUT when something DOES go wrong you can see what happened and when. Ok, thats about that. This document is getting boring. Any Problems??? X/Files BBS +31-(0)70-3253901 or e-mail: alex.vanniel@student-kmt.hku.nl or : pinkie@dds.nl Pinkie Soft 1995 HISTORY ------- 1.31b Beta version with lots of restrictions 1.4b Did not contain the PTPT protoccol. Invented by me! hehehe Now Point Tic Pass Through is ssupported The BACKUP function was hardcoded and therefore irritating for people who did not have the directory. The directory is now removed. Next release will enable a configurable backup dir. 1.71 Beta version seemed good enough to loose the b comment so now it should be the '100%' version. Well, as you might know, this is never the case with programs thats also the reason why I and other coders need beta testers....wanna test TicMover for me? Would be nice...you will get full support and daydream support also. Ok, what has changed? A lot... first of all, I removed a backup bug, is now corrected. Then I added a check option. Well, not an option because you can not turn it off but still. What is it? Well, as I was cleaning up my HD I found some already sent files in my outbound and wonderd why they were still there. Since my program TicMover copied the ticced file and after transfer it is not killed (else other nodes/points would not receive the file) and uses some space.. This was very annoying so I decided to implement it in my program to kill the old already sent files in my outbound. I furthermore enhanced some code. Scrached some stupid useless code and made a bit of a reorganisation and a better overview in the code... Boring? yeah, i bet it is...well, you won't have anything to do with the code, just with the killing of old files. Beware: I am NOT! responsible for any damage or lost files you wished to keep. This program is started at your own risk! That was all.. 1.8 Never mind, don't know the bug-fixes anymore... 1.9 Well when a file was longer then 12 chars (included the exetension) the file WAS included in the Filecatalog BUT the file could not be downloaded because it could not be found (daydream looks for a file with only 12 chars...well, don't want to go into this...) Now the program looks how long the filename length is, if the length is longer then 12 chars, it will rip the chars starting at the begin of the name. Thats it. 1.10 It seemed that bigger-then-12-chars-files where not found because they were not renamed. Stupid me. Well, fixed that and also added two letters to the .TIC files Furthermore I killed some useless code...saved me 10k.:). 2.00 I have been working HARD on this program for this time. What I did was a total reprogramming of the config loading. Now you don't have to enter how many file-areas you have entered, the program will figure this out by itself accourding the number of TIC_FILETAG. tagnames. I cleaned up a bit inside. Then I enhanced some things (I hope) and made it possible to send TIC files to more then one user :) I found out that it was not possible to send TIC files to more then one. I also made it possible for the program to check if the file already has been sent somehow to a node or a boss or point. If so, it will not send it :) wow...brilliant...nooooot... What else? I had the program mention and log when it is renaming a file and fixed a little bug. I let the program log which nodes where send to. Made the program a bit more memory friendly, although I would not use it with 200 file-area-tags. (I have not tested that yet...) 2.1 After I have released 2.00 I discovered I had forgotten to change something that would call the config file. When testing the program I used a TicMover.cfg.new config file and when releasing it I had forgotten to put one of the calls back to TicMover.cfg. Weird? Nooo.. I had been working hard on it and forgetting that kind of things is easy. You will probably get a File not found error. Don't worry this version has been tested and LOOKS 1oo% but it still remains a beta version. Because I don't have beta-testers. Wanna be one? Please tell me! Bug ---- There could occur one bug, and that is: out of memory. Now you should have seen the looks on my face when this happened to me. I could not figure out what and why. But when I configged so 100 file-tags something went wrong.. Don't worry I will try to fix this...