HDTenEightyP/NetNews huggingface dataset:
From: br@briancognos.com (Brian Rosen)
Newsgroups: comp.sys.next.misc
Subject: Re: NeXT vs Amiga
Date: 28 Sep 92 13:45:25 GMT
Organization: Mars Microsystems

In article <1992Sep22.071113.22483@RedBrick.COM>, jfr@glitter.RedBrick.COM writes:
|>                .....  Stuff about 12 bit vs 24 bit deleted
|> 
|>   I also don't see how 12-bit RGB could ever be close to any 24-bit color
|>   system (unless viewed on a crappy monitor)... But that doesn't negate
|>   the usefulness of 12-bit color.  In fact, I have advocated that NeXT
|>   take the steps necessary to support 6-bit color on 8-bit pallette
|>   systems (typically 486-type PCs and 8-bit color Macs).  I do not expect
|>   NeXT to go off and start supporting pallette color... it would change
|>   the consistent behavior of the Display Postscript model, for one thing,
|>   and it is yuccchyy to work with..  However, for things like business
|>   graphics (particularly in deployable "mission-critical custom app"
|>   workstations which are likely to be low-end PCs), 64 colors (6-bit 
|>   RGB) would be just fine.  Many of us used IBM's original 2-bit and
|>   4-bit color (4 and 16 colors, respectively) and these were useful
|>   albeit a bit dull for putting color into what were primarily text
|>   applications (fill-in-the-forms, etc.)  64 colors is pretty good
|>   (the Amiga, known as a premier color workstation, only supports
|>   6-bit color in its most usable and programmable mode and it is
|>   wonderful... dithering to get additional shades helps, of course).
|> 
|> Jon Rosen
|> jfr@redbrick.com
 -----------------------------------------------------------------

Y'know, I thought this too.  We just looked into this very question, and
were very surprised at the results.  We are working on a medical application.
The images are primarily gray scale with color overlay; not photorealistic
color.  We have been using a 'cube with a Dimension.  We use Sony monitors,
generally in good condition.  We have a great deal of experience at high
quality video (we have built gray scale systems that do 2560 x 2048 12 bit, and
color systems for professional pre-press applications).  We know what to look
for. 

Last week, we ran the application on a Color Turbo 'station.  Surprise; we could
not see a substanitive difference! I claim to be able to see a difference in the
gray scale, although several of my associates could not.  But not a difference 
that affected the ability to do the job.  Blow us away.

From this we conclude that either the Dimension has poor output video,
or the 'station, with all of the software, is really very good.  Also
note that the Turbo station was significantly faster at graphics than the
Dimension.  The 860 gets in the way more than it helps.
 

+- -----------------------------+-----------------------------------------+
| Brian Rosen                   |  Cognos*centi Corp.                     |
| br@cognos.visus.com           |  Tel (412) 488-3909  Fax (412) 488-7599 |
+-------------------------------+-----------------------------------------+
From: aha@kiptron.psyc.virginia.edu (Adult Human Abilities Project)
Newsgroups: comp.sys.next.misc
Subject: Re: Call for Volunteers
Date: 6 Oct 92 00:45:55 GMT
Organization: University of Virginia, Department of Psychology

In article <1992Sep30.222442.22322@murdoch.acc.Virginia.EDU> aha@squeeg.psyc.virginia.edu (Adult Human Abilities Project) writes:
>
>Dear NeXT Computer Users-
>
>It has been suggested that NeXT computer users are different than
>other people -- somehow special.  We are psychometricians studying
>adult cognitive abilities and we would like to see if we can measure
>some aspects of these differences.    
>
>We have developed a small NeXTSTEP program that allows us to present
>cognitive abilities tests remotely by using the NeXT computer.  This
>will be, to the best of our knowledge, the first wide-scale remote
>psychometric testing using the Internet.    
>
>

We have had good response to our call for volunteers.
Thank you to all who have replied.

We have two small announcements to make at this time.

