HDTenEightyP/NetNews huggingface dataset:
From: jdickson@jato.jpl.nasa.gov (Jeff Dickson)
Subject: Re: WShell: Hangning forbid!
Organization: Jet Propulsion Laboratory
Date: Sun, 13 Dec 1992 07:41:37 GMT

In article <1992Dec12.143541.21468@sth.frontec.se> bjst@sth.frontec.se (Bjorn Stenberg) writes:
>
>A while ago there was some talk about process syncronization when
>multithreading, and Randell Jesup suggested doing:
>
>   ...
>   Forbid();
>   Signal(parent,sig);     // tell parent we exited
>}
>
>to make sure the child has exited before any other process gets a time slice.
>
>Well, I do this in a child of mine, but after the parent exits WShell
>complains with the message:
>
>***Hanging forbid!
>
>Is WShell just being paranoid or am I doing something wrong? (I'm not supposed 
>to Permit() or anything in the parent, am I?)
>
>Any hints are appreciated.
>
>		-- Bjorn
>
>---------------------------------------------------------------------------
>Bjorn Stenberg, Stockholm, Sweden                       bjst@sth.frontec.se
>---------------------------------------------------------------------------


My guess is that you are mistakenly letting the forbid hang in the parent pro-
cess. When the shell runs a program, the same process is used. This explains
how Wshell could possibly know. Child processes are their own entities (task/
process). Wshell or any shell for that matter is totally oblivious of such.

