response 78 of 156:

Feb 4 19:00 UTC 1999

 Oh no, I think I've started yet another war.

response 80 of 156:

Feb 5 00:19 UTC 1999

Welcome to it.  I use vi.  It knows when to stop.

response 82 of 156:

Feb 5 02:36 UTC 1999

   i prefer pico.

  <void stands in the heretics' corner. ;>

response 84 of 156:

Feb 5 03:47 UTC 1999

TWice today I've had a great deal of trouble with bbs.  The first time, it was
running the whole screenful of information as one line at the bottom of my
screen, typing over each line as it started the next.  It took about 4 tries to
get it to give me a regular screen. Just now, the word wrap isn't working, and
I have to manually put in a carriage return t or else the buffer fills up with
text.  

And I'm working on the third attempt to get into the conferences, at least  one
attempt is suspended with control z in the background, while I tried twice more
to get it to let me see the responses.

And this screen full of typing looks like it is pretty badly mangeld as far
as formatting goes.

I reset my terminal type and screen size three times this afternoon, trying
to get PicoSpan to give me the right stuff.

response 86 of 156:

Feb 5 14:50 UTC 1999

I've spent more than 10 years using vi without having any sort of 
feeling I know everything about it.  It is not as powerful and 
configurable as emacs; it cannot play 'Towers of Hanoi', doesn't supply 
all of the functions of a Usenet News reader, and will not psychoanalyze 
you with the help of an 'Eliza' routine.  It also doesn't ask you twice 
(making you type out the word 'yes' for one of the responses) if you 
want to exit without saving changes, a function I find more appropriate 
for Windows 3.1 than anything that should happen on a Unix machine.  
It's just an editor.  But that's what I want when I just want to edit.

response 88 of 156:

Feb 5 18:27 UTC 1999

Re: cmcgee

None of those seem to be exactly bbs problems.  All of them seem weird.
Overprinting the bottom line of the screen could be either:
  - Grex has got your terminal settings messed up, so it thinks it
    should be sending you carriage returns, but not line feeds. This
    could happen if some program you ran previous crashed in an ugly
    way and left your terminal it a bad mode.  Easiest solution is to
    log off and on again.
  - Your terminal settings on your communications program are in a real
    odd state.  This is less likely, but in some cases it could happen
    just by have a strange control sequence set to your terminal.
    Easiest fix is probably to exit and restart your comm program.

The word wrap not working could be related.  Or not.  Some possibilities
are:
  - For some reason you aren't running "gate".  Picospan itself doesn't
    have automatic word wrap.  You always have to type returns.  If
    word wrap normally works for you, it is because there is a separate
    program called "gate" that is collecting your text, and will pass
    it to Picospan when you are done.  If you somehow fell back into
    the built-in Picospan text collection, you'd lose word wrap, and
    have buffer overflow problems.  I can't imagine why you wouldn't
    be running gate though.  It is configured into your account.
  - Maybe you were running gate, but when it tried to word wrap (by
    sending a carriage-return/newline) it wasn't working because either
    Grex or your terminal program wasn't dealing with carriage returns.
    This doesn't completely make sense to me, because you shouldn't see
    buffer overflows in that case.

So basically, I don't know what was going on, but I'm reasonably
confident that it won't happen the next time you log in.  Seems like
something got into a really bad state, but that usually doesn't carry
from login session to login session.

response 90 of 156:

Feb 5 20:55 UTC 1999

I use emacs because it's what I first learned and I can use it without
seeing the keyboard. I also use it as my mail-reading program and have
used it as my net.news reader, but don't now, since I only can read 
net.news through dejanews... It's a pain to learn, I have found, but
it's instinctive to me, now, and I don't like vi, or anything else.

response 92 of 156:

Feb 6 00:52 UTC 1999

Thanks Jan.  The first time I tried logging in again, nothing changed, but
the next time bbs worked fine.  *shrug* Maxwell posited "daemons" sorting
molecules.  I've always found that a workable theory.  It explains a lot
of what happens with physics and other techie subjects like computers.

(Now Rane is gonna tell me it isn't daemons, it's really quarks)

;-)

response 96 of 156:

Feb 7 22:58 UTC 1999

   We verified that the new sun-4/690 CPU card was working, and took
64M off it and gave it to Grex, hence our 192M of memory.  The 'new'
6/90 card wasn't booting in its normal (as opposed to diagnostic) mode,
so we took two of the little SBUS daughterboard cards off it, and lo
and behold it came up.  We couldn't boot anything off it, as it seems
to have last been used with IPI disks (IPI being another now dead type
of disk interface like IDE and SCSI), so we're going to have to either
boot from CD rom or clone Grex's boot disk for it.  Neither will be
hard to do, but we're out of time for today.

   All in all, I'm happy.  Grex has needed extra memory for a while
now, and todays addition will help out a lot.  The extra CPU card
that we installed, giving us 4 CPUs that run Grex will be an interesting
thing to watch.  There are some theories that with SunOS (as opposed
to the newer SOlaris) having four CPUs will degrade overall performance
because of contention between the four of them waiting to do things in
the kernel, but I'm not sure about that.  I have heard arguments on
both sides, but Grex doesn't seem to use a computer in any normal way
so our results will be different.  If we need to back out a CPU card
its easy enough to take it out again.

   Next step: more disk for Grex.

response 98 of 156:

Feb 7 23:31 UTC 1999

   Just the newest one.  To test the other one we'll need to do a 
CPU transplant.  I was kinda tempted to do that today, but decided
to be more focused.

response 100 of 156:

Feb 10 20:12 UTC 1999

Carol and I made some spiffy mailing labels with our new color printer. 
They have Grex's logo and return address on them.  I'll use them to mail
auction items to people. 

response 102 of 156:

Feb 22 02:53 UTC 1999

   I worked on getting more memory on Grex today, and didn't
succeed.  The expansion card we have has 64M in it, and I was
going to increase that to 128M for a total of 256M in Grex.
   Unforunately, there is a problem with some of the sockets
for the SIMM memory parts and Grex wouldn't boot with the
added memory.  Going into the diagnostics mode it nearly
instantly found a particular SIMM as being bad.  After trying
various things, I took out the new (2nd) 64M ram bank and
found that the card was still damaged.  There are two sockets
which appear to be be damaged.

   It definitely looks to me like we have some bad sockets,
possibly (probably?) due to problems with the previous owners
of the card.  However, not all is lost.  I've straightened out
the little finger of SIMM sockets before, and that may be all
that is needed.

   Right now we're back to 128M, which while not as good as
having 192M, is still fairly decent.