1.  A good number of people within NeXT Computer, Inc. have signed
    up to participate in the experiment.  Due to concerns within
    NeXT about network security, the PsyLog program will be distributed
    within NeXT using a separate channel.  NeXT employees who wish to
    participate can obtain PsyLog from Lars Rabbe in IS.  Your data
    will be encrypted and sent directly to the Adult Human Abilities
    Project at the University of Virginia.

2.  We need some more volunteers.  We especially need people who
    consider themselves unlikely or unwilling to volunteer.  If
    you are such a person, please do help us out.  Sometimes the
    people who don't volunteer are different than the people who
    do.  We need _everyone_!  Do it today!

Steve Boker
 

-- 
The Adult Human Abilities Project      *-------------------------------*
Jefferson Psychometric Laboratory      | aha@kiptron.psyc.virginia.edu |
The University of Virginia             *-------------------------------*
Charlottesville, VA 22903                          
Lines: 22
Date: Mon, 28 Sep 92 15:32:30 MDT
From: yackd@alaska.et.byu.edu (Don Yacktman)
Newsgroups: comp.sys.next.misc
Distribution: world
Organization: Brigham Young University, Provo UT USA
Subject: Re: 3.0 and WriteNow


In article <1a7ievINN5ek@gap.caltech.edu>, madler@cco.caltech.edu (Mark Adler) writes:
>
>>WriteNow 2.1 works fine on my cube running 3.0. Bummer about the lack of a  
>>read-only version though. It's going to be hard to remember not to send  
>>out .wn files...
>
>I just noticed that there are two programs lurking in the WriteNow.app
>directory called wn-rtf and rtf-wn.  They might be part of a solution
>to generating documentation in rtf format.  I'd like them a lot better
>though if they were called "wn-rtfd" and "rtfd-wn", but oh well.


mv wn-rtf wn-rtfd
mv rtf-wn rtfd-wn

Oh, and :-) :-) :-) :-).

Sorry, it's been a long day...

Later,
-Don Yacktman
Newsgroups: comp.sys.next.misc
From: lacsap@plethora.media.mit.edu (Pascal Chesnais)
Subject: Re: ISDN-kit -- Does it exist?
Organization: MIT Media Laboratory
Date: Sun, 27 Sep 1992 15:49:08 GMT

In article <1992Sep25.043828.2237@cubism.portal.com>  
vlahos@cubism.portal.com (Harry Vlahos) writes:
> In article <1992Sep20.065426.601@relief.com> jjfeiler@relief.com (John  
Jay  
> Feiler) writes:
> > 
> > One big disappointment is that the POTS mode doesn't do any tone  
detection.   
> How is someone supposed to do a sophisticated answering machine
> program if you cannot at least duplicate the current functionality
> of a $50 answering machine ?  I

Another case of people believing the documentation.  POTS tone
detection does work.  Just a matter of the documentation not
keeping up with the software.  I tried it,  it works at home
with MessageCenter.  If you want to try it yourself,  add
the toneReceived:key method to MyCall.m..  do something
sophisticated like printing the tone detected to the console.

pasc
Newsgroups: comp.sys.next.misc
From: spagiola@frinext.stanford.edu (Stefano Pagiola)
Subject: Re: Did NeXT anticipate the CD ROM Drive shortage, maybe
Reply-To: spagiola@frinext.stanford.edu
Organization: DSO, Stanford University
Date: Tue, 6 Oct 92 00:06:41 GMT

todd@liveware.com writes
> After following the thread about NeXT delaying CD Drive shipment
> even further I can't help but think they knew there was going
> to be a problem on quantity.  My reasoning (maybe flawed) is
> due to the offer they made to User Groups to purchase a drive
> and CD for a low price of $452 or something. ...
> 
> Now I think the deal was a good one, but at the same time
> it also seems to be the attempt was to cover as much as possible
> with a 'limited' resource pool (ie drives).  It makes some
> sense to me to connect that with the current shortage and point
> a hard finger at NeXT about this issue.  They must have known
> also due to their 'just in time' policy about manufacturing.
> 

Another possible interpretation of the available evidence is that  
NeXT did not anticipate much response to their bundle deal, and so  
(1) did not arrange for massive deliveries, while (2) they offered  
the User Groups a special deal in an effort to ensure that there  
would be enough drives around for people to install their upgrades.  
Hence when the response to the bundle was very high they were caught  
with few drives in the pipeline.

