| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | OS/2-native twit filter |
Bo Simonsen wrote in a message to Roy J. Tellason: BS> Hello Roy. BS> 07 Apr 04 04:07, you wrote to me: RJT>> Rather than mess with that at all, if I had something RJT>> that would work with bink (which I understand compiles RJT>> okay under linux), used squish bases, let me stick RJT>> with a familiar editor like TimED, and *looked* like RJT>> Max to the callers that'd be good enough for me. If RJT>> it'd use some or all of the existing ctl files so much RJT>> the better. BS>> Mess?! It works... RT> Does it? I've been watching the discussion in here for quite some RT> time, ever since this echo pretty much died and then came back to RT> life again when the source to Maximus was finally released. BS> Well I did work on Max the whole January month, and I did fix MEX BS> and other stuff, and the thing seems to work, I did successfully BS> call my BBS by ISDN (Modem or ISDN doesn't matter). BS> The only thing I'm not sure of is how to get Binkley working with BS> MAX, I did try to use "BBS Exit", but the modem hangoff. So it BS> should use BBS Spawn, but I can't test it by a NULL-modem cable, BS> binkley is doing mistery things. So you haven't got that combination working yet. I wonder if anybody has? RT> My immediately accessible archives go back at least four years and RT> some months, but I've been in here a lot longer than that. RT> I've seen problems mentioned, and have seen some of the resolutions RT> to them posted, but by no means all. BS> What problems, I would like if you could be a bit concrete. I don't recall the specifics offhand, and don't feel like digging into the archives just now -- just noting that when I see people in here getting a hold of a copy there are issues with compiling it, and getting it to run, and I don't recall anyone in here ever saying that they'd been successful at it, and had Maximus running under linux. If that'd been the case I surely would have pursued doing the same thing myself. Now it may be that somebody did post such a message and it never made it here, fido has been funny like that in recent times... BS>> I don't see you problem, in what way shouldn't max work properly BS>> under UNIX. Modem is tested and it works well. (I did BS>> successfully do transfering and so on by a NULL-modem cable). RT> Yes? Will I be able to use it under binkley as I'm doing now under RT> dos/desqview? And perhaps use TimED or some sort of a workalike to RT> get at those message bases? BS> There is a bit of a problem there, In theory it should work, I'm BS> just missing the right configuration parameter for binkley. Ah. BS> But it doesn't seems like any of the Binkleyterm maintainers is BS> here anymore. :( I suppose the bink echo might be a good place to try and look into that. I do carry that here as well, even though there hasn't been any traffic in there in a long time. BS>> Sorry Roy, but it seems like you haven't tried it for the last BS>> half of a year. RT> I know one thing for sure, there are posts that are out there in RT> echos that I carry that don't make it here. I guess you can't RT> expect perfection in fidonet, it bein an amateur network and all, RT> but my understanding of the situation was that things weren't RT> finished yet. BS> Aha, but I need some concrete problems... See above. I have bink-max-squish-timed running here under dos/dv. I'd like to switch the whole setup over to linux, and have not yet heard of anyone who has done this or even something close. We also had a discussion in here about a couple of the bits that I'm missing, things having to do with building a files list for people to download and for keeping track of who's downloaded what, but that's fairly minor stuff. If I get the rest of it going I'm sure that can be handled... RT> If this is indeed not the case, and I don't have to worry about such RT> silly stuff as paths embedded in the code, the cases of filenames, RT> and some of the other things I've seen mentioned in here then by all RT> means pass me a URL and I'll snag a copy and have a go at it. BS> Now we are being concrete, the cases of filenames is fixed in QWK BS> where it's needed too, I couldn't find any other problems. What does that mean, exactly? Is QWK working? If so, good, because what few callers I still have these days seem to favor the use of it. Is there anything I need to know with regard to it? RT> I have a particular reason for strongly wanting to have this work, RT> too, *if* it will work for me to replace my current setup. I'm RT> currently one of only three active systems in NET270. Both of the RT> other guys are long distance from me and from each other. BS> Yes I see, but Squish has been stable for a year or so. RT> I'm also LD from any possible feed, so it's costing people money RT> to move this echomail to and from my system. Admittedly not RT> anywhere near as much as it did when fidonet was much bigger, but RT> still a situation I'd like to do away with. BS> I understand. I'm a leafnode so I can do what I want. If I can get this working under linux, I gain a few things right off. First is better connectivity, both with the other nodes in my net, and with the ability to go out and get netmail and echomail myself without having to incur LD charges. It would also enable me to get networking into the setup, so I can build as big of a files section as I want and it doesn't have to reside within the limitations of DOS, which it has to at this point, nor even on the same machine for that matter... There are a few other pluses as well. RT> And there are a few more bits that I need to make the transition, as RT> well... BS> You might be missing third party tools yes.. See above. Mostly it's those two things I mention up there, the files list generator and the download counter. I'll bet I could deal with both of those in c, or perhaps Perl, with a good dose of bash scripting thrown in for good measure. Once I get the momentum going with having the rest of the setup up and working, I'll have enough incentive to work on those parts and get them going. ---* Origin: TANSTAAFL BBS 717-838-8539 (1:270/615) SEEN-BY: 633/267 270 @PATH: 270/615 150/220 3613/1275 123/500 106/2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.