Jeff
From: oahvenla@snakemail.hut.fi (Osma Ahvenlampi)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Attn Commodore: You are making a Big Mistake (Hardware
Date: 11 Dec 92 20:45:41 GMT
Organization: Helsinki University of Technology, Finland
Distribution: inet
	<1992Dec10.011339.14333@kth.se> <jbickers.0l1y@templar.actrix.gen.nz>
NNTP-Posting-Host: lk-hp-4.hut.fi
In-reply-to: jbickers@templar.actrix.gen.nz's message of 12 Dec 92 04:35:20 PST

In article <jbickers.0l1y@templar.actrix.gen.nz> jbickers@templar.actrix.gen.nz (John Bickers) writes:

>Quoted from <1992Dec10.011339.14333@kth.se> by tomasa@dront.nada.kth.se (Tomas Arvidsson):

>> And how, may I ask, do people distinguish a non-OS game from an OS-based game?

>    Some people will have pirated the thing in order to find out. The
>    rest will hang out in comp.sys.amiga.games.

Also, you'll probably notice it from the fact that the OS-based game works like
you'd like it to, meaning that you can multitask it and it doesn't crash on
A4000 even in AGA mode... Not a 100% sure way to distinguish them, but gives
a clue...
--
Osma Ahvenlampi  -  oahvenla@snakemail.hut.fi   * Workstation power for micro-
All my opinions are not necessarily really mine * computer price: Amiga := FUN
Xref: sparky comp.sys.amiga.programmer:17367 comp.sys.amiga.hardware:21512
From: TomK@cup.portal.com (Tom R Krotchko)
Newsgroups: comp.sys.amiga.programmer,comp.sys.amiga.hardware
Subject: Re: Attn Commodore: You are making a Big Mistake (Hardware
Date: Mon, 14 Dec 92 18:58:07 PST
Organization: The Portal System (TM)

>> Yet, Legends of Valour, a fast scrolling game does work. And doesn't
>> blow away the OS.
>
>Fast scrolling ? Maybe on a A4000, they should be fined for
>releasing such a game for the A500 -slowest game I've ever seen
>on an Amiga,

Its pretty darned fast on a 4000. As in "wow...I'm getting dizzy".

But the real point is, *it works* on a 4000. A game that makes the power
light flash and makes the GURU appear doesn't do enough scrolling
that I can tell how fast it goes.


TomK@cup.portal.com
Tom Krotchko
From: bn@mndcrme.uoknor.edu (Bo Najdrovsky)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: DICE assembler error
Date: 17 Dec 92 07:22:39 GMT
Organization: Operation Mindcrime
X-Newsreader: TIN [version 1.1 PL6]

Jean-Guy Speton (Jean-Guy_Speton@tvbbs.wimsey.bc.ca) wrote:
: I'm stumped.  I've been doing a little testing with the unregistered DICE,
: and when trying to compile (using DCC) I get 10-15 "word offset too large"
: errors from DAS,  DC1 gives me no complaints.  I don't have a clue where to
: begin looking.  What should I be looking for?  Any help appreciated.

Use the large code/large data model. I had the same problem, and this
fixed it. (even though Matt claims that we should never have to use
large code model)

--
---------------------------------------------------------------------------
|  Bo Najdrovsky  bn@mndcrme.uoknor.edu bn@okcforum.uoknor.edu|    //	  |
|							      |   //	  |
|      "I remember now, I remember how it started..."         | \X/ AMIGA |
---------------------------------------------------------------------------
Newsgroups: comp.sys.amiga.programmer
From: shulick@navajo.ucs.indiana.edu (Sam Hulick)
Subject: More on ReadArgs() -- figured out some..
Originator: shulick@navajo
Reply-To: shulick@navajo.ucs.indiana.edu
Organization: Vallen Software
Date: Fri, 18 Dec 1992 01:39:38 GMT


Ok, I've figured out a little bit.  I have this:

  LONG arr[500];  /* plenty of space */

  memset(arr, '\0', sizeof(arr));
  rd = ReadArgs("I=Ignore/S,L=Learn/S,Filelist/F/A", arr, NULL);

  So if arr[0] == -1, that means the user said 'i' or 'ignore'
And if arr[1] == -1, then Learn is chosen.  And for arr[2], I get the
files picked.  Now this is a MAJOR problem if the user selects 200
files.  How in the world do I parse a string like: "file1 file2 ...
file200".  What I originally wanted was:

  rd = ReadArgs("Filelist/M/A,I=Ignore/S,L=Learn/S", arr, NULL);

except that when I parsed out the filelist, it wasn't a string.. just
garbage.  Like I said, I wish ReadArgs() was documented in
RMK:Libraries.  Any help would be GREATLY appreciated.. thanks.

-- 
    // Amiga 3000   ___ \ Sam Hulick: shulick@indiana.edu (NeXTmail OK!)
   // 68030 25 MHz /__/\ \ My opinions wear combat boots.  Or whatever.
\\// OS 2.04       \__\/ / "Walk!  Not bloody likely.  I am going in a
 \/                     / taxi."  --George Bernard Shaw
From: Tony-Preston@cup.portal.com (ANTHONY FRANCIS PRESTON)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: contract programmers wanted
Date: Tue, 15 Dec 92 08:25:25 PST
Organization: The Portal System (TM)

That is an interesting idea, but I believe C= CATS has already done
something similar.  They are collecting a database of all developers
and have a list available.  

o
Newsgroups: comp.sys.amiga.programmer
From: dingebre@imp.sim.es.com (David Ingebretsen)
Subject: Re: MPEG on the Amiga
Reply-To: dingebre@imp.sim.es.com (David Ingebretsen)
Organization: Evans & Sutherland Computer Corp., Salt Lake City, UT
Date: Fri, 11 Dec 1992 23:25:01 GMT

In article <1ga0g2INN6a0@uni-paderborn.de>, tron@uni-paderborn.de (Matthias Scheler) writes:
> |> Dale Luck ported it for his X11 system running under AmigaOS. He reported
> |> 2fps on an 040 equipped Amiga. A lowly A500 would probably spit out a frame
> |> every 30 or 40 seconds.
> 
> There's a Amiga MPEG Player on amiga.physik.unih.ch. I couldn't test it yet,
> because the SS10 corrupted my MS-DOS transfer disk.
> 
> -- 
> Matthias Scheler                                         tron@uni-paderborn.de
> University of Paderborn (Germany)

However, the current version requires DOS 3.0. A version for 2.X was promised
in the readme file.

-- 
	David

	Disclaimer: The content of this message in no way reflects the
	            opinions of my employer, nor are my actions
		    encouraged, supported, or acknowledged by my
		    employer.
Newsgroups: comp.sys.amiga.programmer
From: jimomura@tndb.UUCP (Jim Omura)
Newsgroups: comp.sys.amiga.programmer,comp.sys.amiga.hardware
Subject: Re:  CISC and RISC
Distribution: world
Date: 18 Dec 92 09:08:59 EST
Organization: Not an Organization

In article <1992Dec16.185521.21232@ichips.intel.com> tjehl@sedona.intel.com (Timothy Jehl) writes:
>
>In article <1gnl0mINNpq2@crcnis1.unl.edu>, tbills@cse.unl.edu (Trent Bills) writes:
>> 
>> |> >What are the advantages of CISC and RISC?
>> 
>> RISC is based on several observations made by looking at compiler generated
>> code.  The first is that compiler writers have great difficulty in trying

...

>   There is one (and only one) reason for RISC processors : clock speed.
>There is absolutely no advantage to having a lesser instruction set unless
>you can make the device run faster.

...

>   On the die area front, we are rapidly reaching the point where the
>computational logic on a high end processor is being dwarfed by the
>on chip storage.  Minor area savings in the computation are becoming
>less important, so expect 1) RISC processors to become more complex,
>as the process technology becomes available to allow high speed operation
>while performing complex tasks, and 2) CISC processors to move to both
>super-scaler and super-pipeline as the processing area becomes cheaper.
>In addition, expect the instructions sets of both types of processors to
>start expanding to allow conditional execution commands.  As the pipelines
>get deeper, the penalty for branches get more expensive.  Instructions
>which allow you to do conditional execution without branching will become
>vital to maintain code throughput.

