HDTenEightyP/NetNews huggingface dataset:
From: nelson@crynwr.com (Russell Nelson)
Newsgroups: comp.unix.bsd
Subject: [386BSD]: DEPCA support in future?
Date: 1 Sep 92 14:20:19 GMT
Organization: Crynwr Software

In article <veit.715250703@du9ds3> veit@du9ds3.uni-duisburg.de writes:

   In <1992Aug28.153333.3797@desire.wright.edu> ejones@desire.wright.edu writes:

   >Are there any plans to include a DEC DEPCA ethernet card in the supported
   >ethernet contollers? I have a 16 bit DEC card that I really like, but
   >in order to use 386BSD I need to swap it with a 3com503 board. Also, will
   >it be possible in the future to run X386 on a VGA screen instead of SVGA?
   >Thanks for the help.
   
   >       Ed Jones
   >       Wright State University
   >       ejones@desire.wright.edu

   If my memory serves me right, the DEPCA uses an INTEL 82586 LANCE. There was
   a recent posting for an "ie_driver" based on this chip. It should work, or it
   should be not too difficult to modify it.

Nope.  The LANCE is an AMD part.  The 82586 is an Intel part.  The
LANCE is actually fairly easy to interface to, and DEC uses shared
memory, so you don't have to deal with bus mastering like on most
LANCE-based boards, e.g. ni6510 and NTI.

-russ <nelson@crynwr.com>  I'm proud to be a humble Quaker!
Crynwr Software            Crynwr Software sells packet driver support.
11 Grant St.               315-268-1925 Voice
Potsdam, NY 13676          315-268-9201 FAX
Newsgroups: comp.unix.bsd
From: colin@marsh.cs.curtin.edu.au (Colin Manning)
Subject: Re: What is included in the ectdist directoy?
Organization: Curtin University of Technology
Date: Wed, 2 Sep 1992 03:16:55 GMT

kilroy@mik.uky.edu (Paul S. Kilroy) writes:

>Hi, 
>  does anyone have a list of the files in the ectdist distribution?

You could read the MANIFEST.ETC01 (not sure if thats exact) on agate,  but it
is the manifest file for the srcdist.  Could someone fix this please?

>thanks
>paul
>(kilroy@mik.uky.edu)
>--
>                       -Paul   (kilroy@mik.uky.edu)
--
Colin [colin@cs.curtin.edu.au]

"Knowledge is not knowing all the answers, but knowing where to find them."
                                                                  -anon.
Newsgroups: comp.unix.bsd
From: rpr@st1-par.oce.nl (Rob Prikanowski)
Subject: Re: An overview of 17" monitors
Organization: OCE Nederland B.V.
Date: Tue, 1 Sep 92 07:11:07 GMT

In article <rcpt.715301018@rwb.urc.tue.nl> rcpt@urc.tue.nl writes:
>
>monitor type              refresh rate   dot pitch  MPR-II  price
>                         1280x1024 (Hz)     (mm)             (DM)
>ViewMagic MX-17H Trinitron     ?             ?         ?     2388

This one is actually the MAG MX17H. It doesn't use a Trinitron tube, but a
Hitachi INVAR tube (flatscreen). The dot-pitch is 0.26mm and it is NOT MPR-II (I
don't know if that means that it is not tested or that it didn't qualify). I'm
not sure about the refresh rate at 1280x1024, but at 1024x768 it does 73 Hz.

I have one and it's great!

Greetings,

Rob Prikanowski (rpr@oce.nl)
................................................................................

     |   |     Rob Prikanowski (rpr@oce.nl)
   -[ ]-[ ]-      
     |   |     Oce Nederland B.V.         Direct dial: +31 77 593530
               P.O. Box 101               Telefax    : +31 77 595450
               5900 MA Venlo
               The Netherlands

   This note does not necessarily represent the position of
   Oce Nederland B.V. Therefore no liability or responsibility for
   whatever will be accepted.

................................................................................

      ###########################################################
      #  This note does not necessarily represent the position  #
      #     of Oce-Nederland B.V. Therefore no liability or     #
      #      responsibility for whatever will be accepted.      #
      ###########################################################
Newsgroups: comp.unix.bsd
From: colin@marsh.cs.curtin.edu.au (Colin Manning)
Subject: Re: virtual tty's for 386bsd ?
Organization: Curtin University of Technology
Date: Wed, 26 Aug 1992 03:52:04 GMT

