These are the most common messages I see

=============================================================================
* Forwarded by Barry Blackford (3:774/605)
* Area : NETMAIL (Netmail)
* From : FastEcho, 3:774/605 (05 Mar 06 17:47)
* To : Barry Blackford
* Subj : TOSS error report ============================================================================= Error tossing to EASTSTAR: Message too long
Error tossing to STATS: Message too long =============================================================================

Best Rgds, Bazz
barry@glonet.co.nz
---
* Origin: Global NetWork ARGUS IP Mailer & FTP Fidonet New Zealand (3:774/605)

Hi! Barry,

In a message to All you wrote:

These are the most common messages I see
Error tossing to EASTSTAR: Message too long
Error tossing to STATS: Message too long

Can't say if I've seen it before, mate.

If there are no other side-effects _and_ you are game, try this option:

8.7.17 - NOERREP flag

FastEcho has the ability to report to the sysop several errors
occourred while it processes mail. By Default the report is
automatically generated and addressed to the SysOp in a NetMail message
but you can disable this feature with the NOERREP flag.

See page 144 in the doco. Have fun with it! ;-)

Cheers,
Paul.

--- Radius 4.010/21.01.2005(Final)
* Origin: I only started a BBS to save on the phone bill. (3:640/384)

*** Quoting Barry Blackford to All dated 03-05-06 ***

These are the most common messages I see

(bit del)

Error tossing to EASTSTAR: Message too long
Error tossing to STATS: Message too long

I don't see this message, I just see short posts.
The short posts don't even have tag lines or such.

Rich
I-Net turtil@frontiernet.net


... Frogs are smart ... they EAT what bugs them.
---
* Origin: Turtil's Pond BBS. Monroe NY 845-783-2106 (1:2624/50)

These are the most common messages I see

===================================================================
* Forwarded by Barry Blackford (3:774/605)
* Area : NETMAIL (Netmail)
* From : FastEcho, 3:774/605 (05 Mar 06 17:47)
* To : Barry Blackford
* Subj : TOSS error report ===================================================================
Error tossing to EASTSTAR: Message too long
Error tossing to STATS: Message too long ===================================================================

