Hello everybody.

Hi there... I'm playing around with OS2 and ELE/2 and I have a quick question. I have SIO deal running but when I go to load a dos door, I'm trying to telnet in, the BBS works fine but the dos door choaks and says there is no fossil driver loaded. Is there some other command I'm missing??

Thanx

Joe

--- FMail/Win32 1.60
* Origin: ----> Joesbbs.no-ip.com <---- (1:275/400)

Hello Joe!

Thursday January 19 2006 10:01, Joe Schweier wrote to All:

Hi there... I'm playing around with OS2 and ELE/2 and I have a quick question. I have SIO deal running but when I go to load a dos door,
I'm trying to telnet in, the BBS works fine but the dos door choaks
and says there is no fossil driver loaded. Is there some other
command I'm missing??

In the settings for the DOS session that your door runs in, you need to add DOS_DEVICE=C:\SIO\VX00.SYS so that you load the (virtual) FOSSIL driver. This can be done in CONFIG.SYS (which would make the FOSSIL available in all DOS sessions), or with extra utilities you can start VX00.SYS in only those sessions that need it.

Here's a quote from my batch files:

SPAWNBBS.CMD (I use BTXE/2):

=== Cut ===
@Echo Off
Echo SPAWNBBS.CMD; BBS Loader Command File, Version 1.00α1
Echo Copyright (C) 1997 by Andrew J. Leary. ALL RIGHTS RESERVED.
Echo  
Echo Creating batch file...
Echo EXEBBS1 %2 1 %4 %5>DOBBS.BAT
Echo Starting the BBS...
Start "BBS Node 1" /FG /FS /WAIT /DOS=E:\RA\NODE1\NODE1.INI DOBBS.BAT
If Not Exist K:\Flags\BBSMail.FLG Goto End
CD \FE
FastEch2 Scan -A
CD \RA\Node1
:End
=== Cut ===

NODE1.INI:

=== Cut ===
DOS_DEVICE=D:\SIO2K\VX00.SYS
SIO_Allow_Access_COM1=1
SIO_Screen_Sync_Kludge=1
=== Cut ===

I'm using the START command built into 4OS2. I believe that most other Start utilities also have the ability to do something similar.

Andrew

---
* Origin: Bits & Bytes BBS * V.Everything! * 860/535-4284 (1:320/119)

Joe,

*** Quoting Joe Schweier from a message to All ***

Hi there... I'm playing around with OS2 and ELE/2 and I have a quick question. I have SIO deal running but when I go to load a dos door,
I'm trying to telnet in, the BBS works fine but the dos door choaks
and says there is no fossil driver loaded. Is there some other
command I'm missing??

Do you have the - in the calling line in CONFIG.SYS?

As in: COM1(38400,3F8,IRQ4,-)

(that's just made up, I don't remember the exact values)

The - is a poorly documented parameter to allow DOS doors to use the FOSSIL under SIO.

HTH,
Sean

// sean@outpostbbs.net | http://outpostbbs.net | ICQ: 19965647

--- Telegard/2 v3.09.g2-sp4/mL
* Origin: Outpost BBS - bbs.outpostbbs.net (1:18/200)

Whilst masticating on <Jan 19 06>, Andrew Leary (1:320/119)
wrote to Joe Schweier:

In the settings for the DOS session that your door runs in, you
need to add DOS_DEVICE=C:\SIO\VX00.SYS so that you load the
(virtual) FOSSIL driver. This can be done in CONFIG.SYS (which
would make the FOSSIL available in all DOS sessions), or with
extra utilities you can start VX00.SYS in only those sessions
that need it.

Shouldn't that just be DEVICE=, rather than DOS_DEVICE=? That's how it'a always been in my config.sys. *adh*

--- Msged/2 6.0.1
* Origin: tncbbs.no-ip.com - Try the CROSSFIRE echo - all welcome (1:261/1000)

In a message to Andrew Leary <17:43 ~> Alan Hess wrote:

Shouldn't that just be DEVICE=, rather than DOS_DEVICE=? That's how
it'a always been in my config.sys. *adh*

