|
|
| Author |
Message |
| 25 new of 306 responses total. |
janc
|
|
response 170 of 306:
| 
May 19 12:53 UTC 1998 |
If your .plan is owned by group "cfadmg" then that is because someone
(presumably you) editted it via Backtalk. Nobody is in group "cfadmg"
except the Backtalk program itself, and Backtalk only lets people edit
files if they have logged in as the owners. The same thing happens with
your conference participation files. It is all a bit odd, but has to be
done to be compatible with Picospan. You are welcome, of course, to
change to permissions/group on your .plan back to anything you like, but
I can't see why you'd want to do so. If you edit it again with
Backtalk, Backtalk will reset the permissions it needs (it has extremely
limited root access to enable it to get access to participation files
created by Picospan by putting them into the cfadmg group).
|
carson
|
|
response 171 of 306:
|
May 19 16:51 UTC 1998 |
(ah! I'd wondered about the cfadmg group. thanks for the explanation,
Jan!)
|
senna
|
|
response 172 of 306:
|
May 19 23:13 UTC 1998 |
Was grex rebooted this afternoon? I haven't seen anything in the MOTD
explaining why it was down.
|
other
|
|
response 173 of 306:
|
May 22 21:14 UTC 1998 |
Ok: !uptime
5:13pm up 2 days, 23:36, 57 users, load average: 81.76, 74.14, 71.93
What's up with that?!!!
|
scott
|
|
response 174 of 306:
|
May 23 00:48 UTC 1998 |
Marcus changed some settings that makes us more resistant to certain
denial-of-service attacks. What you saw there might have crashed us before.
|
valerie
|
|
response 175 of 306:
|
May 23 03:28 UTC 1998 |
This response has been erased.
|
keesan
|
|
response 176 of 306:
|
May 24 01:56 UTC 1998 |
Grex Board Meeting Wed May 22 - Jan, is this supposed to be May 27?
(See motd).
|
davel
|
|
response 177 of 306:
|
May 24 18:14 UTC 1998 |
(Well, the motd now says "May 27".)
|
janc
|
|
response 178 of 306:
|
May 25 01:26 UTC 1998 |
It is the 27. Thanks to whomever fixed it.
|
keesan
|
|
response 179 of 306:
|
May 26 14:41 UTC 1998 |
My screen keeps freezing up when I am typing something in Pine (yesterday)
or in a conference (just now). The phone line stays connected, but I have
to reboot, which takes 5-10 minutes (because Jim set me up with an expanded
memory manager, a virtual drive, a compressed hard disk, and probably a few
other clever tricks), then hang up the phone line with Procomm before I can
dial to get back on to grex. Is there some way to at least not have to
disconnect and reconnect the phone line?
This one cannot be related to line wrap, as Misti suggested,since I
am not using mail and there is automatic line wrap (I think). Am I doing
something wrong, or is the freeze-up just normal?
|
scott
|
|
response 180 of 306:
|
May 26 18:22 UTC 1998 |
Probably your setup, especially if recently changed. I've never had that
problem, although I never use Pine, either. Conference freezes never happen.
|
davel
|
|
response 181 of 306:
|
May 26 21:25 UTC 1998 |
What flow control are you using (that is, what flow control is Procomm using)?
<Dave tries to remember what was available in DOS Procomm>
|
keesan
|
|
response 182 of 306:
|
May 26 21:33 UTC 1998 |
Hardware flow control, Scott fixed that for me.
I just had it freeze up when trying to download a file, too.
Could it possibly have something to do with the shell room (shroom) program,
or the virtual disk, or the expanded memory card and software?
My other question was is there some way to get back to grex without
disconnecting and reconnecting.
|
davel
|
|
response 183 of 306:
|
May 27 12:33 UTC 1998 |
Actually, if your modem hasn't hung up, you *may* be able to just proceed.
Make sure Procomm is set to the appropriate settings. (I used to do this,
when I used DOS Procomm.)
|
keesan
|
|
response 184 of 306:
|
May 27 16:43 UTC 1998 |
I can't 'just proceed', as there is nothing on my screen resembling grex after
I reboot. What do I do next? What do you mean by 'appropriate settings'?
|
scott
|
|
response 185 of 306:
|
May 27 17:01 UTC 1998 |
'Proceed' by pressing the Enter key to see if you have a connection. If
entering a conference response, try using Control-L to redraw the screen.
|
rcurl
|
|
response 186 of 306:
|
May 27 17:15 UTC 1998 |
On my computer (MacOS) the comm program will think the serial modem port
is occupied, if I reboot without shutting down (i.e. resetting) the modem.
This is because the comm program does not overrule the serial interface
extension when it is doing its thing.
|
keesan
|
|
response 187 of 306:
|
May 27 18:35 UTC 1998 |
I tried Ctl-L a few times with no luck, probably also tried Enter. I will
try them both again next time this happens. I don't have a Mac and have no
idea how to reset the modem. Thanks, this is not serious, just annoying.
(I am still hoping a helper will explain to me how to decode binary files that
were sent to me as attachments, that is more urgent. It seems I have to know
whether unix decodes mime or uuencode so they know what to send me, as well
as how to decode the file after saving the attachment. HELP! I will soon
have a large binary file coming my way that I won't be able to read.)
|
rcurl
|
|
response 188 of 306:
|
May 27 20:13 UTC 1998 |
You can interrupt the connection by turning off the modem. Of course,
you don't keep the connection that way.
You donwnload the binary file and open it in the application for which
it was written. Saving the file in your directory decodes the MIME.
You have do uudecode, or whatever is required. Usually people just send
me documents in the original binary form (MS_WORD, e.g.) and once I
save them and download them, they open fine.
|
keesan
|
|
response 189 of 306:
|
May 27 20:37 UTC 1998 |
It worked to hit Ctl-L from Procomm (not from DOS).
Obviously this document was not sent to me in MIME, I will ask them to resend
it in MIME. I assume PINE automatically codes things in MIME.
How do I decode uuencode, in case I ever need to? Typing uudecode followed
by the filename did not work.
|
keesan
|
|
response 190 of 306:
|
May 27 21:00 UTC 1998 |
I downloaded the file which I think was sent to me MIMEd, and when I read it
in WP, instead of gibberish consisting of lower-level ASCII characters (7-bit)
this time I also got the upper level characters (8-bit). I suggested that
they resend the file in binary form without encoding it, but they have
probably gone home for the day by now.
|
keesan
|
|
response 191 of 306:
|
May 27 22:34 UTC 1998 |
I found that instead of rebooting I can just exit Procomm, disconnect (it did
not work to do Ctl-L the last two times it froze up, once while typing in
Pine, once in Pico in a conference response), and redial. This saves about
5 minutes, and I can read a book for a few minutes while redialing. One time
it froze up when I was doing right arrow to the end of a line (buffer problem)
a few minutes ago, in Pico editor editing a response of mine.
I received another MIME copy of a file, which they suggested might work better
since they were sending just one attachment instead of three at a time.
Time to download it and try again to read it.
|
keesan
|
|
response 192 of 306:
|
May 27 22:39 UTC 1998 |
The single attachment gave the same upper-ASCII file as the three attachments
did (when I saved them individually). MIME files give upper ASCII, uuencode
lower ASCII only. Saving to my home directory (V for View, S for Save) does
not seem to automatically decode files. Am I autmoatically encoding when I
send binary files with PINE as attachments? I asked them again to send an
uncoded binary file.
|
keesan
|
|
response 193 of 306:
|
May 27 23:58 UTC 1998 |
The freezeups generall seem to occur about one third of the way through a
line, this time on the second line of a paragraph of response to an item.
I have not had this problem in this response so far, despite not using a hard
return at the ends of lines. Any ideas what causes the problem? It is at
least three times today, maybe four.
|
ivynymph
|
|
response 194 of 306:
|
May 28 02:22 UTC 1998 |
Has anyone else had people apparently attempting to log in to their accounts?
(There were a few failures listed when I logged in today, and they don't make
sense as far as my time constraints are concerned...)
|