...

     Putting this into context, with the current trend to multiple
processing to handle graphics and sound (DSPs are coming), you can
isolate the various processors to an extent, but there are going to
be times where the various busses are going to be the main bottlenecks.
Fancy DMA schemes will have to be used to optimize the resolution
of the contentions.  But the less a processor needs to access the
buss the better.  Well now, doesn't it sound like a good idea if
I can have 1 instruction that requires 2 buss cycles, leaving the
buss free for the graphics or sound processors, while the CPU does
the work of maybe 3 or 4 instructions?  Superscalar is going to mean
even more buss contention problems for such situations.  So at bottom,
there are going to be a lot of good reasons to have CISC processors
in some systems.  In fact, I expect we have seen the last of the
"everbody will either have either type X or type Y CPUs" and there
are going to be a fairly wide range of processors commonly used.

--

Jim Omura, (416) 652-3880
'jimomura@lsuc'
From: jesup@cbmvax.commodore.com (Randell Jesup)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Detecting root directories
Date: 11 Dec 92 22:20:19 GMT
Reply-To: jesup@cbmvax.commodore.com (Randell Jesup)
Organization: Commodore, West Chester, PA

rick@IMD.Sterling.COM (Richard Ohnemus) writes:
>>>How can I detect if a Locked directory is a root directory

>>Pass the device part to GetDeviceProc and if the dvp_Lock field is zero, 
>>the name refers to a root directory. Don't forget FreeDeviceProc after-
>>wards. Under 1.3 use DeviceProc/IoErr.

	"device part"?  He has a lock, not a path.  He'd have to call 
NameFromLock() to get a path (which walks to the root using ParentDir)!