It's DEVICE= in CONFIG.SYS, DOS_DEVICE= in the individual session DOS settings. I had forgotten that; it's been a LONG time since I set that up.

Andrew


---
* Origin: Bits & Bytes BBS * V.Everything! * (860) 535-4284 (1:320/119)

Hi there... I'm playing around with OS2 and ELE/2 and I have a quick question. I have SIO deal running but when I go to load a dos door,
I'm trying to telnet in, the BBS works fine but the dos door choaks
and says there is no fossil driver loaded. Is there some other
command I'm missing??

Do you have the - in the calling line in CONFIG.SYS?

As in: COM1(38400,3F8,IRQ4,-)

(that's just made up, I don't remember the exact values)

The - is a poorly documented parameter to allow DOS doors to use
the FOSSIL under SIO.

actually, the '-' tells SIO so allow the port to be shared by more than one program at a time... it can be a gotcha, too... like the time that i forgot and
clicked on the wrong telix icon and loaded the one configured the same as the bbs and both programs were trying to use the same comport at the same time... not a very pretty picture ;)

)\/(ark


* Origin: (1:3634/12)

Quoting mark lewis to Sean Dennis <=-

actually, the '-' tells SIO so allow the port to be shared by more
than one program at a time... it can be a gotcha, too... like the time that i forgot and clicked on the wrong telix icon and loaded the one configured the same as the bbs and both programs were trying to use the same comport at the same time... not a very pretty picture ;)

OUCH! I hate it when that happens. I'm still trying to get the
Os2Shares and DosShares keywords in SIO2K to cooperate (they're the
counterpart of the - parameter in SIO 1.x.) I had it working (mostly)
when running EleBBS/2 with DOS doors, but when I add the mailer into the
mix (also OS/2 native), I get dropped carriers when returning from DOS
doors or the doors can't detect carrier when loading. I can't use the
SIO 1.60d version, since VMODEM in that version is broken with respect
to recent versions of TCP/IP.

Andrew

---
* Origin: Bits & Bytes BBS * V.Everything! * (860) 535-4284 (1:320/119)

Mark,

*** Quoting mark lewis from a message to Sean Dennis ***

actually, the '-' tells SIO so allow the port to be shared by more
than one program at a time... it can be a gotcha, too... like the
time that i forgot and clicked on the wrong telix icon and loaded the
one configured the same as the bbs and both programs were trying to
use the same comport at the same time... not a very pretty picture ;)

Oh, I have had that happen more than once. I've had two front-end mailers monitoring the modem at once. When the modem rang, all chaos broke loose. <G>

Later,
Sean

// sean@outpostbbs.net | http://outpostbbs.net | ICQ: 19965647

--- Telegard/2 v3.09.g2-sp4/mL
* Origin: Outpost BBS - 423.926.0556 - bbs.outpostbbs.net (1:18/200)

Joe Schweier wrote to All:

Hi there... I'm playing around with OS2 and ELE/2 and I have a quick question. I have SIO deal running but when I go to load a dos door, I'm trying to telnet in, the BBS works fine but the dos door choaks and says there is no fossil driver loaded. Is there some other command I'm missing??

You may want to be sure that VX00.SYS is loaded in your config file so
that any DOS windows that open up automatically load the VX00.SYS FOSSIL driver.

Greetings, Robert Wolfe

... "640K ought to be enough for anybody." Bill Gates '81

--- MBSE BBS v0.83.11 (GNU/Linux-Sparc)
* Origin: Buffalo Online | Buffalo NY | bbs.net261.com (1:261/1)

*** Quoting Sean Dennis from a message to mark lewis ***

Oh, I have had that happen more than once. I've had two front-end
mailers monitoring the modem at once. When the modem rang, all chaos broke loose. <G>

Later, Sean

Sean, installed TG/2 here and am using it to post now. What mail tosser/scanner are you using by any chance? Using the shareware version of Fastecho/2 here.

---
* Origin: Another Good Point About eComStation! (1:261/20.1)

Robert,

*** Quoting Robert Wolfe from a message to Sean Dennis ***

Sean, installed TG/2 here and am using it to post now. What mail tosser/scanner are you using by any chance? Using the shareware
version of Fastecho/2 here.