oh neat! i've never seen one of those... i don't currently carry EASTSTAR or STATS but i do have a few other areas that contain large messages... they must not be large enough to trigger the fault...

)\/(ark
member, FastEcho Beta Team


* Origin: (1:3634/12)

Hello Barry!

Sunday March 05 2006 22:20, you wrote to All:

These are the most common messages I see

====================================================================== ======= * Forwarded by Barry Blackford (3:774/605) * Area : NETMAIL (Netmail) * From : FastEcho, 3:774/605 (05 Mar 06 17:47) * To :
Barry Blackford * Subj : TOSS error report ====================================================================== ======= Error tossing to EASTSTAR: Message too long Error tossing to STATS: Message too long ====================================================================== =======

Same here :(

Sean

---
* Origin: There Can Only Be 1 (2:263/950)

Hi there, mark!

On 06 Mar 2006 13:30 you wrote Barry Blackford:

oh neat! i've never seen one of those... i don't currently carry
EASTSTAR or STATS but i do have a few other areas that contain large messages... they must not be large enough to trigger the fault...

Message must be larger than 64k in size.


--- mailto:burning.shadow#gmail.com
* Origin: ·∙■[MUSIC·STATION]■[583-9830]■[00:00-08:00]■∙· (2:5030/1997)

Hello there Sean!

06 Mar 06 at 19:53, Sean Rima writes to Barry Blackford:

These are the most common messages I see

======================================================================
======= * Forwarded by Barry Blackford (3:774/605) * Area : NETMAIL
(Netmail) * From : FastEcho, 3:774/605 (05 Mar 06 17:47) * To :
Barry Blackford * Subj : TOSS error report
======================================================================
======= Error tossing to EASTSTAR: Message too long Error tossing to
STATS: Message too long
======================================================================
=======

Same here :(

That's good, i'm not alone :-)

Best Rgds, Bazz
barry@glonet.co.nz
---
* Origin: Global NetWork ARGUS IP Mailer & FTP Fidonet New Zealand (3:774/605)

Hello there mark!

06 Mar 06 at 13:30, mark lewis writes to Barry Blackford:

===================================================================
Error tossing to EASTSTAR: Message too long
Error tossing to STATS: Message too long
===================================================================

oh neat! i've never seen one of those... i don't currently carry EASTSTAR or STATS but i do have a few other areas that contain large messages... they must not be large enough to trigger the fault...

They are the most common ones I see by far..

Best Rgds, Bazz
barry@glonet.co.nz
---
* Origin: Global NetWork ARGUS IP Mailer & FTP Fidonet New Zealand (3:774/605)

Hello there Alexey!

07 Mar 06 at 09:47, Alexey Fayans writes to mark lewis:

Message must be larger than 64k in size.

Must be...

Best Rgds, Bazz
barry@glonet.co.nz
---
* Origin: Global NetWork ARGUS IP Mailer & FTP Fidonet New Zealand (3:774/605)

Hi! Barry,

In a message to Alexey Fayans you wrote:

07 Mar 06 at 09:47, Alexey Fayans writes to mark lewis:

Message must be larger than 64k in size.

Must be...

It's definitely along those lines. (Pun intended. :)

I tried to push through a 2000+ line message (roughly 101.8k) from a point setup into FIDOTEST and FE hiccupped with the infamous error message. (BTW, FE
throws it/them into the BADMAIL defined area.)

Cheers,
Paul.

--- Radius 4.010/21.01.2005(Final)
* Origin: Dear Santa, all I want is the your list of *bad* girls. (3:640/384)

Hello there Paul!

07 Mar 06 at 21:19, Paul Quinn writes to Barry Blackford:

07 Mar 06 at 09:47, Alexey Fayans writes to mark lewis:

Message must be larger than 64k in size.

Must be...

It's definitely along those lines. (Pun intended. :)

I tried to push through a 2000+ line message (roughly 101.8k) from a point setup into FIDOTEST and FE hiccupped with the infamous error message. (BTW, FE throws it/them into the BADMAIL defined area.)

Was the message in badmail complete or truncated (I'll look there next time).

Best Rgds, Bazz
barry@glonet.co.nz
---
* Origin: Global NetWork ARGUS IP Mailer & FTP Fidonet New Zealand (3:774/605)

Hi! Barry,

On 08 Mar 06 06:32, you wrote to me:

07 Mar 06 at 09:47, Alexey Fayans writes to mark lewis:

Message must be larger than 64k in size.

Must be...

[ ...trim... ]

(BTW, FE throws it/them into the BADMAIL defined area.)

Was the message in badmail complete or truncated (I'll look there next time).

Fascinating stuff: it was chopped at exactly the 64k 'mark'.

Cheers,
Paul.

--- FPD v2.7.050306 GoldED+/DPMI32 1.1.5-30512
* Origin: Quinn's Post - Maryborough, Queensland, OZ (3:640/384.1)

mark lewis wrote to Barry Blackford <=-

oh neat! i've never seen one of those... i don't currently carry
EASTSTAR or STATS but i do have a few other areas that contain large messages... they must not be large enough to trigger the fault...

Keep in mind that the OS/2 version does up to 512k messages; well above
what any other fido software can handle, AFAIK.

Andrew

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

oh neat! i've never seen one of those... i don't currently carry
EASTSTAR or STATS but i do have a few other areas that contain large messages... they must not be large enough to trigger the fault...

Message must be larger than 64k in size.

i run the OS/2 version and have been set for 512k forever... my system tosses a
lot of messages larger than 64k on a daily basis and i've never seen this message... ever...

now, i'm sure i'd see it if i were to run my experimental message tool and create a message up to 2GIG in size ;)

)\/(ark
member, FastEcho Beta Team


* Origin: (1:3634/12)

===================================================================
Error tossing to EASTSTAR: Message too long
Error tossing to STATS: Message too long
===================================================================

oh neat! i've never seen one of those... i don't currently carry
EASTSTAR
or STATS but i do have a few other areas that contain large messages... they must not be large enough to trigger the fault...

They are the most common ones I see by far..

i have a direct connection with the eastern star... i'll see about hooking into
EASTSTAR and we'll see what happens...

)\/(ark
member, FastEcho Beta Team


* Origin: (1:3634/12)

oh neat! i've never seen one of those... i don't currently carry
EASTSTAR or STATS but i do have a few other areas that contain large messages... they must not be large enough to trigger the fault...

Keep in mind that the OS/2 version does up to 512k messages; well
above what any other fido software can handle, AFAIK.

well above most known fidonet software, yes... i'm aware of several packages that can handle large messages without problems... one tosser, in fact, spools to disk based swap files when it runs out of memory that it can process in...

and i hate to bring it up, yet again, but... if coders were to actually follow the specs, we'd not be having these "problems" with message sizes... fidonet specifications specifically allow for large messages via use of the phrasing "message body unbounded" ;)

)\/(ark
member, FastEcho Beta Team


* Origin: (1:3634/12)

Hello there mark!

07 Mar 06 at 19:53, mark lewis writes to Barry Blackford:

i have a direct connection with the eastern star... i'll see about hooking into EASTSTAR and we'll see what happens...

It may turn out to be okay on the OS/2 version (I'll not be surprised).

Best Rgds, Bazz
barry@glonet.co.nz
---
* Origin: Global NetWork ARGUS IP Mailer & FTP Fidonet New Zealand (3:774/605)

Hi there, mark!

On 07 Mar 2006 19:51 you wrote me:

Message must be larger than 64k in size.

i run the OS/2 version and have been set for 512k forever... my system tosses a lot of messages larger than 64k on a daily basis and i've
never seen this message... ever...

Because it is OS/2 version. We are talking about DOS version.


--- mailto:burning.shadow#gmail.com
* Origin: ·∙■[MUSIC·STATION]■[583-9830]■[00:00-08:00]■∙· (2:5030/1997)

Message must be larger than 64k in size.

i run the OS/2 version and have been set for 512k forever... my system tosses a lot of messages larger than 64k on a daily basis and i've
never seen this message... ever...

Because it is OS/2 version. We are talking about DOS version.

i didn't realize that there was only one flavor of FE under discussion...

)\/(ark
member, FastEcho Beta Team


* Origin: (1:3634/12)

Hello Alexey!

Tuesday March 07 2006 09:47, you wrote to mark lewis:

Hi there, mark!

On 06 Mar 2006 13:30 you wrote Barry Blackford:

oh neat! i've never seen one of those... i don't currently carry
EASTSTAR or STATS but i do have a few other areas that contain
large messages... they must not be large enough to trigger the
fault...

Message must be larger than 64k in size.

Yeah they seem to be :(

Sean

---
* Origin: There Can Only Be 1 (2:263/950)

Hello Barry!

Wednesday March 08 2006 06:32, you wrote to Paul Quinn:

Hello there Paul!

07 Mar 06 at 21:19, Paul Quinn writes to Barry Blackford:

07 Mar 06 at 09:47, Alexey Fayans writes to mark lewis:

Message must be larger than 64k in size.

Must be...

It's definitely along those lines. (Pun intended. :)

I tried to push through a 2000+ line message (roughly 101.8k)
from a point setup into FIDOTEST and FE hiccupped with the
infamous error message. (BTW, FE throws it/them into the BADMAIL
defined area.)

Was the message in badmail complete or truncated (I'll look there next time).

They are never complete :(
Sean

---
* Origin: There Can Only Be 1 (2:263/950)

Hi there, mark!

On 08 Mar 2006 10:48 you wrote me:

Because it is OS/2 version. We are talking about DOS version.

i didn't realize that there was only one flavor of FE under
discussion...

It was mentioned before, that non OS/2 versions have maximum message buffer size limited to 64k.


--- mailto:burning.shadow#gmail.com
* Origin: ·∙■[MUSIC·STATION]■[583-9830]■[00:00-08:00]■∙· (2:5030/1997)

Because it is OS/2 version. We are talking about DOS version.

i didn't realize that there was only one flavor of FE under
discussion...

It was mentioned before, that non OS/2 versions have maximum
message buffer size limited to 64k.

i can see this problem with the DOS version, yes... however, the DPMI and WINdows versions should be like the OS/2 version and not have this problem...

)\/(ark
member, FastEcho Beta Team


* Origin: (1:3634/12)

Hi there, mark!

On 09 Mar 2006 07:01 you wrote me:

It was mentioned before, that non OS/2 versions have maximum
message buffer size limited to 64k.

i can see this problem with the DOS version, yes... however, the DPMI
and WINdows versions should be like the OS/2 version and not have this problem...

DPMI version has the same limit as DOS version (I wonder why). And there is NO windows version.


--- mailto:burning.shadow#gmail.com
* Origin: ·∙■[MUSIC·STATION]■[583-9830]■[00:00-08:00]■∙· (2:5030/1997)

Re: TOSS error report
By: mark lewis to Andrew Leary on Tue Mar 07 2006 08:35 pm

well above most known fidonet software, yes... i'm aware of several packages to disk based swap files when it runs out of memory that it can process in..

Can you list a few... I Always thought that was a Y2K issue. I noticed you had a beta tester sig on your post.. Is FE still in production or was 1.46.1 the last.






--- SBBSecho 2.11-Win32
* Origin: (1:229/430)

It was mentioned before, that non OS/2 versions have maximum
message buffer size limited to 64k.

i can see this problem with the DOS version, yes... however, the
DPMI and WINdows versions should be like the OS/2 version and not
have this problem...

DPMI version has the same limit as DOS version (I wonder why).

so do i... it shouldn't have...

And there is NO windows version.

yeah, ok... whatever you say O:)

)\/(ark
member, FastEcho Beta Team


* Origin: (1:3634/12)

well above most known fidonet software, yes... i'm aware of several
packages to disk based swap files when it runs out of memory that it
can process in..

Can you list a few...

one that i'm thinging of was written specifically for a bbs package that i never ran... the coder was pretty well known back in the day but for the life of me i cannot remember his name or the name of the tosser he wrote... he was the first that i specifically recall detailing how he did it in NET_DEV when others were moaning about why they didn't do it... i think it started with a 'V' but it has been so long... _no_, it wasn't anything to do with that virtual
or virtual advanced malstrom...

I Always thought that was a Y2K issue.

no, Y2K stuffs were only concerned with erroneous dates...

I noticed you had a beta tester sig on your post..

yes, my reader is set with it from way way back...

Is FE still in production or was 1.46.1 the last.

at this time, 1.46.1 is the latest available public release for the DOS, OS/2 and DPMI flavors... i cannot speak of more due to nondisclosure... however, toby may be reading and might be willing to answer... then again, he might not 'cause folk would swamp him with questions...

)\/(ark
member, FastEcho Beta Team


* Origin: (1:3634/12)

mark lewis wrote to Andrew Leary <=-

well above most known fidonet software, yes... i'm aware of several packages that can handle large messages without problems... one tosser,
in fact, spools to disk based swap files when it runs out of memory
that it can process in...

Not a bad idea, although I'm sure that slows things down a bit.

and i hate to bring it up, yet again, but... if coders were to actually follow the specs, we'd not be having these "problems" with message sizes... fidonet specifications specifically allow for large messages
via use of the phrasing "message body unbounded" ;)

Yes, the specs have always said that, and almost nobody ever read that
part! ;-)

Andrew

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

well above most known fidonet software, yes... i'm aware of several packages that can handle large messages without problems... one tosser,
in fact, spools to disk based swap files when it runs out of memory
that it can process in...

Not a bad idea, although I'm sure that slows things down a bit.

speed is not always the best answer...

and i hate to bring it up, yet again, but... if coders were to actually follow the specs, we'd not be having these "problems" with message sizes... fidonet specifications specifically allow for large messages
via use of the phrasing "message body unbounded" ;)

Yes, the specs have always said that, and almost nobody ever read
that part! ;-)

oh, they read it but they didn't pay attention... instead they interpreted and/or assigned their own specs... that is and always has been the downfall of hobbiest coders :( sadly, i, too, am one of those... at least until i don't know how many years ago... since then, the code that i've written has endevored
to follow the actual specs as far as it could... the really troublesome problem
that i've faced, personally over the years, is how so many terminals and users could be handled by machines with only 64K of RAM and yet, today, it takes a gig or more of RAM to barely service just one miniscule user :(

)\/(ark
member, FastEcho Beta Team


* Origin: (1:3634/12)

one that i'm thinging of was written specifically for a bbs package that i never ran... the coder was pretty well known back in the day but for the lif of me i cannot remember his name or the name of the tosser he wrote... he wa

Hrmmm now you got me woundering.

no, Y2K stuffs were only concerned with erroneous dates...

Ahh, I see

yes, my reader is set with it from way way back...
at this time, 1.46.1 is the latest available public release for the DOS, OS/ and DPMI flavors... i cannot speak of more due to nondisclosure... however, toby may be reading and might be willing to answer... then again, he might n

So, much like most DOS stuff (TG, maximus, ext.) it's discontinued.

Quicken2k

one that i'm thinging of was written specifically for a bbs package
that i never ran... the coder was pretty well known back in the day
but for the life of me i cannot remember his name or the name of the
tosser he wrote...

Hrmmm now you got me woundering.

my memory of this is ~10 old and it is hard to remember things from that far back unless it is something that i spent a lot of time with... i can see the message(s) from him in my mind's eye but can't get close enough to actually read them for his name or the name of his package that was being talked about :(

yes, my reader is set with it from way way back...
at this time, 1.46.1 is the latest available public release for the
DOS, OS/2 and DPMI flavors... i cannot speak of more due to nondisclosure... however, toby may be reading and might be willing
to answer... then again, he might not...

So, much like most DOS stuff (TG, maximus, ext.) it's
discontinued.

i don't know about that... maximus is still being developed... it is hosted on sourceforge, nowadays... most of the development on it has been for linux based
systems... i've got it here on one of the linux boxes but have problems getting
it to compile... i have no idea if the dos or os/2 flavors will compile or not...

)\/(ark
member, FastEcho Beta Team


* Origin: (1:3634/12)

mark lewis wrote to Andrew Leary <=-

oh, they read it but they didn't pay attention... instead they
interpreted and/or assigned their own specs... that is and always has
been the downfall of hobbiest coders :( sadly, i, too, am one of
those... at least until i don't know how many years ago... since then,
the code that i've written has endevored to follow the actual specs as
far as it could... the really troublesome problem that i've faced, personally over the years, is how so many terminals and users could be handled by machines with only 64K of RAM and yet, today, it takes a gig
or more of RAM to barely service just one miniscule user :(

That was back when programmers took the time to conserve resources,
because at the time RAM and disk space were EXTREMELY expensive. Now
that prices have dropped drastically, people don't seem to notice that
they need 4 times the RAM to run the program, or 16 times the disk space
to store it on. My first computer (an original Tandy Color Computer)
came with a whole 32K of RAM, and used a cassette recorder to save/load programs. I remember how exiting it was when they finally came out with
a floppy disk drive for it.

Andrew

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

Andrew Leary wrote to Mark Lewis:

That was back when programmers took the time to conserve resources,
because at the time RAM and disk space were EXTREMELY expensive.

Wasn't it though! Funny how things have changed, and that wasn't
really that long ago.

My first computer (an original Tandy Color Computer) came with a
whole 32K of RAM, and used a cassette recorder to save/load programs.
I remember how exiting it was when they finally came out with a
floppy disk drive for it.

My first computer was given to me with a morse code program so I
could learn the code and get my amateur HF license, an 8086 with
512K, two 5 1/4 inch floppy drives and a 2400 baud modem. I did get
my HF license too although I never used it much, but I've been
modeming ever since.. :)

Ttyl :-),
Al

... * GROWING OLD is Mandatory: GROWING UP is Optional *

--- MBSE BBS v0.83.15 (GNU/Linux-i386)
* Origin: What's GNU? - The Fidonet DEBIAN GNU/Linux Echo (1:153/757)

Re: TOSS error report
By: mark lewis to Mark Da Silva on Sun Mar 12 2006 02:07 am

my memory of this is ~10 old and it is hard to remember things from that far :(

Ok, Then I guess we will never know. I knew about Max for nix refering to the NT/OS2/Dos ver of it.. (yes there was an NT ver) if memory is right.

Mark
--- SBBSecho 2.11-Win32
* Origin: (1:229/430)

Hello Alan.

12 Mar 06 13:47, you wrote to Andrew Leary:

Andrew Leary wrote to Mark Lewis:

That was back when programmers took the time to conserve
resources, because at the time RAM and disk space were EXTREMELY
expensive.

Wasn't it though! Funny how things have changed, and that wasn't
really that long ago.

My first computer (an original Tandy Color Computer) came with a
whole 32K of RAM, and used a cassette recorder to save/load
programs. I remember how exiting it was when they finally came out
with a floppy disk drive for it.

My first computer was given to me with a morse code program so I
could learn the code and get my amateur HF license, an 8086 with
512K, two 5 1/4 inch floppy drives and a 2400 baud modem. I did get
my HF license too although I never used it much, but I've been
modeming ever since.. :)

My first computer was a 8088 running at 4.77Mhz and had two 360K
floppy drives. One of the first upgrades was to install a 20M MFM HD to
put the BBS on and upgrade the 300b modem. It wasn't until a few computers later that I installed morse code software to help get my HAM ticket.

Ttyl :-),
Al

... * GROWING OLD is Mandatory: GROWING UP is Optional *

--- MBSE BBS v0.83.15 (GNU/Linux-i386)
* Origin: What's GNU? - The Fidonet DEBIAN GNU/Linux Echo (1:153/757)

Jeff

---
* Origin: The OUIJA Board (763)533-1058 V34+ (1:282/1031)

Jeff Smith wrote to Alan Ianson:

my HF license too although I never used it much, but I've been modeming ever since.. :)

My first computer was a 8088 running at 4.77Mhz and had two 360K floppy drives. One of the first upgrades was to install a 20M MFM HD to
put the BBS on and upgrade the 300b modem. It wasn't until a few computers later that I installed morse code software to help get my HAM ticket.

Sounds just like mine, maybe it wasn't even 4.77 Hmz.. ;)

Ttyl :-),
Al

... Itisdifficulttobeverycreativewithonlyfiftysevencharacters

--- MBSE BBS v0.83.16 (GNU/Linux-i386)
* Origin: What's GNU? - The Fidonet DEBIAN GNU/Linux Echo (1:153/757)