|
|
| Author |
Message |
valerie
|
|
System Problems
| 
Sep 23 21:25 UTC 1998 |
This item has been erased.
|
| 181 responses total. |
keesan
|
|
response 1 of 181:
|
Sep 24 13:48 UTC 1998 |
Why was I put directly from item 1 to item 14, then when I typed r n there
were no new items, when I typed browse new likewise? r 3 n got me here.
|
keesan
|
|
response 2 of 181:
|
Sep 24 13:51 UTC 1998 |
r n worked after I got to item 3.
|
omni
|
|
response 3 of 181:
|
Sep 24 14:42 UTC 1998 |
Because whenever you join a new conference you onlyget to read the first
and the last items. You should do a r all, to properly catch up. (I do this
and it only takes a few more minutes)
|
mcnally
|
|
response 4 of 181:
|
Sep 24 20:23 UTC 1998 |
It's a conscious decision meant to keep first-time conference users
from being overwhelmed when they join a conference with hundreds of
items. Personally, I disagree with it -- my thinking is that many
readers will drop in, see only two items (one of which is almost
always fluff), and decide "Hmmm.. not much going on here, guess I
won't bother to come back." But it's not a system problem, per se,
it's the way Grex has behaved for time immemorial..
|
keesan
|
|
response 5 of 181:
|
Sep 24 23:54 UTC 1998 |
I vaguely recall asking about this last agora. Hope it is helpful to new
users, except they would not have been able to find this item. Does someone
want to put the info in item number 1?
|
mcnally
|
|
response 6 of 181:
|
Sep 25 03:15 UTC 1998 |
Between Valerie's "about conferences" response (item 1, resp 2)
and the introductory info that shows up the first time you read
the new conference it's probably covered already. In any case
it's doubtful that many readers who really need the info would
find it 30-40 responses deep in item #1.
|
keesan
|
|
response 7 of 181:
|
Sep 29 19:03 UTC 1998 |
We have been calling grex at 761-3000, 9600 bps, with a 25 sec wait before
giving up, and could not get through on 4 tries. This has happened often,
sometimes we get through the second or third try. We also tried 14.4 bps at
the other number, same problem. As an experiment I called 761-3000 at 2400
bps and got through right away? Why? This has been going on for a few days
at least. We dial and get the usual static sound, but no connect.
|
scott
|
|
response 8 of 181:
|
Sep 29 20:09 UTC 1998 |
Line noise would be my guess. are you on a phone line or modem setup that
has changed recently?
|
rcurl
|
|
response 9 of 181:
|
Sep 30 03:37 UTC 1998 |
I suggest that new users be put into agora with all items read but
'new' from (say) the previous day. Then they immediately see a little
of quite a few, rather than too much of two.
|
hhsrat
|
|
response 10 of 181:
|
Sep 30 15:23 UTC 1998 |
When I try to telnet in during my lunch 35 minutes, I usually end up
somewhere around 45 in the telnet queue. (usually around 11:30 am)Is
this just a busy time to telnet in, or is there something I'm doing
wrong?
|
valerie
|
|
response 11 of 181:
|
Sep 30 16:12 UTC 1998 |
This response has been erased.
|
keesan
|
|
response 12 of 181:
|
Sep 30 19:50 UTC 1998 |
Re 7, we have not changed anything in our setup and are still unable to dial
in sometimes except at 2400. It worked at 9600 an hour ago but not now.
|
