Re: Errors with xFree86

[Alfred Vahau <Alf dot Vahau at upng dot ac dot pg>]

Ed,
We're almost half a day apart - hence delay in response. The problem is best
posted on the mailing list. In fact in the first reply, I forgot to do a cc to
cygwin/xfree86. Later I realized this and did post the reply on the mailing
list.

The errors you're reporting here are related to the path. The files not found
are not on the path searched when startxwin.bat is executed. So as a start, I'd
suggest that you print out the startxwin.bat and look at the path included in
the batch file. I assume that you know what I mean by path. If you're from a
Unix background, it takes quite a while to figure things out in cygwin.

For the purpose of the wider cygwin and xfree86 community, I'm copying your mail
to cygwin.

Best wishes,

Alfred Vahau


Ed Mullen wrote:

> Alfred,
>
> Sorry.  I spoke too soon.  There are other errors.  One DOS screen says:
>
> Path not found - \cygwin\tmp\.X11-unix\X0
> Path not found
> Invalid path, not directory,
> or directory not empty
> Cannot find file 'mxterm' (or one of its components). Check
> to ensure the path and filename are correct and that all required
> libraries are available.
>
> C:\cygwin\usr\X11R6\bin>
>
> And a second DOS screen says:
>
> winFinishScreenInitFB () - Calling winCreateDefColormap ()
> winCreateDefColormap () - Deferring to fbCreateDefColormap ()
> error opening security policy file /usr/X11R6/lib/X11/xserver/SecurityPolicy
> Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing
> from li
> st!
>
> I am using Windows 98.
>
> Ed
>
> -----Original Message-----
> From: Alfred Vahau [mailto:Alf.Vahau@upng.ac.pg]
> Sent: Sunday, July 01, 2001 1:20 AM
> To: Ed Mullen
> Subject: Re: Errors with xFree86
>
> Find attached one solution to your problem. It's not everything that you
> want to
> know but hope this is a start as its quite a recently asked question.
>
> Alfred Vahau
> School of Natural and Physical Sciences
> University of Papua New Guinea
> email: alf.vahau@upng.ac.pg
>
> Subject:
>          RE: Can't get up and running on Windows 98
>    Date:
>          Wed, 27 Jun 2001 16:21:39 -0400
>    From:
>          Suhaib Siddiqi <ssiddiqi@inspirepharm.com>
>      To:
>          "'Dan Draeger'" <ddraeger@umich.edu>,
>          "'cygwin-xfree@xfree.cygwin.com'" <cygwin-xfree@xfree.cygwin.com>
>
> > -----Original Message-----
> > From: Dan Draeger [mailto:ddraeger@umich.edu]
> > Sent: Wednesday, June 27, 2001 2:06 PM
> > To: cygwin-xfree@xfree.cygwin.com
> > Subject: Can't get up and running on Windows 98
> >
> >
> > I'm using X 4.03.  I extracted all the binaries and run
> > startxwin.bat in DOS
> > and all I get is a blank window with an X-shaped cursor.  How
> > do I run and X
>
> That means X-server is runing...
> you need to edit /usr/X11R6/bin/startxwin.bat and remove /B  you will find
> for xterm etc.  Windows 9x/ME does not accept /B option
> for start, therefore xterm failed.
>
> Suhaib
>
> > terminal?  Here are the messages that come up on the console...
> > _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
> > winDetectSupportedEngines () - Windows 95/98/Me
> > winDetectSupportedEngines () - DirectDraw installed
> > winDetectSupportedEngines () - DirectDraw4 installed
> > winDetectSupportedEngines () - Returning, supported engines 00000007
> > winSetEngine () - Using user's preference: 4
> > winAdjustVideoModeShadowDDNL () - Command line depth: 32,
> > using depth: 16
> > winCreateBoundingWindowWindowed () - WindowClient width 1018
> > height 704
> > winInitVisualsShadowDDNL () - Masks 0000f800 000007e0
> > 0000001f RGB 6 d 16
> > winInitVisualsShadowDDNL () - Returning
> > error opening security policy file
> > /usr/X11R6/lib/X11/xserver/SecurityPolicy
> > Could not init font path element
> > /usr/X11R6/lib/X11/fonts/CID/, removing
> > from li
> > st!
> >
> > Any ideas?
> >
>
> Ed Mullen wrote:
>
> > I would like to use OpenDX which is a free data analysis program from IBM
> > but I was told I would need something called an "x-server" (whatever that
> > is).  I haven't downloaded OpenDX yet, but I downloaded cygwin and
> > xFree86-4.1.0 as the xServer.  I followed all the instructions to download
> > and install xFree86-4.1.0 and it seemed to go fine.  There were no errors.
> > The last page of the xFree86 instructions say that to start xFree86 you
> > should doublclick startxwin.bat.  I did this and received two DOS screens
> > and one large gray screen with an "X" that moves across the screen in
> > response to the mouse.  I have no clue what this is supposed to do, but
> the
> > two DOS screens appear to have error messages on them.
> >
> > One of the DOS screens says the following:
> >
> > Path not found - \cygwin\tmp\.X11-unix\X0
> > Path not found
> > Invalid path, not directory,
> > or directory not empty
> > Invalid switch - /B
> > Invalid switch - /B
> > Invalid switch - /B
> > Invalid switch - /B
> >
> > C:\WINDOWS\Desktop>
> >
> > The other DOS screen says:
> >
> > winDetectSupportedEngines () - Windows 95/98/Me
> > winDetectSupportedEngines () - DirectDraw installed
> > winDetectSupportedEngines () - DirectDraw4 installed
> > winDetectSupportedEngines () - Returning, supported engines 00000007
> > winSetEngine () - Using user's preference: 4
> > winAdjustVideoModeShadowDDNL () - Windowed, command line depth: 32, using
> > depth:
> >  16
> > winCreateBoundingWindowWindowed () - WindowClient width 1018 height 742
> > winInitVisualsShadowDDNL () - Masks 0000f800 000007e0 0000001f BPRGB 6 d
> 16
> > winInitVisualsShadowDDNL () - Returning
> > winFinishScreenInitFB () - Calling winCreateDefColormap ()
> > winCreateDefColormap () - Deferring to fbCreateDefColormap ()
> > error opening security policy file
> /usr/X11R6/lib/X11/xserver/SecurityPolicy
> > Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing
> > from li
> > st!
> >
> > Based on the errors in these DOS screens, it would appear that
> xFree86-4.1.0
> > is not working properly (although I admit I wouldn't know what it looks
> like
> > if it was working properly).  Does anyone know what the problem could be?
> >
> > Ed Mullen