HDTenEightyP/NetNews huggingface dataset:
From: rseymour@reed.edu (Robert Seymour)
Newsgroups: comp.sys.next.hardware
Subject: Re: Nitro (really the new keyboard)
Date: 5 Oct 92 15:58:24 GMT
Article-I.D.: reed.1992Oct5.155824.18047
Reply-To: rseymour@reed.edu
Organization: Reed College, Portland, OR

In article <1992Oct5.085406.4875@liveware.com> todd@liveware.com writes:
	[stuff deleted...]
> The keyboards are supposed to be really good based on the ergo
> feel and the person's ability to adjust the keyboard to different
> angles/heights.  In theory this is a good idea, but really the bloody
> problem in my experiences has been how you are able to rest
> your wrists.  This really has to do with the resulting extension
> of your wrists, as well as the amount of pressure that builds up
> during long times at the keyboard.  Simson does make a good point
> in that you can't expect any keyboard to help you out if you do
> 20 hour a day of typing.  The recommended portions of typing might
> be 1-2 hours and then some rest.  Do read the article from Dan Lavin
> and Simson's subsequent opinions/experiences.  I have seen the keyboard
> and again I say it sucks, as well as the mouse.  But then the current
> hardware human interface sucks too.  Is the new stuff better, only
> time can tell.
> 
> Todd
	Nothing (new keyboards, adjustability, layouts, etc.) can substitute  
for a work station with good ergonomics. When typing, you should not rest your  
wrists anywhere (that is ideally, wrist rests are alright, but not great...).  
The real problem with the keyboard (short of lack of inquiry into ergonomics)  
with the keyboard is that when your thumb hits the space bar, it pops out of  
the socket at the extreme end of the motion. This can wreck the cartilidge  
(sp?) and cause premature arthritis. The problem is that your hand has a  
natural angle of inclination which the keyboard does not match (your hand wants  
to be about 5 degrees off vertical, while the keyboard is 90 degrees). Having  
to splay out your wrists is why your thumb dislocates, and is a major cause of  
carpal tunnel syndrome (one variety of repetitive stress syndromes related to  
typing). Dvorak keyboards help, but the best thing you can do for yourself is  
to calculate what an ergonomic workstation should be for yourself, and  
build/adjust one (get a book on ergonomics or architecturual furniture design,  
it will tell you about keyboard height, monitor height, work surface level,  
angle of divergence from monitor, etc.). And on a last note, why hasn't NeXT  
made the mice fit your hand. I have yet to meet someone with a hand that fits  
the mouse, and I find it a real pain in the butt compared to my ADB and  
X-terminal mouses.
--
Robert Seymour					rseymour@reed.edu
Departments of Physics and Philosophy
Artificial Life Project				NeXTmail preferred
Reed Solar Energy Project (Sunrayce 1993)
Reed College, Portland OR
Newsgroups: comp.sys.next.hardware
From: gad@eclipse.its.rpi.edu (Garance A. Drosehn)
Subject: Re: Nitro  -- Really speed of NS 3.0
Date: Wed, 7 Oct 1992 03:40:24 GMT

jmd@cube.handheld.com (Jim De Arras) writes:
  [skipping along]
> I'm afraid you are not in touch with reality, here!  Even the current NeXT  
> apologists admit it's slower.  I have 32 meg of ram, and do not normally
> swap to disk.  And a 1.4 gb harddisk, and do not usually access data
> from the network.
> The same setup as before, only 30-50% slower in the user interface.

I have no reason to doubt what you are reporting, but I can't help but think  
that there must be something significantly different about your machine.  I  
would not characterize release 3.0 as 50% slower on any system I've seen it  
run on.  

I wish we could pin this performance issue down, and know what the  
difference is between people who are getting significant performance  
penalties and those who aren't seeing much of a change in performance.  Some  
even seem to think that the performance is slightly better (though certainly  
no one with an 8-meg greyscale station has said that...).  Maybe that's just  
wishful thinking on their part, but it's hard to imagine that a system which  
was (in fact) 50% slower would "seem" faster to anyone.

--
Garance Alistair Drosehn     =     gad@eclipse.its.rpi.edu
ITS Systems Programmer            (handles NeXT-type mail)
Rensselaer Polytechnic Institute;           Troy NY    USA
From: nash+@cs.cmu.edu (Richard Nash)
Newsgroups: comp.sys.next.hardware
Subject: Re: Nitro
Date: 5 Oct 92 14:04:58 GMT
Organization: School of Computer Science, Carnegie Mellon