I'm using Squish and BinkleyTerm. FastEcho may be registered for free now (netmail me for more details), but I could not get it to work right with BT-style outbound.

Later,
Sean

// sean@outpostbbs.net | http://outpostbbs.net | ICQ: 19965647

--- Telegard/2 v3.09.g2-sp4/mL
* Origin: Outpost BBS - 423.926.0556 - bbs.outpostbbs.net (1:18/200)

Robert Wolfe wrote to Sean Dennis:

Sean, installed TG/2 here and am using it to post now. What mail tosser/scanner are you using by any chance? Using the shareware version of Fastecho/2 here.

I'm just curious how fastEcho handles large messages, are you reading
messages in the STATS echo there by chance? I know squish can't toss
some of the bigger messages in that echo and I'm just wondering if
FE tosses them ok.

Ttyl :-),
Al

... Gee! How'd you ever get it to do THAT?

--- MBSE BBS v0.83.12 (GNU/Linux-x86_64)
* Origin: The Rusty MailBox - Penticton, B.C. Canada - trmb.ca (1:153/757)

Alan,

*** Quoting Alan Ianson from a message to Robert Wolfe ***

messages in the STATS echo there by chance? I know squish can't toss
some of the bigger messages in that echo and I'm just wondering if FE

I've had Squish handle 64K messages just fine. Then again, I run the OS/2 version...

Later,
Sean

// sean@outpostbbs.net | http://outpostbbs.net | ICQ: 19965647

--- Telegard/2 v3.09.g2-sp4/mL
* Origin: Outpost BBS - 423.926.0556 - bbs.outpostbbs.net (1:18/200)

Sean Dennis wrote to Alan Ianson:

messages in the STATS echo there by chance? I know squish can't toss some of the bigger messages in that echo and I'm just wondering if FE

I've had Squish handle 64K messages just fine. Then again, I run the OS/2 version...

Some messages in there now are over 400k, the os2 version of squish
might handle that OK, I'm not to sure. Do you read the STATS echo?

Ttyl :-),
Al

... ASCII stupid question, get a stupid ANSI.

--- MBSE BBS v0.83.12 (GNU/Linux-x86_64)
* Origin: The Rusty MailBox - Penticton, B.C. Canada - trmb.ca (1:153/757)

*** Quoting Alan Ianson to Robert Wolfe dated 02-11-06 ***

I'm just curious how fastEcho handles large messages, are you reading messages in the STATS echo there by chance? I know squish can't toss

FE chops the message if its to long. :{

Rich
I-Net turtil@frontiernet.net


... Enjoy yourself today.Tomorrow may never come at all.
---
* Origin: Turtil's Pond BBS. Monroe NY 845-783-2106 (1:2624/50)

Rich Wonneberger wrote to Alan Ianson:

I'm just curious how fastEcho handles large messages, are you reading messages in the STATS echo there by chance? I know squish can't toss

FE chops the message if its to long. :{

Not so good, I guess it doesn't get passed on to your links at all
either?

Ttyl :-),
Al

... Survival tip #42 - Never play leapfrog with a unicorn.

--- MBSE BBS v0.83.12 (GNU/Linux-x86_64)
* Origin: The Rusty MailBox - Penticton, B.C. Canada - trmb.ca (1:153/757)

Alan,

*** Quoting Alan Ianson from a message to Sean Dennis ***

Some messages in there now are over 400k, the os2 version of squish
might handle that OK, I'm not to sure. Do you read the STATS echo?

I used to, but then again, I realized that the only stats that mattered were on
my own board. :)

Later,
Sean

// sean@outpostbbs.net | http://outpostbbs.net | ICQ: 19965647

--- Telegard/2 v3.09.g2-sp4/mL
* Origin: Outpost BBS - 423.926.0556 - bbs.outpostbbs.net (1:18/200)

Alan,

*** Quoting Alan Ianson from a message to Rich Wonneberger ***

Not so good, I guess it doesn't get passed on to your links at all
either?

If someone's posting 400K messages, they ought to be slapped.

