HDTenEightyP/NetNews huggingface dataset:
From: glenc@netcom.com (Glen Collins)
Subject: [386BSD] Help with install!!!! Please help!
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Distribution: na
Date: Sun, 8 Nov 1992 03:29:38 GMT

Hello all!

	My system:

	386 33/40
	4 megs ram
	AMI bios with the opti chip set
	SVGA card
	68 meg drive rll'ed to 104 megs

	I have been trying to install 386BSD for the last week. It will

	not get past the part of it saying hight level formating of
	386 BSD storage. I have used the debug option and it writes the
	386 partition ok, then make the root and swap space okay, then
	it will label the drive ok, then it goes down hill from there.
	I think there maybe a prolem with NEWFS. Is there any? Can
	someone forward their setting of their chipset to me? It seems
	strange to me that I am having this problem when noone else has.
	I have picked up the dist.fs from berkeley with t WD boot patch
	but it won't work either. I have also tried to goto the lowest
	speed the system will go (no turbo) and to no avail. Any one
	that can help me I would appriciate it!

Thans....Glen Collins
	(glenc@netcom.com)






Newsgroups: comp.unix.bsd
From: harry@atlas.socsci.umn.edu (Kuo-Chen Chang)
Subject: OLD Logitech Mouse setup??
Organization: University of Minnesota
Date: Sun, 8 Nov 1992 03:46:13 GMT

Hi netters!

	I finally have the X server up.  The problem was the name(s)
	of comport under /dev.  The installation created serial devices
	named /dev/ttyp0, /dev/ttyp1 ....  But in the generic Xconfig.sample
	file, they are named as /dev/tty00, /dev/tty01 ...  Once I corrected
	the naming problem, the Fatal error 32 disappered.  But my old
	Logitech 3 buttom serial mouse won't work.  In Linux, it is set as
	MouseSystems	"/dev/ttys0".  I tried both Logitech and MouseSystems
	and had no luck.  Any idea?

	Thanks!

	-- Harry

Newsgroups: comp.unix.bsd,comp.benchmarks,comp.arch,comp.arch.storage
Subject: Drive geometries
Organization: FidoNet node 2:252/305 - The Purple Tentacle, Reading
Date: Wed, 4 Nov 1992 22:16:08 +0000

Well, I decided to have yet another bash at getting 386bsd to live in a 
partition on my HD and share it with Linux...

  Firstly the drive is a Maxtor LXT535A IDE. The postage stamp, er, manual I 
got with the drive gives several recommendations for CMOS parameters, the 
two that give the highest capacity being 1024 cylinders, 16 heads, 63 
sectors and 1036 cylinders, 16 heads, 63 sectors. Another piece of paper I 
got with another Maxtor drive give physical specifications for several 
drives among them the LXT535A which it says has 11 data heads and 1560 
cylinders.

  Hmmm... The 1024 and 1036 look like DOS-isms. I tried the physical 
parameters. No joy. Classic failure - unable to read disklabel after the 
kernel has loaded.

  No problem. Run Frank's ide_conf. The drive seems to be claiming to be 
1024x16x63. Hey! I *know* it's bigger than that! The manual gives 1036 as a 
possible config!

  Tried it. No joy. Install hangs before it even asks me if I want to 
install in the 386bsd partition. I can ^C out though, so maybe this is 
something other the device driver barfing?

  Just to check I set the parameters to 1560x11x63 and used Linux to build 
filesystems all over - no problems, it seems valid. (An extra cylinder 
killed it).

  Moral? Well, just because a drive has a default geometry doesn't mean it 
should be automatically prefered. It seems that even if I installed 386bsd 
on the whole drive I would be better off running it with a translated 
geometry since it lies about the number of heads it has by default!?!


                                Mike

(BTW Anyone any clues as to why install hangs now? It worked with my 
initial attempts when using the geometry from the physcial spec. but not now 
with the default geometry.)
Newsgroups: comp.unix.bsd
Subject: Need help getting 386BSD.
From: Dan the Man <DED110@psuvm.psu.edu>
Date: Sun, 8 Nov 1992 22:51:56 EST
Organization: Penn State University

     I'm on a cranky IBM 3090 running VM/ESA and I'm trying to ftp 386BSD.