--
-
Stefano Pagiola
Food Research Institute, Stanford University
spagiola@frinext.stanford.edu (NeXTMail encouraged)
Newsgroups: comp.sys.next.misc
From: gmk@pegasos.ccsr.uiuc.edu (Gottfried Mayer-Kress)
Subject: Re: Mathematica- can't get our passwords
Reply-To: gmk@pegasos.ccsr.uiuc.edu (Gottfried Mayer-Kress)
Organization: University of Illinois at Urbana
Date: Tue, 29 Sep 1992 05:15:12 GMT

In article <20724@plains.NoDak.edu> enders@bolshoi.cc.misu.NoDak.edu (Todd  
Enders) writes:
> Bill Smith writes
> So, I punched up the Password installer and followed the directions about
> where to call, what to have ready, etc.  Called the number.  This is the
> gist of the conversation:
> 
(...)
>     
>      Me:  Well, I don't have the registration form here at the office right
>           now...  Can't I get the password over the phone?
> 
well, next time read the instructions a little more careful before you start 
your flame:
NOBODY at WRI can give you the password WITHOUT the license number because 
it is calculated from it....
--
Gottfried Mayer-Kress
Center for Complex Systems Research, Department of Physics
3025 Beckman Institute, 405 N Mathews, Urbana, Il 61801
gmk@pegasos.ccsr.uiuc.edu (NeXT-Mail)
gmk@goshawk.lanl.gov, gmk@santafe.edu 
(217)-244-5877 (voice/fax modem),x8371(fax), x1994 (msg)
From: madler@cco.caltech.edu (Mark Adler)
Newsgroups: comp.sys.next.misc
Subject: Re: OD under 3.0
Date: 6 Oct 1992 19:24:08 GMT
Organization: California Institute of Technology, Pasadena
NNTP-Posting-Host: sandman.caltech.edu


Volker Herminghaus-Shirai believes the documentation and says:

>> The Disk->* Workspace menu is greyed out when the active file viewer window
>> does not display a directory on a removable media. Click on the appropriate
>> icon in the file viewer to display a (e.g. the root) directory of the
>> OD or Floppy disk. Then the Disk->Eject menu item should be selectable.

That's the way it's supposed to work.  However, there are two bug symptoms
that violate that in both directions.  First, depending on what my auto-
launched applications are (seriously!), Workspace leaves the Disk menu
grayed out when a removable media is selected, whether it is the OD, CD,
or floppy.  Removing Librarian from my dock fixed this.  (Other combinations
of removed apps worked also.)

The other problem is that when my dock is set up to prevent the above bug,
then if I have three removable media in there at the same time (OD, CD, and
floppy), and I have selected my root hard drive in Workspace, then the
Disk menu *is* lit, and cmd-e will eject one of the three media.  I do not
know how to predict which one--it does not seem to depend on the order in
which they were mounted.

I have sent this to bug_next.

Mark Adler
madler@cco.caltech.edu
From: bestor@jabberwocky.cs.wisc.edu (Gareth S. Bestor)
Newsgroups: comp.sys.next.misc
Subject: Re: NeXT Step on RS/6000?
Keywords: RS/6000, NextStep
Date: 6 Oct 92 22:33:37 GMT
Organization: U of Wisconsin Madison - Computer Sciences

In article <1992Oct6.092017.25312@newstand.syr.edu>  
rdlankes@rodan.acs.syr.edu (Virtual Dave) writes:
> 
> Hi,
> I once heard someone say you could run NeXTStep on an IBM RS/6000
> workstation because they both use the Mach kernal. I called
> all over the country talking to NeXT and IBM, and no one seems
> to have a definitive answer. Finally someone in Cambridge suggested
> I ask on the net. He mentioned Carnegie Mellon in particular. 
> 
> So here it is, has anyone ported NeXTStep to another platform?
> I know about NeXT working on the Intel 486 version. We have lots
> of RS/6000's and just want the OS. The other platform that would be
> nice is the SGI's. I would apprieciate any thoughts and would be
> glad to post a summary.
> 
NextStep was ported to the RS6K and was being used by internal IBM users
at one time. How do I know this? There is a (dead) internal IBM forum that
was devoted to NextStep on the RS6K.