Any sysop would realize that not everyone's systems can handle messages that big and put them into 64K chunks (possibly still, 16K). But to be honest, who really needs that kind of statistical data broadcast? I can see a major hub generating statistics locally, but really now, 400K? :)

I do believe that you aren't going to see any tosser go over 64K, period. I read the docs and FE does cut the packets as does Squish. I can't speak for any other tosser, but those two do truncate the message.

Later,
Sean

// sean@outpostbbs.net | http://outpostbbs.net | ICQ: 19965647

--- Telegard/2 v3.09.g2-sp4/mL
* Origin: Outpost BBS - 423.926.0556 - bbs.outpostbbs.net (1:18/200)

Sean Dennis wrote to Alan Ianson:

If someone's posting 400K messages, they ought to be slapped.

I dunno how big he is.. :)

Any sysop would realize that not everyone's systems can handle messages that big and put them into 64K chunks (possibly still, 16K). But to be honest, who really needs that kind of statistical data broadcast? I can see a major hub generating statistics locally, but really now, 400K? :)

Yep, I exported one to a file last night to see, 451Kb.. it's a bigun. :)
It contains a list of every message area that hub carries (many nets)
that lists how many messages were sent & recieved in those areas. I read
the area from time to time just to see what areas are getting traffic
and be sure I am connected.. :)

It's a tough read for sure but lots of good info if FTN traffic is what
your looking for.

I do believe that you aren't going to see any tosser go over 64K, period. I read the docs and FE does cut the packets as does Squish. I can't
speak for any other tosser, but those two do truncate the message.

Squish skips a message if it's to large, so your links don't get the
message at all and it's not in your own message base. FE tries to toss
the message but when the buffer runs out.. that's the end of that.

As far as FTSC standards go, message size is unbounded (from what I understand). Still, I believe you are right about message size. A
large message should be split so all interested parties get it. It'll
still be a big message, just in a few pieces.

Ttyl :-),
Al

... Dew knot trussed yore spell chequer two fined awl mistakes!

--- MBSE BBS v0.83.12 (GNU/Linux-x86_64)
* Origin: The Rusty MailBox - Penticton, B.C. Canada - trmb.ca (1:153/757)

Alan Ianson wrote to Robert Wolfe:

I'm just curious how fastEcho handles large messages, are you reading messages in the STATS echo there by chance? I know squish can't toss
some of the bigger messages in that echo and I'm just wondering if
FE tosses them ok.

FE cans SOME, but not all messages.

Greetings, Robert Wolfe

... "Keyboard? How quaint!" - Scotty

--- MBSE BBS v0.83.11 (GNU/Linux-Sparc)
* Origin: Buffalo Online | Buffalo NY | bbs.net261.com (1:261/1)

Alan,

*** Quoting Alan Ianson from a message to Sean Dennis ***

I dunno how big he is.. :)

I was just figuratively speaking, of course. :) It's a little hard to slap someone from behind a console.

Squish skips a message if it's to large, so your links don't get the message at all and it's not in your own message base. FE tries to
toss the message but whenthe buffer runs out.. that's the end of
that.

The OS/2 version of Squish can handle 256K messages according to the documentation. But I'd think that large messages are a no-no with respect to other people's systems. My opinion, of course, but that's being rather disrepectful to put out a message that you know other people's systems may or may not be able to handle.

Squish/2 does what I want and if it deletes a message that's that big, well, it
doesn't need to be in my system anyway.

Later,
Sean

// sean@outpostbbs.net | http://outpostbbs.net | ICQ: 19965647

--- Telegard/2 v3.09.g2-sp4/mL
* Origin: Outpost BBS - 423.926.0556 - bbs.outpostbbs.net (1:18/200)

Robert Wolfe wrote to Alan Ianson:

I'm just curious how fastEcho handles large messages, are you reading messages in the STATS echo there by chance? I know squish can't toss some of the bigger messages in that echo and I'm just wondering if
FE tosses them ok.

FE cans SOME, but not all messages.

Well, at least that MBSE BBS of yours will toss them fine and pass
them on to your links.. :)

Ttyl :-),
Al

... A little ignorance can go a long way.

--- MBSE BBS v0.83.12 (GNU/Linux-x86_64)
* Origin: The Rusty MailBox - Penticton, B.C. Canada - trmb.ca (1:153/757)