>In article <dillon.0oq2@overload.Berkeley.CA.US> dillon@overload.Berkeley.CA.US  
>(Matthew Dillon) writes:
>> 
>>     The main problem with 3.0 is in paging from disk, a faster processor
>>     will not help at all in that area.
>> 
>>                                       -Matt
>> 
>> --
>> 
>>     Matthew Dillon            dillon@Overload.Berkeley.CA.US
>>     1005 Apollo Way           uunet.uu.net!overload!dillon
>>     Incline Village, NV. 89451        ham: KC6LVW (no mail drop)
>>     USA                       Sandel-Avery Engineering (702)831-8000
>
>If only it were really that simple!
>
>Jim

But it is true! Most of the perceived 'slowness' about next machines have to
do with disk or network access. Even if the processor was infinitely fast,
executing in zero time, the machine would look and feel almost as slow as
it does today.

Rich

-- 

Richard V. Nash
nash@vi.ri.cmu.edu
Newsgroups: comp.sys.next.hardware
From: bohlkejh@nextwork.rose-hulman.edu
Subject: Re: V.32bis modem on NeXT serial port slow...
Organization: Rose-Hulman Institute of Technology
Date: Tue, 29 Sep 1992 00:46:41 GMT


In article <1992Sep28.201813.2490@cronkite.ocis.temple.edu>  
ray@astro.ocis.temple.edu (Ray Lauff) writes:
> I have a 9600 speed modem connected to my NeXT which
> works fine at 9600 but will not compress and run at 57,600
> as the documentation states.  It seems to me that since I set
> the port to 9600 in the /etc/ttys file that it can't send
> data any faster.  As a result, when I transfer files I am
> getting typical character per second rates of around 650 cps.

I did not change my /etc/ttys file and I am getting > 50kbps with my ZyXel  
modem which runs at 38.4kbps to the serial port.


Jon
From: eboltz@jhunix.hcf.jhu.edu (Eric Scott Boltz)
Newsgroups: comp.sys.next.hardware
Subject: Re: 40MHz NeXTs?
Date: 2 Oct 92 16:13:21 GMT
Article-I.D.: jhunix.1992Oct2.161321.26063
Organization: HAC - Johns Hopkins University, Baltimore

I think that October is too soon.
To my knowledge there are still some problems with the 40MHz '040.
As soon as these problems are fixed I'd expect a new NeXT, but not
by October. Maybe early '93. NeXT will stick with the '040 so I don't 
doubt they'll make a machine based upon the 40MHz flavor.

Eric
Newsgroups: comp.sys.next.hardware
From: jmd@cube.handheld.com (Jim De Arras)
Subject: Re: Nitro
Organization: Hand Held Products, Inc.
Date: Tue, 6 Oct 1992 13:36:11 GMT

In article <BvnJ4A.pL.2@cs.cmu.edu> nash+@cs.cmu.edu (Richard Nash) writes:
> >In article <dillon.0oq2@overload.Berkeley.CA.US>  
dillon@overload.Berkeley.CA.US  
> >(Matthew Dillon) writes:
> >> 
> >>     The main problem with 3.0 is in paging from disk, a faster processor
> >>     will not help at all in that area.
> >> 
> >>                                       -Matt
> >> 
> >> --
> >> 
> >>     Matthew Dillon            dillon@Overload.Berkeley.CA.US
> >>     1005 Apollo Way           uunet.uu.net!overload!dillon
> >>     Incline Village, NV. 89451        ham: KC6LVW (no mail drop)
> >>     USA                       Sandel-Avery Engineering (702)831-8000
> >
> >If only it were really that simple!
> >
> >Jim
> 
> But it is true! Most of the perceived 'slowness' about next machines have to
> do with disk or network access. Even if the processor was infinitely fast,
> executing in zero time, the machine would look and feel almost as slow as
> it does today.
> 
> Rich
> 
> -- 
> 
> Richard V. Nash
> nash@vi.ri.cmu.edu

I'm afraid you are not in touch with reality, here!  Even the current NeXT  
apologists admit it's slower.  I have 32 meg of ram, and do not normally swap  
to disk.  And a 1.4 gb harddisk, and do not usually access data from the  
network.
The same setup as before, only 30-50% slower in the user interface.

