Hello Mike.

18 Oct 03 13:49, you wrote to me:

 BS>>> By boss is a old squish user, he told about the buffer problem,
 BS>>> if a line had more than 512 charecters, Squish didn't read the
 BS>>> rest.. And it was very problematic because he did have over 200
 BS>>> points, and many links too..

 MG>> The upper write limit is 128k in the 32 bit version. Isn't that a bit
 MG>> more than 512 characters?

 MT> Bo's referring to the line length limit for a EchoArea definition in
 MT> SQUISH.CFG, and it is indeed 512 characters.  Scott's answer to that was
 MT> supporting more than 1 line per area.

Well I distribute quite a lot of internet newsgroups via Squish, and some
of them have quite long tag names. The longest one I found was 39
characters and even with tab spaces, paths and links, the total line length
was 102 characters. Now I can see if you have a lengthy path line or a lot
of downlinks linked, but even the echo I have some thirty links hooked up
to tops out at around 328 characters, and that can be shortened quite a lot
by removing unnecessary spaces and reducing the link addresses as much as
possible to a 2D format.

Although it would be very nice to remove that limit if it can be done, I
don't really see it as a big problem. There are lots of ways to control the
line length, like removing the unnecessary spaces, placing the message
bases in a location that will shorten the path name, using CRC generated
file names instead of the echo tag names, and reducing link addresses to 2D
wherever possible.


--- GoldED/W32 3.0.1