HDTenEightyP/NetNews huggingface dataset:
From: steves@truevision.com (Steve Spicklemire)
Subject: Apple Talk / domain name service
Organization: Truevision Inc., Indianapolis, IN
Date: Fri, 02 Oct 1992 21:36:22 GMT

Hi,
	I just got my station today. It's an 8/250 mono. I'm
generally *very* pleased! However I'm having a couple of problems
I hope someone out there in net.land might be able to help 
with. 

1) I want to print! The only printers around are AppleTalk 
printers. I noticed that the NetWare stuff is on the base distribution
pre-loaded on the machine, but (I guess) the AppleTalk isn't! :-(.
I ordered a CD-ROM drive at the same time as the station, but
it isn't here yet. I *have* an Apple CD-Rom drive, but the cable
is wrong! If I buy a centronics style cable to work with the Apple
drive from NeXT connection, will it work with the NeXT CD as well?
Is there any sane way I can get the software to print *now*
without waiting for my NeXT CD Drive?

2) I can telnet/mail etc. to any machine that I *explicitly* 
name with HostManager. Fine. How do I tell the NeXT to ask
our campus domain name server for names that aren't in netinfo?

thanks!
-steve   waiting, but basically happy :-)


-- 
Steve Spicklemire
steves@truevision.com (daily)	spicklemire@gandlf.uindy.edu (sometimes)
Dept. of Mathematics and Physics, Univ of Indianapolis 
(317) 788-3313
From: coco@cbnewsl.cb.att.com (felix.lugo)
Newsgroups: comp.sys.next.sysadmin
Subject: Re: SLIP doesn't like dialins on two different 3.0 systems
Date: 4 Oct 92 15:47:39 GMT
Organization: AT&T

