|
|
| Author |
Message |
| 25 new of 156 responses total. |
steve
|
|
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.
|
janc
|
|
response 99 of 156:
|
Feb 8 03:27 UTC 1999 |
Doing a CPU transplant would be easy. But I think we'd also have to put
some memory on it, which is not so easy. I think we should concentrate on
the other one for now.
Anyway, for a vastly more detailed discussion of all this, see item:garage,
86
(That's item 86 in the garage conference for those of you not reading this
with Backtalk). That's probably also a better discussion place for techie
details.
|
aruba
|
|
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.
|
remmers
|
|
response 101 of 156:
|
Feb 17 01:07 UTC 1999 |
The Grex Board of Directors will meet Tuesday, Feb 23, 6:30pm
upstairs at Zingerman's Next Door, 422 Detroit Street, Ann Arbor.
The public is invited. See item 75 in coop (item:coop,75) for
the agenda.
|
steve
|
|
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.
|
remmers
|
|
response 103 of 156:
|
Feb 22 20:01 UTC 1999 |
REMINDER: Grex Board of Directors meeting Tuesday, Feb. 23, 6:30pm
upstairs at Zingerman's Next Door, 422 Detroit St., Ann Arbor.
The public is invited.
See Item 75 in the Coop conference (item:coop,75) for the agenda.
|
steve
|
|
response 104 of 156:
|
Feb 24 05:19 UTC 1999 |
Grex is now running with its memory card again, thanks to the
efforts of Charles (arthurp). He fixed the mangled simm sockets
and after some fighting with it, Grex was able to boot up with
this card. It now has 128M, making for a total of 256M of ram
here. Several of us have been here in the Pumpkin for the last
hour, waiting to see if any errors would develop. We've been here
for a little more than an hour now, and all is well.
Thanks Charles for your efforts.
|
aruba
|
|
response 105 of 156:
|
Feb 24 14:51 UTC 1999 |
Thanks Charles and STeve!
I'd like to announce that Kiwanis, through keesan and jdeigert, has donated
a photocopyier to Grex. It's in my office, on top of the file cabinet they
donated, and it seems to work fine.
|
steve
|
|
response 106 of 156:
|
Feb 24 17:12 UTC 1999 |
Wow. Thats cool.
|
remmers
|
|
response 107 of 156:
|
Feb 24 18:30 UTC 1999 |
Grex seems to be running along pretty zippily on 256M. Thanks to
arthurp and steve for their efforts!
Thanks also to keesan and jdeigert for the photocopier.
|
keesan
|
|
response 108 of 156:
|
Feb 24 19:47 UTC 1999 |
See the coop item on tax deductability of dues, this copier will allow grex
to keep better tax records as a nonprofit.
|
steve
|
|
response 109 of 156:
|
Feb 24 21:40 UTC 1999 |
The interesting part about that memoey is that we really are using it.
Watching the 'vmstat' program is fun; you can see when lots of sendmails
fire off, with the pool of available memory going down. We're doing a lot
less swapping right now, which is a good thing. I'm still on the lookout
for more ram, and once we have the alternate Sun-4/670 populated with 64M
ram, I'd like to get more memory here. ...I shall continue to beg for
ram. ;-)
|
janc
|
|
response 110 of 156:
|
Feb 26 18:21 UTC 1999 |
A test version of Backtalk 0.9.6 is now available on Grex. To try it go to
http://www.cyberspace.org/cgi-bin/pw/bt.new/pistachio/confhome?conf=backt
alk
IMPORTANT NOTE:
This has been deliberately broken so that you can only join the
"backtalk" and "backtalk2" conferences. It will claim all other
conferences do not exist if you try to join them. It does some
different things with item files, and we want to make sure it isn't
going to drive Picospan crazy before we allow it into any of the
regular conferences.
If you want to go back to reading the other conferences, change the
"bt.new" in the URL back to "bt".
WHAT'S NEW:
- HTML responses. You now have the option of using HTML tags in
your response and item text. This means pictures, tables, links,
font changes, and so forth can be done in responses.
Sanity checking is done on the HTML to make sure you don't use
any tags that would mess up the page, and to close any tags
you left open.
Backtalk automatically generates a (much less pretty) plaintext
version of all HTML responses so that Picospan users don't have
to look at HTML tags.
- Preview button. Lets you see what your response would look like if
posted, both to other Backtalk users and to Picospan users. Very
useful for composing HTML responses.
- Forget works better. Fixed some bugs here.
- A few more button color options.
- Updates to help files.
- More aggressive item indexing. Item indexing makes Backtalk faster,
but it used to be so timid about it that it wasn't being done in
most conferences.
- Several minor bug fixes.
And various other features not relevant to Grex: support for password
protected conferences, lastlog maintainance, better user list functions
(turned off here because we have too many users), and better Yapp
compatibility.
|
other
|
|
response 111 of 156:
|
Feb 26 18:59 UTC 1999 |
wow. sounds like te html parsing required a lot of work and will make
conferencing a whole new range of fun stuff! thanks, jan!!
|
other
|
|
response 112 of 156:
|
Feb 26 19:29 UTC 1999 |
just tried it, but communicator 4.05 crashed twice at the same spot (scrolling
through responses). running a powerbook 190cs (68lc040) with os 8.0.
|
hhsrat
|
|
response 113 of 156:
|
Feb 27 03:38 UTC 1999 |
YAPP compatibility is a good thing? I used YAPP on M-Nut for a few
days, and it drove me crazy. (this was back in Nov.) Backtalk seemed
like a much more sophisticated interface.
Maybe things have changed
|
senna
|
|
response 114 of 156:
|
Feb 27 10:16 UTC 1999 |
Not that fast. You might want to keep tabs on what people do with html,
becuase it's possible for that to be misused.
|
jep
|
|
response 115 of 156:
|
Feb 27 21:55 UTC 1999 |
The current YAPP interface for the WWW is buggy to the point where I
can't stand using it. I've used Backtalk about every day for a year
and a half, and I'm very pleased with it. I hope M-Net will adopt
Backtalk if it's compatible with the YAPP text system.
|
dang
|
|
response 116 of 156:
|
Feb 28 03:43 UTC 1999 |
YAPP compatability refers to Backtalk working with YAPP the way it does
with Picospan. Backtalk itself doesn't seem any different, either way.
|
steve
|
|
response 117 of 156:
|
Feb 28 04:05 UTC 1999 |
Grex has been running for 96 hours now with the new ram and
repaired memory card, so I think that can be called a success.
If either the card or individual SIMMs were to have failed we'd
have experienced it. Thanks to Charles for some nimble repair
work on that card!
|
russ
|
|
response 118 of 156:
|
Feb 28 04:26 UTC 1999 |
Uh-oh. I'm not sure I like what this represents, Jan. The strength
of Grex (and M-Net, once) was what the users brought to it. When the
conferences become more of an impromptu web page where most of the
content is links, Grex will become a poor cousin of SlashDot. The
inaccessibility of the graphical content to many computers is another
negative to this change. Up to now, anybody with a dumb terminal and
a modem could be a full participant. When large parts of the conferences'
content is only accessible using much more advanced (and expensive)
hardware, what becomes of that part of the user base?
I fear this will be like the file read feature in party: most often
used to dazzle rather than illuminate.
|
mcnally
|
|
response 119 of 156:
|
Feb 28 05:58 UTC 1999 |
Put me down in the Luddite column, too.. I think the addition of
HTML extensions is unlikely to add much (beyond annoyance) to responses.
I hope there's a way to turn it off and still enjoy the other benefits
of the new Backtalk version..
|
steve
|
|
response 120 of 156:
|
Feb 28 06:48 UTC 1999 |
Russ, Mike: the technology is changing, and *fast*. All three of
us are old-timers; what we know and have used is not what the masses
use. The web is the net. Not a component of it, but the backbone as
seen by an ever increasing number of people. Probably we should move
this discussion to another item, however.
|
janc
|
|
response 121 of 156:
|
Feb 28 19:02 UTC 1999 |
I'd have no huge objection to turning it off (there isn't a way right
now, but it isn't hard to add - eventually I plan to make it a setting
that fairwitnesses can fiddle with on a per-conference basis).
Frankly, I don't believe it will be a problem. Simple HTML gets
translated to plaintext just fine. Doing things like images and tables
well is enough extra work that few people will bother, and you won't
mind missing responses where people do them badly.
And I do agree with STeve - Grex has to keep exploring current
technology. We don't have to try everything that comes along, but we
have to be adverturous in trying things.
|
keesan
|
|
response 122 of 156:
|
Feb 28 23:03 UTC 1999 |
I would appreciate if people would not put anything in their responses that
cannot be easily accessed by dial-in users. If there is a link, make sure
that we can read the URL if we want to go look at it with lynx.
|