HDTenEightyP/NetNews huggingface dataset:
From: aozer@next.com (Ali Ozer)
Newsgroups: comp.sys.next.misc,comp.sys.next.programmer
Subject: Re: looking at the bits in video frames (3.0 NeXT Dimension)
Date: 1 Sep 92 15:22:00 GMT
Followup-To: comp.sys.next.misc
Organization: Next Computer, Inc.

In article <1992Sep1.033025.7164@news.media.mit.edu> mike@media-lab.mit.edu writes:
>The problem is this: when you grab the frame, you get an
>image with representation NXCachedImageRep, which presumably
>somewhere has a pointer to the raw image in NeXTDimension memory.
>There are no methods to directly read this data, although you
>can draw it out to another view.  I tried compositing the
>NXCachedImageRep image into a newly allocated image with
>an NXBitmapImageRep (a TIFF), but the latter was converted
>to an NXCachedImageRep! ...
>What I would like to do is simply get my hands on the pixel array
>that underlies the NXCachedImageRep of a grabbed frame,
>without copying and converting the whole frame.

First or all, there's no way to get a pointer to the bits in the
frame buffer.

However, under 3.0 the process of reading images back from the
window server is efficient enough such that if you use NXBitmapImageRep's
initData:fromRect: method, you might get back what is essentially
a vm_copy() of the window's backing store. To process the data you need
to pay attention to the bitsPerPixel and bytesPerRow parameters of the
NXBitmapImageRep.

Clients of NXReadBitmap() and 2.0 apps do not get back unpacked data;
so for them the data might have to be packed after it's brought over
from the window server. However, even in that case the process of reading
images back is faster as the data is brought back out of line.

Now, on the NeXTdimension, the out of line data transfer always requires
a copy over the bus, so the gain isn't as great, and it's not as if
you are simply getting a pointer to the image data.

Going back to your question... One easy way to get a NXBitmapImageRep 
from an NXImage is to lockFocus on the NXImage, and create a bitmap 
image rep with initData:fromRect:. This is not the ideal in all cases, 
but when the NXImage is basically a cached image, it works fine. And if
the situation is right, the initData:fromRect: will be very fast.

Ali, Ali_Ozer@NeXT.com
Newsgroups: comp.sys.next.misc
From: jmd@cube.handheld.com
Subject: Re: NewsBase 2.1
Reply-To: jmd@cube.handheld.com
Organization: Hand Held Products, Inc.
Date: Sat, 12 Sep 1992 15:13:55 GMT

