* Replying to a message originally in area Fido.Bluewave

Hi, Mike-

Sure...we might as well see if it's still working.

Is it working? <G>

Later,
Sean


--- Maximus/2 3.01
* Origin: Nocturnal State BBS - nsbbs.info (1:18/200)

Hello Sean!

22 Feb 09 14:55, Sean Dennis wrote to Mike Tripp:

Sure...we might as well see if it's still working.

Is it working? <G>

Yep...1st message since 5/27/08.

.\\ike

--- GoldED/2 2.50+
* Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k (1:382/61)

Hello Sean.

22 Feb 09 14:55, you wrote to Mike Tripp:

Sure...we might as well see if it's still working.

Is it working? <G>

Got here, tho you original netmail to me has not yet arrived here, maybe you could resend it?

Russell

--- GoldED+/LNX 1.1.5
* Origin: Rusty's BBS - Bloemfontein, Free State, South Africa (5:7105/1)

Hi RUssell,

On Tue 2037-Feb-24 18:26, Russell Tiedt (5:7105/1) wrote to Sean Dennis:

Got here, tho you original netmail to me has not yet arrived here,
maybe you could resend it?

I sent you nm through Janis once iirc, and same thing
happened. REsent through my primary uplink, 3634/12 and it
arrived and you replied. <hmmmm>

seems I can't reach z2 via 261/38 either. Bbbs often
complains about my netmails anyway. If it's destined for
r19 I route it through rc19. SAme with other regions con us or nets that have working pots.

IF we continue this discussion in this vein we should
probably be kind and choose another echo <g>.

Russell

Regards,
Richard
--- timEd 1.10.y2k+
* Origin: Radio REscue net operations BBS (1:116/901)

Hello Richard.

24 Feb 09 19:18, you wrote to me:

Got here, tho you original netmail to me has not yet arrived here,
maybe you could resend it?

I sent you nm through Janis once iirc, and same thing
happened. REsent through my primary uplink, 3634/12 and it
arrived and you replied. <hmmmm>

Your uplink notified me, he had mail for me, from you, and how did I want it handled, as I happen to have a direct link to him, I said, "Why not route it direct" ...

seems I can't reach z2 via 261/38 either. Bbbs often
complains about my netmails anyway. If it's destined for
r19 I route it through rc19. SAme with other regions con us or nets
that have working pots.

Right, now you should not have a problem routing mail to any Zone, unless your routing tables are buggered, or someone between you and the Zone you are sending mail to has buggered routing tables ...

IF we continue this discussion in this vein we should
probably be kind and choose another echo <g>.

:-)

Choose ...

Russell

--- GoldED+/LNX 1.1.5
* Origin: Rusty's BBS - Bloemfontein, Free State, South Africa (5:7105/1)

Hi RUssell,

On Thu 2037-Feb-26 16:44, Russell Tiedt (5:7105/1) wrote to Richard Webb:

I sent you nm through Janis once iirc, and same thing
happened. REsent through my primary uplink, 3634/12 and it
arrived and you replied. <hmmmm>

Your uplink notified me, he had mail for me, from you, and how did I
want it handled, as I happen to have a direct link to him, I said,
"Why not route it direct" ...

YEp, I route all my outbound, all zones via him unless it's
continental U.S> and has a pots connection closer as noted
earlier.

Right, now you should not have a problem routing mail to any Zone,
unless your routing tables are buggered, or someone between you and
the Zone you are sending mail to has buggered routing tables ...

True enough. AS Janis explains, bbbs seems to be rather
sticky about its interpretation of fidonet tech standards.
MEthinks it has to do more with the way squish handles
routing when used with static mailers such a binkley,
although I don't know what the heck it is. MEthinks that's
why Sean's nm to you is somewhere in limbo world as well
<g>.

IF we continue this discussion in this vein we should
probably be kind and choose another echo <g>.

:-)

Choose ...

I'm linked to both fido_sysop and fn_sysop. Also, since
this is essentially an argument between squish and bbbs
which causes the problem tub might be appropriate as well.
Seems to be that imho anyway.