In article <15880@umd5.umd.edu> bchin@is-next.umd.edu (Bill Chin) writes:
>
>Also make sure that NXFax isn't running - the way it takes over the serial ports
>conflicts with Transys SLIP (haven't tested it with Teleconnect).
>
>Bill Chin
>
>-- 
>Bill Chin				Internet & NeXTmail:
>PC/IP Group, Computer Science Center		bchin@terminus.umd.edu
>University of Maryland, College Park	*Standard Disclaimers Apply*

	Then, how come the combination NXFax/Transys SLIP (DialUpIP) work
on my 3.0 system?  His problem lies somewhere else, though I don't know
where that might be!

--Felix
Newsgroups: comp.sys.next.sysadmin
From: n9240566@animal.cc.wwu.edu (leif e. harrison)
Newsgroups: comp.sys.next.sysadmin
Subject: swapdisk oddities
Summary: swapdisk mounts in (pseudo) random location
Keywords: swapdisk
Date: 6 Oct 92 16:51:01 GMT
Article-I.D.: animal.n9240566.718390261
Organization: Western Washington University


	Okay, I have an old '030 Cube with the 40M swap drive, an external
660M Fujitsu, the OD, and now a new CD-ROM (NeXT).  When installing 3.0 I
noticed something very strange about where the OS was mounting the
swapdrive...It seemed as if it randomly decided between /swapdisk and
/private/swapdisk when it booted, mounting the swapdrive on one of those
two directories.  I noticed this problem both before and after I had
installed 3.0.  Anybody have an explanation?

Further info: Using SCSIInquirer it gives me SCSI ID of 1 for the Fujitsu,
 4 for the CD-ROM, and 6 for the 40M Quantum.  When it mounts them,
The Fujitsu goes to sd0a, the Quantum to sd1a or sd2a, and I can't
remember what it mounts the CD-ROM to...?

	
	Oh, and NeXT is serious when they say not to run other applications
when installing 3.0.  I forgot that Preferences was running and spent about
3 hours wondering why Upgrade_3.0 kept bombing on me...

	Bleck...
Newsgroups: comp.sys.next.sysadmin
From: silbar@mpx2.lampf.lanl.gov (Dick Silbar)
Subject: why the "incomplete termcap" warning?
News-Software: VAX/VMS VNEWS 1.41    
Organization: LAMPF Data Analysis Center, Los Alamos, New Mexico
Date: Sat, 3 Oct 1992 17:35:00 GMT

In checking out the dial-in procedure through a ZyXel modem, I get
the following warning just after I log in:

    Warning: incomplete termcap entry.  Editing disabled. 

The termcap found in /etc was 166290 bytes and from Aug 13, 1991 (this
is a fairly new NeXTStation answering the phone).  The problem does
not go aware if I replace the termcap from the one in my older cube
(166338 bytes, Nov 2, 1989).  I haven't had the courage to try using
the termcap from a nearby Sun, yet.

Related perhaps is that, because of the "editing disabled" message,
I checked 'echo $TERM' and found it to return "unknown".  In fact, 
emacs would not load until I did BOTH 'setenv TERM vt100' and 
'unsetenv TERMCAP', at least with my initial .login file.  When
substituting a .login file which has a line

   setenv TERM `tset - -m ':?vt100' -Q`

I end up with the peculiar situation, when logging in, of still getting 
the "incomplete termcap" warning BUT with 'echo $TERM' => "vt100" and 
emacs being able to load just fine!  (I hit the <cr> on login in response 
to the prompt.)

Does anyone know what's going on here?  I'm baffled.

   Dick Silbar
Newsgroups: comp.sys.next.sysadmin
From: BrianW@SoundS.WA.com (Brian Willoughby)
Subject: Re: 3.0 kills itself
Reply-To: BrianW@SoundS.WA.com
Organization: SoundSoftware, Bellevue, WA, USA
Date: Sat, 3 Oct 1992 07:23:51 GMT

Mark Adler writes
| Well, this time the log off process hung, and the OD didn't come out.
| I have to think that these two things were related, since I had had
| no problem logging out before.  After waiting some time, seeing nothing
| but the dock of applications on the right, I used command-` to get the
| "restart or power-down" prompt.   This worked, appeared to power off
| the machine correctly, including ejecting the OD.
| 
| madler@cco.caltech.edu

I can't help you repair your unbootable machine, but I have seen similar  
symptoms.

On at least three occasions, my logout sequence has hung my NeXT.  The second  
time, I walked out of the room to see how long it would sit there.  When I came  
back, there was an alert asking me if I wanted to save some edited files in one  
of the active applications.  I clicked on the button to save the files and  
watched the NeXT go back to its hung state - this time for good.

Now, I'm afraid to log out with any processes running (especially that buggy  
Librarian.app) for fear that I might have to resort to Command-` and 15 minutes  
of system disk repair (with its inherent risk of file loss).  So far I've had  
good luck since my machine still boots, but how long before I join Mark crowd  
and have a machine that refuses to boot?
-- 
Brian Willoughby	Software Design Engineer, BSEE NCSU
BrianW@SoundS.WA.com	Sound Signal Processing Software and Consulting
NeXTmail welcome	- NO EMAIL SOLICITATION without prior permission
Newsgroups: comp.sys.next.sysadmin
From: jeffo@uiuc.edu (J.B. Nicholson-Owens)
Subject: No more floppy format questions please (was: Re: so how do you format a floppy for the MAC?)
Reply-To: jeffo@uiuc.edu (J.B. Nicholson-Owens)
Organization: University of Illinois at Urbana
Date: Fri, 2 Oct 1992 03:53:37 GMT

A lot of people are posting about this.  It is covered in the various posts and  
literature discussing NeXTSTEP 3.0, but here it comes again, hopefully for the  
last time:

* ONLY HD (High Density) floppies can be used with Mac formatting.
* SD, DD and HD (Single, Double and High Density) disks can be used with DOS 
  formatting.  "DOS" refers to MS-DOS or Microsoft Disk Operating System.
* SD, DD, HD and ED (Single, Double, High and Extended Density) disks can be 
  used with NeXT formatting.

How to format ANY floppy disk using NeXTSTEP 3.0's File Viewer:
---------------------------------------------------------------
(keeping in mind the above restrictions)
1. Insert the floppy disk into your floppy drive.
2. Select the disk in the File Viewer.
3. Select Disk->Initialize... from the menu.
4. A panel will come up.  In it will be a popup requestor with the valid 
   choices according to the type of disk you inserted.  For instance, if you 
   inserted a Double Density floppy, you will only be able to format it as a 
   NeXT or DOS floppy.  If you had inserted a HD disk you could select NeXT, 
   Mac or DOS formatting.  Mac floppy use on a NeXT computer requires a HD (or 
   HIGH DENSITY) disk.
5. If you continue the format, the floppy you inserted will be formatted with 
   the filesystem displayed in the popup requestor.

This answers the recent rash of floppy format questions and (hopefully) answers  
upcoming questions as well.
-- 
-- Jeff (jeffo@uiuc.edu)
-- NeXTmail ok
From: anderson@sapir.cog.jhu.edu (Stephen Anderson)
Newsgroups: comp.sys.next.sysadmin
Subject: Re: Linking to make man pages work (was: Re: oddity with man pages in 3.0 -- RESOLVED)
Date: 1 Oct 92 13:29:32 GMT
Organization: Dept. of Cognitive Science, The Johns Hopkins University
In-reply-to: jeffo@uiuc.edu's message of 1 Oct 92 00:50:18 GMT

In addition to linking /NextLibrary/ManPages to /usr/man in order to
make "man" work, the initial installation also has to link
/NextDeveloper/Headers to /usr/include to make lots of things work. It
turns out that under certain circumstances, the 3.0 installer can
remove those links when installing other packages: that happened to me
when I installed a new version of co-Xist. It's easy enough to remake
these links (if you know about them), but it's apparently a bug in the
installer.  So if you're lacking /usr/man (or /usr/include), it may
have been removed when you installed something else, rather than the
links not having been made in the first place.

--Steve Anderson
Newsgroups: comp.sys.next.sysadmin
From: lmccullo@nyx.cs.du.edu (Michael McCulloch)
Subject: Re: AppleTalk and 3.0. It does not work.
Organization: University of Denver, Dept. of Math & Comp. Sci.
Date: Tue, 6 Oct 92 19:51:16 GMT

In article <1992Oct3.115657.15290@csus.edu> eps@futon.SFSU.EDU (Eric P. 
Scot) writes:

> + Logging out did not unmount AppleShare servers.  Logging in
>   again would wedge the automounter resulting in NFS getattr
>   failures on terminals or a hopelessly hung Workspace when
>   attempting to browse AppleShare, making it impossible to log
>   out.  (Reboot seems to be the best course of action here.)
> + The automounter didn't always dismount properly at shutdown,
>   with the message "CAUTION: some processes wouldn't die"
>   appearing.
> 
> "Really looking forward to NeXTSTEP 3.1"

I have had problems with printing. I've printed OK from root every time I've
tried it, but when logging in as a user the print job seems to hang. After
a few minutes, trying to access the /Net/AppleShare folder locks up my
WorkSpace, forcing me to reboot without first being able to sync the
filesystem.

The automounter sequence(s) used under AppleShare are causing me great pain.
In fact, AppleShare has been disabled on my machine and will remain that
way until NS 3.1. If NeXT is going to advertise AppleShare connectivity as an 
advantage, then it better work or it severely damages the reputation of
NeXT. I've found one of the major advantages of NeXT has been stability of
major OS releases. 3.0 is on the hairy edge so far. If the new IB, PB, DL,
etc. cause me more grief, then I'll start wishing I had waited to install
3.1.

As far as AppleShare, doesn't it strike you a bit funny that several pages
of the 3.0 Release Notes were dedicated to NetWare problems/fixes, while
NO problems in using AppleTalk were noted? Sounds like untested SW to me...

Michael McCulloch
Huntsville, AL
Newsgroups: comp.sys.next.sysadmin
From: zenon@resonex.com (Zenon Fortuna)
Subject: smail3 != sendmail
Organization: Resonex Inc., Sunnyvale CA
Date: Sat, 3 Oct 1992 23:54:46 GMT

Here is my experience with installation of the SMAIL, given under the
GENERAL PUBLIC LICENCE to all of us by Ronald S. Karr and Landon Curt Noll.

The simplest way to install smail under the NS 3.0 is the following:

1. Get the  smail-3.1.28.tar.Z  latest distribution file (about 980kB)
	e.g. via ftp from ftp.uu.net in /networking/mail/smail.
2. Unpack the above tar file, and (maybe) read the "guide/admin/install" file,
   which can be read as "nroff -ms install|less".
3. Copy the edit/EDITME-dist file to edit/EDITME and modify the edit/EDITME
   file adding the following 4 lines (placing them perhaps arround the 1240
   line):
MISC_C_DEFINES='
#define HAVE_VFPRINTF
#define INET_NTOA_USE_STRUCT
'
4. Execute the "make". On the non-turbo 68040 system it takes about 10 minutes.
5. Be ROOT, be sure that you have the "/usr/local/bin" directory and execute
   "make install".
6. You may execute also the "make installman" (you need to have in
   /usr/local/man the man1,man5 and man8 directories).

REMARKS:
The "make install" saves "/bin/rmail" to "/bin/rmail.O" (actually links it
also to "/bin/rmail.SAV), saves also the "/usr/lib/sendmail", and copies
the "smail" executable under the "/usr/lib/sendmail".
There are additional 9 hard-links done to this file, namely "/bin/rmail",
"/usr/ucb/newaliases" and 7 other files in "/usr/local".

The main "smail" installation directory is a newly made "/usr/lib/smail",
and for the (future) operation files the "/usr/spool/smail" is made.

The "smail", in contrast to the "sendmail", does not require any config files
(though it can accept some of them - read the "config" and "cookbook" files,
again with "nroff -ms file|less").

The "smail" is NOT a new version of the sendmail, but (as the authors write)
it is "compatible with the external interface of the Berkeley 'sendmail'
program... this compatibility does not apply to either the internal operation
or the configuration file formats."

AND THIS IS ALL. It "just works".

	-Z.
From: gbol@rglnext.geol.vt.edu (Gregory B. Lampshire)
Newsgroups: comp.sys.next.sysadmin
Subject: Re: so how do you format a floppy for the MAC? (SOLVED)
Date: 2 Oct 92 13:55:44 GMT
Reply-To: gbol@rglnext.geol.vt.edu

In article <1992Oct1.172421.28650@constellation.ecn.uoknor.edu>  
slfields@essex.ecn.uoknor.edu (Scott Landon Fields) writes:
> gbol@rglnext.geol.vt.edu (Gregory B. Lampshire) writes:
> >It seems that BuildDOS is gone from NS3.0.  So how does one explicitly  
> >build a DOS or MAC floppy?
> 
> Well, in the workspace manager you activate the Disk menu (I think) and
> pick Initialize or Format disk. Sorry, but I don't remember off the top  
of
> my head but it is in the menu.

Indeed, as several people pointed out, Initialize is in the menu.  It is  
only highlighted when you select the floppy itself which was my problem.   
Without the highlighted selection I simply didn't see the entry.  I always  
fired up BuildDOS when I needed to format a floppy before and never really  
looked at any other menu option under Disk.

I dropped the ball on this one... :-)

-gregory
Xref: sparky comp.sys.next.sysadmin:5597 comp.sys.next.software:1938
From: bfjeld@obelix.cs.uoregon.edu (Bjorn S. Fjeld Pettersen)
Newsgroups: comp.sys.next.sysadmin,com.sys.next.misc,comp.sys.next.software
Subject: Re: gcc 2.2.2 and NeXTSTEP 3.0
Date: 3 Oct 92 07:49:54 GMT
Article-I.D.: cs.1992Oct3.074954.22608
Organization: University of Oregon Computer and Information Sciences Dept.

>Hi, Has anyone out there tried compiling gcc 2.2.2 under 
>3.0? I tried to compile it the same way I did under 2.1 
>and I am getting compile errors on the file rtl.c! Did I 
>forget a path or something? 
>
>Thanks Jon 

Many people are having this problem (myself included). It is something
3.0 specific, but I am not sure what. The solution that has been posted
is to either compile it with gcc 2.1 from the archives, or wait for 
gcc 2.3 wich is supposed to be released in early october. If anyone has any 
fixes for this, please mail me, or post to the net.

Bjorn
From: mrc@Tomobiki-Cho.CAC.Washington.EDU (Mark Crispin)
Newsgroups: comp.sys.next.sysadmin
Subject: Re: 3.0: what gives with cron
Date: 26 Sep 92 20:54:44 GMT
Article-I.D.: Tomobiki.MS-C.717540884.662824084.mrc
Organization: University of Washington
Content-Type: TEXT/PLAIN; charset=US-ASCII
To: alevine@ucsd.edu
Mime-Version: 1.0

I encountered the same problem with cron in 3.0.

I'll bet you're piping your backup data to rsh, eh?  Sorry, bunkie; rsh in 3.0
does not work under cron.  I spent several hours on this problem and fairly
conclusively proved that rsh just dies silently when it is run under cron.

Don't think of trying an old rsh from 2.1 and seeing if that will work; you'll
get a no such host name error.

I reported this bug to NeXT.  Judging from past performance, we can expect to
see this fixed sometime in 1995.  After all, 3.0 finally fixes some bugs we
reported in 0.8 days.
From: borchers@poogh.llnl.gov (Robert R. Borchers)
Newsgroups: comp.sys.next.sysadmin
Subject: Re: AppleTalk and 3.0. It does not work.
Date: 30 Sep 92 16:22:29 GMT

In article <137555@lll-winken.LLNL.GOV> borchers@poogh.llnl.gov (Robert R.  
Borchers) writes:
Sorry about the multiple postings, our server kept telling me it would not  
post, and like a good soldier i kept trying. Mea Culpa. Bob

> Robert R. Borchers
> L-414
> Livermore, Ca 94551
> borchers@llnl.gov
> NeXTmail Welcome
Newsgroups: comp.sys.next.sysadmin
From: zenon@resonex.com (Zenon Fortuna)
Subject: Re: bug in tar, anyone fixed it?
Organization: Resonex Inc., Sunnyvale CA
Date: Tue, 6 Oct 1992 19:31:47 GMT

In article <1992Oct6.204852.16384@wam.umd.edu> elitman@nxstep.com (Eric A. Litman) writes:
>Ludger Solbach (ti6ls@tuhhco.rz.tu-harburg.de) wrote:
>: As the man pages say "The current limit on file name length is 100 characters."
>: Has anyone fixed this bug?
>
>GNU tar is definitely the answer, but it is not necessary to "get" it off of
>some archive site somewhere. Under 3.0, it's /usr/bin/gnutar.
>
>--
>Eric A. Litman  #import <std/disclaimer.h> | NeXTMail, MIME accepted - please 
>U. of Maryland, NeXT Campus Consultant     | indicate in Subject line.

The original posting was about tar-like program which should handle names
longer than 100 characters.
MANY PEOPLE answered, that the gnutar is the solution. Somebody is wrong   :)
because the following test shows, that the gnutar also does not like long
names:

	% echo > /tmp/aaaaa...aaaa	(repeat this 'a' more than 100 times)

	% gnutar cvf /tmp/x.tar /tmp/aaaaa*

	    and the gnutar protests: ...aaaa is too long: mangling to ...

