This message *should* not go out if I read things right this time.
I am still trying to figure out how to make an area read only, even
for myself. I found a keyword that was preventing what I thought was
the block to writing in this area. This message *should* not go out
if I read things right this time.
I am still trying to figure out how to make an area read only, even
for myself. I found a keyword that was preventing what I thought was
the block to writing in this area. This message *should* not go out
if I read things right this time.
How about a -X1:261/1466, for that area in your Squish config file? See page 80 in the doco file. Just a guess... I've never used Squish to toss or scan.
How about a -X1:261/1466, for that area in your Squish config
file? See page 80 in the doco file. Just a guess... I've never
used Squish to toss or scan.
Hmm.. I thought that Dale tried to do it in BlueWave and/or Maximus.
In tosser level it would block all traffic?
How about a -X1:261/1466, for that area in your Squish config
file? See page 80 in the doco file. Just a guess... I've never
used Squish to toss or scan.
Hmm.. I thought that Dale tried to do it in BlueWave and/or Maximus.
In tosser level it would block all traffic?
I don't know real life with Squish. I used FastEcho which could toss/scan Squish areas (you may know what that is like too). But, the Squish doc file says that that rule will make an echo "read only" for a node and that is what he wants. It may suit his situation. [sfx: shrug, fingers-crossed]
file says that that rule will make an echo "read only" for a node
and that is what he wants. It may suit his situation. [sfx:
shrug, fingers-crossed]
Ok. My bad. :)
I've never used squishmail the tosser, so...
again.file says that that rule will make an echo "read only" for a node
and that is what he wants. It may suit his situation. [sfx:
shrug, fingers-crossed]
Ok. My bad. :)
I've never used squishmail the tosser, so...
How will we know if it _does_ work? We won't see anything from him ever
Oh no!
OTOH, a hardware fault would have the same result. ;)
Hi! Dale,
On 02 Dec 18 02:44, you wrote to All:
I am still trying to figure out how to make an area read only, even
for myself. I found a keyword that was preventing what I thought was
the block to writing in this area. This message *should* not go out
if I read things right this time.
How about a -X1:261/1466, for that area in your Squish config file?
See page 80 in the doco file. Just a guess... I've never used Squish
to toss or scan.
How about a -X1:261/1466, for that area in your Squish config file?
See page 80 in the doco file. Just a guess... I've never used Squish
to toss or scan.
I am thinking he means "read only" from within Maximus itself.
Paul Quinn wrote to Robert Wolfe <=-
How about a -X1:261/1466, for that area in your Squish config file?
See page 80 in the doco file. Just a guess... I've never used Squish
to toss or scan.
I am thinking he means "read only" from within Maximus itself.
So was I. I figured he's the expert, and had exhausted his options.
I used Max a few times, as an unwashed user. Don't have no manual for
it. :)
| Sysop: | Winzlo |
|---|---|
| Location: | Minnesota, USA |
| Users: | 11 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 495943:58:41 |
| Calls: | 82 |
| Files: | 1,070 |
| D/L today: |
27 files (11,920K bytes) |
| Messages: | 287,032 |