Sean Dennis wrote to Alan Ianson:

I was just figuratively speaking, of course. :) It's a little hard to slap someone from behind a console.

I was just having fun.. :)

Squish/2 does what I want and if it deletes a message that's that big, well, it doesn't need to be in my system anyway.

Yep, there are some systems that simply can't toss that message, so
if you want to be read it's necessary to cut it down to size somewhat.
But to what? 256Kb? MBSE BBS can create messages like that too (new
file announcements), but if there are a lot of files recieved on any
day they get split at 32kb. I'm pretty sure any tosser on any OS can
toss those.. :)

Ttyl :-),
Al

... *** ERROR *** Unable to insert witty tagline.

--- MBSE BBS v0.83.12 (GNU/Linux-x86_64)
* Origin: The Rusty MailBox - Penticton, B.C. Canada - trmb.ca (1:153/757)

Sean Dennis wrote to Robert Wolfe <=-

I'm using Squish and BinkleyTerm. FastEcho may be registered for free
now (netmail me for more details), but I could not get it to work
right with BT-style outbound.

That is a tough thing to do, I ended up getting it to work somehow,
Forget if I had the same problem, but I did have a problem, but it all
works now. So Fastecho will work, but there is a obstacle to overcome.
If it comes up we could compare config files and I can probably
remember what I ended up doing.

Kev


... "Look at all the Indians!" - General Custer
~~~ TGWave v1.12+
--- Telegard/2 v3.09.g2-sp4/mL
* Origin: Razor's Domain BBS (1:397/10)

*** Quoting Sean Dennis from a message to Alan Ianson ***

I've had Squish handle 64K messages just fine. Then again, I run the
OS/2 version...

Ditto.

---
* Origin: Another Good Point About eComStation! (1:261/20.1)

I'm using Squish and BinkleyTerm. FastEcho may be registered for
free now (netmail me for more details), but I could not get it to
work right with BT-style outbound.

please netmail me with details on both situations ;)

)\/(ark


* Origin: (1:3634/12)

I'm just curious how fastEcho handles large messages, are you reading messages in the STATS echo there by chance? I know squish can't toss

FE chops the message if its to long. :{

and that highly depends on the version/flavor of FE your are running... IIRC, the OS/2 version has a 512k limit but i have to check my config settings to confirm that...

)\/(ark


* Origin: (1:3634/12)

As far as FTSC standards go, message size is unbounded (from what I understand).

absolutely... 100% correct...

Still, I believe you are right about message size. A
large message should be split so all interested parties get it.
It'll still be a big message, just in a few pieces.

and it should be the receiving system's problem to split large messages... after all, they should know their software's limits... why should i, as a mail mover, have to know the limits of all the software my downlinks may run? why should i have to degrade the performance of my system or my delivery mechanism by having to play to the slowest participant al la public schools?? hello?

)\/(ark


* Origin: (1:3634/12)

Yep, there are some systems that simply can't toss that message, so
if you want to be read it's necessary to cut it down to size
somewhat. But to what? 256Kb? MBSE BBS can create messages like
that too (new file announcements),

hell. i've got software that i wrote that can create messages as large as my available drive space up to 2gig, in size... it has been actively tested by posting the largest nodelist in fidonet's history to one message in one test echo...

but if there are a lot of files recieved on any day they get split
at 32kb. I'm pretty sure any tosser on any OS can toss those.. :)

yup but who really wants to be tossing 100's of small messages when tossing one
will do, go faster, and take up less space (due to no duplication of the headers and other control information) O:)

)\/(ark


* Origin: (1:3634/12)

mark lewis wrote to Alan Ianson:

but if there are a lot of files recieved on any day they get split
at 32kb. I'm pretty sure any tosser on any OS can toss those.. :)

yup but who really wants to be tossing 100's of small messages when tossing one will do, go faster, and take up less space (due to no duplication of the headers and other control information) O:)

Yep, posting ten 32kb msgs instead of one 320kb message doesn't seem
like a very good solution. Even at that I've only seen it get split
once so I've never really had much reason to think about it. I leave
it at that because I've had tossers crash in the past and don't wish
that on anyone.

I guess that third party utility you spoke of is a good option if a
tosser can't do the deed itself, although I don't like the idea much.

Tossers that I know of, that are still being developed (HPT, MBSE,
SBBSECHO) and likely more that I have no experience with, do toss
large messages so we are moving in the right direction.

Ttyl :-),
Al