Yes, the /NextAdmin/Installer.app/installer_bigtar accepts longer names,
but the resulted archive-file is not compatible with "normal" tar.

	-Z.

PS
And in the GNUtar sources the NAMSIZ parameter is set to 100.
Newsgroups: comp.sys.next.sysadmin
From: elitman@nxstep.com (Eric A. Litman)
Subject: Re: bug in tar, anyone fixed it?
Organization: U. of Maryland, College Park.
X-Newsreader: TIN [version 1.1 PL6]
Date: Tue, 6 Oct 1992 20:48:52 GMT

Ludger Solbach (ti6ls@tuhhco.rz.tu-harburg.de) wrote:
: As the man pages say "The current limit on file name length is 100 characters."
: Has anyone fixed this bug?

GNU tar is definitely the answer, but it is not necessary to "get" it off of
some archive site somewhere. Under 3.0, it's /usr/bin/gnutar.

--
Eric A. Litman  #import <std/disclaimer.h> | NeXTMail, MIME accepted - please 
U. of Maryland, NeXT Campus Consultant     | indicate in Subject line.
Xref: sparky comp.sys.next.sysadmin:5523 comp.sys.next.misc:20354 comp.sys.next.software:1900
From: osiris@ucrengr.ucr.edu (mark radleigh)
Newsgroups: comp.sys.next.sysadmin,comp.sys.next.misc,comp.sys.next.software
Subject: Pascal Compiler on the NeXT
Date: 30 Sep 92 18:24:53 GMT
Followup-To: comp.sys.next.sysadmin
Organization: University of California, Riverside


    Is there a FREE (or very cheap) pascal compiler out there for the NeXTS 