Regards,
Richard
... Braille: support true literacy for the blind.
--- timEd 1.10.y2k+
* Origin: Radio REscue net operations BBS (1:116/901)

Sure...we might as well see if it's still working.

Is it working? <G>

Yep...1st message since 5/27/08.

.\\ike

I noticed that! Where did everyone go? I am still stuck on the same Linux base of Maximus and I thught my uplink or the linux version of squish went bizerk. Speaking of Max on Linux... Bo..... Do you have any new updates for me to snag?
I haven't done a CVS update in ages, over a year as far as I can guess.

I was thinking of setting up a msdos version of max to allow me to put some doors up. Still have a dialup line here and several telnet nodes.

Of course if someone figured out how to get dos games running on max with Dosemu... I could sure use a few clues.

I need to find some games that I can use around here that will work with this port of maximus. I will do dos based ones, as I said. if someone can explain how to do it. or perhaps as I suggested a dos based max running under dosemu. I
tried that idea years ago. Max worked OK. but I had problems with the dos based
squish 1.11, its been so long I can remember exactly what went awry.
Still my squish only does ARC packets. never found the cause in the source. it unzips/unarjs etc ... etc... but still only ARCs things despite what compress.cfg tells it to do.

Oh yes. I am back on the ORIGINAL bbs phone number of 860-738-7176. Just in case someone wants to give it a jingle-jangle.

--- Maximus/UNIX 3.03b
* Origin: Planet Maca's Opus (860)738-7176 (1:142/7176)

Hello Michele!

28 Feb 09 00:18, Michele Marie Dalene wrote to Mike Tripp:

someone can explain how to do it. or perhaps as I suggested a dos
based max running under dosemu. I tried that idea years ago. Max
worked OK. but I had problems with the dos based squish 1.11, its been
so long I can remember exactly what went awry. Still my squish only
does ARC packets. never found the cause in the source. it
unzips/unarjs etc ... etc... but still only ARCs things despite what compress.cfg tells it to do.

Can't help you with the Linux/dosemu specifics. Handing hot comm ports around between binaries built for different target environments is difficult on any platform.

But I think I can solve your Squish archive flavor issue. ARC is the default archiver flavor defined in the stock SQUISH.CFG. You can change the general default, as well as pick any specific flavor you'd like to assign to any specific address. Without some manual changes, ARC for all is what you'll get.

COMPRESS.CFG basically tells Squish =how= to use flavors, SQUISH.CFG tells it what flavors for whom, and ROUTE.CFG determines whether compression is enabled/disabled. These statements from my SQUISH.CFG make ZIP default, but use ARJ for a few specific addresses:

Pack ARJ 382/95 102
DefaultPacker ZIP


.\\ike

--- GoldED/2 2.50+
* Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k (1:382/61)

Thanks for the correction on the compress.cfg vs squish.cfg I did try changing one nodes option from ARC to zip (yes, I have zip installed) and it stil arced his packets. Has any other linux based squish user ran into this same problem?
B'ichela


--- Maximus/UNIX 3.03b
* Origin: Planet Maca's Opus (860)738-7176 (1:142/7176)

Hi Michele

Thanks for the correction on the compress.cfg vs
squish.cfg I did try changing one nodes option from
ARC to zip (yes, I have zip installed) and it stil
arced his packets. Has any other linux based squish
user ran into this same problem?
B'ichela

I'm very surprised! It looks like this must be an operating system specific bug as in both DOS and OS/2 here I have to use both ARC and ZIP for different nodes in the Net 117 operation. Which the compress.cfg does diiferentiate between just fine here.

Sleep well; OS/2's still awake! ;)

Mike @ 1:117/3001

--- Maximus/2 3.01
* Origin: Ziplog Public Port (1:117/3001)

Hello, Mike.

Tuesday March 03 2009 at 07:37, you wrote to Michele Marie Dalene:

I'm very surprised! It looks like this must be an operating system specific bug as in both DOS and OS/2 here I have to use both ARC and
ZIP for different nodes in the Net 117 operation. Which the
compress.cfg does diiferentiate between just fine here.