For some reason IBM never went public with it and the project died. Don't
expect to ever get your hands on it.

- Gareth
From: mhn@black.ucop.edu (Mark H  Needleman)
Newsgroups: comp.sys.next.misc
Subject: softpc
Date: 6 Oct 1992 19:30:06 GMT
Organization: University of California, Berkeley
NNTP-Posting-Host: black.ucop.edu

Im considering getting a copy of softpc for a Nextstation turbo because  
one of our users wants to be able to run Microsoft word rather than  
Wordperfect. Can anyone tell me how well doing that under softpc will  
work? Will it work with Windows or will they have to run it in native DOS?
Also how well integrated is it with the Next. Can applications under  
softpc acces the next printers on the net and the fax modem out there the  
same way that next applications can?

Thanks for any info

Mark Needleman
University of California
Newsgroups: comp.sys.next.misc
From: ron@hugo.next.nd.edu (Ronald J. Hugo)
Subject: EPS-Animation Program
Organization: University of Notre Dame
Date: Mon, 28 Sep 1992 21:12:12 GMT

A few weeks back I read about a program at sonata.cc.purdue.edu that was  
capable of making an animated "movie" out of a series of EPS files.  I now  
need to do some animation of EPS files but have forgotten the name of the  
program.  I would be very grateful if anyone could tell me the name of  
this program and what directory it now resides in at sonata.  Thank-you in  
advance.


Ronald J. Hugo 
Newsgroups: comp.sys.next.misc
From: tlm@iastate.edu (Dr. T.L. Marchioro II)
Subject: A Modest Proposal
Keywords: Peace and Quiet : -)
Organization: Iowa State University, Ames IA
Date: Mon, 5 Oct 1992 01:51:52 GMT

At the risk of seeming ignorant (or, even worse, proving what 
everyone already suspects :-) I thought I might offer a "modest
proposal" about a subject which has been banging around  this group
for a couple of weeks now.  Specifically, starting with Louis Mamakos'
post about "gee, they unbundled WriteNow and then dropped the read-only
version. What should I make my documentation in?" we now have arguments
running about bundled versus unbundled software, the value of said
things versus those things added to 3.0, etc.  

Personally, I find the unbundling of a read-only right now rather 
strange, but would guess it has something to do with (1) keeping the
3.0 distribution smaller and (2) (from my cynical side) giving Appsoft
a boost.  

Sadly, there's little to do about it now (except complain, which we're all
quite good at :-) but perhaps I can offer a better solution to Louis' original
question --- i.e. a solution with pagenumbering, headers, etc. which runs on 
any NeXT --- which at least "calms the waters" on one aspect of this 
question.  Why not have everyone put their documentation in troff??  I
just checked and troff seems to be fully installed on both my 105 Mb internal
(I keep a skeleton system in case of "big disc failure") and my external
whcih has the extended OS.  I'm no big troff fan, would have difficulty
writing a letter in it to be honest, but often get documents in it from
collaborators and can obey the instructiosn necessary to view and/or
print it.  Associated figures/screen grabs could be in EPS files numbered
1, 2, 3, .....  which the reader could view as he/she read through the 
document.  I would even assume it's trivial to write a shell script 
that would drive the troff file, and it's figures, to a Postscript (or, 
better yet for those with the full OS, TeX) document?  

It seems to me this would be a great long term solution since troff comes
with all Unix systems --- I don't want to pick a fight, but some have
recently said the NeXT doesn't come with a bundled WP: actually, it comes with
several, nroff, troff, Edit, TeX, etc. It's just that it doesn't come with
WriteNow, which has a particularly convenient combination of features, anymore
--- and there are lots of troff --->> XXXX convertors.  Again, I'm no
troff expert, but is there any reason it couldn't serve as a standard for
documentation?  (I agree that TeX and InfoTeX are out because that would
just be another screw for those with small discs).  