> NewsBase 2.1 is one cool news reader! It works with the nntp server at my site! (NewsGrazer doesn't) Thanks to the authors for a job well done!
> 
> I will be eternally grateful if some kind soul can spare a few moments to translate all the Japanese documentation to English.
> 
> Joe
> ---
> Joseph Chin				Prodigy Technologies Corp.
> jchin@prodigy.bc.ca (NeXTmail welcome)	Vancouver, British Columbia
> phone 16046874636 / fax 16046871671	Canada  V6Z 2H6
>  **** "Heaven won't take me and Hell's afraid I'll take over!" ****
> 

Clever, but SLOW!  I don't remember the call, but there is an NNTP call that's used to speed things up, and is needed by NewGrazer.  NewsBase needs to use it, at least if it's there.

Jim

Newsgroups: comp.sys.next.misc
From: srmaster@hocm.nhlbi.nih.gov (Stephen R. Master)
Subject: Re: more on why NeXT has not earned much credibility
Organization: National Institutes of Health
Date: Tue, 15 Sep 1992 22:35:11 GMT

In article <MS-C.716580141.377401575.mrc@Tomobiki-Cho.CAC.Washington.EDU>  
mrc@Tomobiki-Cho.CAC.Washington.EDU (Mark Crispin) writes:
> Well, I called up NeXT's 3.0 order management group, and learned some
> interesting facts:
> 
> 1) Officially, 3.0 is NOT YET SHIPPING.  They said `it is possible that  
some
>    people got early copies, but we are not shipping until later this  
week.'  In
>    other words, certain high-profile customers got their copies special  
to give
>    the appearance of 3.0 shipping.
> 

I can't speak for anyone else, but I personally got my 3.0 (which was
ordered as part of the drive bundle through a local dealer) last week.

Stephen
=============
srmaster@hocm.nhlbi.nih.gov (NeXTmail welcome)
Newsgroups: comp.sys.next.misc,comp.sys.ibm.ps.programmer,misc.jobs.misc,misc.jobs.offered
From: smithw@hamblin.math.byu.edu (Dr. William V. Smith)
Subject: JOB wanted: Unix, Netware, PC exp.
Organization: Brigham Young University-Math. Dept
Date: 13 Sep 92 20:40:31

I'm posting this for a friend without net access.  You may either
reply to my address, or call him at (801) 226-1784

Glen R. Ashby -  Electrical Engineer, Systems programer
(Unix, IBM system/36, Novell Netware Engineer)

Education:

	1. Novell Certified Netware Engineer (1992)
	2. B.S. Electrical and Computer Engineering (BYU - 1990)
	3. Education in
		a. Microprossor operation
		b. Input/Output devices		
		c. Computer Arch.
		d. Digital error-correcting codes		
		e. Digital mechanics and design

Experience:

	1. American Laser Corp. - Production Engineer		
		a. Production scheduling for ion laser tubes		
		b. Inventory control
		c. Maintenance of processing station equipment		
		d. Design of upgrades to existing systems	
	2. GHA MEDCARE  - System Manager
		a. IBM System/36 support		
		b. Programming in RPG II
		c. Customer service for sites across the country
Related skills:

	1.  Novell Certified Netware Engineer (CNE)	
	2.  Qualified on Novell Netware 2.15, 2.2, and 3.11	
	3.  RPG II, C  languages
	4.  IBM System 36	
	5.  VMS, UNIX, X-windows

Further info available on request, call (801) 226 - 1784  or write:
       	
	Glen R. Ashby	1058 N. 1000 E.
	Orem, UT 84057
	email: bill@mathnx.math.byu.edu				
--
EMail:  smithw@hamblin.math.byu.edu  or  uunet!hamblin.math.byu.edu!smithw
SMail:          Math Dept. -- 314 TMCB; BYU; Provo, UT 84602 (USA)
NeXTmail:                   bill@mathnx.math.byu.edu
Phone:            +1 801 378 2061         FAX:  +1 801 378 2800
From: hardy@golem.ps.uci.edu (Meinhard E. Mayer (Hardy))
Subject: Re: Version of TeX on NS3.0?
In-reply-to: tlm@iastate.edu's message of Mon, 7 Sep 1992 05:03:31 GMT
Newsgroups: comp.sys.next.misc
Organization: Department of Physics, UC Irvine, CA 92717-4575, USA
Distribution: na
	<tlm.715741601@scl1.al.iastate.edu>
	<CALLSEN.92Sep6214626@ganges.cs.uiuc.edu>
	<tlm.715842211@scl1.al.iastate.edu>
Date: 7 Sep 92 06:05:00 GMT

In the same vein --- Tom Rokicki $= \sqrt{i}$ software 8-). 
My TeX on my HP/9000/345 is TeX 3.14t3 -- I am away from CA (in MA)
and don't even know if I got NS 3.0 yet. 
--
Hardy 
-----
Meinhard E. Mayer,  Department of Physics, UC Irvine 
e-mail: hardy@golem.ps.uci.edu (preferred) or MMAYER@UCI.BITNET

Newsgroups: comp.sys.next.misc
From: Joseph R. Grace <jgrace@TetraSoft.com>
Subject: A Posting Policy for Comp.Sys.NeXT.Announce
Keywords: $ KIIS KISS CSNA comp.sys.next.announce
Organization: TetraSoft International
Date: Fri, 4 Sep 1992 22:32:22 GMT

Hi,

this pricing issue has become gross and unwieldy.  May I suggest 2 principles  
(in the spirit of Usenet postings) to resolve the confusion?

1.  KISS:  Keep it simple silly!
2.  KIIS:  Keep it informative silly!

By principle 1, let's make comp.sys.next.announce a self-contained source of  
information.  If people *want* other or differently organized information, feel  
free.  But let's make comp.sys.next.announce serve the purpose for which it is  
meant --- announcing NeXT products and services in a useful and independent  
medium.  Let's not force its users to do go through silly, bureacratic or  
arbitrary loops just to get useful information.

By principle 2, let's keep the information level high (and complete) and  
include the pricing.  Pricing information is part of the product and sometimes  
even defines and distinguishes a product.  New markets have even been created  
via pricing alone --- the pricing defined the product and the market.  CSNA  
users deserve complete, informative announcements.  Pricing makes the messages  
informative, so don't raise the noise to information content by XXX'ing prices.

If we adhere to these 2 principles, I think we will be much more faithful to  
Usenet policy and spirit than otherwise.  Let's drop this pricing fiasco and  
all the noise it perpetually generates.  Could we now return to genuinely  
informative messages?

Thanks,

= Joe =
-- 
Joe Grace <jgrace@TetraSoft.com>
TetraSoft International   Business and Personal Productivity Tools for NeXTSTEP
From: izumi@pinoko.berkeley.edu (Izumi Ohzawa)
Newsgroups: comp.sys.next.misc
Subject: Re: why NeXT is still having credibility problems
Date: 15 Sep 1992 06:39:20 GMT
Organization: University of California, Berkeley
Distribution: world
Reply-To: izumi@pinoko.berkeley.edu
NNTP-Posting-Host: moica.berkeley.edu

In article <MS-C.716532025.1103527590.mrc@Tomobiki-Cho.CAC.Washington.EDU> Mark Crispin  
<mrc@Tomobiki-Cho.CAC.Washington.EDU> writes:

>
>I though that ordering some additional DSP memory might help some
>problems I had been having with music.  I called up NeXT to order it.
>
>I also found out from the fellow at NeXT that DSP memory is `not
>listed as a product available to ship.'  Great.  Now they tell me.  I
>ordered vaporware.

