This is the mail archive of the cygwin-xfree@sources.redhat.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

RE: Keyboard Prob


Hello Everybody

I joined the list a couple of days ago, and had a crack at installing the
directX xfree86/cygwin test7 server on my Win98 machine
yesterday.   (Win98SE, Dell Inspiron 7000 laptop, ATI Rage Mobility graphics
card)

It took a while, but eventually I got everything going quite well [well good
for win98 anyway]

I got those keyboard errors, or crashes as I called them too. So I started
going through the mailing list archives and found a thread starting with the
following message:

http://sources.redhat.com/ml/cygwin-xfree/2000-q4/msg00599.html


This seemed to lay the blame (possibly) on rgb.txt
I had this file, but was still getting the error
.....[blah blah blah]
to cut a long story short things started not crashing when I installed:

xfree86-4.0-devel.tar.bz2

the rgb.txt from this was identical to the one I had before, so I can only
guess that something else that this provided (or replaced) fixed the
problem.

WARNING: people on Win98 will need to reapply (or pre-save) XWin.exe and
xf_dx.dll, as the tar will overwrite the test7 versions with some other
versions.

I just thought I'd share my experiance, just in case it helps someone else,
obviously this isn't a proper explanation of why the problem was occuring in
the first place.

I then went on the edit the startx shell script that the above archive
placed in /usr/X11R6/bin/. I also created an xinitrc file in
/etc/X11/xinit/. And the result is that I can how start the Xserver nicely
from typing startx at a normal Cygwin (ie. command prompt) window. [and I
can also exit the x-server with out it crashing]. If anyone is interested I
can share further details on this.

What this leads me to ask is why is startx not included in the normal
binaries? (ie. why does someone need to install the devel one too?).
I can see the point of startxwin.bat, it lets you start the xserver without
having a cygwin window up before hand, but it still uses (at least) one
empty window. The nice thing about startx and xinitrc is that at least it is
more standard, in the sense that we don't have to start xterms etc from a
DOS batch file etc, and it matches linux implementations a little (i think,
not that I know anything about linux).

I also have a nice Xmodmap file, that gives 'proper' (or at least less
wrong) keyboard key bindings for UK Keyboards. [again give us a shout if u
want it]

cya

Sagar

--------------------------------------------------------------------------
Sagar R. Shah                 www: http://www.netnexus.co.uk/
Sidney Sussex College         ICQ: 34249234
Cambridge, CB2 3HU
--------------------------------------------------------------------------

On Mon, 1 Jan 2001, John T. Stonick wrote:
> [snip]
> Then when I type anything I get the following messages added to the popup
> window.
> 
>  0 [main] xterm 513267 handle_exceptions: Exception: STATUS_ACCESS_VIOLATION
>  4748 [main] xterm 513267 stackdump: Dumping stack trace to
> XTERM.EXE.stackdump
> 
> BTW, I am using win98 on a Compaq armada M700 and I am using the standard
> startxwin.bat file. I am using a standard 101 key English keyboard.



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]