Just my demented thoughts --- Tom


Newsgroups: comp.sys.next.misc
From: sears@tree.egr.uh.edu (Paul S. Sears)
Subject: Re: ROM boot command
Reply-To: sears@tree.egr.uh.edu
Organization: University of Houston
Distribution: usa
Date: Mon, 5 Oct 1992 16:47:03 GMT

In article <1992Oct3.180446.17361@ni.umd.edu> louie@sayshell.umd.edu (Louis A.  
Mamakos) writes:
=>In article <1992Sep29.163803.20641@dvorak.amd.com> rpomeroy@aunext3.amd.com  
writes:
=>>OK,
=>>
=>>Let's say I'm in the rom monitor ( i.e. the NeXT> prompt ).  I want to  
change  
=>>the boot parameter such that the device at SCSI address 4 is the default  
boot  
=>>device.  I have 4 devices on the bus.  
=>>
=>>	internal 100meg		SCSI 1
=>>	internal floppy		SCSI 7
=>
=>Actually, the floppy is not a SCSI device.  SCSI address 7 corresponds to
=>the NeXT host adaptor's SCSI address.
=>
=>>	cdrom drive		SCSI 2
=>>	external 400meg		SCSI 4  <--- boot from here!!!!
=>>
=>>Exactly what do I enter at the "boot command" prompt ?
=>
=>SCSI disk devices are numbered sequentially, ordered by SCSI address.
=>So in your case,
=>
=>sd0	- SCSI address 1 - internal 100M
=>sd1	- SCSI address 2 - CDROM
=>sd2	- SCSI address 4 - external 400M
=>
=>The boot command would be
=>
=>bsd(2,0,0)sdmach rootdev=sd2
=>
=>You need to pass the rootdev=sd2 specificiation to have the kernel use
=>the disk you booted from (sd2) rather than sd0 as the root file
=>system.
=>
=>For more information, see page 145 of the release 2.x "Network and
=>System Administration" manual.
=>
=>louie

Another way is the change the SCSI address of the 400M drive to 0.  The  
internal drive is set by NeXT to have an SCSI address as 1.  The device with  
the lowest SCSI address will end up being sd0.  The default boot device for  
the NeXT is sd0....

--
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."
Newsgroups: comp.sys.next.misc
From: wkwong@kalman.eng.ohio-state.edu (Waihon Andrew Kwong)
Subject: fsck question.
Organization: The Ohio State University Dept of Electrical Engineering
Date: Sun, 4 Oct 1992 19:20:41 GMT

I have just perform builddisk on a 349M Maxtor drive with NS2.0.
Then, I reboot the system with the Maxtor and used the command 'fsck'
to check the file system. It said there are some unreferenced inodes.
It gives me several questions like remove it, adjust it, and salvage
it. After I answered yes to all the questions. I let me go and tell me
to reboot without sync. So, I tried to power off the system. But I got
system panic. What is happening?

I used ROM monitor to switch it off. When I start it up again, using
the HD instead of OD, it perform file check very long. It tried to
modified whatever I allow fsck to modify before. If I perform another
fsck after the system is up, these things repeated.

Please help,
Andy

Newsgroups: comp.sys.next.misc
From: tim@rri.UUCP (Tim Buck)
Newsgroups: comp.sys.next.misc
Subject: Re: Help: recovering next-mail
Date: 30 Sep 92 12:33:10 GMT
Organization: Recognition Research Inc., Blacksburg, VA

In article <tlm.717458994@scl1.al.iastate.edu> tlm@iastate.edu (Dr. T.L. Marchioro II) writes:
>
>>Suppose someone sends me next-mail to my non-next machine.  Mail
>
>>Is there anyway to resend this to a Next machine so that it properly
>>arrives as next-mail?  Or, is there any way to uudecode the file
>
>save the mail message to a file, say foo.uu
>then uudecode foo.uu
>then do an ls -a which shows you all the files in the directory.
>There will be a file called something like .tar.611.file.attach
>
>move that file to something more convenient, say foo.tar.Z
>then
>
>uncompress foo.tar.Z
>tar -xvf foo.tar 
>
>and all of our stuff will be there.  HINT:  If this happens to you *a lot*