So far I've been unable to connect to several ftp sites, and those that I
have been able to get to have files tar'ed and Z'ed.  I can deal with Unix
Z-compression on my host machine, but it chokes when trying to de-Tar.  As
if that weren't enough, I can't seem to mget files with mutliple.names.like.
this; I'm only allowed a file Name and Type.  Argh.
     I'm also not sure what files I need or what to do with them when I get
them.  If anyone could explain how they got their copy, I'd be most thankful
(and less stressful :).  Please E-mail, (or post too) as our news server has
been a pain lately.  Thanks in advance.

                                                 Dan the Man
 Peace, Love, and                        Average uninvolved, apathetic
 Professional Detachment!                misunderstood, (independant)
                                         bonehead weenie.  (newbie too!)
Newsgroups: comp.unix.bsd
From: uwp@cs.tu-berlin.de (Udo Wolter)
Subject: 386BSD, XFree, Mouse...
Organization: Technical University of Berlin, Germany
Date: Mon, 9 Nov 1992 09:14:19 GMT

Hi !
I've problems with XFree under 386BSD. I can only start it in 640x480 Mode, 
I can't find any working configuration for other (800x600, 1024x768) Modes.
I have a SIGMA Legend VGA Card with a TSENG4000 chip. Can anyone mail me an
example XConfig file ?
The second is that I have a Genius Microsoft compatible mouse with 3 buttons,
but I only get 2 buttons to work. How can I use all 3 buttons of my mouse ?
The last thing I want to know is how can I find out how much memory my system
uses ? I mean the real memory. And how to find out how much swap space my
system uses ? I ask this cause my system becomes very slow if I use the xclock
with 1 sec update. My harddisk led then always flashes and the load
increases...:-( 

Thanx in advance,
		  Udo

-- 
Udo Wolter   
INTERNET:    uwp@cs.tu.berlin.de, wolter@db0tui11.cs.tu-berlin.de	
BITNET/EARN: WOLTER@DB0TUI11
Newsgroups: comp.unix.bsd
From: alm@netcom.com (Andrew Moore)
Subject: cp/cpio over NFS unreliable? [386BSD]
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
Date: Thu, 12 Nov 1992 08:55:12 GMT



cp'ing sbin/* across two NFS-mounted 386BSD systems with SMC
WD8003EP adapters yields errors like:

cp: ./inetd: No such file or directory

and though most files copy okay, the files for which an error is
reported get truncated.  Worse, when using cpio -p, truncation occurs,
but no errors are reported!  

Nathan Williams pointed out that the wsize and rsize parameters must be
set if the RAM buffer is less than 8K.  But this shouldn't be a problem
with the SMC which uses an 8K buffer.  Are there other parameters I
should look at?  Explanations? Thanks.
-Andrew Moore <alm@netcom.com>

Newsgroups: comp.unix.bsd
From: cflatter@nrao.edu (Chris Flatters)
Subject: Re: has anyone ported epoch(x-oriented emac
Reply-To: cflatter@nrao.edu
Organization: NRAO
Date: Tue, 10 Nov 92 17:09:41 GMT

In article 65iU02D92auP01@JUTS.ccc.amdahl.com, gpw10@phoenixcd.amdahl.com (Gary Ward) writes:
>In article <1992Nov9.043048.24907@netcom.com>, hasty@netcom.com (Amancio
>Hasty Jr) writes:
>> Well the title says it all...
>> It will be nice to have epoch since we have X up and running...
>> 
>> Amancio
>
>Yes, I ported it.  It was not very difficult at all.  I used the same
>configuration files that were posted here a while back for (text-base)
>Gnu Emacs and it compiled right up.  For those interested parties, here
>is a copy of the previous post with the configuration files:
>

I would take the versions from GNU emacs 18.59.  They are a little tidier.

	Chris Flatters
	cflatter@nrao.edu

Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: mountd/portmap/NFS problem
Organization: University of Utah Computer Center
Date: Fri, 6 Nov 92 05:06:51 GMT

In article <1992Nov5.175351.26079@cs.brown.edu>, lr@cs.brown.edu (Luigi Rizzo) writes:
|> 
|> It must be something trivial but... I installed 386bsd 0.1 on a
|> 486-33 with IDE drive, we8013-clone ethernet with no problems.
|> Everything including the network seems to work (at least, ftp, telnet,
|> rsh  work fine and quickly in both directions). However, when I try to
|> boot with the nfs-related stuff enabled (portmap, mountd etc.) mountd
|> hangs without being able to register with portmap. If I press ^C on the
|> console during boot, things proceed more or less regul;arly and the
|> system comes up (the only thing is, mountd takes most of CPU time).
|> Other things (nfsd, nfsiod) apparently register correctly (as shown by
|> using rpcinfo from another machine).  Now, I cannot either NFS-mount
|> the 386 disk from another machine (clearly because mountd does not
|> work, the error message is
|> 
|> nfs_mount: bsd386a:/ server not responding: rpc program not registered
|> 
|> or mount other disks on the 386bsd machine. (this time the error
|> message is 
|> 
|> Bad MNT RPC: RPC: Authentication error; why = Invalid client credential
|> 
|> 
|> I haven't installed the crypt routines or any of the patches yet,
|> because from the descriptions I have it's not clear which ones
|> apply to my problem. Any help from the net ?

Install the NFS and mount patches at the very least.  You seem to be running
into the overlap and reserved port problems.


					Terry Lambert
					terry@icarus.weber.edu
					terry_lambert@novell.com
---
Any opinions in this posting are my own and not those of my present
or previous employers.
-- 
-------------------------------------------------------------------------------
                                        "I have an 8 user poetic license" - me
 Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------
From: spedpr@thor.cf.ac.uk (Paul Richards)
Newsgroups: comp.unix.bsd
Subject: Xview and gdb problems: maybe?
Date: 11 Nov 92 22:09:38 GMT
Organization: University of Wales College at Cardiff
X-Mailer: Cardiff Computing Maths PP Mail Open News Gateway

I'm trying to port xvtdl and xvgr both of which core dump due to FP
exceptions. When I try and use gdb to run them both display their
windows and then I get the following error:

Program received signal 11, Segmentation fault
0xe91a7 in ndis_d_pri:ndis_send_ascending_fd (1753088, 2147483647,
-71375700, 621208)

This only happens when running under gdb, I do not get segmentaion
faults when not running gdb.

A quick grep through the libraries show this to be in the xview library.
Does anyone know what's happening. 

-- 
  Paul Richards at Cardiff university, UK.

  spedpr@uk.ac.cf.thor	Internet: spedpr@thor.cf.ac.uk
  UUCP:     spedpr@cf-thor.UUCP or ...!uunet!mcsun!uknet!cf!thor!spedpr
+++
Newsgroups: comp.unix.bsd
From: migieger@delos.stgt.sub.org (Michael Giegerich)
Subject: : How create /dev/lp within 386bsd-0.1
Date: Tue, 10 Nov 1992 21:03:30 GMT
Organization: Delos Stuttgart, Germany

Hi,

the subject says it all...
When booting I receive a message like "lpd[] /dev/lp not found";

I'm sure this question has been answered more than once, but I
don't find anything in the INSTALL.NOTES nor in the FAQ :-((

Any help is appreciated.
Thanx in advance,

Michael
From: veit@du9ds3.fb9dv.uni-duisburg.de (Holger Veit)
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] capslock -> control key mapping
Date: 12 Nov 92 17:44:57 GMT
Organization: Uni-Duisburg FB9 Datenverarbeitung
Distribution: comp
Reply-To: veit@du9ds3.uni-duisburg.de
NNTP-Posting-Host: du9ds3.fb9dv.uni-duisburg.de

In <JKH.92Nov11210101@esel.lotus.com> jkh@esel.lotus.com (Jordan K Hubbard) writes:

>	This patch is obsolete with codriver (aka keycap-0.1.1.tar.Z), it has been
>	obsolete since the first days of the 0.1.0 version and Helmut Michaelis'

>If there is a better way of doing this, then you guys need to make its
>presence better known!  *Any* console driver that:

>a) Breaks Xfree86
>or
>b) Is not compatable with the main patch line (PL58).

>Is totally useless in my eyes, since I'll need to become responsible
>for a rather large 3rd party derivation or hack it around the X
>support code (or both).  My patch breaks rule (b) but is at least
>small enough to keep adding back in and doesn't break X.

>					Jordan

Codrv, as announced some time ago, addresses several problems that
happen between 386bsd and XFree86. There are problems on both side,
so you have to fix both 386bsd (new driver) and X386 (mainly new
keyboard handler), the "agate" X386 is incompatible for some important
reasons. Codrv will likely be part of future versions of 386bsd and XFree86
(I don't answer questions on release dates of these!).

The driver for instance supports all 'xset' features,
also xconsole and xdm now work properly. Return from X mode without
hangup is possible as well. A national keyboard mapping created for text mode
is propagated to X mode, without building an xmodmap table.

Fixes for 386bsd and X386 (based on XFree86-1.1) are in the package.

Reference binary versions of a GENERIC 386bsd pl58 with codrv support
and X386/X386mono (with PEX+Type1) are available, if there are no capacities
to build a new kernel or Xserver.

The driver is compatible with the main patch line (however, you mustn't 
install patches dealing with pccons (the "x p; they are useless).

The package is keycap-0.1.1.tar.Z and is available from
* ftp.duisburg.de (try 134.91.100.14 if name is not resolved yet) in
	/pub/unix/386bsd-0.1/unofficial/keycap/*
	(Binaries and sources)
* ref.tfs.com in /home/veit/* (Sources only)
* agate.berkeley.edu in /pub/incoming/keycap-0.1.1.tar.Z (Sources only)
* other ftp servers, ask archie

Also get the FAQ.ddmmyy and BUGLIST.ddmmyy for recent information.

>When your driver is merged with 386BSD or at least completely
>compatable with the Xfree86 console driver patches, then I'll happily
>consider such hackery 'obsolete'.  Until then, it's of no interest
>at all.

Enough support and compatibility?

Holger Veit
-- 
|  |   / Dr. Holger Veit         | INTERNET: veit@du9ds3.fb9dv.uni-duisburg.de
|__|  /  University of Duisburg  | "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
|  | /   Dept. of Electr. Eng.   |   Sorry, the above really good fortune has
|  |/    Inst. f. Dataprocessing |      been CENSORED because of obscenity"
From: cbusch@ub.d.umn.edu (Chris)
Newsgroups: comp.unix.bsd
Subject: How do you make those -> directories?
Date: 12 Nov 1992 10:52:41 -0600
Organization: University of Minnesota, Duluth
Distribution: world
NNTP-Posting-Host: ub.d.umn.edu

Hello
   How do you make those '->' directories? The first file attribute is
the letter 'l' (what does that stand for?) and the name is something
like 'stuff -> /here/it/is' I searched the manuals but I only found the
normal directory commands.  

Thanks

--
Chris Busch   CBUSCH@ub.d.umn.edu
"I guess Intel invented radioactiveware!"
"The use of COBOL cripples the mind; its teaching should, therefore,
    be reguarded as a criminal offense." - E. W. Dijkista 
"High-level languages should remove burden from the programmer, not
 put burden on the person!"
Newsgroups: comp.unix.bsd
From: nbladt@autelca.ascom.ch (Norbert Bladt)
Subject: [386BSD] Ghostscript 2.4.1 (supp. XFree86/epson/paintjet/FAX) available
Keywords: 386BSD ghostscript X11 FAX epson paintjet
Organization: Ascom Autelca AG, Guemligen, Switzerland
Date: Mon, 9 Nov 1992 07:35:00 GMT

Hello * !

I promised to make Ghostscript 2.4.1 (delivered with the etc01 distribution
of 386BSD) available for anon-ftp. Finally, I managed to do a upload to
the nearest ftp-site. This version of gs includes drivers for epson printers,
HP paintjet printers, X11 (XFree86) and the drivers for low- and high-resolution
fax formats. (I am still working on netfax for 386BSD).
The file is on:
	hasler.ascom.ch:pub/gs2.4.1-bin.386bsd.tar.Z
It includes the gs2.4.1 binary, the makefile (to let you see what is really
included) and a short README.
It doesn't include the fonts. They should be available from different ftp-sites.
I didn't try the new fonts which came with the newer versions of ghostscript
(2.5.1 or 2.5.2).
	hasler.ascom.ch is 139.79.129.1
I will build a boot-image with the new SCSI-drivers, terry's patchkit applied
(and corrected for the introduced "slip" TCP/IP bug) and the new boot-blocks
and load that to the same system in the same directory. This will be available
tomorrow morning (MEZ or CET or MET that is).

Have fun with gs 2.4.1 (it works for me in the XFree86 environment and seems
to work more or less with netfax).

Norbert Bladt.

P.S. If you have problems with the ftp-site please mail-me and I will try to
contact the sys-op.
-- 
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
From: wjolitz@soda.berkeley.edu (William F. Jolitz)
Newsgroups: comp.unix.bsd
Subject: ftp/media sites in Italy?
Date: 13 Nov 92 00:24:40 GMT
Article-I.D.: agate.1dusk8INNrbb
Organization: U.C. Berkeley, CS Undergraduate Association
NNTP-Posting-Host: soda.berkeley.edu


Any anonymous ftp sites in Italy. Also, any PC or UNIX SIGS in Italy
able to distribute on media?

Lynne.
Newsgroups: comp.unix.bsd
From: yeoy@a.cs.okstate.edu (YEO YEK CHONG)
Subject: Help with getting tip to work
Organization: Oklahoma State University, Computer Science, Stillwater
Distribution: usa
Date: Thu, 5 Nov 92 18:34:11 GMT

Hello again,

	One more quick question with tip.  "tip com1" didn't work for me.
"tip /dev/com1" didn't work for me too.  Terry's FAQ suggests recompiling
"tip".  But if the source is in src01*, can I download and install them as
I did with the bin01*?(extract disappeared.)  If I download pcomm instead,
and I couldn't get tip to work, can BSD read from a DOS floppy with mread.
mread doesn't seems to work when the filename is not of the form *01.* like
bin01.*.

Regards,
Yeo...
From: deeken@iti.informatik.th-darmstadt.de (Hans-Christoph Deeken)
Newsgroups: comp.unix.bsd
Subject: Aaaah! (Re: smail 3.1 for Jolitz BSD?)
Keywords: bash stupid mistake
Date: 5 Nov 92 18:31:06 GMT
Organization: TU Darmstadt


Aaaaaaah! *BLUSH*

In article <1992Nov4.154757.26584@news.th-darmstadt.de>, I wrote:
> I'm running smail 3.1 at home for 2 months now, without a problem.
> The diffs for smail 3.1.28 follow my .signature.
> 
> You need a patched make which doesn't go into orbit on a single dash on
> the command line. The patch is in Terry's patchkit.

... and you need bash for the shell scripts.

I have bash linked to /bin/sh, so I forgot to mention this.


Sorry for inconveniences,
Hannes
-- 
Hans-Christoph Deeken                                        (Glenlivet on IRC)
Inst. fuer theoret. Informatik		(deeken@iti.informatik.th-darmstadt.de)
TH Darmstadt, Germany          (I don't speak for THD, they don't speak for me)
        "Whisky ist fluessiges Sonnenlicht --- George Bernard Shaw"
Newsgroups: comp.unix.bsd
From: love@stacken.kth.se (Love Feuer)
Subject: MicroVax II, Reno & Emulex
Organization: Stacken Computer Club, Stockholm, Sweden
Date: Tue, 10 Nov 1992 13:45:25 GMT

We have just laid our hand on an old MicroVax II (or actually a Vax Station 
GPX) equipped with an Emulex QD21 (I think...) ESDI controller together
with a 760 Mb Maxtor drive.

We plugged in an RD53 drive with 4.3BSD Reno with the ambitions to make
UNIX recognize the ESDI controller.

The VMS system that is on the Maxtor drive today is totally convinced that
the Emulex controller is an UDA50 with an RA81 attached to it.

 So we configured the controller as an UDA50 in our Reno system, defined 
some new drive parameters in uda.c that would conform to the Maxtor drive 
and recompiled the kernel together with the AVOID_EMULEX_BUG define that
we threw in just to be on the safe side.

When the new kernel initialized, it found the controller without any
problems, but when slave0 (the maxtor drive) was polled the kernel
panicked with an arithmetic error.

Some investigations gave that uda.c:uda_attach() asked the drive to go on 
line and when the drive interrupted that it was ready, the kernel went
down.

Some guy told us that Emulex has their controllers on a different interrupt 
level than the UDA50 that they are supposed to emulate.


And now for the big one:

What is wrong?
If it is the interrupt level, does anyone know how to set it to some better
value on the Emulex board?

Please mail any answers directly to me, since this problem is quite 
boring for the majority of this newsgroup.

Tnx in advance:
  /Love Feuer (love@stacken.kth.se)






Xref: sparky comp.unix.bsd:8472 comp.os.linux:15769
From: danson@lgc.com (Doug Anson)
Newsgroups: comp.unix.bsd,comp.os.linux
Subject: Re: Linux/386BSD on Compaq Deskpro 386/25
Date: 5 Nov 92 17:43:40 GMT
Organization: LandMark Graphics Corporation LGC

In article <id.L9PU.XI2@ferranti.com>, peter@ferranti.com (peter da silva) writes:
|> I'm considering buying a used Compaq Deskpro 386/25. I'll be using a Maxtor
|> XT4380E or Miniscribe 9380E with an as yet undetermined ESDI controller. Has
|> anyone run Linux or 386BSD on a similar platform? What sort of controller
|> would work best in this environment (don't say SCSI, I have a good deal on
|> the drive)? What sort of things should I be watching out for?
|> -- 
|> % Peter da Silva % 77487-5012 % +1 713 274 5180 % Har du kramat din varg idag?
|> (<<VV$@\\$'&O 9$O%'$LT$&$"V6"$&$<4$?'&$ #I&&?$=$444@)24 24 scale newpath/P true
|> def 3 21 moveto{dup 36 eq{pop/P P not def}{dup 7 and 4 sub exch 56 and 8 div 4
|> sub P{rlineto}{rmoveto}ifelse}ifelse}forall stroke showpage %          `-_-'

I have 386BSD :) working fine on a Compaq Deskpro 386/20 with their standard
ESDI controller an a miniscribe drive. I did have some problems making a custom
partition for swap but the standard install works fine.

I may have goofed the custom installation attempt -- I still dunno what went 
wrong or why -- the jest of it was that, after installing a custom partition
(20 Mb swap, / and /usr partitions...) and transfered the Fixit floppy (std
distr), the machine would partially boot off of the hard drive (you'd see the
banner, all the interfaces up to and including npx0 but then nothing else).

I am currently running the standard install configuration very nicely.

Doug
-- 
-------------------------------------------
Doug Anson					
Internet: danson@lgc.com			
Phone:	  713.560.1274
FAX:	  713.560.1277
SNAIL:    Landmark Graphics Corporation LGC	
	  15150 Memorial Drive
	  Houston, TX 77079			
-------------------------------------------
Newsgroups: comp.unix.bsd
From: nbladt@autelca.ascom.ch (Norbert Bladt)
Subject: Re: XView 3.0 (it works ?)
Organization: Ascom Autelca AG, Guemligen, Switzerland
Date: Thu, 5 Nov 1992 07:26:55 GMT

eoahmad@ntuix.ntu.ac.sg (Othman Ahmad) writes:

>David Eugene Dwiggins (dd2x+@andrew.cmu.edu) wrote:
>: Has anyone ported XView 3.0 to 386bsd? If so, where is it archived?
>: 
>Ya. Jonassan(?) ported it and is at nova.cc.purdue.edu under directory
>386bsd/submissions

>This works completely. I have verified it on a large 1.2Mbyte xview program.
Just a warning: I got the patches from there, applied them (no reject files),
compiled it and:
	olwm works, clock works.
	cmdtool -> reboot (or login from a different system/terminal and kill
		the xserver, etc.)
	shelltool -> crash.
	textedit -> crash as soon as a file is loaded.
	Didn't test the other clients, though.
Running just one xview program (1.2 MB file size isn't large, anyway) is
not a real test !
Perhaps this program was even olwm, which, indeed, is working.

Just a hint for others to wait. At least two persons are trying to
get it working (including me).

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
Newsgroups: comp.unix.bsd