Jim
From: alberto@parsec.mixcom.com (Manuel Alberto Ricart)
Newsgroups: comp.sys.next.hardware
Subject: Re: The new mouse
Date: 4 Oct 92 12:33:54 GMT
Article-I.D.: parsec.1992Oct4.123354.908
Distribution: usa
Organization: Is the act or process of organizing or of being organized.



I thought one could order a new keyboard (starting point)
You'll get the new keyboard and a new mouse, right?
So you may not be able to "cheeply" upgrade to color, but
2 out of 3 ain't that bad!


-- 
Manuel Alberto Ricart
alberto@parsec.mixcom.com <NeXTMail Welcome>
From: rseymour@reed.edu (Robert Seymour)
Newsgroups: comp.sys.next.hardware
Subject: Re: Nitro (NeXT disk and network access times)
Date: 5 Oct 92 18:20:11 GMT
Article-I.D.: reed.1992Oct5.182011.27289
Reply-To: rseymour@reed.edu
Organization: Reed College, Portland, OR

In article <BvnJ4A.pL.2@cs.cmu.edu> nash+@cs.cmu.edu (Richard Nash) writes:
> >In article <dillon.0oq2@overload.Berkeley.CA.US>  
dillon@overload.Berkeley.CA.US  
> >(Matthew Dillon) writes:
> >> 
> >>     The main problem with 3.0 is in paging from disk, a faster processor
> >>     will not help at all in that area.
> >> 
> >>                                       -Matt
> >> 
> >> --
> >> 
> >>     Matthew Dillon            dillon@Overload.Berkeley.CA.US
> >>     1005 Apollo Way           uunet.uu.net!overload!dillon
> >>     Incline Village, NV. 89451        ham: KC6LVW (no mail drop)
> >>     USA                       Sandel-Avery Engineering (702)831-8000
> >
> >If only it were really that simple!
>
> But it is true! Most of the perceived 'slowness' about next machines have to
> do with disk or network access. Even if the processor was infinitely fast,
> executing in zero time, the machine would look and feel almost as slow as
> it does today.
>
	This is one area in which NeXT is abhorantly behind the industry  
standards. Take a look at the sequential read rates from disk or over the  
network for the turbo machines, and you'll understand why NeXTs are slow. The  
turbo machines are actually slower that the 25MHz slabs (even with the ASIC  
chip)! I don't know what NeXT was thinking when they designed this, but I hope  
they fix it in the near future (i. e. on the RISC machines or possibly the  
40MHz version of the slab/cube). If you want to see the specifics check out  
Unix Review for Sept. 92, they review the turbo color and the disk/net times  
are amazing (and I don't mean pleasant...).
--
Robert Seymour				rseymour@reed.edu
Departments of Physics and Philosophy
Artificial Life Project			NeXTmail welcome
Reed Solar Energy Project (Sunrayce 1993)
Reed College Portland, OR
From: rab@cs.cmu.edu (Robert Brennan)
Newsgroups: comp.sys.next.hardware
Subject: Re: DSP chips are NOT dinosaurs
Date: 1 Oct 92 14:00:15 GMT
Article-I.D.: cs.BvG48I.A8M.2
Organization: School of Computer Science, Carnegie Mellon

In article <1aek39INN17s@agate.berkeley.edu> izumi@pinoko.berkeley.edu  
(Izumi Ohzawa) writes:
> In article <1aehh5INNa0r@stephen.cs.ubc.ca> sritchie@cs.ubc.ca (Stuart  
Ritchie) writes:
> >In article <1ae4klINNpph@agate.berkeley.edu> izumi@pinoko.berkeley.edu  
writes:
> >>My DSP gets interrupted 150,000 times per second with each sample
> >>being 12 or 16 bits, and 68040 doesn't even notice this unless
> >>something interesting happens in the input samples.
> >
> >Is the DSP fielding interrupts at this rate, or is this while polling?
> >(polling is cheating)
> 
> Interrupts, not polling.  Some CD-quality stereo recording apps run
> with the DSP interrupted 88,200 times per sec to get 44.1k x 2  
samples/sec.
> 
> You get get a lot more than that, although doing anything with the
> obtained samples gets tougher as the data rate increases.
> 
The DSP is the easiest way to get serious quantities of data into the  
machine.  I currently have an A/D running that simultaneously samples up  
to 16 channels at selectable rates.  The current configuration is 16  
channels with each channel at 16KHz which produces 256Ksamples per second.   
This is approximately equivalent to 6 channels of 44.1 data.  Building  
devices that accepted data at these rates would be much more difficult  
without the DSP.

Bob Brennan
Carnegie Mellon University &
Applied Speech Technologies
rab@cs.cmu.edu
Newsgroups: comp.sys.next.hardware
From: rpomeroy@aunext3.amd.com (Ron Pomeroy x(Coop))
Subject: Re: The new mouse
Reply-To: rpomeroy@aunext3.amd.com
Organization: Advanced Micro Devices, Inc.; Austin, Texas
Distribution: usa
Date: Thu, 1 Oct 92 00:19:19 GMT

In article <semThrO00WB44AoG1V@andrew.cmu.edu> gr1c+@andrew.cmu.edu (Greg  
Howard Rhodes) writes:
>>Sorry if this is old news, but I was playing around with a 3.0
>>machine here at school and I saw that one of the help files had a
>>picture of a mouse. It was weird. Kinda cool, though. Round like a DEC
>>mouse, but a bit smaller and with buttons that can not be explained
>>well. I think it looks pretty good--any other comments?
>>
>>Greg Rhodes                             gr1c@andrew.cmu.edu
>>-------------------------------------------------------------------------
>>"...I could not avoid seeing, clear before my eyes...the image of the girl,
>>beautiful and terrible as an army arrayed for battle." -- Umberto Eco, TNOTR.

Yea,
For a better look see the latest NeXTWORLD :-)