ado@bigcomm.gun.de (Christoph Adomeit) writes:

>Hi Freaks,

>i installed 386bsd and I like it very much. Lots of software compile and run 
>without any problems.
>But there is one thing I really miss: Virtual consoles.
>You know what I mean ? Logging in on the console several times, switching
>between the tasks by a hot key (e.g. ALT + Fkeys), Compiling on one Task,
>editing on the second and testing on the third ... .
There is iScreen.  I believe it is in the etcdist, but I got it from elsewhere.
I can't remember where.  Try an archie search for screen.

>Are virtual consoles available for 386bsd ?
--
Colin [colin@cs.curtin.edu.au]

"Knowledge is not knowing all the answers, but knowing where to find them."
                                                                  -anon.
Newsgroups: comp.unix.bsd
From: cl45@cunixf.cc.columbia.edu (Ching-Tse Liu)
Subject: Help with installing srcdist in 386bsd
Reply-To: cl45@cunixf.cc.columbia.edu (Ching-Tse Liu)
Organization: Columbia University
Date: Thu, 27 Aug 1992 18:10:05 GMT

Hi,

	I have problem installing the source distribution. Right after
I installed the binaries distribution, I typed "rm bin01.*" then "
loadfd". Now when it came to src01.37, the system stopped and refused
to copy anymore files and didn't respond to control-c. I had no choice
but to reboot. Of course it came up with the content of /tmp cleared.
What did I do wrong ? I tried this twice with the same problem.
	Is it possible to install the source with the binaries installed?
Or do I have to start all over ? Any help will be greatly appreciated.

       		                     	***********************
--cliu@merlin.appmath.columbia.edu	*   CLifton T. Liu    *
--cl45@cunixf.cc.columbia.edu		***********************

Newsgroups: comp.unix.bsd
From: witr@rwwa.COM (Robert Withrow)
Subject: Re: zsh for 386bsd
Reply-To: witr@rwwa.com
Organization: R.W. Withrow Associates
Distribution: usa
Date: Wed, 26 Aug 1992 20:40:22 GMT

In article <1992Aug26.144114.16304@ntuix.ntu.ac.sg>, 
  eoahmad@ntuix.ntu.ac.sg (Othman Ahmad) writes:
| peter@panther.cosy.sbg.ac.at (Peter Burgstaller) writes:
| : I don't have enough space on my harddisk to install the complete
| : source-distribution. 
| You do not need to install the entire source-distribution.
| With my 60Mbyte space for 386bsd, I managed to install the kernel sources
| and compile it.

Could you summarize the necessary steps?  Lot's of us would like that.

-- 
---
 Robert Withrow, R.W. Withrow Associates, Swampscott MA 01907 USA
 Tel: +1 617 598 4480, Fax: +1 617 598 4430, Net: witr@rwwa.COM
Newsgroups: comp.unix.bsd
From: colin@marsh.cs.curtin.edu.au (Colin Manning)
Subject: Re: backup w/ compression for UN*X?
Organization: Curtin University of Technology
Date: Thu, 3 Sep 1992 04:48:26 GMT

paoletti@cps.msu.edu (David R. Paoletti) writes:

>Does anyone know of any software for UN*X, 386BSD or otherwise,
>that does on-the-fly compression?  Thinking of looking into
>writing my own, or getting some 386BSD people together to help,
>as soon as I get my new machine built with enough HD space to
>re-compile 386BSD...  This would be really nice for people with
>floppies, or even people who want to save on tapes.

GNU tar has a -z option.  This compresses the tar file.

OR

You could use tar -cf - <directory> | compress | tar -cf -

(I think the second one should work, but if you have GNU tar use that.)

>I realize that this isn't the standard UN*X way to do backups,
>but a compressing dump program would be really useful to students.

>Dave Paoletti :)


Colin.

--
Colin [colin@cs.curtin.edu.au]

"Knowledge is not knowing all the answers, but knowing where to find them."
                                                                  -anon.
Newsgroups: comp.unix.bsd
From: sitongia@hao.ucar.edu (Leonard Sitongia)
Subject: [386bsd] does the ethernet device have a /dev entry?
Reply-To: sitongia@hao.ucar.edu (Leonard Sitongia)
Organization: High Altitude Observatory/NCAR, Boulder CO
Distribution: usa
Date: Thu, 3 Sep 1992 01:44:44 GMT