... All of my REALLY GOOD taglines are 1 character too lon

--- MBSE BBS v0.83.13 (GNU/Linux-x86_64)
* Origin: The Rusty MailBox - Penticton, B.C. Canada - trmb.ca (1:153/757)

Mark,

*** Quoting mark lewis from a message to Sean Dennis ***

please netmail me with details on both situations ;)

Netmail going out with this packet (routed).

Later,
Sean

// sean@outpostbbs.net | http://outpostbbs.net | ICQ: 19965647

--- Telegard/2 v3.09.g2-sp4/mL
* Origin: Outpost BBS - 423.926.0556 - bbs.outpostbbs.net (1:18/200)

If someone's posting 400K messages, they ought to be slapped.

^^^^^^^^^^^^^^^^^^^^^^^^^^^

They should actually be strung up by the testicles with rusty barbed wire!


--- Maximus/2 3.01
* Origin: Gargoyle's Place BBS (1:365/3253)

Hey Mark!

and that highly depends on the version/flavor of FE
your are running... IIRC, the OS/2 version has a 512k
limit but i have to check my config settings to
confirm that...

I followed the FE situation for a long time here asking for 'the OS/2 version'.
Was told it had never been released. Also was looking for and OS/2 version of
Allfix. Both to upgrade the 1:117/100 HUB to solid OS/2 instead of DOS.

Can you furnish me with any of the details on any of this? Thanks!

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

Mike @ 1:117/3001

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

but if there are a lot of files recieved on any day they get split
at 32kb. I'm pretty sure any tosser on any OS can toss those.. :)

yup but who really wants to be tossing 100's of small messages when tossing one will do, go faster, and take up less space (due to no duplication of the headers and other control information) O:)

Yep, posting ten 32kb msgs instead of one 320kb message doesn't
seem like a very good solution.

you're darned tootin... especially considering all the additional info that needs to be added to each one... the header is at least 40 characters (for argument's sake, we'll use that figure for calculations) so that means at least
another 400 bytes _plus_ the additional seenbys, paths, and (at least) origin lines... then you also have to add in the additional overhead for the ^aSPLIT lines and anything else that is added during the process of splitting...

Even at that I've only seen it get split once so I've never really
had much reason to think about it. I leave it at that because I've
had tossers crash in the past and don't wish that on anyone.

no doubt... in fact, i doubt that anyone who has really moved the mail hasn't had a tosser crash...

I guess that third party utility you spoke of is a good option if a
tosser can't do the deed itself, although I don't like the idea
much.

i'f my system is the last one remaining that can't handle messages larger than 32k (for instance) why should everyone else in the network have to be saddled with messages that small? the only real problem i'm aware of in this area is that this util might not be available for some platforms that may be being used
in fidonet... however, i must also state that i'm not aware of any remaining systems running things like the COCO, TI99, TRS-80's or other antiquated machines... i'd possibly even go so far as to hazard a guess that most everyone
is running at least a "current" or "recent" OS, too... in this day in time, that means windows 98, 2000, ME, or XP, LINUX in some flavor, OS/2, and possibly the old apple system 9 (i think it was called)... newer apple/machintosh machines are running a flavor of linux and even their chipset is currently changing to intel based chips instead of motorola stuff...

Tossers that I know of, that are still being developed (HPT, MBSE, SBBSECHO) and likely more that I have no experience with, do toss
large messages so we are moving in the right direction.

