HDTenEightyP/NetNews huggingface dataset:
From: gvh@metrosoft.com (Gordon Van Huizen)
Subject: Re: Using the serial # in ROM as a copy protection mechanism...?
Reply-To: gvh@metrosoft.com (Gordon Van Huizen)
Organization: Metrosoft
Date: Sun, 20 Dec 1992 17:53:59 GMT

In article <1gte4tINNs3r@ni.umd.edu> louie@sayshell.umd.edu (Louis A.  
Mamakos) writes:
> The approach that I like is to give the user some piece of
> information that needs to be supplied to enable the
> application.  This piece of information uniquely
> identified the *owner* of the software.  That way, if it
> gets "loose", you know who to trace it back to, and thus who
> violated the terms of the software license agreement.  

Does your software respond to a large number of different
keys? If not, how do you deal with the mass-duplication
issue? 

Gordon
 
-- 
----------------------------------------------------------------
Gordon Van Huizen           vox: 619.488.9411  fax: 619.488.3045
Metrosoft                   gvh@metrosoft.com [NeXTmail welcome]
----------------------------------------------------------------
Newsgroups: comp.sys.next.programmer
From: zeno@phylo.genetics.washington.edu (Sean Lamont)
Subject: Font bug?
Organization: University of Washington, Seattle
Date: Mon, 21 Dec 1992 18:30:57 GMT

In "NeXT-ifying" some type 1 fonts I made the following discovery:  A number
of fonts did not respond to the "lighter", "heavier" buttons, although the
weights were correct in the font file.

I narrowed it down to the following fact: If the font used a standard
encoding vector (Encoding AdobeStandardEncoding) , the lighter/heavier
worked fine on the font.  However, if it used a custom encoding vector
(ie Encoding AppleStandard, with an array in the font file to define
what it was [array 256 def, etc]) it would not work.  For any files
that exhibited this problem I modified the encoding vector back to
adobe standard encoding and it worked fine.

Have other people experienced this problem?  Is it a postscript
weirdness or a bug?


-- 
Sean T. Lamont                           |   "Don't oppress me, It's
zeno@genetics.washington.edu             |    'computer of color!' "
lamont@abstractsoft.com                  |_______________________________
Abstract Software
From: bjorn@darmok.uoregon.edu (Bjorn S. Fjeld Pettersen)
Newsgroups: comp.sys.next.programmer
Subject: Anyone compiled sbprolog or cprolog?
Keywords: prolog
Date: 29 Dec 92 08:53:52 GMT
Article-I.D.: pith.1hp3n0INNku1
Distribution: world
Organization: University of Oregon Network Services
NNTP-Posting-Host: cisco-ts2-line34.uoregon.edu

Have anyone out there compiled sbprolog or cprolog for NextSTEP v. 3.0? If so,  
could you mail it to me? (*pretty pleeeese*)

Bjorn
bjorn@darmok.uoregon.edu
(NeXTMail welcome)
From: alex@cs.umd.edu (Alex Blakemore)
Newsgroups: comp.sys.next.programmer
Subject: Re: Request: info on learning NeXTStep
Date: 22 Dec 92 04:26:23 GMT
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742

In article <1h62lvINNcaf@darkstar.UCSC.EDU> isbell@cats.ucsc.edu (Art Isbell) writes:
> The only book that covers some of the the latest NeXTSTEP version, 3.0, is
> NeXTSTEP Programming, Step One:... by Garfinkle and Mahoney (ISBN 0-387-97884-4).
> Springer-Verlag invoice states that the estimated publication date being 02/93!!
> Has anyone received this book yet?