Now suffering color-envy, new keyboard-envy, and new mouse-envy :-(

--
Ronald Pomeroy		[Objective-Cruntime: [Smalltalk runtime]];
Advanced Micro Devices	[self dream-on];
CAM Applications Group
rpomeroy@aunext3.amd.com (NeXTmail preferred)
Newsgroups: comp.sys.next.hardware
From: sears@tree.egr.uh.edu (Paul S. Sears)
Subject: Re: How to use apple cd-rom drive?
Reply-To: sears@tree.egr.uh.edu
Organization: University of Houston
Date: Mon, 28 Sep 1992 16:39:44 GMT

In article <1992Sep26.001235.4726@dartvax.dartmouth.edu>  
fermat@fermat.dartmouth.edu (Michael Glenn) writes:
=>
=>I've been told by several people that it is possible to use an apple  
=>cd-rom drive to read the 3.0 disk.  I've tried, and get nowhere.  From  
=>within the "disk" utility, I get the following:
=>
=>disk name: SONY CD-ROM CDU-8002
=>WARNING: device sector size (2048)incompatable with DEV_BSIZE 1024
=>disk type: removable_rw_scsi
=>

This will happen if you are trying to read the 3.0 disk on a 2.xx system.  You  
cannot read the disk on an unmodified 2.xx system regardless of the cd-rom  
drive (hardware is irrelevant).  period.  Use the upgradeprep.app on the  
floppy to upgrade your kernel to handle 2K sectors...

=>Well, it isn't a rw device, so it already goofed up.  Do I need a disktab  
=>entry to handle the drive?  And if so, what should it be?
=>

It is as far as 2.xxx is concerned.  It doesn't know anything about the NeXT's  
4.3 bsd fast filesytem like binary 3.0 CD (whew, what a mouthfull!)...

=>Whenever I insert the cd, it says "External disk is unreadable, ignore or  
=>initialize?"
=>
=>I *hate* it when people say "it just works".  For me, it never does. :(
=>

"It just works" if you are reading the disk on a 3.0 system.

=>fermat@fermat.dartmouth.edu (NeXTmail welcome)

--
Paul S. Sears                *  sears@uh.edu (NeXT Mail OK)
The University of Houston    *  suggestions@tree.egr.uh.edu (NeXT
Engineering Computing Center *  comments, complaints, questions)
NeXT System Administration   *  DoD#1967 '83 NightHawk 650SC 
          >>> SSI Diving Certification #755020059 <<<
"Programming is like sex: One mistake and you support it a lifetime."
From: sritchie@cs.ubc.ca (Stuart Ritchie)
Newsgroups: comp.sys.next.hardware
Subject: Re: DSP chips are NOT dinosaurs
Date: 1 Oct 1992 02:48:21 -0700
Organization: Computer Science, University of B.C., Vancouver, B.C., Canada
Distribution: world
NNTP-Posting-Host: stephen.cs.ubc.ca

In article <1ae4klINNpph@agate.berkeley.edu> izumi@pinoko.berkeley.edu writes:
>My DSP gets interrupted 150,000 times per second with each sample
>being 12 or 16 bits, and 68040 doesn't even notice this unless
>something interesting happens in the input samples.

Is the DSP fielding interrupts at this rate, or is this while polling?
(polling is cheating)

>While I understand that not everybody needs the DSP, you should not
>be viewing it as something that is meant to perform a lot of
>computation.  It's an I/O peripheral interface, and a damn flexible
>one at that. 

It might be more flexible and easier to interface with if the "DSP"
was the same architecture as the host processor.  Even more so if
the host and DSP were in the same address space.

But of course, special purpose processors will be around
to kick butt on a general purpose processors for a particular class
of problems.  

What is the future of serial ports?  Most general purpose processors
can't keep up with the high interrupt rate.  Will a serial port
replacement eventually evolve... perhaps something like a serial
port version of SCSI?  What is the bandwidth of Apple Desktop Bus?

...Stuart
From: swede (Jim Mynatt)
Newsgroups: comp.sys.next.hardware
Subject: Re: Extending the laser printer cable?
Date: 6 Oct 92 19:23:48 GMT
Reply-To: jim_mynatt@next.com

In article <1992Oct2.121943.8893@bmw.mayo.edu> brunkhorst@mayo.edu (Geoff  
Brunkhorst) writes:
  > In article <5237@rosie.NeXT.COM> John_Graves@next.com (John Graves)  
writes:
  > > In article <1992Sep28.183056.20440@crash> coconut@crash.cts.com  
(Brian Dear)  
  > > writes:
  > > > NeXT tells me any lengthening of the cable would result in
  > > > loss of signal or degraded signal.  I say a properly shielded  
cable ...etc...

I am not recommending this, but:

From: william hunt <willie@iuvax.cs.indiana.edu>
Subject: Re:  lengthening a NeXT printer cable

I made a cable using seperate coaxs for each signal.  It
works fine, except that when the printer runs out of paper, putting in
more paper does not get the printer printing again.  Wagle found that
he had to turn the printer off using the soft window, and then it
starting printing again.

As far as signal skew goes, there should be no problem with data going
to the printer, since the CPU provides data and data clock.  However, the
return data may be suffering skew problems.  One solution, is to
adjust the length of the cable so the return data is skewed by exact
one clock cycle.  I will try this sometime and let you know how it
works.

Willie

From: william hunt <willie@iuvax.cs.indiana.edu>
Subject: Re:  lengthening a NeXT printer cable

I measured the delay with the oscilloscope and found that that I made
the cable a poor length for skew.  I added enough cable to the return
data line so that the cable is now equal to 80 feet in length.  This
adjusted the skew for the return data one full clock cycle.  Wagle and
I tested to see if the running the printer out of paper still caused a
problem.  We found that the problem is fixed.

So, the moral to this story is to make long cables multiples of 80
feet (for 81% c coax).  The cable can be slightly longer that 80 feet but
not by more than 15 feet.  The cable can not be shorter that 80 feet.
These cable length should work:
    0 to  15 feet  
   80 to  95
  160 to 175
  240 to 255
Of course the lengths will have to be adjusted for the velocity factor
if it is different than 81 percent.  Mabey, Next can make a special cable
and sell it!

Willie




--
-------------------------------------------------------
James L. Mynatt	Regional Systems Engineer	NeXT Computer, Inc.
USPS:		Echelon IV, Suite 400 
		9430 Research Blvd.
		Austin, Tx. 78759
Internet: Jim_Mynatt@NeXT.COM
From: osoelgaultier+@CMU.EDU (Stefan Monnier)
Newsgroups: comp.sys.next.hardware
Subject: Re: 40MHz NeXTs?
Date: 4 Oct 92 12:50:17 GMT
Article-I.D.: andrew.senpY9200VpG0r6WJ8
	<1992Oct3.182500.28069@cs.mcgill.ca>
Organization: Junior, Math/Computer Science, Carnegie Mellon, Pittsburgh, PA

Excerpts from netnews.comp.sys.next.hardware: 3-Oct-92 Re: 40MHz NeXTs?
Darcy BROCKBANK@cs.mcgil (909)

> Hey... what about the 68060 due in a few months... ???

> - db


Hahaha.....a FEW months......hahahaha !!

	Stefan

-----------------------------------------------------
-- On the average, people seem to be acting normal --
-----------------------------------------------------
From: ns111310@longs.LANCE.ColoState.Edu (The BLaCKSMiTHE)
Newsgroups: comp.sys.next.hardware
Subject: keyboard/mouse question
Date: 5 Oct 92 22:10:05 GMT
Organization: Colorado State U. Engineering College

Allright,

I have heard:
1) New NeXT's have ADB Keyboards/mice
2) **ONLY** new colors' have ADB
3) New keyboards and mice are **ONLY** available for ADB