(besides p2c)?  Please reply via E-Mail.  Thanks in advance.



  +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
 /                                                                         \
/  Mark J. Radleigh, Computer Science             | ..!ucsd!ucrmath!osiris  \
\  C.S.L.D. System Administrator, UC Riverside    |   osiris@cs.ucr.edu     /
 \                                                                         /
  +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
Newsgroups: comp.sys.next.sysadmin
From: cs911409@ariel.yorku.ca (RICHARD DAVID ASPINALL)
Subject: Re: 3,0 installation woes
Keywords: 3.0 installation floppies, windowserver-port
Organization: York University, Toronto, Canada
Date: Wed, 30 Sep 1992 02:55:38 GMT

In article <1992Sep28.050130.23485@athena.mit.edu> shanega@athena.mit.edu (Shane G. Artis) writes:
>
>Hi, I have a pair of questions for sysadmin types.  Any hints or
>clues would be very helpful.
>
>First, I'm trying to install 3.0 on my station from handmade floppies
>created using tar and split from a 3.0 optical disk mounted on another
>machine (I am fully licensed for 3.0, but I didn't buy the CDROM drive
>and there's no word on when 3.0 will be available in floppy format).
>I know my NeXT well enough to do a good job getting all the important
>files needed to boot the machine and run NeXTSTEP - at least I thought
>so.  I tar-ed the new machs, the libs, the shlibs, the usr and bin
>directories and created new device drivers using MAKEDEV (while booted
>from a floppy) into the appropriate locations, wrote a new boot block
>to the hard disk so it would boot the new mach, and then rebooted.
>The machine came up in singleuser mode just fine, but when I tried to
>start up the windowserver (by exiting singleuser mode) I got a mouse
>cursor and nothing else.  The mouse cursor went away and then returned
>periodically, along with a bit of disk action, but no windowserver.
>Rebooting back up into NeXTSTEP 2.1 and looking at the private/adm
>messages file gave me one clue.  The final line in the file before the
>most recent booting messages was:
>
>loginwindow: Cannot find windowserver port!
>
>What does this mean I'm missing or doing wrong?  I think everything is
>all there, but maybe I missed a file somewhere.  I'm pretty sure my
>permissions are all set correctly and so on.
>
>
>The second (and simpler) question I have is: Has anyone connected a
>Sun brand CD-ROM drive to their NeXT and successfully used it to
>install 3.0?  Are the drives compatible and the CD formats compatible?
>
>Thanks for any help!
>
>Shane

2./	I have not used a SUN brand CD-ROM, but I have used an Apple
CD-ROM.  In fact I have used an Apple CD-ROM to upgrade my Cube to 3.0
My advice is...plug the sun CD-ROM into your SCSI chain and try it.  You
should be able to tell if it's working from the bootup diagnostics.
PLEASE email with what you find out.

PS.  Make sure you have run the 3.0Prep program...this should allow you
to read the following formats [I assume that SUN CD-ROMs adhere to ISO
9660 standards]  ISO 9660, Rock Ridge, Mac HFS, NeXT Proprietary.
Please note that it was [and is] not necessary for me to upgrade a 2.0
machine inorder to read an ISO 9660 CD using an Apple Drive.

PPS. Please let me know by E-Mail if this works...

David
NeXT Campus Consultant
next@yorku.ca


Newsgroups: comp.sys.next.sysadmin
From: ben@fizz.fdn.org (Benoit Grange)
Subject: DotMatrix printers
Date: Fri, 2 Oct 1992 20:59:48 GMT

I can see in /usr/lib/NextPrinter/Drivers/NXDotMtxDriver somes files about  
dot matrix printers describing the (binary) commands you need to make them  
print some bitmaps and some properties. You also have some descriptions in  
/NextLibrary/PrinterTypes/English.lproj/*.pdf

Where can I get information on how to build such a file for my DeskWriter  
printer ? I did not found any clues in the supplied docs.

Can we build easyly some descriptions ? Does someone has written  
descriptions for DeskWriter (normal or color) ImageWriter (BW) ?

Any information, or help is welcome.

PS: Is NS3 really able to send data to the serial port at 57.6 Kb/s ?
-- 
----
Benoit Grange - PARIS - FRANCE

Mail to : ben@fizz.fdn.org (SMALL NeXTMails accepted, < 10kb)