LogScan 3.4beta --------------- What is this? ------------- A simple proggie to let DDCAllers of DayDream also count your mailers logged in the Trapdoor logfile. How does it work? ----------------- Interesting enough? Nope,... How do I use it? ---------------- Simple, copy erverything into the correct dirs: contents of: configs/ to DayDream:Configs/ utils/ to DayDream:Utils/ Then add this to your user-startup (AFTER! Trapdoor .. at the end of your user-startup preferable!), at the scripts which terminate and start Trapdoor, in Logoff1.script (you should run this Logoff1.script with a 'run <>NIL: execute DayDream:Batch/Logoff1.script' instruction or else everything goes wrong.) and in a script (at the bottom again) which is called after evey mailsession with Trapdoor. The line you should add to all of these files are: wait 5 ;or shorter but don't make it shorter then 3 run <>NIL: DayDream:Utils/LogScan So what to do: add this line BEHIND every call to Trapdoor (Arexx command, open and closing of Trapdoor..etc...) Thats it.... Further? -------- This is an extremely cut-down version compared to 2.0 1oo% release. This release is 1oo% 'E' and is a lot faster since I discovered some real kewl functions in 'E' that made it for me possible to flush the trapdoor and set the read-pointer at the place I wanted faster than lightning :) So, 2.0 took about 30s, this program less then 5s.. I have not clocked the whole stuff but I know it is FAAAAAAAAAAAAAAAAST.... This is my first program in 'E' so I am NOT responsible for ANY damage it could cause to your HD.. or ANYTHING else. (not by throwing because it did not work, not by trashing the HD because the prog did...) NOTHING... You use this program at your OWN! risk... I have not tested it 100% and when I almost finished it, it DID trash my harddisk but now after this release that not yet happened.. If it does happen, think that it might happen to me too:) so don't be mad! .. Ok, having this said...I still hope you will enjoy the program although it has not been tested fully yet. Want to be a beta-tester of dUIM sOFTWaRE?? would be kewl...just phone the number below with yar modem... Config: ------- Line one you put your location of DayDreamX.log where x=your node. Line two you put the location of your Trapdoor.log Only ONE node support for now..if you have more nodes...just let me know next time I will try to make it bigger... Thats it... Last ---- Because this is a beta-version, this program is NOT yet finished. It is not 'smart' in the sense that I have not made it that intelligent that it does not recognise if there is more in the Trapdoor logfile... Some other options are not implemented, but he does extract the userinfo when a trapdoor poller has been on your board...That is the most important side of this program. The rest wil follow in updates. Info needed? ------------ Or bugs?? --------- Call X-Files BBS, member of AGABBS INternational member of aGA_CREW +31-(0)-3253901 or through netmail (AGANet) 171:100/800.0 or e-mail: pinkie@dds.nl History ------- 1.0-1.9 never released because of severe bugs and unreliability! 2.0 Supposed to be the 1oo% release but this was a slow and low reliable program 3.0 Major Speed-up, routines... COmpletely progged in 'E'.... 3.1 Minor bugfix... Forgot to update the .DAT file after every call to LogScan. It only updated it, when a poller had been detected..This is fixed now. 3.2 DreamTosser was only called after a Poller had called. Now it will be called after every incoming call and after outgoing calls. 3.3 DreamTosser was called wrongly. Made an error .. dunno what happened eexactly but it should be fixed now. Also some string outputted some weird stupid code into the .DAT.. should be fixed by now.. Report to me please if this still is not fixed in 3.3b... 3.31 SOme little bug occured .. where I don't know anymore.. I know I had to make some little adjustments.. therefore the small version change. 3.32 I thought I had fixed the bug that occured when making a .DAT after an Incoming call .. I soon found out that it had to do with a wrong Handle referrence. That is fixed now. 3.33 Found a little bug ... what it was I don't exactly know anymore. But it has been fixed :) 3.4 A few changes have been made. In the previous versions the program extracted the login name from the n-th line. Now I have made the program a little smarter and it detects the Sysop: keyword and extracts the Login name from it. There is one odd thing. When your Trapdoor.log gets bigger, the program starts to do wweird things like taking to long. :) In theory this should not be possible because of the way I extract and scan through it, but it still does. Just that you are warned. Sometimes it can take a while. (I have a logfile of 500k)...aarg 3.41 Found a bug which occured when LogScan was activated after a crash, Trapdoor was not able to finish the logfile so LoGScan wend crazy and fucked a little up in my last callers. Sometimes the WRONG people or WRONG lines were entered into the logfile. This should be fixed, although very primitive. I will try to make this a bit smarter again in the next release. 3.43 Hmm, though I had fixed it.. seemed not. Problems occured when one char long day numbers came into the log... should be fixed now 3.44 And STILL the fucking program did fuck it up all! SO now it is fixed AGAIN! Sorry guys... I NEED BETATESTERS!!!!