It is certainly listed, and I ordered 3 of them recently and got them
in 3 weeks approximately.  Part#, name etc are as follows.

N7013		DSP 96KB Memory Expansion Kit


By the way, I don't think MusicKit will start using additional DSP RAM
automatically.  At least 2.1 MusicKit driver/monitor is hard-assembled
for 8kword stock configuration.


>NeXT's order management system (running on a NeXT, perchance?) does
>not have the capability to look up an user by the customer's name.
>The person I talked to at NeXT said as much.  Now, any vendor in the
>Mac world would be laughed out of the market if they couldn't look up
>a customer's order by his name.

Hmmm.  I wonder what happened to the "mission-critical application"
development for their own use.  They've had NeXTSTEP for full 3 years
and still doesn't have a decent order management system?


--
Izumi Ohzawa             [ $BBg_78^=;(J ]
USMail: University of California, 360 Minor Hall, Berkeley, CA 94720
Telephone: (510) 642-6440     Fax:  (510) 642-3323
Internet: izumi@pinoko.berkeley.edu (NeXT Mail OK)
Newsgroups: comp.sys.next.misc
From: agnus@amylnd.stgt.sub.org (Matthias Zepf)
Subject: Re: Amiga graphics => NeXT format?
Reply-To: agnus@amylnd.stgt.sub.org (Matthias Zepf)
Organization: Agnus' new home, Leonberg/Warmbronn, Germany
Date: Tue, 8 Sep 1992 13:34:53 GMT

In article <1704@nextpoint.UUCP> reini@demo10 (Michael_Reinemuth) writes:
> In article <1992Sep5.233758.5678@nntp.uoregon.edu> cdelay@inferno.uoregon.edu  
> (Christian De Lay) writes:
> > Does anyone know of a way to convert amiga "ILBM" graphics into
> > a format that the NeXT will read?  Is there some sort of utility
> > to do this?
> 
> ILBM is an old Amiga grafics format ... normally Amiga works with IFF Format
> I don t now what resolution the pictures have but normaly load it into DPaint
> and save it as IFF .... noe there is no problem...

Forget this ... ILBM is not old or anything like this, ILBM is the
absolut correct name for the Amiga picture file format. The whole
system is called IFF (Interchange File Format). The first four bytes
inside the file specify the type. ILBM is an InterLeaved BitMap - an
image. There are a lot of other IFF file types for text, sound, voice,
animation, etc.

To convert IFF ILBMs to TIFF use the shell application "iff2tiff". It
can be found on several ftp servers. You may also use Jef Poskanzer's
"pbmplus" package (from ftp servers, too).

Matthias
-- 
** Matthias Zepf, Riegelaeckerstrasse 27, 7250 Leonberg, Germany **
** +49 7152 41917    Email: agnus@amylnd.stgt.sub.org (NeXTmail) **
From: grant@Manticore.COM (Grant J. Munsey)
Newsgroups: comp.sys.next.misc
Subject: Hidden feature in IconBuilder (3.0)
Date: 7 Sep 92 00:22:40 GMT
Reply-To: grant@Manticore.COM

I assume everyone but me already knew that holding down the '1' key while
in Icon caused a pattern to paint underneath the graphic in the current
window so that you could get an idea of how transparent the image was.
I noticed today that this also works in the new IconBuilder tool in 3.0.
----
Grant Munsey, Mainticore, Inc. (408)252-1135
grant@Manticore.COM,  uunet!ub-gate!gouche!grant   NeXTMail ok.
Newsgroups: comp.sys.next.misc
From: ben@fizz.fdn.gna.org (Benoit Grange)
Subject: Re: The "receipt" from NeXTmail
Organization: Personal.
Date: Fri, 11 Sep 1992 07:43:25 GMT

In article <1992Sep9.125711.16452@ni.umd.edu> louie@sayshell.umd.edu  
(Louis A. Mamakos) writes:
> Gack!  This RR thing is such a kludge!  I'd had to see it propagated
> to other mail UAs.  Much better to use another header line and attempt
> to get consensus on that.  
> 
> Also, some have found it rude to have their mail UA return an
> acknowledgement automatically when a message is read, and have patched
> their Mail.app to inhibit this behavior.
>
The 'Read receipt' feature is a good idea, BUT

What a horrible hack...

Nearly useless, unless all mail readers get a 'standart' header line  
asking them to return that read receipt in a known format, INCLUDING THE  
ORIGINAL MESSAGE ID.

When posting a mail message and asking for a read-receipt, the mail  
program should keep a copy of the mail around till you have received the  
receipt. It should automagically match the original mail and it's receipt  
and cancel them from the 'not-yet-read-by-the-recipient(s)' list. It  
should also remind you after some days that your message was not read.
I currently do that by hand with a 'RR' mailbox holding those messages.

What about some additional RFC for mailers handling RFC822 mail messages ?
The read receipt should be of very low priority, should never trigger  
errors if not corretly handled in order to get the overhead as low as  
possible. It should be posted in a known format, including the original  
message-id. Some problem may happen if the mail was sent to user 'foo' and  
that foo's mail is forwarded to user 'bar' (whose mailer returns the  
read-receipt'). Also one should write special code for multiple  
recipients.
-- 
----
Benoit Grange - PARIS - FRANCE

Mail to : ben@fizz.fdn.org (SMALL NeXTMails accepted, < 10kb)
Newsgroups: comp.sys.next.misc
From: pascal@nextasy.physics.mcmaster.ca (Pascal Gaudette)
Subject: Re: NEW language list, with 100% more than the FAQ sheet!
Organization: McMaster University, Hamilton, Ontario, Canada.
Date: Mon, 7 Sep 1992 18:52:28 GMT

In article <Bu72J2.FCz@mentor.cc.purdue.edu> asd@sage.cc.purdue.edu (Kareth)  
writes:

> **** FORTRAN
> 
> There is a Fortran to C translator called f2c available.  There is a
> current version of it avaible on the archives.
> 
> obtained from sonata.cc.purdue.edu
>  
> There are also commercially available Fortrans.  I've heard not so
> great comments about these programs, their speed, and their high
> costs.
> 
> 	Absoft (313) 853-0095
> 	Diab Data (415) 571-1700
> 

This list is incomplete:	

NAG is now shipping a FORTRAN 90 compiler for the NeXT.
    NAG: (708) 971-2337

I am not related to them in any way.

One should also note that the Absoft compiler adds OO
extensions to fortran (methods, messaging: essentially,
you can build FORTRAN objects). I am not related to Absoft
in any way except as a satisfied customer.

--
Pascal "The Rascal" Gaudette       pascal@nextasy.physics.mcmaster.ca
MacNUG president                      | *NeXTmail encouraged* 
graduate student, McMaster university | Je ne suis pas infaillible.
Physics and astronomy dep.            | Vive le Quebec LIBRE!
Newsgroups: comp.sys.next.misc,comp.sys.next.software
From: louie@sayshell.umd.edu (Louis A. Mamakos)
Subject: Re: Problems with SLIP, Help needed!
Keywords: SLIP, Louis Mamakos, OS3.0, WindowServer
Organization: University of Maryland, College Park
Date: Tue, 15 Sep 1992 15:03:18 GMT

In article <BuMHyu.1n4@news.cso.uiuc.edu> heller@lisboa.ks.uiuc.edu writes:
>Hello,
>I recently installed SLIP from Louis Mamakos (the latest version from 
>sonata/incoming) and tried to run it on my new NeXTstation (OS 3.0). 
>When I rebooted, everything looked fine, but then, when the loginwindow 
>tried to come up, I got the message that it could not find a port for 
>the window server and it never came up!

Make sure that your NeXT isn't configured to be on a "Netinfo
Network."  This is the usual cause of things like this, where the
system is trying to bind to an upper level netinfo server on the
network.  Usually, if you don't have a network connected, it just gets
an "destination unreachable" error, but it is likely not getting that
with the SLIP interfaces configured.

I'm using it on my (just upgraded last night) 3.0 system, and it seems
to work just fine.

louie



Newsgroups: comp.sys.next.misc
From: andrew@cubetech.com (Andrew Loewenstern)
Subject: Re: NS 3.0, Appletalk, and Macs
Organization: Cube Technologies, Inc.
Date: Tue, 15 Sep 1992 02:25:57 GMT

In article <1992Sep14.000344.22900@cube.handheld.com> jmd@cube.handheld.com (Jim De Arras) writes:
>In article <1992Sep12.204258.1223@metrosoft.com> gvh@metrosoft.com (Gordon Van  
>Huizen) writes:
>> I was pretty shocked to see that 3.0 doesn't allow you access to the  
>> resource fork of Mac files. NeXT seems to think that only the data fork  
>> contains any data we might be interested in!
>> 
>NeXT, if you're reading this, this is WAY wrong!  You need to fix this fast, or  
>you will get clobbered for another missed standard.  Macbinary or apple  
>single/double formats would help.

I sent this in as a bug_report early on (I think I sent on a lot of
bug_reports for the Ethertalk and NetWare clients), and nothing ever
came back from NeXT.  I think Redwood City thinks this one is a
feature.

I don't think that the NetWare and Ethertalk clients have extremely
high priority at NeXT.  I think they were almost thrown in just to
ensnare future big accounts.

Sure, they work pretty well, but they don't work nearly as well as you
would expect something from NeXT to work (and they eat CPU BIGTIME!).


andrew
-- 
andrew@cubetech.com     | "We shall not cease from exploration
Andrew Loewenstern      |  And the end of our exploring
Cube Technologies, Inc. |  Will be to arrive where we started
                        |  And know the place for the first time." -T.S. Eliot
From: rob@shw.optics.rochester.edu (Rob Smith)
Newsgroups: comp.sys.next.misc
Subject: printing to a HP-DeskWrtiterC?
Date: 10 Sep 92 20:23:17 GMT
Organization: University of Rochester Computing Center


There is a HP-DeskWrtiterC on the same apple talk network on which I print to  
Apple LaserWriters. Does anyone know what I would need do print to it?
ie., drivers etc. Has anyone done same?

email prefered

thanks
rob
Newsgroups: comp.sys.next.misc
From: lemson@ux1.cso.uiuc.edu (David Lemson)
Subject: Re: NS 3.0, Appletalk, and Macs
Keywords: Appletalk Macintosh
Organization: University of Illinois at Urbana
Date: Tue, 8 Sep 1992 03:35:59 GMT

heberlei@cs.ucdavis.edu (Louis Todd Heberlei) writes:

>I have heard rumors that NS 3.0 will support Appletalk.  If
>this is true, does anyone know if it would be possible to
>connect my Mac to my NeXT via an Appletalk network?  Furthermore,
>could I then print from the Macintosh to the NeXT printer?

1) NS 3.0 will support EtherTalk, not AppleTalk per se.  EtherTalk
is the kind of AppleTalk that runs over Ethernet (as opposed to
LocalTalk, which is lower speed and runs over a different kind of
cable).  Some people have rumored of drivers that let your NeXT talk
AppleTalk over the serial port (theoretically possible but I have
never heard of any REAL driver that did this).