There's a much easier way than this.  Save the file as (for example) mail.uu.
Then open it in Edit.app, delete the header down to the "From:" line, save
it, and do this:

	cat mail.uu | /usr/lib/sendmail your_userid

Then launch Mail.app and you will soon have your NeXTmail.

If you receive your mail through an IBM mainframe, be sure to pipe it through
"tr \~ \^" before sendmail -- this takes care of the faulty EBCDIC --> ASCII
translation.

Timothy Buck   --   rri!tim@vtserf.cc.vt.edu OR timbuck@borg.lib.vt.edu
 Recognition Research, Inc. (703) 231-6500	++ NeXTmail accepted ++
------------------------------------------------------------------------
 Hate Blacksburg's weather? Wait an hour.  Hate the season? Wait a day.  
Newsgroups: comp.sys.next.misc
From: doberman!mike (Mike Panzitta)
Subject: Re: Edit.app in 3.0.  Goto Line # removed!
Reply-To: doberman!mike@esunix.sim.es.com
Organization: Doberman Systems
Date: Wed, 7 Oct 92 04:02:21 GMT

In article <PAUL.92Oct6104321@music.sie.arizona.edu>  
paul@music.sie.arizona.edu (Paul J. Sanchez) writes:
> Did I miss something, or did they actually remove the "jump to line #"
> feature (command-l) from Edit?  How could they do this???
> --paul

I think _I'll_ handle this one :-) (for those who don't remember, I
asked this same question just a few short weeks ago).

The answer is:  they didn't remove it.  Go into Edit.app's preferences,
set the radio button from User mode to Developer mode, and quit out of
Edit.app.  When you launch it again, all will work as it used to.  With
some nifty new additions.  Like while you are in gdb (or Gdb aka
SuperDebugger), type the command "view", and then notice the new Gdb...
menu item it the Edit.app menu...

Have fun,

-Mike

--
Mike Panzitta
Doberman Systems
doberman!mike@uunet.uu.net (NeXTMail)
From: mwatson@macgyver.next.com (Matt Watson)
Newsgroups: comp.sys.next.misc
Subject: Re: More indications of bugs in 3.0
Date: 1 Oct 92 16:53:48 GMT
Reply-To: Matt_Watson@NeXT.COM

In article <1992Sep29.120859.14990@ornl.gov> woo@ornl.gov (John W. Wooten)  
writes:
> I would report these to NeXT, but they apparently don't want to hear  
> about bugs unless you have a service contract.  If anyone has such a  
> beast and wants to forward bug reports, be my guest.

*Anyone* can send bug reports to bug_next@next.com.  You are not  
guaranteed a response, but the bug will be automatically logged in our bug  
database.  We try to verify and prioritize bug reports so that the problem  
may be resolved in the next release of the software.
--
Matt Watson
NeXT Computer, Inc.
Newsgroups: comp.sys.next.misc
From: dbbrown@eastrg2.cray.com (Dan Brown)
Subject: Re: Digital Librarian and nroff files.
Organization: Cray Research, Inc.
Distribution: usa
Date: 29 Sep 92 00:33:28 CDT

In article <1992Sep29.000833.1529@walter.cray.com> dbbrown@eastrg2.cray.com (Dan Brown) writes:
>I think someone has mentioned this before. I am having problems with
>Digital Librarian indexing my man pages (nroff format). Is there a
>work around for this? Is there something special I should do that
>I should be aware of?
>
>             Dan Brown (dbbrown@eastrg2.cray.com)

I just found the answer to my own question thanks to an alert I just got.
It turns out that if you don't have the "/usr/lib/indexing" directory.
You lose out on alot of support programs for DL. I didn't have this
directory because I did a 2.0 builddisk and then upgraded to 3.0. To fix
the problem I just copied the directory from my 2.1 disk to the same
directory on the 3.0 system.

I hope this helps everyone that experiences the same problem I just had.

Dan Brown (dbbrown@eastrg2.cray.com)
Newsgroups: comp.sys.next.misc