[comp.windows.x] X11R3 on the IBM-RT/PC running 4.3R2

jonnyg@ROVER.UMD.EDU (Jon Greenblatt) (11/02/88)

	Its me again. I downloaded and compiled the core distribution
on a IBM-RT/PC running 4.3bsdR2 on an APA16 display
without a hitch, some of the warning messages were scary though.
Running X11R3 is very problematic, The line drawing is mostly broken on
all but straight lines, Font display works enough to bring up the xdm
login in screen but not enough to bring up an xterm without dumping
core. The second hand on the clock leaves a shadow and the xlogo looks
nothing like a xlogo. Xedit prints the text in the widgets Ok but not
the text being edited. Does someone have the fixes? I'm going to trace
down some of the more scary warning messages in the mean time. Note
that I am using revision 2 of the 4.3bsd software. Has someone followed
these same steps and not have the problems I described?

				JonnyG.
				(jonnyg@umd5.umd.edu)
				(jonnyg@rover.umd.edu)

rws@EXPO.LCS.MIT.EDU (Bob Scheifler) (11/02/88)

In server/ddx/ibm/README you will find:

    At the last minute, some critical server bugs were discovered in the apa16
    driver, and Erik Fortune is busily fixing them even as I type.  Please send
    flames and requests for patches to him at:

            {ucbvax,uunet.uu.net}!ibmuupa!erik

Sorry, but IBM decided to dump new bits on us at the very last moment, and
they didn't discover how badly broken the apa16 was until after we were
already ready to ship (we had the release notes printed and everything).

jim@EXPO.LCS.MIT.EDU (Jim Fulton) (11/02/88)

Yup, there are bugs in the APA16; from server/ddx/ibm/README:

  At the last minute, some critical server bugs were discovered in the apa16
  driver, and Erik Fortune is busily fixing them even as I type.  Please send
  flames and requests for patches to him at:

         {ucbvax,uunet.uu.net}!ibmuupa!erik

feigin@batcomputer.tn.cornell.edu (Adam Feigin) (11/02/88)

I'm also having some problems. The core built without a hitch, but I can't get
the server to work with either my apa16 or mpel display. When I run xinit,
it finds the mpel, but just sits there for awhile, and finally gives:

giving up
xinit: Connection refused (errno 61) unable to connect to X server

I checked all the device entries, and everything looks kosher; sometimes xinit
gives me different errors, like:

waiting for X server to begin accepting connections. giving up
xinit: interrupted system call (errno 4) unable to connect to X server

If I invoke xinit with -apa16, it starts up the server on the apa16, and
attempts to start an xterm window, and then:

xterm: broken pipe

I just cant figure out why the server starts on the apa16, but just sorta
sits there on the mpel (no grey background, no cursor, black screen) and
then dies. Any help is appreciated.

						Adam
------------------------------------------------------------------------------
Internet: feigin@tcgould.tn.cornell.edu		Adam Feigin
Bitnet: feigin@crnlthry				Workstation Consultant
UUCP: {backbones}!cornell!batcomputer!feigin	Cornell National Supercomputer
MaBell: (607) 255-3985				Facility, Visualization Group

	"Bill for president in 1988...America is ill, but so is Bill !"
------------------------------------------------------------------------------