2) NS 3.0 is just an AppleShare client, meaning that you can connect
to an AppleShare server elsewhere on the network (or a Novell
server, too).  It sounds like you want the Printing server package
that goes along with ushare, from IPT.  See the latest NeXTWORLD for
a review of that package.  (IPT's number is 800-233-9993)
People say that CAP6.0 does this for free, too.  (Although you may
need a GatorBox or some kind of LocalTalk->EtherTalk router
somewhere, because CAP only talks EtherTalk, and if you have some
LocalTalk-only Macs, then they will have to bridged onto your
EtherTalk network)
-- 
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
Newsgroups: comp.sys.next.misc
From: agnus@amylnd.stgt.sub.org (Matthias Zepf)
Subject: Re: Stability of Next as a company
Organization: Agnus' new home, Leonberg/Warmbronn, Germany
X-Newsreader: Tin 1.1 PL4
Date: Thu, 10 Sep 1992 22:12:40 GMT

rca@cs.brown.edu (Ronald C. Antony) writes:
: In article <HARDY.92Sep6231009@golem.ps.uci.edu> hardy@golem.ps.uci.edu (Meinhard E. Mayer (Hardy)) writes:
: >With the current DM/OS/USD ratios NeXTs in Europe should be outright
: >bargains.  Something is wrong if prices don't fall together with the 
: >Dollar! (Isn't that the purpose of keeping the dollar low? ).
: 2) If dollar goes up: the price goes up by the same ratio
:    If dollar goes down: nothing happens except occasional special
:    offers.

(Sorry for my bad English.) You are absolutly right.

All the others, please do not forget: 

A simple NeXTstation (Mono, 25 MHz) still costs about
12,312.- DM (German Marks). At the current USD rate
(1 USD = 1.4 DM) this is about 8,800.- USD!!! The US
street price is 3,996.- USD. (German NeXT dealers
offer 5% edu discount.)

NeXT did not change the prices in any way due to the
fallen USD rate. By the way ... the new upcoming Amiga
4000 (with 68040@25Mhz, "AA Chip Set" with 256 and more
colors, four meg RAM, 50 meg hd) will cost about 4,000.-
DM here in Germany. This is not a direct comparable
system, but due to that price, the low-end NeXT should
be sold at 6,000.- or max. 7,000.- DM (what compares
very good with 4,000.- USD).

Matthias
-- 
** Matthias Zepf, Riegelaeckerstrasse 27, 7250 Leonberg, Germany **
** +49 7152 41917    Email: agnus@amylnd.stgt.sub.org (NeXTmail) **
Newsgroups: comp.sys.next.misc
From: hodges@huckleberry.sfsu.edu (Jack &)
Subject: FAQs...where to find them
Keywords: Idiot R Us
Reply-To: hodges@huckleberry.sfsu.edu
Organization: California State University, Sacramento
Date: Fri, 11 Sep 1992 22:41:00 GMT

I saw mention, in my rn files, about someone who was interested in knowing
whether a NeXT cube could be upgraded to a turbo board, and the reply I
saved was something like "ah, another user that doesn't read the FAQs."
Well, I've been looking around for them for an hour or so now, and have
not found them. Any salutations would be appreciated.

Also, does anyone still have information on the folks who modify 030
boards for use in a cube? Or, should I say, does anyone know more
about the outfit, what they do, and how well it works?

Thanks...

Jack Hodges
Xref: sparky comp.sys.next.misc:19520 comp.sys.next.advocacy:2178