I'm all confused about why my system wont recognize the 3C503 ethernet
board.  I see that the probe routine in the sources doesn't print anything,
but the attach routine does.

Anyway, should there be a /dev entry?  How do you figure out the major
device number for it?  Is it a bdev or a cdev?  How does all that ioconf.c
stuff work?  

I take it that the driver entry points dont go into the conf.c file, and the
config command creates ioconf.c, which somehow links into the driver entry
points through the ecdriver structure (plus something else, but I just care
about probe and attach right now :-).

But how the heck is the major device number defined?  Not that it matters,
though, as I would think that the probe wouldn't require /dev/ec0 to exist
anyway.

So, is the problem the IRQ number?

Thanks for your time.
-- 
--Leonard E. Sitongia           HAO System Manager                 
sitongia@ncar.ucar.edu          voice: (303)497-1509   fax: (303)497-1589
High Altitude Observatory       P.O. Box 3000 Boulder CO  80307
Newsgroups: comp.unix.bsd
From: jsaker@cwis.unomaha.edu (James R. Saker Jr.)
Subject: deinstalling 386BSD 0.1 single partition
Keywords: 386BSD,deinstall,DOS
Organization: University of Nebraska at Omaha
Date: Sat, 29 Aug 1992 19:10:36 GMT

After running 386BSD 0.1 on my 486/33 system for about a month, I am
forced to return to the DOS world for the semester to do COBOL work.
However, when I installed 386BSD from the installer disk, I let it
set up my system as one large BSD partition (where it apparently
reconfigured part of the boot partition of my 212MB IDE drive).

Although I went into fdisk and changed the partition to a DOS type,
reformatted and restored the drive from tape backup, it's not able
to boot up on its own (I can only access it after booting from
floppy).

Any hints on how to reset the drive to boot from C: again?

Many thanks! Also, if someone out there knows of a COBOL compiler
(noncommercial) for the BSD world...I'd be thrilled and wouldn't
have to go back to DOS! 


.  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .
.  Jamie Saker					jsaker@cwis.unomaha.edu    .
.  Network Costing Analyst			Business/MIS Major	   .
.  Telenational Communications			Univ. Nebraska at Omaha	   .
.  (402) 392-7548							   .
.  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .
Newsgroups: comp.unix.bsd
Subject: Re: 386bsd:ne1000 and /dev/lp probs
From: scott@clmqt.marquette.MI.US (Scott Reynolds)
Date: Sat, 29 Aug 1992 07:34:28 EDT

In <1992Aug26.135535.100@Urmel.Informatik.RWTH-Aachen.DE>
	kuku@acds.physik.rwth-aachen.de (Christoph Kukulies) writes:

>In article <714768522snx@nutt.demon.co.uk>, pnutty@nutt.demon.co.uk (Peter C Allnutt) writes:
>>1: I can't get my ne1000 cards to work. Upon booting 386bsd sees
>>the cards but reports the wrong ethernet address. It skips every
>>other byte of the cards address.

The unofficial (though correct) fix to this is to change the definition
of the "boarddata" variable.  It currently reads

	static u_short	boarddata[16];

and it should read

	static u_char	boarddata[16];

(I'm doing this from memory, but the relevant piece of information is
the change from a 16-bit unsigned short int to an 8-bit unsigned
character.)

>Could the one who posted a ne1000/2000 driver enhancement please re-post
>or leave a mail. Thank you.

I'm interested in any enhancements to the driver, also; perhaps we can
get it included in the unofficial patches on agate?
--
scott@clmqt.marquette.MI.US       |      Ich bin ein Virus.  Mach' mit und
Scott Reynolds                  --+--    kopiere mich in Deine .signature.
Enterprise Information System     |
        Revive us, oh Lord!       |
Newsgroups: comp.unix.bsd
From: ant@brolga.cc.uq.oz.au (Anthony Murdoch)
Subject: How to access LPT1: under 386bsd ?
Organization: Prentice Centre, University of Queensland
Date: Fri, 28 Aug 1992 13:11:38 GMT


Hi,

This time I checked the FAQ first :)