>    parent = ParentDir(lock);            /* 0 if lock is root of filing system */
>    if (!(root = parent == (BPTR) NULL))
>        UnLock(parent);                  /* release parent lock */
>
>This should work on all versions of AmigaDos >= 1.0 (At least I think it does.

	I prefer the ParentDir() approach.  No version checks needed, and it's
also lower overhead, even if you start with a string.  This is how NameFromLock
finds the root.

-- 
To be or not to be = 0xff
-
Randell Jesup, Jack-of-quite-a-few-trades, Commodore Engineering.
{uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.cbm.commodore.com  BIX: rjesup  
Disclaimer: Nothing I say is anything other than my personal opinion.
Newsgroups: comp.sys.amiga.programmer
From: kopnicky@great-gray.owlnet.rice.edu (Lyle Warren Kopnicky)
Subject: Emacs and SAS/C
Organization: Rice University, Houston, Texas
Date: Tue, 15 Dec 1992 08:58:22 GMT

I have just recently purchased SAS/C 6.0 and I know it allows you to
use whatever editor you wish.  This can be accomplished by changing a
tooltype or something.  But don't you also have to change the
appropriate ARexx scripts for use with the message browser?  I'm using
gnuemacs.  If anyone had the appropriate scripts, it would be very
helpful.  Thanks.

--
+----------------------------Ren & Stimpy--------------------------------+
| "Psst. Hey Guido. It's all so clear to me now. I'm the keeper of the   |
| cheese. And you're the lemon merchant. Get it? And he knows it. That's |
| why he's gonna kill us. So we gotta beat it. Yeah. Before he lets      |
| loose the marmosets on us! Don't worry, little missy! I'll save you!"  |
+--------------- Quantum Seep -- kopnicky@owlnet.rice.edu ---------------+
Newsgroups: comp.sys.amiga.programmer
From: walker@twix.unx.sas.com (Doug Walker)
Subject: Re: alleged Bug in SAS/C V6.1? IS NOT A BUG, but...
Originator: walker@twix.unx.sas.com
Date: Fri, 18 Dec 1992 13:46:51 GMT
Distribution: comp
Organization: SAS Institute Inc.


In article <MfAFgcS00hsBMfL35d@cs.cmu.edu>, mjw+@cs.cmu.edu (Michael Witbrock) writes:
|> However.
|> ~(unsigned short int)0 [the new case that I'm annoyingly introducing], 
|> is  [unsigned int] 1111 1111 1111 1111B   i.e. a large unsigned number!
|> (but still an int, which won't fit into an unsigned short) and CAN'T be
|> written as -1
|> which the compiler does in its warning. 
|> 
|> So the score of now, I think,  SAS/C 1, detractors [well, not really, but...] 1
|> 
|> michael

No, it's now SAS/C 2 opposition 0.

~(unsigned short)0 is the expression.  The type of the expression is signed int.

Reread your K&R quote about the ~ operator:  "The default integer promotions 
will be performed" or some such statement is in there.  The default integer 
promotions are:

   char           -> int
   unsigned char  -> int
   short          -> int
   unsigned short -> int
   int            -> int
   unsigned int   -> unsigned int
   long           -> long
   unsigned long  -> unsigned long

in other words, everything shorter than "int" is promoted to "int",
regardless of whether it was signed or unsigned before the promotion.

What you have is ~ applied to an unsigned short.  The unsigned short
gets promoted to int, with value 0.  The ~ is applied, giving the
hex pattern 0xffffffff and the type "int".  0xffffffff as an "int"
is the value -1.

There's just no way to get any type shorter than int from the ~
operator.  You have to cast the result of ~, not the operand:

  (unsigned short)~0

Of course, there is always

   0xffff

-- 
  *****
=*|_o_o|\\=====Doug Walker, Software Distiller====== BBS: (919)460-7430 =
 *|. o.| ||                                          1200/2400/9600 Dual
  | o  |//     For all you do, this bug's for you!
  ====== 
usenet: walker@unx.sas.com                            bix: djwalker 
Any opinions expressed are mine, not those of SAS Institute, Inc.
From: heinz@edohwg.adsp.sub.org (Heinz Wrobel)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: 1200 Compatibility!
Date: 9 Dec 92 19:12:49 GMT
Organization: Edotronik GmbH

In article <BywBA9.9KA@compsci.liverpool.ac.uk> scst72@csc.liv.ac.uk (Mr. P. Lewin) writes:
>    The only system routine I use is to get the copper list address back at the end of my code. All of my code turns redefines all interupt channels, exceptions etc. So basically you just got the processor, hardware and some memory.

Which one?

>    My code is 100% compatible on all machines although I've never tried a 4000 (YET!!!).

What if the A1300/A5000/bla doesn't have copper?


--
Heinz Wrobel, Edotronik GmbH (ECG018)
FAX +49 89 850 51 25 / TEL +49 89 850 25 20 (HOME!&VOICE, sometimes...)
From: mbs@adastra.cvl.va.us (Michael B. Smith)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: GCC & Amiga.lib
Distribution: world
X-NewsSoftware: GRn-beta 1.16g (10.12.92) by Michael B. Smith & Mike Schwartz
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Date: 20 Dec 92 07:35:41 EDT
Organization: Well, I haven't decided on a name yet...

In article <1992Dec20.015634.12903@newshub.ccs.yorku.ca> wlanders@nexus.yorku.ca (W L Anderson) writes:
> I'm trying to do some programming  using  Intuition  and  various
> other  libraries using GNU C.  I tried using hunk2gcc to take the
> amigal20.lib from DICE and creating a libamiga.a, but as soon  as
> I  tried  to use the SystemTags() function call, I got a EMT sig-
> nal.  My question is, is anybody actually doing  any  development
> with GNU C with a created version of the amiga.lib?  What did you
> do?

I didn't use Matt's .lib to create libamiga.a, I used the one from the
Native Developer's update. A couple things: when you are running 'ar' and
'hunk2gcc', make sure your stack is big enough, like 250K.

Secondly, check closely as to whether or not "libamy.a", included with
GCC 2.2.2, will work for you. It should. It is all of the routines from
the inlines headers merged together into a library.

Thirdly, did you remember to open dos.library? Without some special work,
GCC does not do that automatically like DICE does.

Fourthly, I suggest using the inline headers. They tend to generate better
code (like the pragma concept in DICE/SAS/Manx).
--
  //   Michael B. Smith
\X/    mbs@adastra.cvl.va.us  -or-  uunet.uu.net!virginia.edu!adastra!mbs
From: ry41@rz.uni-karlsruhe.de (Bernhard Moellemann)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Hardware Reference Manual
Date: 12 Dec 1992 13:22:20 GMT
Organization: University of Karlsruhe, Germany
Distribution: world
NNTP-Posting-Host: tp70.rz.uni-karlsruhe.de

In article <6416@pdxgate.UUCP>, idr@rigel.cs.pdx.edu (Ian D Romanick) writes:
>The difference is that with a
>manual people will know the right way to do it!  The idea behind having a
>manual is to prevent the complaints of, "Hey, this (what ever) doesn't work
>on my machine!"

No. There is a lot of stuff (games or tracker, not demos) which run if
I reset the VBR and deactivate caches. And C= stated in all exec manuals
(at least up from 1.1):
"Do not use self modifying code, do not use tight loops for timing and
the IntVecs may move on 68010 or higher."

The people just ignore that. So it doesn't matter if you give them the
info or not. They have to learn it the hard way.

>You'll notice that a lot of the stuff that really breaks is older stuff.

Is Populous II "older stuff" ?

-- 
 Bernhard Mllemann   <spare  space>   Chairman of the Nessy-Fan-Club   //
 internet=zza@rz.uni-karlsruhe.de <space> FIDO=2:241/7506.42  IRC=ZZA  //
 nessynet=008  Lifenet=77:7700/11.42  greetings to my Marsupilami  \\ //
 2000/500 Technical Reference Manual:  "A1000, the original Amiga"  \X/
Newsgroups: comp.sys.amiga.programmer
From: tomasa@hemul.nada.kth.se (Tomas Arvidsson)
Newsgroups: comp.sys.amiga.programmer,comp.sys.amiga.hardware
Subject: Re: Attn Commodore: You are making a Big Mistake (Hardware
Date: 14 Dec 92 22:59:53 GMT
Organization: Royal Institute of Technology, Stockholm, Sweden

In <amipb.04wr@amipb.gna.org> amipb@amipb.gna.org (Philippe Berard) writes:

>    You miss a serious point here : most of the games break on the 4000
>    because of the instruction/data cache. Turn it off, and 80-90% or
>    your games will work again.

I think that you are the one who has missed a point or two...
Yes, some (most) games work if you turn off the caches (and put the VBR and
the supervisor stack in chip-mem) but _why_ should I have to turn off the 
caches? I can't see a single reason why I should have to do that.

There is no excuse for sloppy programming!

>                                   -- Philippe


-- 
Tomas Arvidson			 			     ///
d91tar@csd.uu.se,					    ///
tomasa@nada.kth.se, tomasa@sprawl.adsp.sub.org   	\\\///
Expressed opinions are mine unless stated otherwise      \XX/
-- 
Tomas Arvidson			 			     ///
d91tar@csd.uu.se,					    ///
tomasa@nada.kth.se, tomasa@sprawl.adsp.sub.org   	\\\///
Expressed opinions are mine unless stated otherwise      \XX/
Newsgroups: comp.sys.amiga.programmer
From: wild@nessie.cs.id.ethz.ch (Markus Wild)
Subject: Re: Console RAW mode.
Organization: Swiss Federal Institute of Technology (ETH), Zurich, CH
Date: Thu, 17 Dec 1992 23:24:19 GMT

In article <1992Dec17.051157.23971@serval.net.wsu.edu> rnelson@wsuaix.csc.wsu.edu (roger nelson;S23487) writes:
>Is there an escape sequence that will put the CLI shell into
>unbuffered mode and one that will enter RAW mode.  

Not an escape sequence, but a packet you can send to the handler. It's
called ACTION_SCREENMODE (or SCREEN_MODE don't remember). This should be
feasible in C, I guess you could get into some troubles trying to do it
with scheme (unless your scheme has been enhanced by Amiga-isms).

>    I would like to read the next key pressed with getc() in C or
>    (read-char) in scheme without waiting for the return key to be pressed.
>   
>    If a function key, cursor on num-keypad key is pressed, I want to be
>    able to read the escape sequence.

The above trick switches the CON window into RAW mode, so you get the
same behavior as you'd get if you opened a RAW window for I/O. Unless you
specifically request raw keycodes, you still get plain ascii values, and
escape sequences for the functions keys, no problem here.

-Markus
-- 
Markus M. Wild    -  wild@nessie.cs.id.ethz.ch  |  wild@amiga.physik.unizh.ch 
Vital papers will demonstrate their vitality by spontaneously moving
from where you left them to where you can't find them.
Newsgroups: comp.sys.amiga.programmer
From: remilld@ccu.umanitoba.ca (Jason Remillard)
Subject: Re: Cobol for the Amiga?
Organization: University of Manitoba, Winnipeg, Canada
Date: Thu, 17 Dec 1992 01:28:03 GMT

In <paulk.2oqo@terapin.com> paulk@terapin.com (Paul Kienitz) writes:

>> to answer everyones question, a good reason why we need one is
>> because all those Ami users that are in college going through the
>> computer science program most likely have to take Cobol at one time
>> or another as part of their curiculum.
> 
>I never had to, and I went to a cheap school that was real heavy on
>that sort of thing.
> 
>But think of something else:  so many programmers refuse to touch
>COBOL nowadays that the few who are willing to really get into it
>get LARGE money for maintaining those old programs.

Sorry, but have you checked out the *.*.*.jobs groups lately..


They are laden with Cobol, esp. HP, positions..

I know, I really hate COBOL.  In my *COLLEGE* course, I have to write
almost 10 programs with an average of 600 lines.  SYstem calls, forms
and the like..  But, Cobol 85 is *much* better than System 360 Assembler.
We started cobol just when I started liking the 20 year assembler.. (ARGH!!
Is that possible).

Anyways, unfortunately there are alot of companies out there who have
old apps in Cobol and *will* pay big bucks for programmer/maintainers..


-- 
-----------------------------------------------------------------------------
Jason L.M. Remillard		REMILLARD@ceddwntwn.lan1.umanitoba.ca
MicroLab Assistant		Jason_Remillard@UManitoba.CA
University of Manitoba		REMILLD@ccm.umanitoba.ca
Newsgroups: comp.sys.amiga.programmer
From: mlelstv@specklec.mpifr-bonn.mpg.de (Michael van Elst)
Subject: Re: Hardware Reference Manual
Organization: Max-Planck-Institut f"ur Radioastronomie
Date: Sat, 12 Dec 1992 19:43:40 GMT

In <1992Dec10.132828.10409@cas.org> vjh21@cas.org (Vince Herried) writes:
>I've got a NON game example of why it is important to have
>a good hardware reference manual, without which my program
>appears to me to be impossible to write.

>I'm writing a 'logic analyser' program that will take input from
>the parallel port (or possibly game ports and serial port) capture
>it and then display it.

Well, there's some kind of misunderstanding. What we will not see
is documentation on the AGA chipset, and this is IMHO a good decision.


Regards,
-- 
Michael van Elst
UUCP:     universe!local-cluster!milky-way!sol!earth!uunet!unido!mpirbn!p554mve
Internet: p554mve@mpirbn.mpifr-bonn.mpg.de
                                "A potential Snark may lurk in every tree."