I think they were being conservative with their dates
(a pretty unusual practice when NeXT's are involved :)

its out
mine arrived today, with disk and all !

-- 
---------------------------------------------------
Alex Blakemore alex@cs.umd.edu   NeXT mail accepted
From: biff@biff.gbdata.com (Dwight Everhart)
Newsgroups: comp.sys.next.programmer
Subject: Re: Sending objects between processes
Date: Thu, 31 Dec 1992 07:27:46 GMT

In article <C03x19.Jx2@biff.gbdata.com> I write:
>My second (and latest) approach is to use typed streams on ports, and
>send the objects using NXWriteObject() and NXReadObject().  However,
>I'm having a problem opening the typed streams for reading.  When I call 
>NXOpenTypedStream(), it hangs, apparently blocking on the stream.  I
>assumed it was trying to read some header information identifying the
>type or version of the stream, so I had the client send an object before
>the server tried to open the stream.  Same thing happened.

I figured out what was happening here.  NXOpenTypedStream() is trying to read  
something from the stream.  The reason it hung even when the client wrote an  
object before the server opened the stream was because the client didn't  
flush the stream after writing the object.  In fact, it's not necessary to  
write an object.  What is important is calling NXFlushTypedStream() after  
opening a typed stream for writing.  In most cases, NXFlushTypedStream() is  
also needed after a write to a typed stream on a port.

I'm still interested in suggestions for alternative ways of sending objects  
between processes.  I don't think I can use the pasteboard because security  
is important in my system.  I have to be sure that objects are read only by  
the intended processes and that objects are written only by authorized  
processes.

--
Dwight Everhart          "You'd be surprised what you can get used to
Houston, Texas            when your only other choice is Houston"
biff@biff.gbdata.com      -- Chagall Guevara
NeXTMail and MIME OK     
Newsgroups: comp.sys.next.programmer
From: quarrie@cds001.cebaf.gov (David Quarrie)
Subject: Unresolved references when linking
Reply-To: quarrie@cds001.cebaf.gov (David Quarrie)
Organization: CEBAF (Continuous Electron Beam Accelerator Facility)
Date: Tue, 22 Dec 1992 17:30:36 GMT

--
The following is relevant to NeXTSTEP3.0.

I'm experiencing problems with unresolved references when using archives (.a).
This isn't just my own .a files, but also libX11.a for X-Windows. As far as
I can ascertain, it's a problem with global symbols instead of global routines
and can be illustrated by the following (I haven't actually done the following
since I'm not in front of my NeXT but I think it should illustrate the
problem):

  (a)	Create a file file1.c containing the following:

		int global;

  (b)	Create a file file2.c containing the following:

		extern int global;
	
		int hello()
		{
		        return (global);
		}

  (c)	Create a file file3.c containing:

		main ()
		{
	 	       hello();
		}

   (d)	Compile the files:

		cc -c file1.c file2.c file3.c

   (e)	Create an archive from file1.o and file2.o

		ar -r files.a file1.o file2.o
		ranlib files.a

   (f)	Link the application:

		cc -o myapp file3.o files.a

and with a bit of luck you should get the unresolved reference _global. If you
don't then I've oversimplified the problem and will have to go back to the
drawing board (i.e. my NeXT) to put a better example together.

Am I doing something stupid? Is it a case of RTFM? So far I've managed to force
linking to succeed by extracting the appropriate .o files from the library
and explicitly linking them, but I wouldn't have thought I should need to do 
that. 

Any (constructive) comments and suggestions gratefully received.

		David

-------------------------------------------------------------------------------
	David Quarrie					CEBAF MS 12H
							12000 Jefferson Ave
Internet: quarrie@cebaf.gov				Newport News VA 23606
DECnet  : cebaf::quarrie				Tel: (804) 249-7562
BITNET  : quarrie@cebaf					Fax: (804) 249-5800
Newsgroups: comp.sys.next.programmer
From: mcastle@cs.umr.edu (Michael R Castle)
Subject: ARC on NeXT
Date: Sat, 2 Jan 1993 14:57:52 GMT
Organization: University of Missouri - Rolla


Running 2.x, gcc 1.36.

I'm trying to compile the unix version of the archiving program 'arc',
but not having any luck.  I can't seem to find any recent version of
the arc package (that is, since NeXT came out).  

When I finally get it to build (lotsa hard coded extern rindex()), it
keeps getting a bus error.  Before I start delving more into it, I'm
wondering if anyone else has managed to get it to build successfully?

If so, could you please send me patches, or perhaps the binary?

I've looked on some archive sites, and I can find the binary for lharc,
but not for arc.  

Any pointers suggestions would be appreciated.

regards,
mrc
-- 
Mike Castle .-=NEXUS=-.  Life is like a clock:  You can work constantly
  mcastle@cs.umr.edu     and be right all the time, or not work at all
S087891@UMRVMA.UMR.EDU   and be right at least twice a day.  -- mrc
    We are all of us living in the shadow of Manhattan.  -- Watchmen
From: aking@BBN.COM (Allen King)
Newsgroups: comp.sys.next.programmer
Subject: help with setting up fax and DNS
Date: 2 Jan 1993 00:05:48 GMT
Organization: Bolt Beranek and Newman Inc., Cambridge MA
Distribution: world
Reply-To: aking@BBN.COM (Allen King)
NNTP-Posting-Host: bbn.com

   Well, I'm trying a few things with my new Zyxel modem, and have been unable
to find answers to the following in the manual.

    1. How do you set up /dev/cua as a fax modem that can be chosen by, for
instance FaxReader.app? I was hoping to be able to do that manually without
buying NXFax, but perhaps that is the answer.

    2. Other times I run SLIP on the line. Currently the only host
that is known (as a telnet/ftp host) is my SLIP0REMOTE address. How
does one go about configuring a system to route everything that isn't
local out SLIP0? I'd also like to setup to use the DNS? It would sure
be nice if I could connect to the appropriate IP nameing servers and
have direct internet access from home.
From: izumi@pinoko.berkeley.edu (Izumi Ohzawa)
Newsgroups: comp.sys.next.programmer
Subject: Re: cc problems ???
Date: 21 Dec 1992 09:55:14 GMT
Organization: University of California, Berkeley
Distribution: world
Reply-To: izumi@pinoko.berkeley.edu
NNTP-Posting-Host: moica.berkeley.edu

In article <1992Dec20.172439.11130@musical.fdn.org> sam@musical.fdn.org (Sam Przyswa) writes:

>	Big problem, all the sources files what I have, can t be compiled  
>with NeXTStep 3.0 stuffs, WHAT HAPPENS !?, does I have to back to NeXTStep  
>2.1 ???

Geez.........
You'd better describe what you are getting from the compiler.

--
Izumi Ohzawa             [ $@Bg_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.programmer
From: verket@venice.sedd.trw.com (Paul Verket)
Subject: Additional Librarian docs
Organization: TRW Systems Engineering & Development Division, Carson, CA
Date: Sun, 27 Dec 1992 04:39:03 GMT

From the "I didn't know that was there" department. If one opens up  
/NextLibrary/Bookshelves/NextDeveloper.bshlf and pulls down on the window split  
bar between the shelf and the titles, one will find "Assembler Reference" and  
"Loadable Kernel Servers" entries.

Now how do I play that Audio CD backwards... :-)

Paul Verket (NeXTmail ok)
From: biff@biff.gbdata.com (Dwight Everhart)
Newsgroups: comp.sys.next.programmer
Subject: Sending objects between processes
Keywords: typedstream stream Speaker Listener NXWriteObject NXReadObject
Date: Thu, 31 Dec 1992 04:41:32 GMT

I'm writing a software system involving a server process and several client  
processes.  I'm writing them in Objective-C, although the server is a daemon,  
not an application (it doesn't have a NXApp).  The clients may or may not be  
applications.  I'm using Speaker and Listener objects for the RPC requests.

I need to be able to send objects between the clients and the server.  I  
first tried sending them as a char blocks in the Speaker/Listener messages.   
That worked fairly well, but I ran into problems when the class of the object  
sent was not linked into the server.  (I'm dynamically loading classes as  
they're needed.)  I was also confused about whether the memory was being  
copied and who was responsible for freeing it.

My second (and latest) approach is to use typed streams on ports, and send  
the objects using NXWriteObject() and NXReadObject().  However, I'm having a  
problem opening the typed streams for reading.  When I call  
NXOpenTypedStream(), it hangs, apparently blocking on the stream.  I assumed  
it was trying to read some header information identifying the type or version  
of the stream, so I had the client send an object before the server tried to  
open the stream.  Same thing happened.

What am I doing wrong?  I'm having the client create the port and give the  
server receive rights through a Speaker/Listener message.  The client creates  
the stream and typed stream on its end for writing, and the server takes the  
port given and creates a stream and typed stream for reading.  I don't want  
to send any objects at this point in the code.  I just want to establish  
ports and streams for sending and receiving objects later.  Does  
NXOpenTypedStream() try to read the stream, and, if so, why didn't it read  
the object the client sent?

If you know of a better way to send objects between processes, please  
explain.  I'm running 2.0, so I don't have distributed objects.  Do they  
offer a better approach?

--
Dwight Everhart          "You can't do a musical number about elephants
Houston, Texas            without it being obvious." -- Roger Ebert
biff@biff.gbdata.com     
NeXTMail and MIME OK     
Newsgroups: comp.sys.next.programmer
From: pwm@csis.dit.csiro.au (Peter Milne)
Subject: Getting Renderman examples involving RiLightSource to work?
Organization: CSIRO Division of Information Technology
Date: Mon, 4 Jan 1993 00:02:09 GMT

Following advice from other recent posters I managed to get the simple
Renderman example on page 18 of "The Renderman Companion" to work.
Unfortunately thought, I haven't been able to get the next example on
page 20 to work.  This example involves a RiLightSource call.
When I execute this example I get the following warning msg:

	Warning in context RMContext00001 in command RiLightSource :
	nullpointer: 'light' == 0

and nothing involving the specification of the lightsource gets written into
the .rib file.

Now I've tried it with and without the following RiOption

	RiOption(RI_ARCHIVE, "outputversion", &v31, RI_NULL);

The release notes for 3DKit say not to use this form of RiOption because
the version number doesn't get correctly written to the .rib file
and that instead you should use RiComment("\nversion 3.1");  Trouble is
RiComment doesn't seem to be in Media_s or NeXT_s and isn't commented
anywhere that I could find.

The release notes also say that this form of RiOption causes RiLightSource
to generate invalid sequence numbers and that it should be avoided.

Has anyone succeeded in getting the page 20 example to work?  Is so how
did you do it?

Cheers,
    Peter	(milne@csis.dit.csiro.au)

Newsgroups: comp.sys.next.programmer
From: gpal@fnma.com (Greg Pal)
Subject: Putting images in views
Keywords: image
Organization: Fannie Mae
Date: Mon, 28 Dec 1992 15:14:50 GMT

Does anyone know how to put an image in a view?  I know how to put an  
image on a button, but views don't seem as straight forward.

Any help would be greatly appreciated.  My e-mail address is gpal@fnma.com  
if you wish to contact me directly.
Newsgroups: comp.sys.next.programmer
Subject: Re: Smalltalk for the NeXT - Let's get programming!
From: athomson@otago.ac.nz (Alastair Thomson)
Date: 22 Dec 92 09:38:55 +1300
 <BzD9r6.HA0.2@cs.cmu.edu><4831@ceylon.gte.com> <71952@cup.portal.com>
Organization: University of Otago, Dunedin, New Zealand

In article <71952@cup.portal.com>, lozinski@cup.portal.com (Christopher A Lozinski) writes:
> 
> 
>>Think bigger.  Don't put a NeXTstep front end on GNU Smalltalk, make a
>>version of GNU Smalltalk that lets you send messages to Objective-C
>>objects!  This would be useful on any platform that has GNU
>>Objective-C and SmallTalk, and on the NeXT it would give folks access
>>to just about EVERYTHING.
> 
> My company offers such a product.  It is called the Smalltalk Interface to 
> Objective-C.  It makes Objective-C objects look like Smalltalk Objects.  
> I wonder if it would be worthwhile to port it to the NeXT.
> 
> Regards
> Christopher Lozinski

Please, please Oh please port it to NeXT!

-- 
===============================================================================
                                    |
Alastair Thomson,                   | Phone +64-3-479-8347
University of Otago,                | Fax   +64-3-479-8529
Department of Computer Science,     | e-mail athomson@otago.ac.nz
P.O. Box 56                         |
Dunedin                             |
New Zealand                         |

===============================================================================
Newsgroups: comp.sys.next.programmer
From: "John Michael Ashley" <jashley@garbo.cs.indiana.edu>
Subject: trouble with textfieldcells in a matrix
Reply-To: jashley@cs.indiana.edu
Organization: Computer Science, Indiana University
Date: Sat, 2 Jan 1993 11:15:18 -0500

Hi.  I've got a problem selecting cells in a matrix.  The matrix contains
TextFieldCells, built from a prototype that looks like this:

  cell = [[TextFieldCell allocFromZone:[self zone]] initTextCell: NULL];
  [cell setEditable:NO];
  [cell setBordered:YES];
  [cell setAlignment:NX_LEFT];

The matrix is set up as follows:

  [matrix setPrototype:cell];
  [matrix setMode:NX_RADIOMODE];
  [matrix setTarget:self];
  [matrix setAction:@selector(cellSelected:)];

There's a little more to setting up the matrix than that, but I
believe this is what is relevant to the problem.

Now, when the application is running, I can hold the mouse button
down, and cells will highlight and unhighlight as I pass through them,
but I cannot select them except in the following way: if I drag the
mouse outside of the bounds of the matrix and then let the mouse
button up, the last cell selected before leaving the bounds of the
matrix gets selected.  Strange!

[By "selected", I mean the cellSelected: message gets sent.]

I've gotten this to work using a prototype that was an instance of a
ButtonCell, but I need to use a TextFieldCell.

I'm stuck, and would appreciate any help you can offer.

Thanks, and happy new year.
Mike
From: reggie@stein.u.washington.edu (Reginald Perry)
Newsgroups: comp.sys.next.programmer
Subject: Problems using gcc 2.3.3
Date: 31 Dec 1992 00:44:53 GMT
Organization: University of Washington
NNTP-Posting-Host: stein.u.washington.edu
Summary: Problems using gcc 2.3.3 on NeXT
Keywords: gcc Objective-C

I am having problems using gcc 2.3.3 on the NeXT which is an '040 cube
running NS 3.0. What follows is a snippet of the code followed by the
error. Any help at all would be greatly appreciated.


				Reggie


/* Protocol support */

@class Protocol;

struct objc_protocol_list {
	struct objc_protocol_list *next;
	int count;
	Protocol *list[1];
};

/NextDeveloper/Headers/objc/objc-class.h:77: invalid Objective C keyword `@class'
/NextDeveloper/Headers/objc/objc-class.h:77: parse error before `@class'
/NextDeveloper/Headers/objc/objc-class.h:82: parse error before `Protocol'
/NextDeveloper/Headers/objc/objc-class.h:82: warning: no semicolon at end of struct or union
-----------------------------------------------------------------------------
#ifdef __GNUC__
#ifndef __STRICT_ANSI__
__volatile	/* never returns */
#endif /* not __STRICT_ANSI__ */
#endif /* __GNUC__ */
extern void _NXRaiseError(int code, const void *data1, const void *data2);

/NextDeveloper/Headers/objc/error.h:81: warning: `extern' is not at beginning of declaration
-------------------------------------------------------------------------------
#import <objc/typedstream.h>
#import <objc/zone.h>
@class Protocol;

/NextDeveloper/Headers/objc/Object.h:17: invalid Objective C keyword `@class'
/NextDeveloper/Headers/objc/Object.h:17: parse error before `@class'
-----------------------------------------------------------------------------
- (BOOL) conformsTo: (Protocol *)aProtocolObject;
+ (BOOL) conformsTo: (Protocol *)aProtocolObject;

/NextDeveloper/Headers/objc/Object.h:69: parse error before `Protocol'
/NextDeveloper/Headers/objc/Object.h:70: parse error before `Protocol'
--------------------------------------------------------------------------

@protocol NXEncoding
// encode an objc (parameter) type
- encodeData:(void *)data ofType:(const char *)type;


/NextDeveloper/Headers/remote/transport.h:13: invalid Objective C keyword `@protocol'
/NextDeveloper/Headers/remote/transport.h:13: parse error before `@protocol'
/NextDeveloper/Headers/remote/transport.h:18: method definition not in class context
From: louie@sayshell.umd.edu (Louis A. Mamakos)
Newsgroups: comp.sys.next.programmer
Subject: Re: Using the serial # in ROM as a copy protection mechanism...?
Date: 22 Dec 1992 03:41:38 GMT
Organization: University of Maryland, College Park
NNTP-Posting-Host: sayshell.umd.edu

In article <404@moene.indiv.nluug.nl> toon@moene.indiv.nluug.nl (Toon Moene) writes:

>Well, you'll trust your suppliers or not :-) Your scheme - as effected by  
>the licensing for the (C)SLIP package - works fine for me - except for one  
>little detail.  I obtained a license to use Compressed SLIP with my Neuron  
>1414 modem.  

Actually, you obtained a license from Neuron to use Neuron's software
product "Neuron Dendrite."  This software package is seperate and
distinct from my software package, though it was derived from software
licensed to Neuron by me.  Neuron's software was (supposed) to be
marketed and supported by Neuron.  As we all know by now, this really
didn't happen, nor did they pay their licensing fees to me either
before they did their disappearing act.  Hey, its only $$$ :-(

>Now this weekend I upgraded to 3.0, thereby effectively  
>disabling Compressed SLIP, because it depends on being able to patch the  
>kernel to permit IP packets < 536 bytes. Fortunately - I thought - there  
>was an updated version of your CSLIP package on the Education Software  
>Sampler CD-RON. Alas, installing this package overwrites the license file  
>...  Because I'm very paranoid about keeping originals, I could go back  
>and re-install the old version - and ended up doing the kernel hack myself  

Differences in packaging caused the keyfile to get zapped.  I'm very
careful in my released to not install any files over file that the
user may have customized, which is why all that stuff is in the
SAMPLES directory.

Also, note that the version of my SLIP software on the Educational
Software Sampled CD-ROM is one version short of the one that supports
the 3.0 release for CSLIP.  If you don't do CSLIP, it will work just
fine.  If you do CSLIP and upgrade to 3.0, you really want
SLIP_920904.tar from one of the archive sites.

louie

Newsgroups: comp.sys.next.programmer