I saw a post here asking this same question, but no replies.  /dev/lp
seems to be missing from the distribution.  It's not listed in MAKEDEV.
Does 386bsd support lpt1 ?  The manuals seem to indicate it does.

Thanx muchly
ant
Newsgroups: comp.unix.bsd,comp.os.os2.misc
From: jlu@cs.umr.edu (Eric Jui-Lin Lu)
Subject: DOS + OS/2 2.0 + 386bsd 0.1 installation .....
Date: Fri, 28 Aug 1992 22:04:23 GMT
Organization: University of Missouri - Rolla
Originator: jlu@mcs213e.cs.umr.edu


Dear netters,

I have browsed thru the FAQs without any luck, although I think this
question should be mentioned somewhere.  If I missed something, please
no flame.

After spending nights of reformats, reboots, and reinstallations, I
kinda came out a wierd combination of DOS, OS/2, and 386bsd in one
hard disk.  I used os-bs as the boot manager and its menu looks
like DOS -- part 0, OS/2 part 1, and 386bsd in part 3.  Partition 2
is for logical HPFS OS2.  I'm not quite satisfied with this.  Since
when I choose OS/2, OS2 boot manager menu comes up.  I wish to
eliminate this OS/2 boot manager totally.  Is there a way to do
this? (this will save me another ~1.5MB.)  Thanks!

--Eric
--jlu@cs.umr.edu
-- 
***************************************---       Grad. student 		---*
* Obviousness is always the enemy of  *   \     Jui-Lin Lu (Eric)      /   *
* correctness.  -- Bertrand Russell   *   /      jlu@cs.umr.edu        \   *
***************************************---   Univ. of Missouri-Rolla    ---*
Newsgroups: comp.unix.bsd
From: steve@nuchat.sccsi.com (Steve Nuchia)
Subject: Re: SCSI-2 tape and disk drives recommendations
Organization: South Coast Computing Services, Inc.  Houston
Distribution: comp
Date: Fri, 28 Aug 1992 17:53:22 GMT

In article <1992Aug26.105836.16450@olymp.informatik.uni-bonn.de> volker@sfb256.iam.uni-bonn.de ( Volker A. Brandt ) writes:
>I'd stay away from Figitzsu.  On the other hand, I can only recommend that you
>get a Fujitsu disk drive :-)  I'm using one with 386BSD.  I bought an IBM disk,

I am extremely happy with my Fujitsu 5-1/4" drives, but the original
poster mentioned noise as a consideration.  The Fujitsu 226X drives
are not as loud as a train wreck, but they are close.  If you have
to sleep with them, think about something else.

I use a 3-1/2" Maxtor at one of my client's sites -- nice little drive.

-- 
Steve Nuchia      South Coast Computing Services, Inc.      (713) 661-3301
Newsgroups: comp.unix.bsd
From: blo@fwi.uva.nl ()
Subject: 386bsd FAQ
Keywords: 386bsd FAQ ?
Organization: FWI, University of Amsterdam
Date: Sun, 30 Aug 1992 15:05:24 GMT

Hello everyone out there,

Is there a FAQ list on 386bsd and X386?
Thanx
Ben Lo
From: julian@tfs.com (Julian Elischer)
Newsgroups: comp.unix.bsd
Subject: Makefile change to run newvers.sh
Date: 29 Aug 92 20:18:50 GMT
Distribution: comp
Organization: TRW Financial Systems

Many people who have made their own kernel configurations
have discovered that their kernel won't build until they
change their Makefile to include a reference to vers.o
(missing symbol _version)

I include the following patch to the default makefile
so that the built makefiles are correct

+----------------------------------+       ______ _  __
|   __--_|\  Julian Elischer       |       \     U \/ / On assignment
|  /       \ julian@tfs.com        +------>x   USA    \ in a very strange
| (   OZ    ) 2118 Milvia st. Berkeley CA. \___   ___ | country !
+- X_.---._/  USA+(510) 704-3137(wk)           \_/   \\            
          v

---------8X--------8X---------8X----------
*** /usr/src/syschanges/sys.originals/i386/conf/Makefile.i386	Mon Feb 24 14:52:46 1992
--- /usr/src/sys.386bsd/i386/conf/Makefile.i386	Mon Aug 24 13:02:30 1992
***************
*** 38,44 ****
  SYSTEM_OBJS=locore.o ${OBJS} param.o ioconf.o conf.o
  SYSTEM_DEP=Makefile symbols.sort ${SYSTEM_OBJS}
  SYSTEM_LD_HEAD= 	@echo loading $@; rm -f $@