What is true??  I am looking at buying a Turbo NS monochrome,
and I want the new keyboard and mouse, so what is the deal??

It would be good to get someone from NeXT who knows what
they are talking about (look at the whole "nitro" thread)

-nate

+------------------------------------------------------------------+
|   Nate Sammons                                                   |
|   PLEASE EMAIL at <ns111310@longs.LANCE.ColoState.Edu>           |
|                                                                  |
|  "I don't want to achieve immortality through my work.           |     
      
|   I want to achieve immortality through not dying." -Woody Allen |
|                                                                  |
|  "We are the children of concrete and steele....                 |
|   ..everything is possible, but nothing is real." -Living Colour |
+------------------------------------------------------------------+
Newsgroups: comp.sys.next.hardware
From: halpin@vsg1.dsg.dec.com (Stephen E. Halpin)
Subject: Re: 40MHz NeXTs?
Organization: Digital Equipment Corporation
Date: Sat, 3 Oct 1992 21:45:14 GMT

In article <1992Oct3.181744.6465@leland.Stanford.EDU> mcarling@NetForce.com (M Carling) writes:
  ...
>Motorola has announced that the 40MHz 040 will ship in Q4. That means  
>December at the earliest.
  ...

Since I havent browsed the trades, I thought this might
be the place to ask..  Has Motorola announced when theyll
ship the 88110 in volume?