I recall Wes or Bo talking about that bug quite some time ago...

Later,
Sean

//sean@nsbbs.info | http://nsbbs.info | ICQ: 19965647

... How did a fool and his money get together in the first place?
--- GoldED/2 3.0.1
* Origin: Nocturnal State BBS - Johnson City, TN - nsbbs.info (1:18/200)

Hello Michele!

02 Mar 09 14:58, Michele Marie Dalene wrote to Mike Tripp:

Thanks for the correction on the compress.cfg vs squish.cfg I did try changing one nodes option from ARC to zip (yes, I have zip installed)
and it stil arced his packets. Has any other linux based squish user
ran into this same problem?

You might want to try changing DefaultPacker and see what happens. Might just be the Pack verb that's broken, if it's a bug.

.\\ike

--- GoldED 2.50+
* Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k (1:382/61)

I'm very surprised! It looks like this must be an
operating system specific bug as in both DOS and OS/2
here I have to use both ARC and ZIP for different nodes

It could be a case sensitivity issue somewhere in the source. could it be looking for a lowercase keyword? Does anyone know?
B'ichela

--- Maximus/UNIX 3.03b
* Origin: Planet Maca's Opus (860)738-7176 (1:142/7176)

Hello Richard.

26 Feb 09 20:11, you wrote to me:

I sent you nm through Janis once iirc, and same thing
happened. REsent through my primary uplink, 3634/12 and it
arrived and you replied. <hmmmm>

I have a direct link to 3634/12 ...

True enough. AS Janis explains, bbbs seems to be rather
sticky about its interpretation of fidonet tech standards.
MEthinks it has to do more with the way squish handles
routing when used with static mailers such a binkley,
although I don't know what the heck it is. MEthinks that's
why Sean's nm to you is somewhere in limbo world as well
<g>.

BBBS is a good, package, just when I looked at it, I got the impression, it was built for some other network, and FidoNet got tacked on afterwards ...

I'm linked to both fido_sysop and fn_sysop. Also, since
this is essentially an argument between squish and bbbs
which causes the problem tub might be appropriate as well.
Seems to be that imho anyway.

I am connected to all of those ...

Russell

--- GoldED+/LNX 1.1.5
* Origin: Rusty's BBS - Bloemfontein, Free State, South Africa (5:7105/1)

Hello Michele.

05 Mar 09 21:48, you wrote to Mike Luther:

I'm very surprised! It looks like this must be an
operating system specific bug as in both DOS and OS/2
here I have to use both ARC and ZIP for different nodes

It could be a case sensitivity issue somewhere in the source. could it
be looking for a lowercase keyword? Does anyone know?

Might be ... , it worked fine for me, when I played with it a long while back, but I no longer have that system ... , and I need a power supply for my current test system before I can compile and try again ... BUT ... I always write my config files in lower case, unless there is a requirement for using upper case ...

Worth a try ...

Russell

--- GoldED+/LNX 1.1.5
* Origin: Rusty's BBS - Bloemfontein, Free State, South Africa (5:7105/1)

I sent you nm through Janis once iirc, and same thing
happened. REsent through my primary uplink, 3634/12 and it
arrived and you replied. <hmmmm>

I have a direct link to 3634/12 ...

yup... we've had one for years, eh? ;)

)\/(ark

PS: the peppers did make it over the winter in the basement ;)


* Origin: (1:3634/12)

Hello mark.

11 Apr 09 12:19, you wrote to me:

I sent you nm through Janis once iirc, and same thing
happened. REsent through my primary uplink, 3634/12 and it
arrived and you replied. <hmmmm>

I have a direct link to 3634/12 ...

yup... we've had one for years, eh? ;)

Yes ...

PS: the peppers did make it over the winter in the basement ;)

Glad to hear that ... :-)


Russell

--- GoldED+/LNX 1.1.5
* Origin: Rusty's BBS - Bloemfontein, Free State, South Africa (5:7105/1)