! SYSTEM_LD= @${LD} -z -T FE000000 -o $@ -X ${SYSTEM_OBJS}
  SYSTEM_LD_TAIL= @echo rearranging symbols; symorder symbols.sort $@; size $@; chmod 755 $@
  
  %OBJS
--- 38,44 ----
  SYSTEM_OBJS=locore.o ${OBJS} param.o ioconf.o conf.o
  SYSTEM_DEP=Makefile symbols.sort ${SYSTEM_OBJS}
  SYSTEM_LD_HEAD= 	@echo loading $@; rm -f $@
! SYSTEM_LD= @${LD} -z -T FE000000 -o $@ -X vers.o ${SYSTEM_OBJS}
  SYSTEM_LD_TAIL= @echo rearranging symbols; symorder symbols.sort $@; size $@; chmod 755 $@
  
  %OBJS
***************
*** 63,71 ****
  
  locore.o: assym.s ${I386}/i386/locore.s machine/trap.h machine/psl.h \
  	machine/pte.h vector.s ${I386}/isa/icu.s ${I386}/isa/isa.h \
! 	${I386}/isa/icu.h
  	${CPP} -I. -DLOCORE ${COPTS} ${I386}/i386/locore.s | \
  		${AS} ${ASFLAGS} -o locore.o
  
  # the following is necessary because autoconf.o depends on #if GENERIC
  autoconf.o: Makefile
--- 63,74 ----
  
  locore.o: assym.s ${I386}/i386/locore.s machine/trap.h machine/psl.h \
  	machine/pte.h vector.s ${I386}/isa/icu.s ${I386}/isa/isa.h \
! 	${I386}/isa/icu.h vers.o
  	${CPP} -I. -DLOCORE ${COPTS} ${I386}/i386/locore.s | \
  		${AS} ${ASFLAGS} -o locore.o
+ 
+ vers.c:	Makefile
+ 	sh ../../conf/newvers.sh
  
  # the following is necessary because autoconf.o depends on #if GENERIC
  autoconf.o: Makefile
Newsgroups: comp.unix.bsd
From: eje@irenaeus.mlo.dec.com (Eric James Ewanco)
Subject: Re: How download X386 to floppies?
Reply-To: ewanco@kalvin.enet.dec.com
Organization: Digital Equipment Corporation
Date: Thu, 27 Aug 1992 19:05:05 GMT


In article <22269@venera.isi.edu>, allard@isi.edu (Dennis Allard) writes:
> From: allard@isi.edu (Dennis Allard)
> Subject: How download X386 to floppies?
> Date: Wed, 26 Aug 92 15:36:41 GMT+5:00
> Organization: USC Information Sciences Institute

> My goal: create a set of floppies with the X386 distribution on them
>          and then extract that distribution onto my 386BSD.

> My situation:

>   At home: 386BSD binary distribution up and running on a 386-33 clone
>   At work: HP-UX and SunOS workstations, one which has a floppy drive

> I have already ftp'd the files core-{bin,server,fonts,inc,lib,man}-1.0.3.tar.Z
> from agate.berkeley.edu to a fileserver at work.  How can I create a
> multivolume set of floppies which I can then use to install X on my 386 at
> home?

> I cannot use MCOPY to move the files to floppies as each one is far too big
> to fit on a single floppy.  This has GOT to be a simple problem, what am
> I missing (besides a Unix User's guide, something which two decades of
> Unix users have missed)?

> Dennis
> allard@isi.edu
> (310)399-4740

I assume that you have a high-density 3 1/2" floppy on your machines at work.