yup!

)\/(ark


* Origin: (1:3634/12)

Mike,

*** Quoting Mike Luther from a message to Mark Lewis ***

I followed the FE situation for a long time here asking for 'the OS/2 version'. Was told it had never been released. Also was looking for

I've sent you a netmail (should go out w/this packet).

I'd crash it to you, but no LD on the phone line yet.

Later,
Sean

// sean@outpostbbs.net | http://outpostbbs.net | ICQ: 19965647

--- Telegard/2 v3.09.g2-sp4/mL
* Origin: Outpost BBS - 423.926.0556 - bbs.outpostbbs.net (1:18/200)

*** Quoting Dale A Cook to Sean Dennis dated 02-15-06 ***

If someone's posting 400K messages, they ought to be slapped.

^^^^^^^^^^^^^^^^^^^^^^^^^^^

They should actually be strung up by the testicles with rusty barbed
wire!

Why let them off that easy??

Rich
I-Net turtil@frontiernet.net


... Johnson & Johnson Tagline: █████░░░░░█████
---
* Origin: Turtil's Pond BBS. Monroe NY 845-783-2106 (1:2624/50)

mark lewis wrote to Rich Wonneberger <=-

and that highly depends on the version/flavor of FE your are running... IIRC, the OS/2 version has a 512k limit but i have to check my config settings to confirm that...

You do recall correctly. I've had it set to 512k for ages. I've never seen a message long enough to be truncated by FE.

Andrew


... MultiMail, the new multi-platform, multi-format offline reader!

---
* Origin: Bits & Bytes BBS * V.Everything! * (860) 535-4284 (1:320/119)

and that highly depends on the version/flavor of FE
your are running... IIRC, the OS/2 version has a 512k
limit but i have to check my config settings to
confirm that...

I followed the FE situation for a long time here asking for 'the
OS/2 version'. Was told it had never been released.

that's rather funny... i don't know who told you that but they are/were incorrect...

Also was looking for and OS/2 version of Allfix. Both to upgrade
the 1:117/100 HUB to solid OS/2 instead of DOS.

i'm not sure about allfix... i believe that i am running the OS/2 version but would have to go and dig about on that machine to find out... i may have just left it as the DOS version in case i ever needed to jump back to DOS...

Can you furnish me with any of the details on any of this?
Thanks!

from my files list...


┌────────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Area 129 - FASTECHO: FastEcho EchoMail Tosser ▓▓▓▒▒▒░░░│
└────────────────────────────────────────────────────────────────────────────┘

bupd124a.rar 16k 06-22-94 U/L: waldo kitty Binary Update - a program to patch with

fe146.rar 670k 04-01-97 U/L: waldo kitty ------------------------------------------
## ---------- FastEcho v1.46 ---------- ##
## ------ Bugfixed Easter Update ------ ## ------------------------------------------
Very fast FTN mail processor for Hudson-
(aka QBBS), JAM-, Squish- and Fido/*.MSG-
style messagebases. Internal AreaFix, dupe
checking, full security, NetMail routing,
full screen setup, area grouping, network-
and multitasking-support, auto area add
function supporting all major BBS systems,
great msgbase tool included, carbon-copy-
function. Archive contains DOS executables
plus all files needed for other platforms.
|
--- NEW FEATURES IN v1.46: --- |
Native OS/2 setup program, more groups, |
more areas, enhanced AreaFix functions |
and much more! [Shareware, $15/25] | ------------------------------------------
Copyright (c) 1991-1997 by
Software Technik Burchhardt, Waltrop, FRG. ------------------------------------------

fe146p.rar 464k 04-01-97 U/L: waldo kitty ------------------------------------------
## ---------- FastEcho v1.46 ---------- ## ------------------------------------------
Very fast FTN mail processor for Hudson-
(aka QBBS), JAM-, Squish- and Fido/*.MSG-
style messagebases. [Shareware, $15/25] ------------------------------------------
Includes OS/2 32 bit executables only,
requires full package (FE146.RAR) to run!
Now also included: native OS/2 FESetup ... ------------------------------------------
Copyright (c) 1991-1997 by
Software Technik Burchhardt, Waltrop, FRG. ------------------------------------------

fe146pl1.rar 51k 04-03-97 U/L: waldo kitty ------------------------------------------
## --------- FastEcho 1.46pl1 --------- ## ------------------------------------------
This is a patch from the original FastEcho
1.46 release to patch level 1. Fixes PACK
-P ignoring NetMail messages with several
^aFLAGS set (Binkley-style outbound only!) ------------------------------------------
Needs BUpdate (BUPD124A.RAR) to apply .BDF ------------------------------------------
Copyright (c) 1991-1997 by
Software Technik Burchhardt, Waltrop, FRG. ------------------------------------------

fe146x.rar 640k 04-01-97 U/L: waldo kitty ------------------------------------------
## ---------- FastEcho v1.46 ---------- ## ------------------------------------------
Very fast FTN mail processor for Hudson-
(aka QBBS), JAM-, Squish- and Fido/*.MSG-
style messagebases. [Shareware, $15/25] ------------------------------------------
Includes DPMI executables only, requires
full package (FE146.RAR) to run !!! Now
also featuring 32 bit version of FESetup. ------------------------------------------
Copyright (c) 1991-1997 by
Software Technik Burchhardt, Waltrop, FRG. ------------------------------------------

fecv154.zip 256k 01-04-96 U/L: waldo kitty FeConv 1.54
-----------
-converts your fastecho-setup (1.45a)
to RA/IM/FD/PB/SBBS/Maximus
-creates almost freely definable
text-files with information from
fastecho.cfg
-writes several reports:
passive areas, passive nodes,
errors reported by fastecho,
areas with one/two links,
areas w/o description, etc...

Volker Imre @ 2:246/2001 <<<<

fecv156.zip 257k 03-01-96 U/L: waldo kitty FeConv 1.56
-----------
-converts your fastecho-setup (1.45a)
to RA/IM/FD/PB/SBBS/Maximus
-creates almost freely definable
text-files with information from
fastecho.cfg
-writes several reports:
passive areas, passive nodes,
errors reported by fastecho,
areas with one/two links,
areas w/o description, etc...
-works with FD/IM/McMail/T-Mail/
Binkley/....
-New: RA 2.50 Support

Volker Imre @ 2:246/2001 <<<<

fecv_upd.rar 167k 07-15-99 U/L: file distribution FeConv

.EXE-Update only!

-added support for FE-Groups 1-6
fek155e.rar 97k 01-05-98 U/L: file distribution FeKill V1.55 with English docfile
os/2 & dos version
Maintenance tool for FastEcho 1.46
-Deletes and unlinks "dead" echos
-Notifies downlinks of "dead" echos
-Announces new areas
and many more features, see
WHATSNEW for changes since 1.48
fekil155.rar 98k 01-04-98 U/L: file distribution FeKill V1.55 with German docfile
os/2 & dos version
Maintenance tool for FastEcho 1.46
-Deletes and unlinks "dead" echos
-Notifies downlinks of "dead" echos
-Announces new areas
and many more features, see
WHATSNEW for changes since 1.48
feunl150.rar 18k 10-01-96 U/L: waldo kitty
Feunlink 1.50
-little tool to unlink and delete
echoares by command-line and
writes mails to "areafix" of all
links
-supports FIDOKILL.NA as input
-supports FE's busy-semaphore
-the file "feunlink.anc" is ready
to get posted via FEUTIL POST
-needs Fastecho 1.45(a)
-"netmailware"

=====================================================================

looks to me like the OS/2 version was released in 1997 with a quick patch for BSO problems two days later...

)\/(ark


* Origin: (1:3634/12)

please netmail me with details on both situations ;)

Netmail going out with this packet (routed).

it did arrive... thanks for the info... unfortunately, i've never really worked
with BSOs and can't really help in that area... all my stuff is either fileboxes or frontdoor type dynamic routed stuff...

)\/(ark


* Origin: (1:3634/12)

*** Quoting Mark Lewis to Mike Luther dated 02-17-06 ***

from my files list...

Mark,

Thanks for having the files available
I'm running 1.46.

Rich
I-Net turtil@frontiernet.net


... Be alert! The world needs more lerts
---
* Origin: Turtil's Pond BBS. Monroe NY 845-783-2106 (1:2624/50)

*** Quoting Mark Lewis to Mike Luther dated 02-17-06 ***

from my files list...

Thanks for having the files available
I'm running 1.46.

enjoy them in good health ;)

)\/(ark


* Origin: (1:3634/12)