>M Carling
>Director, Bay Area NeXT Group
>General Manager, NetForce Inc.

-Steve
-- 
~~~~~~~~~~~~~~~~~~~~
Stephen E. Halpin                    halpin@vsg1.dsg.dec.com

"You might just have to waste your life just to live."  - Soul Asylum
Newsgroups: comp.sys.next.hardware,comp.sys.next.programmer
From: deepthought!redbaron!aaronh@ms.uky.edu (Aaron David Herskowitz)
Subject: ISDN Extender and Caller ID on POTS?
Keywords: ISDN POTS PhoneKit MessageCenter
Reply-To: deepthought!redbaron!aaronh@ms.uky.edu
Organization: Case Western Reserve University NeXT Users Group, Cleveland, Ohio
Date: Sat, 3 Oct 1992 00:44:10 GMT

To all those ISDN Extender/PhoneKit/MessageCenter people:

Will an ISDN Extender working on a POTS line accept Caller IDs?  Does  
PhoneKit have any references to Caller ID?

Interested in ISDN/MessageCenter but trying to get a feel for the waters  
first,
Aaron
-- 
Aaron  Herskowitz   deepthought!redbaron!aaronh@ms.uky.edu    [NeXTmail]
Newsgroups: comp.sys.next.hardware
From: lemson@ux1.cso.uiuc.edu (David Lemson)
Subject: Re: V.32bis modem on NeXT serial port slow...
Organization: University of Illinois at Urbana
Date: Mon, 5 Oct 1992 18:20:51 GMT

bkr@drdhh.hanse.de (Bjoern Kriews) writes:

>You can'r go above 9600 with old machines and not above 38400
>with new ones.
You can go to 19.2 with few errors on an 030 cube running 2.1, in my
experience.  (I get 1.7 KB/sec with a V.32bis/V.42bis transferring
uncompressable data with FTP over SLIP)

-- 
David Lemson                                                (217) 244-1205
University of Illinois NeXT Campus Consultant / CCSO NeXT Lab System Admin
Internet : lemson@uiuc.edu                UUCP :...!uiucuxc!uiucux1!lemson 
NeXTMail accepted                                  BITNET : LEMSON@UIUCVMD