Try this.  Find and compile GNU tar on your HP or Sun system.  (Maybe regular
tar will work, I haven't tried it.) Put your disk in the drive, and use

tar cvzf /dev/rrz4a -L 1440 <directory>

or whatever your favorite options (and whatever device your floppy is). It will
prompt you to swap disks.  Then simply transfer the floppies to your 386BSD
system:

tar xvZf /dev/rfd0a 

and that should work.  It works on my Ultrix system.

I should note that actually I may be lying; I don't think I've actually tried
to restore a multidisk compressed archive (I did see some notes on problems
with that) so you might try the same thing uncompressed.  However I know I can
read disks written by my Ultrix machine on 386; I've tried it with single
disks.

Eric
--
/=============================================================================\
| Eric Ewanco - Software Engineer     For the rash and outrageous opinions ex-|
| Digital Equipment Corp, Maynard MA  pressed herein I alone am responsible;  |
| ewanco@kalvin.enet.dec.com          they do not belong to DIGITAL(TM).      |
\==============================- 2 Th 2:15 -==================================/
From: eoahmad@ntuix.ntu.ac.sg (Othman Ahmad)
Newsgroups: comp.unix.bsd
Subject: Ported:f2c,Spice&EE programs,e.g.PetDingo
Date: 3 Sep 92 03:27:48 GMT
Organization: Nanyang Technological University - Singapore
X-Newsreader: Tin 1.1 PL4

I have ported f2c and Spice 2g6 to 386bsd 0.1.
f2c using gcc-1.39 because gcc-2.2.2 does not work, not on my
system without 80387 copro.

I've finished compiling petdingo from which is an estelle interpreter and
verifier, used to specify real-time communication protocols.

estelle is an ISO(?) standard. I've not gone into this in great detail but 
managed to generate the c++ output from petdingo for the example program,
a game called bump. However I failed to compile it.

These programs are useful to Electrical and Electronic engineers. I also
have ported espresso.

I post this message in hoping that I can share my experience with potential
EE students and researchers, working on similar PD software. We can share
problem solving or even consider enhancing the currently available PD software,
e.g. putting VLSI backend to estelle, etc.



--
Othman bin Ahmad, School of EEE,
Nanyang Technological University, Singapore 2263.
Internet Email: eoahmad@ntuix.ntu.ac.sg
Bitnet Email: eoahmad@ntuvax.bitnet
Newsgroups: comp.unix.bsd
From: nbladt@autelca.ascom.ch (Norbert Bladt)
Subject: Re: HELP: Can't install 386bsd-0.1 into own partition!
Keywords: 386BSD
Organization: Ascom Autelca AG, Guemligen, Switzerland
Date: Mon, 31 Aug 1992 14:13:35 GMT

veit@du9ds3.uni-duisburg.de (Holger Veit) writes:

>In <1992Aug31.062144.12176@rucs2.sunlab.cs.runet.edu> bmyers@rucs2.sunlab.cs.runet.edu (B.Myers) writes:

>[..]
>>Install won't create it's own partition on my machine. Every time I try
>>to install it it tells me I already have it installed and it only
>>asks me if I want to overwrite it. I say yes. Then it says use the 
>>whole disk, and I say no. Then it quits. 
>>Before that it says 0 mb free on disk.
[ text about installing and de-installing 386bsd deleted - NB.]

>Regarding the 0 MB problem: it seems that install want to have contiguous
>free space at the end of the disk, lots of MBs in the middle or at the beginning
>is "not existing".
>Creating a partition with fdisk (as the second partition on the disk, after some
>DOS or OS/2 partition) and changing the ID bit to A5 should make a partition
>386bsd is happy with (should ;-))
I did the following (without fiddling with the partition table entries):

Create a DOS primary partition (with DOS fdisk).
Create a DOS secondary partition and delete it, again.
Boot with the dist.fs floppy disk.
After succesful booting, install.
386BSD will happily use the secondary (now deleted) partition on
the disk for installation if you tell it to.

This happened on a no-name 486/25 with 16 MB RAM and Adaptec 1542B SCSI
controller (plus a CP-3100 100 MB Conner Harddisk).

I don't know whether this just works for SCSI systems, but I doubt it.
The reason why I did it this way was, that I tried to change the
partition ID to A5 but the offsets which were given (about 460 ff.)
must be wrong. I looked at sector 0 on the harddisk (with PC-Tools
edit disk feature) but found the following text in this section of
the bootblock: "No system disk ..."
I didn't want to overwrite this text, although nothing would happen,
it wouldn't have helped, anyway.

Norbert.
-- 
Norbert Bladt, Ascom Autelca AG, Worbstr. 201, CH-3073 Guemligen, Switzerland
Phone: +41 31 999 65 52			FAX: +41 31 999 65 44
Mail: nbladt@autelca.ascom.ch   UUCP: ..!uunet!mcsun!chsun!hslrswi!aut!nbladt