What are Squish's area, messages and size limitations ?
From Squish.Doc, it appears that Squish has the following
limitations,
Maximum message size: 63k (16 bit), 256k (32 bit)
I've been wondering for long time about the message size as well. I
think around the beginning of each month Squish boots out messages (I think in the STATS echo) that are big and renames the .pkt files to *.LNG.
I've looked around before and never found any way to deal with these
long messages or the *.lng packet files. Is there a way to do this?
Maximum message size: 63k (16 bit), 256k (32 bit)
I've been wondering for long time about the message size as well. I
think around the beginning of each month Squish boots out messages (I think in the STATS echo) that are big and renames the .pkt files to
*.LNG.
I've looked around before and never found any way to deal with
these long messages or the *.lng packet files. Is there a way to
do this?
Maximum message size: 63k (16 bit), 256k (32 bit)
I've been wondering for long time about the message size as well. I
think around the beginning of each month Squish boots out messages
(I think in the STATS echo) that are big and renames the .pkt files
to *.LNG.
I've looked around before and never found any way to deal with
these long messages or the *.lng packet files. Is there a way to do
this?
Maximum message size: 63k (16 bit), 256k (32 bit)<snippage>
there is the packet split stuff... there's a fido technical document
my bitch about it is/was that it puts the onus on the feeder instead
of the feedee with the size problems...
i'm thinking that the pktsort package does the split stuff as well
as sorting messages in the pkts together by area name which also
helps tossing to go faster...
Maximum message size: 63k (16 bit), 256k (32 bit)
I've been wondering for long time about the message size as well. I
think around the beginning of each month Squish boots out messages (I think in the STATS echo) that are big and renames the .pkt files to
*.LNG.
OS/2 exe (which you may be running?) can be configured to toss as
large as OS/2 has resources to support. 256K is just the largest
Scott Dudley tested with and supported by the canned keyword
"Buffers Large". You have to define buffers manually to go
higher...and have the resources to support them available, of
course. If you want 1gb messages, Squish (SQ386P) can process
them...but maybe your other utils (BBS, online readers, offline
readers) or downlinks can't.
IMHO, messages too long for "Buffers Large" were messages I didn't
care to actually read anyway.<g>
I'm actually running it on a semi-modern Winders98Se machine with like only 256 (or maybe it's 512, can't remember) mego-rams... but I might
toy with the buffers statement and see if it does anything else.
The main point is tht I'd like Squish to at least pretend to handle
them and not create annoying renamed .LNG files I have to delete by
hand from time to time. I know I don't want to read those longy things
my own self.
Maximum message size: 63k (16 bit), 256k (32 bit)
I've been wondering for long time about the message size as
well. I think around the beginning of each month Squish
boots out messages (I think in the STATS echo) that are big
and renames the .pkt files to *.LNG.
I've looked around before and never found any way to deal
with these long messages or the *.lng packet files. Is
there a way to do this?
Hello Paul !
On 15-Mar'08 14:48, Paul Lentz wrote to ALL:
Maximum message size: 63k (16 bit), 256k (32 bit)
I've been wondering for long time about the message size as
well. I think around the beginning of each month Squish
boots out messages (I think in the STATS echo) that are big
and renames the .pkt files to *.LNG.
I only got questions, not answers :)
I think I got those limits from the documentation but have never
tested them. I've never had *.lng files, or a "stats" echo. I'm not
aware that Squish creates statistics in an echoarea. Can you paste
the output of that echo ?;
Are you using Squish/386 (32 bit) or Squish (16 bit) ?
There is a utility called SQREPORT.EXE that will work up some stats.
It's included in the package and is kinda nice. Here's a small piece
of what it spits out...
It then spits out traffic by specific echos live/dead, which I won't
paste in here cause it can take pages... But I use a thing called
carve to turn them into 3 or 4 messages.
I've been wondering for long time about the message size as well. I
think around the beginning of each month Squish boots out messages (I think in the STATS echo) that are big and renames the .pkt files to *.LNG.
I've looked around before and never found any way to deal with these
long messages or the *.lng packet files. Is there a way to do this?
I wrote a small utility program in VB4 to dig through the *.lng files and rebuild the packet, splitting the long messages into smaller ones (the size configurable). Did you say you run Win98? I can run it through the 16 bit compiler if you want to try it out.
Scott basically tried to support whatever the environment had to offer...which is why the 16-bit DOS, 32-bit DOS, OS/2, etc. versions
as released all had different limits. Don't know about the Win32
flavor, myself, as it was released solo, after the general release of
the others...sort of a "So long and thanks for all the fish", before
he left Fido.
Scott basically tried to support whatever the environment had to
offer...which is why the 16-bit DOS, 32-bit DOS, OS/2, etc.
versions as released all had different limits. Don't know about
the Win32 flavor, myself, as it was released solo, after the
general release of the others...sort of a "So long and thanks for
all the fish", before he left Fido.
There's a specific Win32 version of Squish?
| Sysop: | digital man |
|---|---|
| Location: | Riverside County, California |
| Users: | 1,041 |
| Nodes: | 15 (0 / 15) |
| Uptime: | 72:09:28 |
| Calls: | 236,110 |
| Files: | 60,370 |
| D/L today: |
1 files (264K bytes) |
| Messages: | 289,603 |