[ANNOUNCEMENT] Server Test 68

2002-10-20 Thread Harold Hunt
Links:

I just posted Test 68 to the server development page:
http://xfree86.cygwin.com/devel/shadow/

You can install the Test 68 package via setup.exe by selecting the
'test' package (and be sure to check the 'Bin' box): XFree86-xserv-4.2.0-15

Server Test Series binary and source code releases are now
available via the sources.redhat.com ftp mirror network
(http://cygwin.com/mirrors.html) in the
pub/cygwin/xfree/devel/shadow/ directory.  You may wish to note the
desired filename in the links below, then download from your
closest mirror (http://cygwin.com/mirrors.html).

Server binary, direct link:
http://www.msu.edu/~huntharo/xwin/shadow/XWin-Test68.exe.bz2 (1106 KiB)

Server source, direct link:
http://www.msu.edu/~huntharo/xwin/shadow/xwin-20021020-2321.tar.bz2 (90 KiB)

xc/programs/Xserver/hw/xwin (all files) diff against 20021020 XFree86 CVS:
http://www.msu.edu/~huntharo/xwin/shadow/xwin-20021020-2321.diff (14 KiB)


Changes:

1) Add support for non-rectangular windows created by the X Shape Extension
while in Rootless mode (e.g., ``XWin -rootless'').  (MATSUZAKI Kensuke)

2) Not in the release build, but in the sources: Clean up the RANDR
extension code to match the latest RANDR interface.  This can't be enabled
yet because it crashes on startup in 32 bit per pixel mode. (Harold Hunt)


Release plans:

I intend to make XFree86-xserv-4.2.0-15 the stable release as soon as I
receive some feedback that it does not introduce any substantial bugs.  Be
sure to check non-rootless mode with the ``-scrollbars'' parameter and make
sure that the window is created at the correct size and that there is no
wierdness when resizing.  For example, I recall seeing Cygwin/XFree86
startup with the display area being chopped to allow space for scrollbars
that were not being displayed.  I didn't look into that one --- so I would
appreciate it if someone else could verify that it happens.


Enjoy,

Harold




[ANNOUNCEMENT] Server Test 67

2002-10-19 Thread Harold Hunt
Links:

I just posted Test 67 to the server development page:
http://xfree86.cygwin.com/devel/shadow/

You can install the Test 67 package via setup.exe by selecting the
'test' package (and be sure to check the 'Bin' box): XFree86-xserv-4.2.0-14

Server Test Series binary and source code releases are now
available via the sources.redhat.com ftp mirror network
(http://cygwin.com/mirrors.html) in the
pub/cygwin/xfree/devel/shadow/ directory.  You may wish to note the
desired filename in the links below, then download from your
closest mirror (http://cygwin.com/mirrors.html).

Server binary, direct link:
http://www.msu.edu/~huntharo/xwin/shadow/XWin-Test67.exe.bz2 (1105 KiB)

Server source, direct link:
http://www.msu.edu/~huntharo/xwin/shadow/xwin-20021018-2248.tar.bz2 (90 KiB)

xc/programs/Xserver/hw/xwin (all files) diff against 20021018 XFree86 CVS:
http://www.msu.edu/~huntharo/xwin/shadow/xwin-20021018-2248.diff (1 KiB)


Changes:

1) Turn off debugging message in winwindow.c/winAddRgn () that was
being printed thousands, if not millions, of times.  (Harold Hunt)


Enjoy,

Harold




RE: x-server with window-manager

2002-10-19 Thread Harold Hunt
Sven,

  OK, but how to i start XWin.exe so it will work in rootless-mode?

 OK, i found out, that i should start XWin -rootless but i still need a
 window-manager afterwards (like twm) ro have a window-titlebar.

 will there be a window-manager integrated into XWin that uses
 Win32-native windows? (native title-bar, buttons, resizing etc.)


I said earlier that you would still have to run an X Window Manager.  Yes,
Cygwin/XFree86 will eventually have a window manager that opens X windows in
Windows windows.  However, we only got rootless support three days ago, so I
wouldn't count on that integrated window manager being finished any time
soon, unless you are willing to help write it.

Harold




Cygwin synchronization

2002-10-16 Thread Harold Hunt

Many, many changes.

1) Include an X icon and the necessary build rules for building Windows
resource files (even while cross compiling).  (Harold Hunt, Jehan Bing)

2) Include a preliminary rootless mode.  (MATSUZAKI Kensuke)

3) XF86Configfile suppport.  (Alexander Gottwald)

4) Scrollbars support.  (Jehan Bing, Harold Hunt)

5) Warning dialog on disruptive screen depth change --- not quite perfect.
(Harold Hunt)

Harold



xwin-20021016-2004.diff.bz2
Description: Binary data


xwin-newfiles.tar.bz2
Description: Binary data


xc-programs-Xserver-Imakefile-20021016-2004.diff
Description: Binary data


xc-config-cf-cygwin.cf-20021016-2004.diff
Description: Binary data


[ANNOUNCEMENT] Server Test 66

2002-10-16 Thread Harold Hunt

Links:

I just posted Test 66 to the server development page:
http://xfree86.cygwin.com/devel/shadow/

You can install the Test 66 package via setup.exe by selecting the
'test' package (and be sure to check the 'Bin' box): XFree86-xserv-4.2.0-13

Server Test Series binary and source code releases are now
available via the sources.redhat.com ftp mirror network
(http://cygwin.com/mirrors.html) in the
pub/cygwin/xfree/devel/shadow/ directory.  You may wish to note the
desired filename in the links below, then download from your
closest mirror (http://cygwin.com/mirrors.html).

Server binary, direct link:
http://www.msu.edu/~huntharo/xwin/shadow/XWin-Test66.exe.bz2 (1106 KiB)

Server source, direct link:
http://www.msu.edu/~huntharo/xwin/shadow/xwin-20021016-2004.tar.bz2 (90 KiB)

xc/config/cf (all files) diff against 20021016 XFree86 CVS:
http://www.msu.edu/~huntharo/xwin/shadow/xc-config-cf-20021016-2004.diff (3
KiB)

xc/programs/Xserver/Imakefile diff against 20021016 XFree86 CVS:
http://www.msu.edu/~huntharo/xwin/shadow/xc-programs-Xserver-Imakefile-20021
016-2004.diff (2 KiB)

xc/programs/Xserver/hw/xwin (all files) diff against 20021016 XFree86 CVS:
http://www.msu.edu/~huntharo/xwin/shadow/xwin-20021016-2004.diff.bz2 (22
KiB)

xc/programs/Xserver/hw/xwin new files:
http://www.msu.edu/~huntharo/xwin/shadow/xwin-newfiles-20021016-2004.tar.bz2
(10 KiB)



Changes:

1) Include an X icon and the necessary build rules for building
Windows resource files (even while cross compiling).  (Harold Hunt,
Jehan Bing)

2) Include a preliminary rootless mode.  (MATSUZAKI Kensuke

3) XF86Configfile suppport.  (Alexander Gottwald)

4) Scrollbars support.  (Jehan Bing, Harold Hunt)

5) Warning dialog on disruptive screen depth change --- not quite perfect.
(Harold Hunt)


Enjoy,

Harold




RE: x apps cant start from bashW

2002-10-06 Thread Harold Hunt

Rupert,

Excellent.  I've had a full disk bite me before too.

However, I was also going to ask why you are using the -g parameter for ssh?
If you just want to tunnel X applications between your two hosts then -X is
all you need (and I recommend -C for slow links --- compression).  Do you
have some specific scenario that requires -g?  No need to explain your
scenario if you have one, a simple yes will do.

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Rupert Brooks
 Sent: Sunday, October 06, 2002 8:57 AM
 To: Rupert Brooks
 Cc: [EMAIL PROTECTED]
 Subject: Re: x apps cant start from bashW


 Yeesh, I am embarassed again.  Found the problem - full local disk so
 Xauth could not set a cookie.  something I really should have noticed
 *blush*

 Works now.  hopefullly it helps someone searching the list

 Rupert B.

 --
 --
 Rupert Brooks
 McGill Centre for Intelligent Machines (www.cim.mcgill.ca)
 PhD. Student
 http://www.cyberus.ca/~rbrooks
 [EMAIL PROTECTED]
 ICQ: 27978014  CELL: 6137997873
 SMS: send short mail to CELL#@pcs.rogers.com







RE: XFree 4.2.1 + fontconfig-2

2002-10-06 Thread Harold Hunt

Alan,

Somehow my cygwin.rules file got a bogus newline in one of the new rules.  I
removed the newline and I am doing a test build now.  So far it has
progressed past where it was bombing before.

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Alan Hourihane
 Sent: Wednesday, October 02, 2002 11:12 AM
 To: [EMAIL PROTECTED]
 Subject: Re: XFree 4.2.1 + fontconfig-2


 On Wed, Oct 02, 2002 at 11:01:37AM -0400, Harold L Hunt II wrote:
  Alan,
 
  Everytime I a build check I do something like the following:
 
  cd ../ [from foo/xc]
  cd build
  mkdir std
  cd std
  lndir ../../xc  /dev/null
  make CROSSCOMPILEDIR=/cygwin/bin World  World.log 21
 
 
  Thus, I know for sure that any built file is being rebuilt :)
 
  Next idea?

 None. Like I said, I don't have a cross compile environment and it
 works fine natively. Alexander - any ideas ?

 Alan.




RE: x apps cant start from bash

2002-10-05 Thread Harold Hunt

Rupert,

Hey, we like users that solve their own problems, we would like you to stick
around :)

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Rupert Brooks
 Sent: Saturday, October 05, 2002 4:00 PM
 To: [EMAIL PROTECTED]
 Subject: Re: x apps cant start from bash


 Solved my own problem; sorry to bother y'all

 FTR, the solution is that
 a) if the DISPLAY variable in bash is set without export, then when SSH
 starts up its not noticed, and then SSH does not notice where to send
 the X11 stream

 b) you have to set and export the display variable, it is neither set
 automatically, nor does ssh have a default.

 I'm a tcsh user, so didnt realize that necessity under bash.

 This seems to be covered in the SSH notes message, sorry I didn't see that
 before.

 Rupert B


 On Sat, 5 Oct 2002, Rupert Brooks wrote:

  Hi
   - having a strange problem here.  Just installed a fresh install of
  Cygwin / Xfree.  startxwin.bat works, and an xterm appears.  From that
  xterm I can start other xapps and they work.
 
  BUT, from another cygwin bash shell, started independently, I get the
  following error
  xterm XT error: Can't open display:
 
  I have tried with numerous variations in the DISPLAY variable
  localhost:0
  localhost:0.0
  127.0.0.1:0
  127.0.0.1:0.0
  192.168.1.150:0.0
 
  etc
 
  I have done a tracert on all those addresses, and my routing seems ok,
  that is packets for the localhost don't get routed out into the network
  where the router might frig with them.
 
  Xwin.log shows no signs of having refused the connections.  So I am
  guessing that the request never made it to the Xserver.
 
  The problem I am ultimately trying to solve, is to get a remote
 connection
  tunnelled over openSSH or putty.  I have that setup on another machine,
  and working well.  there are two differences with this machine - this OS
  is WinME not Win2K, and this one lives behind a LinkSys router.
 
  Anyway, I think I should get the local set up working right first before
  trying to diagnose the SSH part.  I don't see, though, why the router
  should stop packets from the localhost.  There is no firewall
 software on
  this machine.
 
  Has anyone seen this before?  Can anyone suggest where else to look?
 
  Thanks much
  Rupert B.
 
 

 --
 --
 Rupert Brooks
 McGill Centre for Intelligent Machines (www.cim.mcgill.ca)
 PhD. Student
 http://www.cyberus.ca/~rbrooks
 [EMAIL PROTECTED]
 ICQ: 27978014  CELL: 6137997873
 SMS: send short mail to CELL#@pcs.rogers.com







RE: SSH Notes

2002-10-04 Thread Harold Hunt



 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Alexander Gottwald
 Sent: Friday, October 04, 2002 5:57 AM
 To: [EMAIL PROTECTED]
 Subject: Re: SSH Notes


 Harold L Hunt II wrote:

  ssh should assume ``DISPLAY=127.0.0.1:0.0'' when the DISPLAY
 variable is
  not set on the Cygwin host.  I am not sure why this is not
 currently the
  case.  I can only guess that the lack of this assumption is
 either do to
  1) a whiny security geek on the openssh project, or 2) that the assumed
  usage scenario for openssh is more like a Linux/X machine where
 you have
  probably got your X Server running when you connect to your remote
  machine with ssh, thus DISPLAY would already be set.

 What if you are remote on an machine (linux or cygwin, does not
 matter) and
 a user has already started a xserver on localhost:0.0. You are not allowed
 to connect. So you don't set DISPLAY. If ssh would automaticly set DISPLAY
 it would try to connect to an xserver which then refuses the connect.
 ssh would abort because of an error. Not setting DISPLAY means
 don't use X


That doesn't make any sense.  ssh picks up the DISPLAY value on your Cygwin
host because it needs to know where to direct the data that comes in over
the X11 tunnel.  So, a DISPLAY of 127.0.0.1 on your Cygwin host can only
cause ssh to try to connect to the X Server on your Cygwin host ---
127.0.0.1 does not mean that ssh will try to connect to the remote host's
local X Server.

My point is, why on earth did the user run ``ssh -X [...]'' if they did not
want to actually enable X11 tunnelling?  I would say it is a pretty safe
assumption that they want to use the X Server on their Cygwin host to
display the tunnelled data.  Most users are entirely confused when they run
``ssh -X [...]'' and X11 tunnelling does not actually get enabled.  We
should not be making users jump through any hoops to use X11 tunnelling.

 If users want DIPLAY explicitly set they can add it to their .profile


Are we talking about the same type of users?  :)

Harold

 bye
 ago
 --
  [EMAIL PROTECTED]
  http://www.gotti.org   ICQ: 126018723





RE: right 1/4 of XWin.exe window displays white bar instead of graphics on wide display

2002-10-04 Thread Harold Hunt

Could you send in a link to a screenshot of this?  Or, personally email me a
PNG of this and I will post a link to it.  Do not send the graphic to the
mailing list, as most users do not want to download a large image from the
mailing list.

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of GOULDEY,ANDREW
 (HP-FtCollins,ex1)
 Sent: Friday, October 04, 2002 1:41 PM
 To: '[EMAIL PROTECTED]'
 Subject: right 1/4 of XWin.exe window displays white bar instead of
 graphics on wide display


 Hi,

 I am trying to use Cygwin/XFree86 as an X server on my PC so that I can
 remote-display my hpux box.  When I start up X, I get a window
 that fills my
 entire screen, but I only see the cursor and thatch background pattern on
 the left 3/4 of the window; the right 1/4 of the window is white, and if I
 move the cursor over it, the cursor disappears.

 My setup:
 NVIDIA Quadro4 900XGL w/ 128MB, dual monitor
 Win2k, SP3
 either 2560x1024x32bpp or 3200x1200x32bpp

 The /tmp/XWin.log file indicates that XWin.exe thinks it is using
 the whole
 screen, and when I fire up gnome on my hpux box, it seems to think it has
 the full XWin window to work with (but I can only see the left 3/4 of my
 unix desktop).

 My /tmp/XWin.log:
 $ cat /tmp/XWin.log
 winInitializeDefaultScreens - w 3200 h 1200
 winInitializeDefaultScreens - Returning
 _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
 winDetectSupportedEngines - Windows NT/2000/XP
 winDetectSupportedEngines - DirectDraw installed
 winDetectSupportedEngines - Allowing PrimaryDD
 winDetectSupportedEngines - DirectDraw4 installed
 winDetectSupportedEngines - Returning, supported engines 001f
 winSetEngine - Using Shadow DirectDraw NonLocking
 winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits per
 pixel
 winAdjustForAutoHide - Original WorkArea: 0 2 1172 3200
 winAdjustForAutoHide - Found LEFT auto-hide taskbar
 winAdjustForAutoHide - Adjusted WorkArea: 0 3 1172 3200
 winCreateBoundingWindowWindowed - WindowClient w 3191 h 1147 r 3191 l 0 b
 1147 t 0
 winCreateBoundingWindowWindowed -  Returning
 winAllocateFBShadowDDNL - lPitch: 12764
 winFinishScreenInitFB - Masks: 00ff ff00 00ff
 winInitVisualsShadowDDNL - Masks 00ff ff00 00ff BPRGB
 8 d 24 bpp
 32
 winCreateDefColormap - Deferring to fbCreateDefColormap ()
 winScreenInit - returning

 I can't figure out how to tell what version of XWin.exe I have installed,
 but I just grabbed it a week or two ago, and 'man XWin' has a
 4.2.0 at the
 bottom, so it should be up-to-date.

 By playing around with the -screen option, I have determined that the
 maximum width I can get without the white bar appearing is 2040 or 2041
 pixels.

 The interesting thing is that I can get a full dual-monitor
 display (without
 the white bar) if I go into window's Display
 Properties-Settings-Advanced-Troubleshooting and move the hardware
 acceleration slider to a position that disables directdraw/direct3d.

 Has anyone successfully run Cygwin/XFree86 on a display wider than 2040
 pixels with directx enabled?  On an NVIDIA card?  ATI card?  I updated my
 drivers to the latest and greatest, and it made no difference.  I can
 successfully run ReflectionX (commercial X server) full screen on my dual
 monitor setup (I assume that uses directx also, so I am not
 convinced it is
 just my video card), but I haven't been all that happy with ReflectionX.

 Any help would be appreciated.

 Andrew

 ~~
 https://ecardfile.com/id/Andrew+Gouldey




RE: Remote sessions with HP UX CDE ?

2002-10-01 Thread Harold Hunt

George,

Your email has been received.  However, I do not work with HP-UX and I am
not sure if anyone here does, so I didn't want you to think that you were
being ignored if you don't get any further replies.

Hopefully someone around here will be able to help you out.

I can start with the usual though: send in your /tmp/XWin.log contents.

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of George Thomas P
 Sent: Tuesday, October 01, 2002 8:56 AM
 To: [EMAIL PROTECTED]
 Subject: Remote sessions with HP UX CDE ?


 Hi there,

 I'm a newbie with Cygwin. I have the following problem after executing the
 following command to start an X session with a HP UX machine:-

 XWin -query nn.nn.nn.nn

 where nn.nn.nn.nn is our HPUX ip. My Cygwin instance hangs after that.

 I was wondering if any of you folks were successful in starting remote X
 Sessions with HP-UX ?

 HP-UX uses the CDE window manager I believe, I saw some
 suggestions for the
 Solaris CDE in the Cygwin FAQ, do they apply to HP UX as well ?

 If anyone out there could offer some pointers I'd be most grateful. Thanks
 in advance


 regards George






RE: XFree 4.2.1 + fontconfig-2

2002-10-01 Thread Harold Hunt

Alan,

If I recall correctly, the reason we have to override ComplexProgramTarget_1
for cross compiling is that the correct dependency list is not generated for
the first run through the build tree.  Some executables are not going to be
built until a second pass through the build tree.  No errors are generated
when this problem occurs, so the only way you know that there is a problem
during cross compiling is to go and audit one of the sets of targets that
are built with ComplexProgramTarget and make sure that all of those targets
were built.

With that being said, I will do a build check.  However, I can think of
nothing that has been done to remedy this problem, so I will almost
guarantee that #if CrossCompiling will be needed for ComplexProgramTarget_1.

Will let you know.

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Alan Hourihane
 Sent: Tuesday, October 01, 2002 10:59 AM
 To: [EMAIL PROTECTED]
 Subject: Re: XFree 4.2.1 + fontconfig-2


 On Tue, Oct 01, 2002 at 04:52:29PM +0200, Alexander Gottwald wrote:
  On Tue, 1 Oct 2002, Alan Hourihane wrote:
  
   Can someone test a Cross Compile environment. I needed to comment
   out the ComplexProgramTarget_1 rule which isn't needed when building
   on Cygwin in my tests, but may well be needed for cross compiles. If
   so I can stick in the #if CrossCompile/#endif stuff.
 
  Are these recent changes? All testing I've done was only in a
 crosscompile
  environment.

 Yes, then they are probably needed, so just check for me and I'll make
 the change.

   We're also awaiting the new cygwin dll and relevant binutils packages
   before we can turn on shared libraries for Xaw/Xt as they export
   arrays which the auto-import can't currently deal with.
 
  And the new binutils will help? I've run into this problem too.

 Yes, aparently so. Check out the cygwin archive lists for more details.

 Alan.




RE: XFree 4.2.1 + fontconfig-2

2002-10-01 Thread Harold Hunt

Alan,

Something is definitely borken:

make[4]: Nothing to be done for `Makefiles'.
make[4]: Leaving directory `/home/harold/x-devel/build/cross/doc/man/GLU'
make[3]: Leaving directory `/home/harold/x-devel/build/cross/doc/man'
make[2]: Leaving directory `/home/harold/x-devel/build/cross/doc'
make[1]: Leaving directory `/home/harold/x-devel/build/cross'
make -f xmakefile  BOOTSTRAPSUBDIRS= clean
make[1]: Entering directory `/home/harold/x-devel/build/cross'
RemoveFile(Concat3(lib,libname,-rev.dll.a))
/bin/sh: -c: line 1: syntax error near unexpected token
`RemoveFile(Concat3('
/bin/sh: -c: line 1: `RemoveFile(Concat3(lib,libname,-rev.dll.a))'
make[1]: *** [cleandir] Error 2
make[1]: Leaving directory `/home/harold/x-devel/build/cross'
make: *** [World] Error 2


What do you make of that?

I have the latest cygwin.rules and I updated my entire tree about 10 hours
ago (or a little less than that).

Harold




Donations

2002-10-01 Thread Harold Hunt

I have setup a Donations page on the Cygwin/XFree86 site.
http://xfree86.cygwin.com/donations.html

On the page is a link to contribute funds to Cygwin/XFree86 on the
project-level (which I will collect and distribute to anyone needing a book
or some equipment for development --- after they have become an established
Cygwin/XFree86 developer).  There is also a section for links to any
individual contributor's web pages.  Currently there is only my own link on
this page:
http://www.msu.edu/~huntharo/xwin/donations.htm


The PayPal account that I have setup can accept credit card payments from
anyone; additionally, PayPal members should be able to directly transfer
funds into my PayPal account from their own account.


By all means, do not feel obligated to make a donation.  Also, realize that
future Cygwin/XFree86 development does not depend upon the amount of
donations received.  Granted, it will be easier to do development when I
know that my hardware upgrade costs are taken care of, but I will always be
spending some amount of time tinkering with Cygwin/XFree86 regardless of the
amount of donations.  Think of the donations as either a way for you to give
a token of your appreciation or as a way for you to influence the priority
and amount of time put in to developing some feature that you would benefit
from.


Let the donations begin! ;)


Harold

P.S. One contributor has already given $25 and I thank him for that (he
knows who he is).




RE: x2x or XWin -screen 0 2048 768 ?

2002-09-26 Thread Harold Hunt

Jean-Claude,

 All that aside, it would be an interesting feature to implement user
 window-sizing to arbitrary resolutions via the -scrollbars
 parameter so that
 a user might stretch the X display to the size s/he wants. But
 I'm not clear
 on whether or not X allows resizing once an X 'console' has started. Does
 it?


Oops, that was one of the things I was going to mention.  It is not possible
to resize the X display after it has been initialized.  The RandR extension
will eventually allow this, but I am not sure if it is stable/complete yet.

Harold




Devel update

2002-09-26 Thread Harold Hunt

I had a little bit of time today and yesterday so I made some build-bustage
fixes to the CVS tree and I finished up a little feature that has been
holding me up from making any kind of release.  That little feature I was
working on was embedding an icon in XWin.exe via a compiled Windows resource
file.  My initial work with the resource file required that ``windres'' be
run manually to compile the resource file, but the compiled resource file
was automatically linked into the executable.  Today I created resource
build rules in cygwin.rules that work both under Cygwin and when cross
compiling.  I've been using Cygwin/XFree86 with a little ``X'' icon for over
a month now but I couldn't make any test releases until I either pulled the
icon support out or until I reimplemented it properly.

There is nothing holding me up from making a new test release now, other
than the 100 KB diff that I have to clean up, so I will try to get a test
release out sometime in the next week.  Perhaps this will be followed by a
4.2.1 release, but perhaps not.


Harold




Cygwin Build Bustage Fix

2002-09-25 Thread Harold Hunt

xc/lib/Xcursor/Imakefile:
1) Change an #elif without a conditional to #else.  This has got to be one
of the dummer mistakes I have ever seen.  How does this work on any
platform?  This busts the build on Cygwin.


Harold



xc-lib-Xcursor-Imakefile.diff
Description: Binary data


One more Cygwin build bustage fix

2002-09-25 Thread Harold Hunt

xc/config/cf/cygwin.tmpl:
1) Add SharedXcursorReqs with $(XLIB) so that libXcursor builds.

Harold


xc-config-cf-cygwin.cf.diff
Description: Binary data


RE: Running xterm on localhost with XWin

2002-09-24 Thread Harold Hunt

Mario,

Just follow the User's Guide instructions:
http://xfree86.cygwin.com/docs/ug/using-remote-apps.html

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Mario Ohnewald
 Sent: Tuesday, September 24, 2002 5:46 AM
 To: [EMAIL PROTECTED]
 Subject: Running xterm on localhost with XWin
 
 
 Hello!
 Should this not work:?
 
 XWin -screen 0 640 480   # open X
 set DISPLAY=127.0.0.1:0.0 # set Display
 xterm.exe # run app. wich should appar in X
 
 xterm Xt error: Can't open display:
 
 Cheers, Mario



RE: minimized XWin is killed

2002-09-18 Thread Harold Hunt

That is really bizarre.

I'd like to take a look at this, but can you send in your /tmp/XWin.log
contents from when this happens?

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Norbert Schmidt
 Sent: Wednesday, September 18, 2002 11:09 AM
 To: [EMAIL PROTECTED]
 Subject: minimized XWin is killed



 If I start remote windowmanager via ssh to my local _minimized_
 fullscreened XWin, it disappears from desktop. (up to XWin-Test65.exe)

 (workaround is a remote script with sleep 1 before starting Xsession in
 order to switch quickly from terminal to fullscreened XWin)

 Norbert





RE: XFree hangs after first client is started

2002-09-18 Thread Harold Hunt

Carlos,

Sorry I didn't get back to you, but you did find the explanation in the FAQ.
Basically, Aventail does something to the TCP/IP stack that breaks
compatibility with the standards that Cygwin and XFree86's sockets layers
are expecting.  Aventail replaces a couple of Windows DLLs with its own
versions, thus it does not matter if Aventail is running or not, because you
are always passing your sockets requests through their broken DLLs.  If you
ask me, that is simply a design flaw or implementation flaw with Aventail
and they need to fix that.  You, being a paying customer, should demand that
of them.

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Carlos Santiago
 Sent: Tuesday, September 17, 2002 12:01 PM
 To: [EMAIL PROTECTED]
 Subject: Re: XFree hangs after first client is started


 Hello Harold,

 I went ahead and checked the XFree FAQ, and found
 that Aventail Connect is, indeed, one of the software
 VPNs with known problems.

 I guess I will assume then that a box with Aventail
 Connect will not be able to bring the X server up
 properly even for local use.

 Thanks,

 - Carlos






RE: xcb port to Cygwin; questions about packaging

2002-09-18 Thread Harold Hunt

 Window Maker news
 -

 Oh, I also patched and built Window Maker 0.80.1 (the latest release),
 and submitted my patches back to the WM developers, and they've been
 included.  So, future builds of WM should be as simple as running
 ./configure; make; make install.  (Then each user runs wmaker.inst in
 the usual way from a shell prompt to create the necessary files in their
 home directory.)

Luke,

Hmm... I guess that means I will have to update the Cygwin WindowMaker
package.  :)

Harold




RE: xwinclip - update and motif clipboard

2002-09-18 Thread Harold Hunt

Chris,

I thank you for putting so much time into developing xwinclip.

I really appreciate that you got the long-awaited setjmp lngjmp
functionality implemented so that we are not killed upon X Server shutdown
and restart.

I don't know anymore about the CLIPBOARD than what I wrote in the xwinclip
source comments, which was something to the effect of, ``help! can't find
CLIPBOARD documentation, how does it work?''

I am going to integrate your changes into a future release of xwinclip, but
I cannot tell you when that will be.  However, a little schedule update: I
am taking 10 credits this semester in three classes (this is not much), I am
working 30-35 hours a week at an Active Server Pages (blah :( ) job (but it
pays really well), and I am working 6-8 hours a week at the National
Superconducting Cyclotron Laboratory at Michigan State University (where I
translate old Fortran program for VMS to Tru64 UNIX and Linux).  Next week
my ASP job is supposed to slow down because they haven't got another
contract for me to work on, so I may, in theory, have a whole week to catch
up on Cygwin/XFree86.  On the other hand, shit happens, so don't expect
anything extraordinary.  :)

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Chris Twiner
 Sent: Thursday, September 05, 2002 11:58 AM
 To: [EMAIL PROTECTED]
 Subject: xwinclip - update and motif clipboard


 Hi All,

 Quick update, got the signal working properly for ctrl-c or closing the
 windows command window.  Solution (as the SIGINT handler is run in a
 seperate thread in windows) is to set a variable in the windows loop that
 sends the kill message that kill_xwinclip was doing.

 That means that all the kill_.. apps that I wanted to get rid of
 can be (and
 have). It also means that I don't need a window to handle turning
 on and off
 clipboard operations a simple close of the window would be sufficient.

 Also I believe that handling the xIO error as a thread within
 XWin should be
 possible but I'd still be tempted to run it seperately as xwinclip.  It
 could work integrated if it was run as a seperate thread (would
 need to be
 anyway really), as such longjmp and setjmp should affect only
 that thread.
 Again I don't see how much sense this really makes.

 I do have a remaining issue that I'd like to solve, CLIPBOARD operations.
 The problem seems to be the application I'm using i.e. NEdit uses Motif
 programming interfaces (or lesstif) in the default distribution.  This
 leaves four questions :

 1) Should we try to get Motif clipboard operations (like klipper)?
 2) If so how do we identify that what client owns the clipboard
 is a motif
 one (to use the motif mechanism for getting the clipboard data)?
 3) Should we try to get motif clipboard before the X clipboard or after?
 4) How exactly do we get the motif clipboard?

 I belive 1) should be a yes but as yet I'm at a loss to attempt
 the other 3
 questions.  I have read that the root window property CLIPBOARD holds the
 clipboard for Motif apps but xprop dumps when i do
 xprop -root CLIPBOARD.

 Either way I've have only just started looking at that issue and I'm just
 about to read

 http://www.ist.co.uk/motif/books/vol6A/ch-21.fm.html#649570

 But any help would be nice from someone who knows the answers now :-)

 anywho,

 chris

 PS (Jehan and Harold, it was all tab characters that I was
 inserting, I'll
 change them to the two space's that Harold uses).

 _
 Send and receive Hotmail on your mobile device: http://mobile.msn.com





RE: Cygwin/XFree86 Multi-Monitor on Matrox G550

2002-09-08 Thread Harold Hunt

Bryan,

There is not currently support in the X server for specifying a Windows
display that a particular screen should be displayed upon initially.  It may
not be that hard to add, but no one has scratched that itch yet.

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Bryan Hundven
 Sent: Sunday, September 08, 2002 1:49 AM
 To: [EMAIL PROTECTED]
 Subject: Cygwin/XFree86 Multi-Monitor on Matrox G550


 I was looking on cygwin.com for help with setting up XFree86 on w2kpro
 w/Dual-Head.
 Windows 2000 already has dual head setup with my Matrox drivers.
 Right now my primary display is 1280x1024@60Hz 32bit, and my secondary
 display is 1024x768@60Hz 32bit.

 I would like to have X start as a window 1024x768 on my secondary (as
 apposed to on the primary). How would I do that without having to
 start the
 server at 1024x768 and drag it to the second display?

 Bryan Hundven bryanh AT nventure DOT com





RE: Using KDE as default desktop under Windows

2002-09-02 Thread Harold Hunt

Interesting.

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of David Fraser
 Sent: Saturday, August 31, 2002 12:55 PM
 To: [EMAIL PROTECTED]
 Subject: Using KDE as default desktop under Windows


   Hi there
 I posted this to the kde-cygwin mailing list and someone suggested
 reposting it here.
 Basically an explanation of my kde setup under Windows...

 I am now using KDE as my default shell under Windows.
 Thanks to everyone for the effort - it's so much nicer than explorer :-)
 I thought it would be nice to have a page on the web site explaining how
 to do it,
 and indicating status as more integration gets done...
 basically this is what I did (this is for Windows 2000 but should be
 portable to others):

 make XFree86 server run full screen without window decoration
   change ~/.xserverrc to include -fullscreen in the parameters:
 exec X - screen 0 1024 879 -engine 4 -fullscreen -depth 32 -ac
 -nowinkill -noreset -emulate3buttons 100
   you can say -nodecoration (which -fullscreen implies) instead if you
 want a non-fullscreen window without border etc.

 replace the default shell, explorer.exe with X-windows
   change the following reg entry under from explorer.exe to
 c:\cygwin\bin\bash --login -c startx
 HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
 NT\CurrentVersion\Winlogon\Shell
 Once this is done, logging in starts up the X server but no Windows
 desktop, Start bar etc.
 Note: if you want to run windows programs from here, on Windows 2000 you
 can press Ctrl-Shift-Esc
 which brings up the Task Manager, then go File/Run.
 Logging out from KDE doesn't actually log out, you need to close KDE in
 another way and then press Ctrl-Alt-Del
 and choose logout. Depending on your .xserverrc parameters,
 Ctrl-Alt-Backspace or Alt-F4 can be made to close
 the X server. Otherwise, you can close it from the Task manager (select
 the Cygwin task and say End Task).
 This also brings up a bash shell window which is behind the X server. I
 tried to get rid of it by running
 cmd /c start /b bash ... but this was unsuccessfull.
 If you switch to any windows applications, the X server will be minimised.
 I seem to remember some discussion on slashdot or somewhere about how
 Cygwin XFree86 cannot run in rootless
 mode (as the actual background window like Windows exlporer does for the
 desktop). Does anyone have any info
 on why this is, or on how we could patch it so that it will? That way
 windows apps will run in front...

 Next step: get KDE to run windows applications from short cuts.
 I created a simple script called win32start:

 #!/bin/bash
 startpath=$*
 if [[ -L $startpath ]]
   then
   # this is a symbolic link. find the actual file, start that
   startpath=`find $startpath -printf %l`
 fi
 startdir=`dirname $startpath`
 startfile=`basename $startpath`
 cd $startdir
 cmd /c start \starting application\ $startfile

 This is put in /usr/bin
 It handles cygwin unix-style symbolic links to Windows shortcut files as
 well (both are given
 the extension .lnk, but have different stuff inside ... if you create a
 link to a shortcut it is thus
 called .lnk.lnk).
 Basically it gets whatever parameters are given (it needs to use them
 all so you can pass spaces
 without it separating them out; escaping the spaces with backslash
 confuses cmd, although they
 could be unescaped) and works out what directory the file to start is in.
 It's easiest to get into this directory as we then don't have to convert
 the path from unix to windows
 style. Then it runs cmd and tells it to start the application. The first
 parameter to start is the window
 title which has to be given if we quote the start file. But this window
 title only applies to cmd, which
 just starts the application and quits.
 Example:
 $ win32start /c/Documents\ And Settings/All\ Users/Start\
 Menu/Programs/Acrobat\ Reader\ 5.0.lnk
 on my system this starts up Acrobat.

 Now we want to make KDE associate these files with win32start so we can
 click on them from konqueror
 and put them in menus.

 First we need a mime type for the Windows shortcut files...
 Add the following to a new file
 ~/.kde2/share/mimelnk/application/win32shortcut.desktop
 (on most systems, it could be ~/.kde/... - I've had KDE 1 installed ...)
 This users the link icon which just looks like a shortcut. It would be
 nice to get KDE to read
 the windows Icon out of the shortcut file but probably lots of work

 [Desktop Entry]
 Comment=Win32 shortcut file
 Hidden=false
 Icon=link
 MimeType=application/win32shortcut
 Patterns=*.lnk
 Type=MimeType

 Then create the association. To do this, create a desktop file under
 ~/.kde2/share/applnk/win32start.desktop
 and place the following into it:

 [Desktop Entry]
 Comment=Start Win32 applications or files
 Exec=win32start
 Icon=exec
 InitialPreference=3
 MimeType=Application;application/win32shortcut
 Name=Win32 Starter
 Path=
 ServiceTypes=
 Terminal=false
 TerminalOptions=
 

RE: building XFree86 from cvs

2002-08-26 Thread Harold Hunt

Guy,

Okay, this looks reasonable.  I will take a look at it and submit it when I
get a chance.  Classes start today, so it may be a few days.

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Guy Harrison
 Sent: Sunday, August 25, 2002 5:13 PM
 To: [EMAIL PROTECTED]
 Subject: Re: building XFree86 from cvs


 On Fri, 23 Aug 2002 14:58:33 +0200 (CEST), Alexander Gottwald
 [EMAIL PROTECTED] wrote:

 On Fri, 23 Aug 2002, Guy Harrison wrote:
 
 
  I've done similar to other Imakefiles that require it. Should I post
  details?
 
 You could send a diff against current CVS

 Here goes...

 Index: xc/config/util/Imakefile
 ===
 RCS file: /cvs/xc/config/util/Imakefile,v
 retrieving revision 3.45
 diff -r3.45 Imakefile
 32,33c32,33
  PROGRAMS = $(RMAN_PROG) $(LNDIR_PROG) ProgramTargetName(makestrs) \
 ProgramTargetName(revpath) $(EXPORTLISTGEN) $(CMKDIRHIER)
 ---
  PROGRAMS = rman lndir makestrs revpath $(EXPORTLISTGEN) $(CMKDIRHIER)
 
 83c83
  SimpleProgramTarget_2($(LNDIR_PROG))
 ---
  SimpleProgramTarget_2(lndir)
 114c114
  AllTarget(ProgramTargetName(rman))
 ---
  AllTarget(rman)
 Index: xc/programs/bitmap/Imakefile
 ===
 RCS file: /cvs/xc/programs/bitmap/Imakefile,v
 retrieving revision 3.7
 diff -r3.7 Imakefile
 56c56
 PROGRAMS = ProgramTargetName(bitmap) ProgramTargetName(bmtoa)
 ProgramTargetName(atobm)
 ---
 PROGRAMS = bitmap bmtoa atobm
 Index: xc/programs/proxymngr/Imakefile
 ===
 RCS file: /cvs/xc/programs/proxymngr/Imakefile,v
 retrieving revision 1.12
 diff -r1.12 Imakefile
 19c19
  PROGRAMS = ProgramTargetName(proxymngr)
 ---
  PROGRAMS = proxymngr
 Index: xc/programs/xclipboard/Imakefile
 ===
 RCS file: /cvs/xc/programs/xclipboard/Imakefile,v
 retrieving revision 1.3
 diff -r1.3 Imakefile
 11c11
 PROGRAMS = ProgramTargetName(xclipboard)
 ProgramTargetName(xcutsel)
 ---
 PROGRAMS = xclipboard xcutsel
 Index: xc/programs/xdm/Imakefile
 ===
 RCS file: /cvs/xc/programs/xdm/Imakefile,v
 retrieving revision 3.47
 diff -r3.47 Imakefile
 206c206
   XDM_SHADOW = ProgramTargetName(xdm-shadow)
 ---
   XDM_SHADOW = xdm-shadow
 209c209
  CHOOSER = ProgramTargetName(chooser)
 ---
  CHOOSER = chooser
 211c211
 PROGRAMS = ProgramTargetName(xdm) ProgramTargetName(xdmshell)
 ProgramTargetName(sessreg) $(CHOOSER) $(XDM_SHADOW)
 ---
 PROGRAMS = xdm xdmshell sessreg $(CHOOSER) $(XDM_SHADOW)
 Index: xc/programs/xfindproxy/Imakefile
 ===
 RCS file: /cvs/xc/programs/xfindproxy/Imakefile,v
 retrieving revision 1.4
 diff -r1.4 Imakefile
 15c15
PROGS1 = ProgramTargetName(xfindproxy)
 ---
PROGS1 = xfindproxy
 Index: xc/programs/xinit/Imakefile
 ===
 RCS file: /cvs/xc/programs/xinit/Imakefile,v
 retrieving revision 3.16
 diff -r3.16 Imakefile
 24c24
 PROGRAMS = ProgramTargetName(xinit)
 ---
 PROGRAMS = xinit
 Index: xc/programs/xsm/Imakefile
 ===
 RCS file: /cvs/xc/programs/xsm/Imakefile,v
 retrieving revision 1.8
 diff -r1.8 Imakefile
 38c38
PROGS1 = ProgramTargetName(xsm)
 ---
PROGS1 = xsm

 ...it might even still cross-compile! ;-)

 Only one problem left: xterm compilation error. Probably a
  header which I don't want to look at until all these script issues are
  sorted out.
 
 Please send the output from that error

 Cockpit error on this one (me using ccache): and no, I haven't been
 using it all the time. The main problem existed well before I thought
 about speeding things up with it.


 --
 [EMAIL PROTECTED]




RE: displaying windows outside the main window

2002-08-25 Thread Harold Hunt

Speaking of a PayPal account... I have one.  I even set it up to accept
credit card payments a few weeks ago, but I haven't yet put a link to it
from my personal page.  I think I now have some motivation to do so :)

I'll will post once to the list to let people know that the link exists, and
I'll make sure that there are links to my home page from the Cygwin/XFree86
page, but I won't put a PayPal link directly on the Cygwin/XFree86 page
because I believe that would violate the spirit of the project.  --- That
was just so that everyone knows that I will be ethical about this :)

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Rasjid Wilcox
 Sent: Sunday, August 25, 2002 10:22 AM
 To: [EMAIL PROTECTED]; Rahul Amaram-RollNo.286
 Subject: Re: displaying windows outside the main window


 On Sun, 25 Aug 2002 9:48 pm, Rahul Amaram-RollNo.286 wrote:
  Hi,
  Is it possible to display the clients' windows like xterm, rxvt,
  ymeesenger, etc. outside the main single window??? Any help would be
  appreciated.
  Rahul.

 See http://xfree86.cygwin.com/devel/todo.html.  It is at the top
 of the list,
 but Cygwin-XFree is developed in peoples spare time.

 Harold did offer to develop needed features in return for some
 renumeration.
 http://cygwin.com/ml/cygwin-xfree/2002-07/msg00090.html

 I didn't respond to Harold's post at the time, as unfortunately I
 don't hold
 the purse strings where I work, but philosophically I am strongly
 in favour
 of people paying money to get features they want developed in Open-Source
 software.  I have helped my workplace become a paying customer to two
 open-source products, Mitel's SME server and Astaro's Security Linux.

 If Harold had a pay pal account, I would happily contribute US$10,
 particularly if a number of other people did so too.  Perhaps
 setting up some
 kind of pledge system.  Something along the lines of:

 Task 1: Rootless mode
 --
 ---
 |Name   | Amount Pledged   | Contact
   | Rec'd |
 --
 ---
 | Joe Blogs |  $20 |
 [EMAIL PROTECTED]  |  Yes  |
 | Mary Smith|  $15 |
 [EMAIL PROTECTED]  |   |
 | etc

 Task 2: ..

 Once the task is complete, someone follows up each pledge. I
 would suggest
 that that someone not be the developer(s).  An automated system would be
 better.  Anyone know of an existing system that could be coerced
 to do the
 task?

 Would RedHat be happy to host such a pledging system on their servers?  I
 would be happy to host it on my sever. Note that it is only on an ADSL
 connection with a 64kbs uplink speed.  However, it is up 24/7 and
 does have a
 fixed IP.

 The contact email address would need to be obscured from the spammers, or
 perhaps kept off public pages altogether.

 What do people think?  Could it work?  Is it already being done somewhere?

 I have just found some pages by Christopher Browne, called the
 Free Software
 (Gift) Exchange Registry (http://cbbrowne.com/info/fssp.html),
 but he just
 talks about a similar idea.  There is no reference to someone actually
 putting his idea into practice.  Christopher does raise the issue
 of gifts
 and tax, and his article is generally a good read.

 Rasjid.





RE: building XFree86 from cvs

2002-08-20 Thread Harold Hunt

If that is the case then the Imakefile for xterm needs to be fixed because
some non-Cygwin programmer that has an empty ProgramTargetName macro
accidentally wrapped each target name in PROGRAMS with ProgramTargetName.
On their non-Cygwin platform this makes no difference, but on Cygwin this
makes a huge difference because our ProgramTargetName appends .exe to the
target name.  Thus, someone simply needs to remove the ProgramTargetName
wrappings from xterm's Imakefile and submit that as a patch.

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Alexander Gottwald
 Sent: Tuesday, August 20, 2002 5:25 AM
 To: [EMAIL PROTECTED]
 Subject: RE: building XFree86 from cvs


 On Mon, 19 Aug 2002, Harold L Hunt wrote:

  Do you understand what PROGS_EXE is for?  Do you understand why
 we cannot use
  PROGRAMS?

 No.
 PROGS_EXE is simply all strings from PROGRAMS with .exe added. But
 the .exe is already added before ComplexTarget is called.

 So if eg. compiling xterm, PROGRAMS contains xterm.exe and PROGS_EXE the
 contains xterm.exe.exe

 bye
   ago
 --
  [EMAIL PROTECTED]
  http://www.gotti.org   ICQ: 126018723





RE: building XFree86 from cvs

2002-08-18 Thread Harold Hunt

Michael,

Oh, you are only missing about 30 pages that describe exactly how to build
XFree86 for Cygwin:
http://xfree86.cygwin.com/docs/cg/cygwin-xfree-cg.html

Start with those.  It is unlikely that you will have problems.

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Michael D. Harnois
 Sent: Sunday, August 18, 2002 1:34 PM
 To: [EMAIL PROTECTED]
 Subject: building XFree86 from cvs


 All of the build instructions I've been able to find on the web
 suggest that the same simple make World instructions that work on
 other platforms ought to work on cygwin as well. Well ... I am getting
 a bunch of errors, all of which look pretty much like this one. What
 am I missing here?

 make[4]: *** No rule to make target `lndir.exe.o', needed by `lndir.exe'.
 gcc -O2 -fno-strength-reduce -Wall -Wpointer-arith -I../..
 -I../../exports/i
 nclude   -D__i386__ -DWIN32_LEAN_AND_MEAN -DX_LOCALE -D_X86_
 -D__CYGWIN__ -D_XOP
 EN_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE
 -D_GNU_SOURCE -
 DNO_ALLOCA  -DFUNCPROTO=15 -DNARROWPROTO   -c -o revpath.o revpath.c
 rm -f revpath.exe
 gcc -o revpath.exe -O2 -fno-strength-reduce -Wall -Wpointer-arith
  revpath.o
   -L/usr/X11R6/lib -Wl,--enable-auto-import
 make[4]: Target `all' not remade because of errors.
 make[4]: Target `all' not remade because of errors.
 make[4]: *** No rule to make target `lndir.exe.man', needed by
 `lndir.exe._man'.
 make[4]: Target `all' not remade because of errors.
 make[4]: Target `all' not remade because of errors.
 make[4]: *** No rule to make target `rman.exe.exe', needed by `all'.
 make[4]: *** No rule to make target `makestrs.exe.exe', needed by `all'.
 make[4]: *** No rule to make target `revpath.exe.exe', needed by `all'.
 make[4]: Target `all' not remade because of errors.


 --
 Michael D. Harnois   bilocational bivocational
 Pastor, Redeemer Lutheran ChurchWashburn, Iowa
 2L, UST School of Law   Minneapolis, Minnesota
  Where ignorance is our master, there is
  no possibility of real peace. -- the Dalai Lama





RE: XWin not found

2002-08-17 Thread Harold Hunt

Run:
cygcheck -c XFree86-xserv

Send the results to [EMAIL PROTECTED]

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Ben Jobse
 Sent: Saturday, August 17, 2002 3:19 PM
 To: [EMAIL PROTECTED]
 Subject: XWin not found
 
 
 LS,
 
 I am new to this list and not familiar to Cygwin.
 I am rather familiar to Unix
 
 I downloaded and installed the latest release which also contains Xfree.
 I am running XP Home
 
 Attempting to startup Xfree (startxwin.sh) results in
 XWin: not found. And indeed I can't locate XWin.
 
 Looked into the install log but everything went well.
 Looked into FAQ's and the mail archive without success.
 
 ?
 
 thx,
 Ben Jobse
 
 
 
 



RE: newbie - export X(-Applications) from Linux Server

2002-08-01 Thread Harold Hunt

Mario,

After launching XWin and before launching xterm, you need to:

export DISPLAY=127.0.0.1:0.0

This is why you should really be using startxwin.bat or startxwin.sh, as
outlined in the Cygwin/XFree86 User's Guide.

http://xfree86.cygwin.com/docs/ug/using.html#using-starting


Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Mario Ohnewald
 Sent: Thursday, August 01, 2002 3:23 AM
 To: [EMAIL PROTECTED]
 Subject: RE: newbie - export X(-Applications) from Linux Server


 Hello!
  Mario,
 
   From what I know, doing this doesn't always work:
install@MUNICH ~
$ cd /usr/X11R6/bin
   
install@MUNICH /usr/X11R6/bin
$ ./XWin.exe 
[1] 108
   
install@MUNICH /usr/X11R6/bin
$ ssh -X [EMAIL PROTECTED]
[EMAIL PROTECTED]'s password:
Last login: Sat Jan  5 06:42:18 2002
Have a lot of fun...
dex@linuxserver:~ xclock
 
  What you need to do instead is:
  install@MUNICH ~
  $ cd /usr/X11R6/bin
 
  install@MUNICH /usr/X11R6/bin
  $ ./XWin.exe 
 
  install@MUNICH /usr/X11R6/bin
  $ ./xterm.exe 
 

 I did that, and thats what i get:

 install@MUNICH /usr/X11R6/bin
 $ ./xterm.exe
 ./xterm Xt error: Can't open display:

 ;/
 here is the logfile:
 -
 install@MUNICH /tmp
 $ cat XWin.log
 OsVendorInit - Creating bogus screen 0
 winInitializeDefaultScreens - w 1152 h 864
 winInitializeDefaultScreens - Returning
 _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
 (EE) Unable to locate/open config file
 Error reading config file
 winDetectSupportedEngines - Windows NT/2000/XP
 winDetectSupportedEngines - DirectDraw installed
 winDetectSupportedEngines - Allowing PrimaryDD
 winDetectSupportedEngines - DirectDraw4 installed
 winDetectSupportedEngines - Returning, supported engines 001f
 InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1
 winSetEngine - Using Shadow DirectDraw NonLocking
 winAdjustVideoModeShadowDDNL - Using Windows display depth of 16 bits per
 pixel
 winCreateBoundingWindowWindowed - Initial w: 1152 h: 864
 winAdjustForAutoHide - Original WorkArea: 0 0 811 1152
 winAdjustForAutoHide - Adjusted WorkArea: 0 0 811 1152
 winCreateBoundingWindowWindowed - WindowClient w 1146 h 786 r
 1146 l 0 b 786
 t 0
 winCreateBoundingWindowWindowed -  Returning
 winAllocateFBShadowDDNL - lPitch: 2292
 winFinishScreenInitFB - Masks: f800 07e0 001f
 winInitVisualsShadowDDNL - Masks f800 07e0 001f BPRGB
 6 d 16 bpp
 16
 winCreateDefColormap - Deferring to fbCreateDefColormap ()
 winScreenInit - returning
 (EE) No primary keyboard configured
 (==) Using compiletime defaults for keyboard
 Rules = xfree86 Model = pc101 Layout = us Variant =
 (null) Options =
 (null)
  Now, from the xterm in Cygwin/XFree86 (you are getting a
  Cygwin/XFree86
  window, right?  If not something else is broken and you need
  to send in
  /tmp/XWin.log) run the ssh command:
  [xterm window]
  install@MUNICH /usr/X11R6/bin
  $ ssh -X [EMAIL PROTECTED]
 
  Now you can run xclock and it should work.
 
  Harold
 

 Cheers!
 Mario





RE: [ITP]: Qt-2.3.1

2002-07-25 Thread Harold Hunt

Well, remember also that the X11 version is licensed under the GPL, so it is
fine.  They do make some other versions that are not yet licensed under the
GPL.  The native Windows version used to be non-GPL, but I think I remember
seeing something in the news about this changing a few months ago or
something.

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Robert Collins
 Sent: Thursday, July 25, 2002 8:52 AM
 To: [EMAIL PROTECTED]
 Subject: Re: [ITP]: Qt-2.3.1


 On Thu, 2002-07-25 at 22:45, Corinna Vinschen wrote:

  Are you sure that we don't get licensing issues here?  AFAIK, Qt is
  (roughly) only free when running on a free OS.  Basically we're
  still running on Windows...

 http://www.trolltech.com/developer/licensing/

 Summary, 2.2 and later is QPL and GPL. They may not like it, or they may
 like it. Who knows. But... they can't stop it.

 Rob





RE: Cygwin/XWin - winkeybd.c/winKeybdBell(...) not being called?

2002-07-24 Thread Harold Hunt

John,

*You* screwed up in two major ways, not me:

1) You emailed me directly.  I do not appreciate email sent to me from
people wishing to deal with the Cygwin/XFree86 project.  I do not need your
permission to forward such emails to the mailing list.

2) You did not inform me at the top of the email that you were protective of
your email address.  If you had, I would have simply deleted your email
rather than forwarding it to the mailing list.

You have to remember that with the Internet, you have to look out for
yourself.  If you are truly concerned about the protection of your email
address, then you should be using temporary accounts for any emails that you
SPAM project leaders with.  Yup, you spammed me.  You sent me an unsolicited
personel email rather than sending it to the project that I work on.

Thanks, now go away,

Harold

P.S.  You will notice that I have taken the care to remove your email
addresses from the bottom of this message.

 Harold,

 Thank you for your reply, however I would have appreciated it if
 you had *not* forwarded my query directly to the mailing list.

 I am quite capable of sending such an email myself.  I've had
 very bad experiences with spam originating from www mailing list
 archives and I would not have included my signature which has now
 been archived onto the web:

 http://www.cygwin.com/ml/cygwin-xfree/2002-03/msg00266.html

 If you can now *remove* that message from the list archive, I would
 be most grateful.  It includes my `' address quoted as-is,
 which I have tried *extremely* hard to keep from spammers.

 I'd assume that normally signatures are removed by the list, however
 you had quoted my message and so it remained.

 John.


 On Wed, Jul 24, 2002 at 12:20:58AM -0400, Harold Hunt wrote:
  John,
 
  You are asking a question of the Cygwin/XFree86 project.  As
 such, you need
  to send all correspondence regarding Cygwin/XFree86 to
  [EMAIL PROTECTED]  I cannot answer email sent directly to me.
 
  Note: I have forwarded your question to [EMAIL PROTECTED]
 
  Harold





RE: problems with XFree

2002-07-24 Thread Harold Hunt

 Harold, thanks for the suggestions.  I was hoping that oue of them would
 solve the problem.  I checked and found only one cygwin1.dll on the
 system.  It's dated 5 July.  I update frequently using setup.exe.

 I agree with you assessment of Windows.  However, my problem isn't the
 BSOD but XFree86 seg fault.  Windows keeps on working and the (apparent)
 memory leak resolves itself after CFree86 croaks.

 Let me know if there is anything else I can do on my end to identify the
 problem.

 Thanks,
 Tom

Tom,

Have you sent in the contents of /tmp/XWin.log from a time when this problem
happens?

Harold




RE: problems with XFree

2002-07-24 Thread Harold Hunt

Jehan,

Excellent summarization of the thread regarding how we can add
/usr/X11R6/bin to the path.

Looks like we had Dave Cook and Robert Collins discussing the best way to do
things but then the thread died.

I don't really think that I know how to implement the best solution here, so
I will just have to leave this up to others.

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Jehan
 Sent: Tuesday, July 23, 2002 10:17 PM
 To: [EMAIL PROTECTED]
 Subject: Re: problems with XFree


 Harold L Hunt II wrote:
  Sylvain Petreolle wrote:
 
  Why not install a file in /etc/profile.d ?
 
 
  Sylvain,
 
  I am not sure why we didn't use /etc/profile.d.  I remember discussing
  it, but when I searched the mailing list archives using the search
  function at the top of the archive page, all I got was a bunch of spam
  messages that I don't recall ever seeing on the mailing list (at least
  not on the dates mentioned).  I will have to do a google search for
  profile.d on our site, but I haven't got time now.  If you could do the
  search and summarize where the thread left off, that would be great.
 
  I seem to remember that a profile.d would work for some cases, but it
  wouldn't work for all cases... but I cannot give a specific example
  (might be the archives as well).

 There was some talk about that on this thread:
 http://sources.redhat.com/ml/cygwin-xfree/2001-q2/threads.html#01549

 There they say that the path to X should be set before any call to
 /etc/profile.d/* to be more Unix like (i.e. near the top of /etc/profile).

 It was suggested to add
   if ! echo $PATH | /bin/grep -q /usr/X11R6/bin ; then
 PATH=$PATH:/usr/X11R6/bin
   fi

 at the top of /etc/profile. The comment was:
   Now the stock Cygwin /etc/profile (unlike the Linux one)
   actually sets a default PATH on the first line via

   PATH=/usr/local/bin:/usr/bin:/bin:$PATH

   Fortunately this puts the important system paths ahead of
   anything already defined, so it's OK to add /usr/X11R6/bin at
   the top.

 Post http://sources.redhat.com/ml/cygwin-xfree/2001-q2/msg01574.html;
 is supposed to give a patch but I don't see it. Anyway, it was for the
 cygwin install (with the assumption that Cygwin/XFree would soon use
 Cygwin's setup). It's probably better to have a post-install
 script to do it

   Jehan







RE: Obtaining Hummingbird-like behavior

2002-07-24 Thread Harold Hunt

Brian,

 Assuming you're not speaking tongue in cheek, Nicholas, I can see
 a need for
 doing this ... and intend to demo it on some of haplass end users someday.

Does this mean that you are working on a rootless mode for Cygwin/XFree86?

Harold




RE: problems with XFree

2002-07-23 Thread Harold Hunt

Tom,

I bet that you either have two copies of cygwin1.dll on your system, or that
you have a really old version of cygwin1.dll.  For more information see:

http://xfree86.cygwin.com/docs/faq/cygwin-xfree-faq.html#q-status-access-vio
lation

I run XDMCP sessions for several hours with no slowdowns or lockups.  I also
log off and back on to XDMCP sessions all the time.  A couple of days ago I
did identify and fix a memory leak that happens when the X server resets,
which happens when you logoff an XDMCP session.

I think that Windows 2000 and Windows XP do not show a bluescreen anymore by
default.  You can change that option in the Control Panel.  You mention that
this also happens on Windows 95/98/Me, which seems to be about the level of
information that you can expect from those OSes when they crash.

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Tom Bozack
 Sent: Monday, July 22, 2002 10:32 PM
 To: [EMAIL PROTECTED]
 Subject: Re: problems with XFree


 I think Cygwin/XFree86 is a great product  -- but there is nothing so
 good that it can't be improved.  I agree with all of you comments,
 although I haven't had the system reboot experience.

 One persistant problem that you didn't mention (manybe you haven't run
 into it yet) is a very persistent and repeatable lock-up when used to
 login to another host using XDMCP.  The symptom is of a sudden large
 memory leak after 15-30 minutes of use.  XFree86 becomes unresponsive,
 system memory and swap resources are rapidly used up, and finally
 XFree86 crashes with a seg fault.  This also happens immediately (you
 don't have to wait 15-30 min) when you logoff the host and login again.
   I've experienced this under Windows 98/98SE/ME.

 For me this is a showstopper since it makes Cygwin/XFree86 unusable as
 an X server platform.  It's fun to play with, but this bug makes it
 unacceptable for routine use as an X server.

 Tom

 [EMAIL PROTECTED] wrote:
  (last email I sent complained about HTML MIME. i hope i'm not
  double-posting)
 
  I started playing with XFree last week. It's been a few years
 since I've
  used UNIX, so you can call me a newbie, if you like. I'm
 running Windows
  2000 Pro on a P4 1.7 GHz with 768 MiB of RAM and 10 GB free on my hard
  drive. I (eventually) did a full Cygwin/XFree86 download and install
  (binaries, not source).
 
  Please don't flame me if I'm out of line. I didn't know if I
 should break
  this up into several emails or have one big one. Also, please send
  responses to me by email.
 
  Here are my obervations/problems.
  Showstoppers:
  1) The very first time I brought up the X server, I had modified
  startxwin.bat
  to use wmaker instead of twm. It crashed because /home
  hadn't been created yet. This was fixed by running the text-mode bash
  icon first.
  2) when I run Xman, it says No App-Defaults File. If I run
 Xman -notop
 
  instead, I can browse one man page, and then it stops working.
 (it gives a
 
  likeToSave message box with yes and no buttons that don't seem to do
  anything.) It seems to be related to missing a locale binary.
 Is there a
  way to get this to work?
  3) within the first few hours of usage, I ran a find / -name
 abc -print
  from the command-line, and my trusty Windows 2000 box
 restarted. no blue
  screen, no error. it was like someone pulled the power plug and
 plugged it
 
  back in. after it came up, i tried the same command and it worked fine.
  4) i had a similar restart to #6 when I ran setup.exe while
 cygwin was
  up. of course, bad user, i should have stopped cygwin before running
  setup, but i'm still amazed at how easily my robust kernel, based on NT
  Technology, came down.
 
  Nice-to-haves:
  5) it'd be nice if setup.exe showed the size (in bytes or
 megabytes, etc.)
 
  of each package (it's in setup.ini). on my 56 Kb/s modem, downloading a
  large, unnecessary file takes a painfully long time, but a small
  unnecessary file is not so bad.
  6) on that note, how about displaying those nice descriptions from
  setup.ini in setup.exe so we can see what the packages are before
  downloading them. a resizable window would come in handy for this.
  7) the first time I downloaded (a partial download, not full), i picked
  more and clear, but next time I went into setup.exe, it had
  forgotten that. perhaps if I can unrust my C, I can fix some of these
  bugs myself. give me a few weeks.
  8) the XFree86-fnts package is 16 MiB. it's kind of big. the
 first time i
  downloaded from http:uiuc, it got 98% and stopped responding--1 hour
  wasted (at 56 Kb). the second time (no joke) it got 99% and
  stopped--another hour wasted. so i copied it from somewhere else.
  9) my X clients on an AIX box didn't work because i didn't use the -kb
  switch on XWin. but i found that one on the faq. a possible
 enhancement to
 
  setup.exe?
  10) using K (or Ki) and B for byte on setup.exe is always nice.
 make sure
  to leave a space between 

RE: need help scripting multiple xfree startups

2002-07-21 Thread Harold Hunt

Dennis,

I always launch Cygwin/XFree86 from an icon on the desktop that points to
the startxwin.bat file in c:\cygwin\usr\X11R6\bin.  The batch file starts an
xterm and when the xterm pops up I run:

ssh -X -C username@hostname

I type in my password and that is it.

As for avoiding typing in your password, I can say a few things, but I can't
hold your hand on this one.  You should already know that saving a password
on a computer in plaintext represents a huge security risk.  With that being
said, I am sure that you know that ssh allows you to use keys to verify the
identity of a user and to provide authentication (via a password check).
You can, I am told, clear the password on an ssh key.  Clearing the password
on an ssh key is just a dangerous as saving a password to disk in plaintext.

However, if you are willing to except the risks of having an ssh key with no
password, then I suggest that you search google for ``OpenSSH'' and read the
docs on their site about how to change the password on a key, etc.  I have
never personally done this, so I cannot provide any further details.

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Dennis Foreman
 Sent: Sunday, July 21, 2002 2:30 PM
 To: [EMAIL PROTECTED]
 Subject: need help scripting multiple xfree startups


 Hi,
 I need some hints on how to reduce the manual efforts in logging
 in remotely
 under ssh.
 Currently I can start Xfree using these steps:
 1. Open a Cygwin window.
 2a. run: ssh -Xl myuserid UNIX_system_domain_name
 2b. enter password
 3. open ANOTHER Cygwin window
 4. in this new window, run: startxwin.sh
 5. click to place the xterm on the X desktop
 6. run my program

 I need to repeat this 8 more times for each of 8 different machines. Is
 there some way of automating this? (Yes, I know a script will do
 it. I need
 some detailed help on what to put in the script.) Especially eliminating
 having to type a pw every time and clicking to establish the
 Xwindow on the
 X desktop.

 regards,
 D. J. Foreman
 website: http://WWW.CS.Binghamton.EDU/~foreman





RE: Problems starting X server

2002-07-21 Thread Harold Hunt

Run the ``mount'' command from a Cygwin bash shell, you will see something
like:

Administrator@HUNTHARO ~
$ mount
C:\cygwin\usr\X11R6\lib\X11\fonts on /usr/X11R6/lib/X11/fonts type system
(binmo
de)
C:\cygwin\bin on /usr/bin type system (binmode)
C:\cygwin\lib on /usr/lib type system (binmode)
c:\PalmDev on /PalmDev type system (textmode)
C:\cygwin on / type system (binmode)
c: on /cygdrive/c type user (binmode,noumount)


Except, on your system, one of two things is happending:

1) The fonts are installed on drive X (where X is a wildcard) along with the
rest of Cygwin, while the mount for the fonts directory points to some other
drive.

2) The fonts are installed on drive X, while Cygwin is installed on drive Z,
and the mount for the fonts directory points to drive Z.


You are first going to have to figure out where the Cygwin/XFree86 fonts got
installed to.  Then you are going to need to move them to be in the correct
place with respect to the rest of Cygwin.  After that you might have to
unmount and remount the fonts directory mount to point to the correct
location.

I can't hold your hand on these, but perhaps someone else will be willing to
answer further questions about the details of doing this.

Harold




RE: On a side note - display resolution changes now handled

2002-07-21 Thread Harold Hunt

Jehan,

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Jehan
 Sent: Sunday, July 21, 2002 6:43 PM
 To: [EMAIL PROTECTED]
 Subject: Re: On a side note - display resolution changes now handled


 Harold Hunt wrote:
  On the other hand, display depth changes are much more
 disruptive, I think.
  I don't think that DirectDraw can handle transfering bits from
 an offscreen
  surface of different format than the primary surface; doing so
 would seem to
  defeat the whole purpose of DirectDraw.  My current thinking is
 that we will
  simply display a popup message indicating that Cygwin/XFree86 will be
  unavailable until the display depth is returned to the original depth.

 Isn't it possible to just froget about the previous offscreen buffer and
 ask all X windows to redraw themselves into the newly created surface?

   Jehan

You must be tired.  If we create a new offscreen surface (which I was not
talking about doing, I only said we have to recreate the primary (onscreen)
surface) with a different depth/format/etc than the original offscreen
surface, then we have effectively changed the X graphics mode and we would
need to use some sort of X extension to notify clients that all pixmaps and
visuals have been reset.  If there is such an extension, I am not aware of
it.

Harold




RE: New (Delphi) xlauncher

2002-07-21 Thread Harold Hunt

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Tim Thomson
 Sent: Sunday, July 21, 2002 9:41 PM
 To: cygwin-xfree Mailing List
 Subject: New (Delphi) xlauncher


 Hi there,

 To those of you interested in the progress of my xlauncher program(s), I
 have added some more features to the Delphi version. These include
 storing and retrieving configuration sessions to and from the registry,
 multiple font path, or font server specification, and better support for
 -from parameter, it now uses your IP, instead of name. If it can't find
 an IP address, it doesn't provide the parameter to XWin.exe.

 It is available at http://xlauncher.sourceforge.net


Fair enough.

 I'm still not sure where to head with the non-delphi version. I have
 some options, but all have disadvantages:

 libW11 doesn't look like it will do everything I need without the use of
 more libraries, ie xforms or gtk.


Whoever suggested libW11 was smoking some great crack.  libW11 is by no
means a complete API.  I'll just forget that this was ever mentioned.  (I'm
not complaining to you, I'm just complaining)

 gtk isn't stable enough yet?

 wxWindows - a _lot_ like MFC, but cross-platform. Would need to be made
 into a cygwin package. Would be the easiest to rewrite the delphi app
 in.

 win32api isn't very cross platform. Could use wine to port it to
 unix/linux?

 I'll look at how hard it would be to build wxWindows dll for cygwin, if
 that works well, I may use it, otherwise win32api may be the way,
 although pretty much eliminates a cross platform approach.


I am getting seriously confused here.  Why are you so excited about making
this a cross-platform application?  Cite me one example of someone that
would need this program to be cross platform.

Think about it: you are creating a graphical application that launches a
graphical windowing system.  Therefore, you have to already have a graphical
windowing system of some form running.  At last count, that means that you
are running either Windows, Mac OS X, OS/2, or maybe BeOS.  You certainly
can't be running on any platform that uses X11 as the graphical windowing
system, because you would have to have X11 running in order to launch X11
via your launcher.

Now, the Mac OS X folks have lots of neat ways that their server is already
tied into the Mac OS X-specific startup methods and such.  Supporting BeOS
would be a silly academic waste of effort.  OS/2 is similar, but good luck
finding a cross-platform toolkit that includes OS/2 support.

So, what are your real targets here?  Have I missed some operating system
that also needs an X launcher utility?

Harold




RE: need help scripting multiple xfree startups

2002-07-21 Thread Harold Hunt

Dennis,

Never email me directly.  Only respond to [EMAIL PROTECTED]

Harold

 -Original Message-
 From: Dennis Foreman [mailto:[EMAIL PROTECTED]]
 Sent: Sunday, July 21, 2002 7:27 PM
 To: Harold Hunt
 Subject: RE: need help scripting multiple xfree startups


 Harold,
 My computer is in a secure area (unless someone wants to mess
 with my attack
 cat), so passwords on the machine are NOT a problem. I have read about the
 RSA protocol, so that ,might work. Remember that I said I needed
 to run this
 procedure a total of NINE TIMES before I can begin doing any
 work. And this
 happens EVERY time I want to do the work. Thus, I need a script that will
 automate as much as possible. Time is money!

 What is the difference between:
 1.  running cygwin then startxwin.sh
 2.  startxwin.bat, then ssh from inside the xterm?

 The problem is connecting to multiple systems. How can I script it?

 regards,
 D. J. Foreman
 website: http://WWW.CS.Binghamton.EDU/~foreman

 -Original Message-
 From: Harold Hunt [mailto:[EMAIL PROTECTED]]
 Sent: Sunday, July 21, 2002 4:50 PM
 To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
 Subject: RE: need help scripting multiple xfree startups


 Dennis,

 I always launch Cygwin/XFree86 from an icon on the desktop that points to
 the startxwin.bat file in c:\cygwin\usr\X11R6\bin.  The batch
 file starts an
 xterm and when the xterm pops up I run:

 ssh -X -C username@hostname

 I type in my password and that is it.

 As for avoiding typing in your password, I can say a few things,
 but I can't
 hold your hand on this one.  You should already know that saving
 a password
 on a computer in plaintext represents a huge security risk.  With
 that being
 said, I am sure that you know that ssh allows you to use keys to
 verify the
 identity of a user and to provide authentication (via a password check).
 You can, I am told, clear the password on an ssh key.  Clearing
 the password
 on an ssh key is just a dangerous as saving a password to disk in
 plaintext.

 However, if you are willing to except the risks of having an ssh
 key with no
 password, then I suggest that you search google for ``OpenSSH''
 and read the
 docs on their site about how to change the password on a key, etc.  I have
 never personally done this, so I cannot provide any further details.

 Harold

  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED]]On Behalf Of Dennis Foreman
  Sent: Sunday, July 21, 2002 2:30 PM
  To: [EMAIL PROTECTED]
  Subject: need help scripting multiple xfree startups
 
 
  Hi,
  I need some hints on how to reduce the manual efforts in logging
  in remotely
  under ssh.
  Currently I can start Xfree using these steps:
  1. Open a Cygwin window.
  2a. run: ssh -Xl myuserid UNIX_system_domain_name
  2b. enter password
  3. open ANOTHER Cygwin window
  4. in this new window, run: startxwin.sh
  5. click to place the xterm on the X desktop
  6. run my program
 
  I need to repeat this 8 more times for each of 8 different machines. Is
  there some way of automating this? (Yes, I know a script will do
  it. I need
  some detailed help on what to put in the script.) Especially eliminating
  having to type a pw every time and clicking to establish the
  Xwindow on the
  X desktop.
 
  regards,
  D. J. Foreman
  website: http://WWW.CS.Binghamton.EDU/~foreman
 






RE: [ANNOUNCEMENT] Server Test 65

2002-07-18 Thread Harold Hunt

Rasjid,

Excellent.

Thank you for the screenshots.  I will work on this over the weekend.

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Rasjid Wilcox
 Sent: Thursday, July 18, 2002 10:35 AM
 To: [EMAIL PROTECTED]
 Subject: Re: [ANNOUNCEMENT] Server Test 65


 On Tue, 16 Jul 2002 3:08 pm, Harold Hunt wrote:
 
  I just posted Test 65 to the server development page:
  http://xfree86.cygwin.com/devel/shadow/
 
  You can install the Test 65 package via setup.exe by selecting the
  'test' package (and be sure to check the 'Bin' box):
 XFree86-xserv-4.2.0-12
 

 I have given this a quick test on my DualHead Matrox G400.

 Screenshots are available at

 http://www.openminddev.net/files/cx-1.jpg
 http://www.openminddev.net/files/cx-2.jpg
 http://www.openminddev.net/files/cx-3.jpg
 http://www.openminddev.net/files/cx-4.jpg
 http://www.openminddev.net/files/cx-5.jpg

 Shot 1 is just the intial opening.
 Shot 2 is the first maximisation.
 Shot 3 is re-maximisation after minimising.
 Shot 4 is maximising on the second screen (which in my setup is
 actually on
 the left).
 Shot 5 is showing that when maximised on screen 2, you can still move the
 window around.  *This is not supposed to happen.* It should be locked in
 place.

 Note: The 'locked in place' quality works okay on screen 1.

 Cheers,

 Rasjid.





RE: Corrupted file x2x-1.27-1-src.tar.bz2

2002-07-15 Thread Harold Hunt

Thomas,

Well, looks like I get to throw this one right back at you.

I right-clicked on the link at:
http://cygwin.com/ml/cygwin-xfree/2002-07/msg00393.html

and chose save as... blah blah.

I did this in both IE and Mozilla 1.0.  The result is that the browser
thinks that the file is an HTML file (both of them thought this).  I
corrected the extensions in both browsers, but the resulting download was
16719 bytes both times.

I would prefer that you either find some ftp space to store this files at,
or email them to me (not to the list) directly.

Harold

 -Original Message-
 From: Thomas Chadwick [mailto:[EMAIL PROTECTED]]
 Sent: Monday, July 15, 2002 9:27 AM
 To: [EMAIL PROTECTED]
 Cc: [EMAIL PROTECTED]
 Subject: RE: Corrupted file x2x-1.27-1-src.tar.bz2


 Harold,

 I need you assitance in fixing this problem.  Can you please re-upload to
 sources.redhat.com the tarball located here?

 http://members.tripod.com/tomandlaura0/cygwin/release/x2x/x2x-1.27
 -1-src.tar.bz2

 The problem is that the file up on sources.redhat.com (and all
 the mirrors)
 is 16719 Bytes.  The file at the above location is 16720 Bytes,
 which is the
 correct size.  Don't know what happened to that 1 Byte.

 Thanks.

 From: Robert Collins [EMAIL PROTECTED]
 To: 'Alexander Gottwald' [EMAIL PROTECTED]
 CC: [EMAIL PROTECTED]
 Subject: RE: Corrupted file x2x-1.27-1-src.tar.bz2
 Date: Sun, 14 Jul 2002 09:42:27 +1000
 
 
 
   -Original Message-
   From: [EMAIL PROTECTED]
   [mailto:[EMAIL PROTECTED]] On Behalf Of Alexander Gottwald
   Sent: Saturday, 13 July 2002 5:04 AM
   Cc: [EMAIL PROTECTED]
   Subject: Re: Corrupted file x2x-1.27-1-src.tar.bz2
  
  
   On Fri, 12 Jul 2002 [EMAIL PROTECTED] wrote:
  
In the directory release/XFree86/x2x/, the file
   x2x-1.27-1-src.tar.bz2 has
the correct md5sum (being
   87075ba00b0cd15f35975c956f14591a); but running
bzip2 -tv gives a file ends unexpectedly error message,
   and attempting to
run bzip2 -dv fails.
  
   Have you downloaded it via ftp? The please check you fetched
   it in binary
   and not ascii mode.
 
 If he'd downloaded in ascii ftp mode the md5 would not match.
 
 Rob


 _
 Join the world’s largest e-mail service with MSN Hotmail.
 http://www.hotmail.com





RE: LibICE.DLL is a BIG problem

2002-07-15 Thread Harold Hunt

Michael,

No it is not amazing that the default Cygwin installation does not install
XFree86.

Just read the Cygwin mailing list archives and notice how often people bitch
about how large the default installation is already.  The default
installation continues to get smaller, rather than larger, as a result of
all of this bitching.  Now we have reached the point where people bitch
about there being too much just about as much as people bitch about there
being too little.  Thus, we have reached a nice stable point, and we intend
to stay there.

Harold

-Original Message-
From: Michael Jennings [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 15, 2002 1:38 AM
To: Harold Hunt
Subject: Re: LibICE.DLL is a BIG problem


Amazingly, the default Cygwin install does not install XFree86. It is
necessary to choose it. That's why there are so many problems with it being
missing.

You can see all the trouble people are having by puting
LibICE.dll
into Google.

Michael

___


Harold Hunt wrote:

Michael,

Because I have never heard of any problems with libICE.

You are going to have to provide details, even if those details are only
links to the relevant bits of discussions that you have found via Google.

Thanks,

Harold


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Michael Jennings
Sent: Monday, July 15, 2002 12:14 AM
To: [EMAIL PROTECTED]
Subject: LibICE.DLL is a BIG problem


There are lots of messages on Google that say people are having a
problem with a missing DLL, LibICE.dll. No one has answered that message
with a definitive answer. There are FTP and HTTP addresses given that
don't lead to the file.

I'm trying to install Nedit, and it is asking for this file.

Why doesn't Cygwin provide everything necessary, or links, or
explanations? Re-installing made no difference.

Michael Jennings













RE: Corrupted file x2x-1.27-1-src.tar.bz2

2002-07-15 Thread Harold Hunt

Thomas,

I've uploaded the src tarball.  It should be on mirrors within 24 hours.

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Thomas Chadwick
 Sent: Monday, July 15, 2002 10:06 AM
 To: [EMAIL PROTECTED]
 Cc: [EMAIL PROTECTED]
 Subject: RE: Corrupted file x2x-1.27-1-src.tar.bz2


 Strange...  I could have sworn that I did exactly what you describe
 (right-click followed by Save-As) to test the tarbals when I originally
 posted them, and they turned out just fine.  However, I re-tried
 that just
 now and I'm seeing the problem.  Classic ASCII vs. binary transfer snafu.

 Since I don't have access to an FTP server, I'll have to send
 them as email
 attachments (off-list).

 Thanks.

 From: Harold Hunt [EMAIL PROTECTED]
 To: Thomas Chadwick [EMAIL PROTECTED]
 CC: cygx [EMAIL PROTECTED]
 Subject: RE: Corrupted file x2x-1.27-1-src.tar.bz2
 Date: Mon, 15 Jul 2002 09:46:28 -0400
 
 Thomas,
 
 Well, looks like I get to throw this one right back at you.
 
 I right-clicked on the link at:
 http://cygwin.com/ml/cygwin-xfree/2002-07/msg00393.html
 
 and chose save as... blah blah.
 
 I did this in both IE and Mozilla 1.0.  The result is that the browser
 thinks that the file is an HTML file (both of them thought this).  I
 corrected the extensions in both browsers, but the resulting download was
 16719 bytes both times.
 
 I would prefer that you either find some ftp space to store this
 files at,
 or email them to me (not to the list) directly.
 
 Harold
 
   -Original Message-
   From: Thomas Chadwick [mailto:[EMAIL PROTECTED]]
   Sent: Monday, July 15, 2002 9:27 AM
   To: [EMAIL PROTECTED]
   Cc: [EMAIL PROTECTED]
   Subject: RE: Corrupted file x2x-1.27-1-src.tar.bz2
  
  
   Harold,
  
   I need you assitance in fixing this problem.  Can you please
 re-upload
 to
   sources.redhat.com the tarball located here?
  
   http://members.tripod.com/tomandlaura0/cygwin/release/x2x/x2x-1.27
   -1-src.tar.bz2
  
   The problem is that the file up on sources.redhat.com (and all
   the mirrors)
   is 16719 Bytes.  The file at the above location is 16720 Bytes,
   which is the
   correct size.  Don't know what happened to that 1 Byte.
  
   Thanks.
  
   From: Robert Collins [EMAIL PROTECTED]
   To: 'Alexander Gottwald'
 [EMAIL PROTECTED]
   CC: [EMAIL PROTECTED]
   Subject: RE: Corrupted file x2x-1.27-1-src.tar.bz2
   Date: Sun, 14 Jul 2002 09:42:27 +1000
   
   
   
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]] On Behalf Of Alexander
 Gottwald
 Sent: Saturday, 13 July 2002 5:04 AM
 Cc: [EMAIL PROTECTED]
 Subject: Re: Corrupted file x2x-1.27-1-src.tar.bz2


 On Fri, 12 Jul 2002 [EMAIL PROTECTED] wrote:

  In the directory release/XFree86/x2x/, the file
 x2x-1.27-1-src.tar.bz2 has
  the correct md5sum (being
 87075ba00b0cd15f35975c956f14591a); but running
  bzip2 -tv gives a file ends unexpectedly error message,
 and attempting to
  run bzip2 -dv fails.

 Have you downloaded it via ftp? The please check you fetched
 it in binary
 and not ascii mode.
   
   If he'd downloaded in ascii ftp mode the md5 would not match.
   
   Rob
  
  
   _
   Join the world’s largest e-mail service with MSN Hotmail.
   http://www.hotmail.com
  
 




 _
 Send and receive Hotmail on your mobile device: http://mobile.msn.com





RE: [ITP] glib-1.2.10 gtk+-1.2.10

2002-07-14 Thread Harold Hunt

Lapo,

Okay, I'll wait for the -2 pacakges.  Could you put links to the setup.hint
files in your email as well?  That makes it a lot easier to upload the
packages.

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Lapo Luchini
 Sent: Sunday, July 14, 2002 7:29 AM
 To: Mailing List: CygWin-XFree
 Subject: Re: [ITP] glib-1.2.10 gtk+-1.2.10


 Lapo Luchini wrote:

  What to say?
  Its only thanks to Steven O'Brien's patches that those packages
  contains DLLs.
  See http://homepage.ntlworld.com/steven.obrien2/

 I'm currently doing -2 version of them, relibtoolizing them instead of
 using Steven patches.

 --
 Lapo 'Raist' Luchini
 [EMAIL PROTECTED] (PGP  X.509 keys available)
 http://www.lapo.it (ICQ UIN: 529796)







RE: Bug in startxwin.bat after installing with setup.exe in win98SE

2002-07-14 Thread Harold Hunt

Wow.

I sure am glad that I was out of town, throwing a party, and replacing the
power steering pump in my Jeep this weekend while you guys slugged this one
out.

The end result is that I have a couple of scripts to look at and evaluate.
Right now I am still trying to get that scrollbars patch release, so the
scripts will have to wait until 4.2.0-12 is released.

Once again, wow.

Harold




RE: Using the new cross compilation system - and a request for help

2002-07-11 Thread Harold Hunt

Alexander,

 So this seems to be normal. For cygwin, there is
 #ifdef __CYGWIN__
 #define MacroIncludeFile cygwin.cf
 #define MacroFile cygwin.cf
 #define cygwinArchitecture
 #define i386Architecture
 #undef i386
 #undef __i386__
 #undef _X86_
 #undef __CYGWIN__
 #endif /* CYGWIN */

 We just have to add #undef i686, #undef i486, #undef i586 here

Excellent.  I have applied just such a fix.

Thank you for tracking this down.

Now, regarding the imakemdep_cpp.h that I sent you, have you seen warnings
similar to the ones I'm getting below?  The reason I asked if your
imakemdep_cpp.h was similar was because I wanted to know if it has those
``#1 imakedep_cpp.h'' lines like mine does.

Harold


make[5]: Entering directory
`/home/harold/x-devel/build/newhostdef/config/util'
rm -f rman.o
gcc -c -I../.. -I../../exports/include -DVOLLIST='1:2:3:4:5:6:7:8:9:o:l
:n:p' -DMANTITLEPRINTF='%s(%s) manual
page' -DMANREFPRINTF='%s.%s.html' -DPOLYGLOTMANVERSION='3.0.8+XFree86' 
-DXFree86 rman.c
rm -f rman
gcc -I../../exports/include -o rman  rman.o
make[5]: Leaving directory
`/home/harold/x-devel/build/newhostdef/config/util'
okay, continuing in config/makedepend
rm -f makedepend.1.html makedepend.1-html
../../config/util/rman -f HTML  mkdepend._man \
 makedepend.1-html  mv -f makedepend.1-html makedepend.1.html
macro UC not recognized -- ignoring
make[4]: Leaving directory
`/home/harold/x-devel/build/newhostdef/config/makedepend'
okay, continuing in config/imake
../../config/makedepend/makedepend  -- -I../../include -I../../exports/inclu
de/X11  -I../.. -I../../exports/include   -D__i386__ -DWIN32_LEAN_AND_MEAN -
DX_LOCALE -D_X86_ -D__CYGWIN__ -D_XOPEN_SOURCE -D_POSIX_C_SOURCE=199309L -D_
BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -DNO_ALLOCA  -DFUNCPROTO=15 -DNARROW
PROTO -DCPP_PROGRAM=\cpp\ -DHAS_MERGE_CONSTANTS=`if
gcc -fmerge-constants -xc /dev/null -S -o /dev/null 2 /dev/null 1
/dev/null; then echo 1; else echo 0;
fi`  -DCROSSCOMPILE -DCROSSCOMPILEDIR=\/cygwin/bin\  -DUSE_MAKEDEPEND --
imake.c
../../config/makedepend/makedepend: warning:  imake.c (reading
imakemdep_cpp.h), line 1: unknown directive == # 1 imakemdep.h
../../config/makedepend/makedepend: warning:  imake.c (reading
imakemdep_cpp.h), line 37: unknown directive == # 191 imakemdep.h
../../config/makedepend/makedepend: warning:  imake.c (reading
imakemdep_cpp.h), line 187: unknown directive == # 398 imakemdep.h
../../config/makedepend/makedepend: warning:  imake.c (reading
imakemdep_cpp.h), line 222: unknown directive == # 446 imakemdep.h
../../config/makedepend/makedepend: warning:  imake.c (reading
imakemdep_cpp.h), line 235: unknown directive == # 466 imakemdep.h
../../config/makedepend/makedepend: warning:  imake.c (reading
imakemdep_cpp.h), line 246: unknown directive == # 500 imakemdep.h
../../config/makedepend/makedepend: warning:  imake.c (reading
imakemdep_cpp.h), line 258: unknown directive == # 547 imakemdep.h
../../config/makedepend/makedepend: warning:  imake.c (reading
imakemdep_cpp.h), line 260: unknown directive == # 568 imakemdep.h
../../config/makedepend/makedepend: warning:  imake.c (reading
imakemdep_cpp.h), line 287: unknown directive == # 610 imakemdep.h
../../config/makedepend/makedepend: warning:  imake.c (reading
imakemdep_cpp.h), line 298: unknown directive == # 644 imakemdep.h
../../config/makedepend/makedepend: warning:  imake.c (reading
imakemdep_cpp.h), line 311: unknown directive == # 667 imakemdep.h
../../config/makedepend/makedepend: warning:  imake.c (reading
imakemdep_cpp.h), line 318: unknown directive == # 688 imakemdep.h
../../config/makedepend/makedepend: warning:  imake.c (reading
imakemdep_cpp.h), line 321: unknown directive == # 699 imakemdep.h
../../config/makedepend/makedepend: warning:  imake.c (reading
imakemdep_cpp.h), line 344: unknown directive == # 869 imakemdep.h
../../config/makedepend/makedepend: warning:  imake.c (reading
imakemdep_cpp.h), line 420: unknown directive == # 1282 imakemdep.h
../../config/makedepend/makedepend: warning:  imake.c (reading
imakemdep_cpp.h), line 470: unknown directive == # 1341 imakemdep.h
make[3]: Leaving directory
`/home/harold/x-devel/build/newhostdef/config/imake'
depending in config/makedepend...
make[3]: Entering directory
`/home/harold/x-devel/build/newhostdef/config/makedepend'




RE: Using the new cross compilation system - and a request for help

2002-07-11 Thread Harold Hunt

Alexander,

I don't know if you ever explicity described how you got around the
glibc_major and glibc_minor symbols not being defined.  The fun error that I
get is below.

Harold


Building Release 6.6 of the X Window System.

I hope you checked the configuration parameters in ./config/cf
to see if you need to pass BOOTSTRAPCFLAGS.

Thu Jul 11 20:59:52 EDT 2002

cd ./config/imake  make  -f Makefile.ini BOOTSTRAPCFLAGS= CC=cc clean
make[1]: Entering directory
`/home/harold/x-devel/build/newhostdef/config/imake'
rm -f ccimake imake.o imake
rm -f *.CKP *.ln *.BAK *.bak *.o core errs ,* *~ *.a tags TAGS make.log \#*
rm -f -r Makefile.proto Makefile Makefile.dep bootstrap
rm -f imakemdep_cpp.h
make[1]: Leaving directory
`/home/harold/x-devel/build/newhostdef/config/imake'
make  Makefile.boot
make[1]: Entering directory `/home/harold/x-devel/build/newhostdef'
cd ./config/imake  make -w -f Makefile.ini BOOTSTRAPCFLAGS= CC=cc
make[2]: Entering directory
`/home/harold/x-devel/build/newhostdef/config/imake'
making imake with BOOTSTRAPCFLAGS= and
CROSSCOMPILEFLAGS=-DCROSSCOMPILEDIR=/cygwin/bin in config/imake
cc -o
ccimake -DCROSSCOMPILEDIR=\/cygwin/bin\  -O -I../../include -I../../import
s/x11/include/X11 ccimake.c
if [ -n /cygwin/bin ] ; then \
/cygwin/bin/cc -E `./ccimake` \
-DCROSSCOMPILE_CPP imakemdep.h  imakemdep_cpp.h; \
else touch imakemdep_cpp.h; fi
cc -c  -O -I../../include -I../../imports/x11/include/X11 `./ccimake`
imake.c
imake.c: In function `define_os_defaults':
imake.c:1503: `glibc_major' undeclared (first use in this function)
imake.c:1503: (Each undeclared identifier is reported only once
imake.c:1503: for each function it appears in.)
imake.c:1505: `glibc_minor' undeclared (first use in this function)
make[2]: *** [imake.o] Error 1
make[2]: Leaving directory
`/home/harold/x-devel/build/newhostdef/config/imake'
make[1]: *** [imake.proto] Error 2
make[1]: Leaving directory `/home/harold/x-devel/build/newhostdef'
make: *** [World] Error 2




RE: cygwin1.dll 1.3.12-2 and attempt to install xfree

2002-07-10 Thread Harold Hunt

First: Do *not* email me directly.  I am not helping you.  The project is
helping you.

Second: Reread what I wrote you the first time.  You should not be trying to
run Xinstall.sh, nor should you be trying gunzip extract.exe.gz.  Everything
is done via Cygwin's setup.exe.  It this making any sense to you?  It seems
like you didn't even read what I wrote the first time.

Harold

 -Original Message-
 From: J. W. Ballantine [mailto:[EMAIL PROTECTED]]
 Sent: Wednesday, July 10, 2002 2:28 PM
 To: Harold L Hunt
 Subject: Re: cygwin1.dll 1.3.12-2 and attempt to install xfree



 Thanks.

 As I indicated in my note, one of the issues, and more than likely the
 more important one, was what causing the weird (at least for me) error
 messages and results that were being generated.  The secondary problem
 was really the install.  Once I resolved the Invalid argument issues
 the install would be a piece of cake.



 --  In Response to your message -

   Date:  Wed, 10 Jul 2002 14:07:46 EDT
   To:  James Ballantine [EMAIL PROTECTED], [EMAIL PROTECTED],
 [EMAIL PROTECTED]
   From:  Harold L Hunt [EMAIL PROTECTED]
   Subject:  Re: cygwin1.dll 1.3.12-2 and attempt to install xfree
 
   James,
 
   First: wrong mailing list.  Use [EMAIL PROTECTED]  I
 have redirected
   this email to the appropriate list, but please be careful to remove
   [EMAIL PROTECTED] if you hit ``reply to all''.
 
   Second: the Cygwin/XFree86 User's Guide is out of date.
 Cygwin/XFree86 is n
 ow
   entirely installed via Cygwin's setup.exe.  Just rerun
 setup.exe, expand the
   XFree86 category, and select at least the XFree86-base package.
 
   Harold
 
 
 
   James Ballantine [EMAIL PROTECTED] said:
 
Hi all,
   
I'm trying to install xfree and I'm getting strange error
messages/results before the install starts.
   
I've downloaded and installed the most current cygwin  bits  (as of
7/9/02), and downloaded the must current
xfree bits.  When I try to gunzip extract.exe.gz I get the
 error message :
   gunzip: extract.exe.gz: Invalid arguement
When I look in the dir, the gunzipped file is there, with a
 permission
of rw--- .
   
When I try and run the Xinstall it tells me:
   
  checking which OS you're running...
  uname reports 'CYGWIN_NT-5.0' version '1.3.12(0.54/3/2)'
 architecture
'i686'.
   
  chmod: changing permissions of 'extract': no such file or directory
  ./extract: not found
  extract doesn't work properly, renaming it to 'extract.bad'
  mv: preserving times for 'extract.bad' : No such file or directory
  mv: preserving ownership for 'extract.bad': No such file
 or directory
  mv: cannot unlink 'extract': No such file or directory
  mv: cannot remove 'extract': No such file or directory
  chmod: changing permissions of 'extract': no such file or directory
  ./extract: not found
  extract.exe doesn't work properly, renaming it to 'extract.exe.bad'
   
  The versions of  'extract and 'extract.exe' you have do not run
  correctly.  Make sure that you have downloaded the correct
  binaries for your system.  To find out which is correct,
  run 'sh ./Xinstall.sh -check'.
   
This appears to me to be a problem with the setup of cygwin
 rather than a
problem with xfree, which is why I've mailed to this list.
 I've checked
the archives
and either no one else has had this problem, or I've
 searched for the
wrong key words.
   
Any pointers to resolving this problem would be appreciated.
   
Thanks
   
Jim Ballantine
   
   
--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/
   
   
 
 
 






RE: New xlauncher (was: Re: Success with Java prog in XFree)

2002-07-08 Thread Harold Hunt

Actually, I am just about to add per-user registry support, so you might as
well use the registry.

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Rasjid Wilcox
 Sent: Monday, July 08, 2002 6:33 AM
 To: Tim Thomson; [EMAIL PROTECTED]
 Subject: Re: New xlauncher (was: Re: Success with Java prog in XFree)


 On Mon, 8 Jul 2002 7:08 am, Tim Thomson wrote:
 snip
  I would prefer that xlauncher, or a variant be installable via
 setup.exe,
  so it can be used by anyone. If it means porting/rewriting,
 I'll give it a
  shot :) (There isn't all that much code there, most is just writing to
  registry, and reading it back. Which is another thing, would it
 be better
  to use a config file rather than registry? Currently, I'm
 writing to HKEY
  Local Machine, but should be writing to current user, so that
 people with
  few rights on an NT style box can use it. If I were to use a
 config file,
  where to put it?)

 Personally, I would go for a config file.

 As mentioned in another post of mine, I was working on a
 Python/wxWindows GUI.
 I can send you what I've done if you are interested.

 My most recent thoughts was to create a generic 'Remote X
 desktop' launcher,
 which would run on Windows (with Cygwin-XFree86 backend) and on
 Linux/Unix
 (with a XNest backend), and possibly Mac.  Further plans were to include
 support for other remote display tools like VNC.

 I was also considering switching to Java (due to better IDE's available),
 although the discussion here as left me unsure.  Is the GNU
 compiler able to
 deal with Java/Swing, or is Python/wxWindows a better 'pure open source'
 option?

 Anyway, Tim, if you want to do it in C/C++, I'll help test/debug,
 but I can't
 really help code.  OTOH, if Python/wxWindows interests you, I'd
 help with the
 coding too.  If you know C, Java and Pascal, I'd say you could
 pick up Python
 in a day.  :-)

 Rasjid.





[ANNOUNCEMENT] Server Test 64

2002-07-08 Thread Harold Hunt

Links:

I just posted Test 64 to the server development page:
http://xfree86.cygwin.com/devel/shadow/

You can install the Test 64 package via setup.exe by selecting the
'test' package (and be sure to check the 'Bin' box): XFree86-xserv-4.2.0-11

Server Test Series binary and source code releases are now
available via the sources.redhat.com ftp mirror network
(http://cygwin.com/mirrors.html) in the
pub/cygwin/xfree/devel/shadow/ directory.  You may wish to note the
desired filename in the links below, then download from your
closest mirror (http://cygwin.com/mirrors.html).

Server binary, direct link:
http://www.msu.edu/~huntharo/xwin/shadow/XWin-Test64.exe.bz2 (1100 KiB)

Server source, direct link:
http://www.msu.edu/~huntharo/xwin/shadow/xwin-20020708-2212.tar.bz2 (81 KiB)

xc/programs/Xserver/Imakefile diff against 20020708 XFree86 CVS:
http://www.msu.edu/~huntharo/xwin/shadow/xc-programs-Xserver-Imakefile-20020
708-2212.diff (2 KiB)

xc/programs/Xserver/hw/xwin (all files) diff against 20020708 XFree86 CVS:
http://www.msu.edu/~huntharo/xwin/shadow/xwin-20020708-2212.diff.bz2 (3
KiB)

xc/programs/Xserver/hw/xwin new files:
http://www.msu.edu/~huntharo/xwin/shadow/xwin-newfiles-20020708-2212.tar.bz2
(8 KiB)


Changes:

1) winconfig.c, winconfig.h, winmsg.c, winmsg.h, InitOutput.c,
winkeybd.c - Add support for using XF86Config-style configuration
files.  (Alexander Gottwald)


Enjoy,

Harold




RE: New xlauncher (was: Re: Success with Java prog in XFree)

2002-07-07 Thread Harold Hunt

Tim,

 How does this work, do I just make a package, and then email cygwin-apps?
 Is this valid for this sort of program, where it isn't even compiled using
 cygwin?

I haven't had any comments on this program yet because, while it is a neat
exercise and will be useful for other work, it will not be distributed with
Cygwin/XFree86 until it is written in a language that can be compiled with a
free software compiler, preferrably gcc or g++.

The reason for this restriction is that we cannot have any barriers to entry
that keep people without `Commercial Compiler of the Day' from contributing.
When I joined the project we had a DLL that was compiled with MSVC++.  I was
told that it was impossible to avoid using this MSVC++ because the
DirectDraw interfaces compiled in that DLL could not be compiled in Cygwin.
Naturally, the first thing I worked on, and succeeded on, was making the
DirectDraw interfaces compile under Cygwin without any MSVC++ compiled DLL.

Eventually I see that either XWin.exe itself will have the functionality of
your xlauncher, or we will have a stand-alone c or c++ program that provides
the same functionality.  Everyone here would greatly appreciate it if you
would start working on a c or c++ xlauncher.

Good luck, and thanks for contributing,

Harold




Slashdotting

2002-07-07 Thread Harold Hunt

We have been Slashdotted, with a post that mentions that we are now easily
installable via Cygwin's setup.exe:

http://slashdot.org/article.pl?sid=02/07/07/1227202mode=nestedtid=104


I'd like to express my thanks to all Cygwin/XFree86 contributors.

This time we might get a lot of new users because we are so easy to install
now.  Crossing my fingers...

Harold




RE: New xlauncher (was: Re: Success with Java prog in XFree)

2002-07-07 Thread Harold Hunt

Chuck,

 WTF?  I don't follow the xfree list all that closely, but didn't this
 thread start out as Success with Java prog in XFree?  I just assumed
 that 'xlauncher' WAS that Java prog.  Sorry for the confusion.

You know... sometimes I'm just not paying any attention at all.  What has
happened to me?!?

A Java xlauncher sounds fine to me, for now.  I'd eventually prefer that it
be written in C or C++.

How large are the Java runtimes for Cygwin?  I'm sure we'll get complains
along the lines of, ``before I had to install 100 MB for Cygwin/XFree86, now
I have to install XX MB more for the xlauncher program, blah''.  So I'm not
really excited about sticking with Java forever.

Feeling like an idiot,

Harold




RE: xf86config patch

2002-07-07 Thread Harold Hunt

Alexander,

1) In winconfig.c, why is this there:

#ifndef PROJECTROOT
#define PROJECTROOT /usr/X11R6
#endif


2) Are any of these files significantly copied from hw/xfree86, or anywhere
else that we should attribute?

3) Will there be any effect, whatsoever, on users that do not use an
XF86Config file?

Harold


 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Alexander Gottwald
 Sent: Saturday, July 06, 2002 3:40 PM
 To: [EMAIL PROTECTED]
 Subject: xf86config patch


 Hi,

 after long time, I remade the xf86config patch. The diffs are made
 against todays cvs.

 The patch includes support for

 - reading /etc/XF86Config
 - setting the fontpath from the configfile
 - setting XKB settings from the configfile (foreign keyboard support)
 - setting rgbpath from the configfile

 I don't expect that I will ever support other configuration options,
 since the monitor, device and screen sections have no meaning for
 windows. For supporting the mouse section a huge change to the current
 has to be made and any settings can already be given on the commandline.

 A precompiled binary for testing is available at
 http://www-user.tu-chemnitz.de/~goal/xfree/test-config-1/X-Server.tar.bz2

 bye
 ago
 --
  [EMAIL PROTECTED]
  http://www.gotti.org   ICQ: 126018723





Cross Compiling

2002-07-07 Thread Harold Hunt

Yup, cross compiling is toroughly broken right now.  It will take awhile to
get it working properly.  I'd appreciate it if anyone that is cross
compiling the current XFree86 cvs would send in their host.def, any
modification they made to cygwin.cf, etc. and their build command.

Thanks,

Harold




RE: [PATCH] -scrollbars option

2002-07-07 Thread Harold Hunt

Jehan,

That is an excellent patch!  I was just thinking that we should add this
sort of functionality.  Yes, I was reading the ./ posts too :)

However, there are a bunch of ^M's showing up in the patch file for
winwndproc.c starting at about line 496 (in the patch file).  Could you
clean that up and resubmit?

Thanks for the great work,

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Jehan
 Sent: Sunday, July 07, 2002 11:27 PM
 To: [EMAIL PROTECTED]
 Subject: [PATCH] -scrollbars option


 Hello,

 Since I've seen a couple complaints about not being able to resize the
 windows in this mailing list and on slashdot, I've decided to implement
 it. So here it is.
 With this option, when in windowed mode, you can resize the window (if
 you use decoration) and have a virtual screen bigger than your desktop
 (so now you can have a real 1024x768 screen on your 1024x768 monitor
 without having to go fullscreen, or you can have a 1600x1200 on your
 320x200 monitor :) ).

 Harold, I left a comment in wincreatewnd.c (line 263 for me). At this
 place, you map the client area coords to fullscreen but you never use
 them. So either I missed something and I'm sorry for bothering you, or
 this is some left over from some old code that can be removed.
 Also, I didn't change the Primary FB since it's deprecated and you
 said in the contributor's guide that the Development of the Primary FB
 engine has ceased.

   Jehan





RE: xf86config patch

2002-07-07 Thread Harold Hunt

Alexander,

I've merged your patch with my local tree and I'm going to try to test it
tomorrow.

Could you send me a sample and/or skeleton (containing commented versions of
each config option) config file?

Thanks,

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Alexander Gottwald
 Sent: Saturday, July 06, 2002 3:40 PM
 To: [EMAIL PROTECTED]
 Subject: xf86config patch


 Hi,

 after long time, I remade the xf86config patch. The diffs are made
 against todays cvs.

 The patch includes support for

 - reading /etc/XF86Config
 - setting the fontpath from the configfile
 - setting XKB settings from the configfile (foreign keyboard support)
 - setting rgbpath from the configfile

 I don't expect that I will ever support other configuration options,
 since the monitor, device and screen sections have no meaning for
 windows. For supporting the mouse section a huge change to the current
 has to be made and any settings can already be given on the commandline.

 A precompiled binary for testing is available at
 http://www-user.tu-chemnitz.de/~goal/xfree/test-config-1/X-Server.tar.bz2

 bye
 ago
 --
  [EMAIL PROTECTED]
  http://www.gotti.org   ICQ: 126018723





CVS Sticky Tags

2002-07-06 Thread Harold Hunt

Nicholas,

 You might want to set your cvs sticky tag to the xf-4_2-branch for the
 checkout if you run into problems with HEAD.  If you do go this route, be
 sure to unset the sticky tag in the /xc/programs/Xserver/hw/xwin
 directory.  This way you'll get the latest Cygwin/XFree updates while
 keeping the rest of the distribution stable.

Okay, lets say I check out the xf-4_2-branch.  What command to I run, and in
what directory, to unset the sticky tag for teh hw/xwin directory?

Harold




FW: xc/lib/fontconfig/fonts.conf depends on existing fonts installation

2002-07-05 Thread Harold Hunt

Alan,

Hmm... as usual I misspoke... I was bitching about the ``findfonts'' script
which runs on the installed fonts rather than on fonts being built.

I'll have to look into the font build utility problem.

I hate it when I get confused.  Anyway, here is what I wrote to the XFree86
devel list.

Harold


-Original Message-
From: Harold Hunt
Sent: Saturday, April 13, 2002 7:44 PM
To: xf-devel
Subject: xc/lib/fontconfig/fonts.conf depends on existing fonts
installation


I don't understand why xc/lib/fontconfig/fonts.conf runs the script
xc/lib/fontconfig/findfonts which looks at the *currently installed fonts*.
That doesn't make any sense to me.  Shouldn't you be able to build XFree86
on a machine that doesn't have any fonts installed, or for that matter, any
piece of XFree86 installed?

The problem that I'm running into on Cygwin is that even if
/usr/X11R6/lib/X11/fonts exits but /usr/share/fonts doesn't exist then the
findfonts script fails because 'find' cannot find that directory.  I'm not
certain that this is a Cygwin only problem, but it is the only platform that
I am building on.

I propose that one of two things be done:

1) Do not execute the scripts that do things for *installed* fonts, as this
makes no sense.

2) Or, change the findfonts script to silently fail if either of the fonts
directories cannot be found, thus removing a non-error error from build
logs.


Please CC me, as I am not currently subscribed to the devel list.

A snippet of my build log follows.


Harold Hunt




make[1]: Leaving directory
`/home/Administrator/x-devel/build/std/lib/fontconfig
/fc-list'
rm -f fonts.conf
sh ./setfontdirs
find: /usr/share/fonts: No such file or directory
ed: not found
make: *** [fonts.conf] Error 127




RE: Use Tcp.h?

2002-07-05 Thread Harold Hunt

Nicholas,

 I just tried...  Not as complete as one would hope...  Nevermind about
 this... :-)

What did you find that was broken?  Were there build errors or did it just
not run?  See my message that I just sent.  I've done a build so far and saw
no problems related to removing -DNO_TCP_H.  I have to do a rebuild before I
can run test it though because I found some problems with the
Xserver/Imakefile patch that had to be fixed... I forgot to stop linking to
$(LAYER), which caused XWin.exe to fail in the link step because the layer
library is no longer being built.

I'll let you know the results of my build test later tonight or tomorrow,
after the fireworks.

Harold




RE: xfree problem (new snapshot available)

2002-07-01 Thread Harold Hunt

Chris,

 Doh.  system_printf != syscall_printf.  I've checked in a fix
 and am rebuilding the snapshot.
 
 And, additionally, I put Pierre's patch in the wrong place in the code.
 Sigh.  I had to interpret it because the formatting was GNU standard and
 I interpreted it wrong.
 
 This snapshot was hosed.  I'm regenerating it *again*.

 The new snapshot is available.

I'm home now.  I'll have to wait until tomorrow to test the new snapshot,
when I have access to the strange machine.

Harold




RE: [ANNOUNCEMENT] Server Test 61

2002-06-27 Thread Harold Hunt

Okay, I'll stick with the current lenghty-when-necessary format.

I'm glad they are helping people,

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Jean-Claude Gervais
 Sent: Thursday, June 27, 2002 10:14 PM
 To: [EMAIL PROTECTED]
 Subject: RE: [ANNOUNCEMENT] Server Test 61
 
 
 I second that.
 
 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED]]On
 Behalf Of Franz Wolfhagen
 Sent: Thursday, June 27, 2002 3:58 AM
 To: [EMAIL PROTECTED]
 Subject: RE: [ANNOUNCEMENT] Server Test 61
 
 
 Your long changelogs are doing a very nice educational reading for me at
 least - I appreciate them very much...
 
 Med venlig hilsen / Regards
 Franz Wolfhagen
 



RE: [ANNOUNCEMENT] Server Test 61

2002-06-27 Thread Harold Hunt

I need someone with a graphics card capable of 15 bits per pixel to run Test
61 and tell us what happens.  Also, run XWin.exe with
'XWin -fullscreen -depth 15' (when you are running Windows in some depth
other than 15) and let us know what happens.

Both of these situations are expected to not go well, but I need some
specifics.

Thanks for testing,

Harold




RE: New Xfree User Question

2002-06-26 Thread Harold Hunt

You're not supposed to launch startxwin.bat from a Cygwin prompt, you are
supposed to double-click the batch file from Windows Explorer or you can
launch startxwin.bat from a Windows command prompt (not a Cygwin command
prompt).

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Martin Bosticky
 Sent: Wednesday, June 26, 2002 9:14 PM
 To: '[EMAIL PROTECTED]'
 Subject: RE: New Xfree User Question


 Dear XFree crew,

 can I add that i also have the same problem and that I tried to get the
 latest cygwin snapshot as described in a recent email and it didn't help.
 Perhaps i have missed something during configuration i suppose
 but the bash
 shell seems to be working fine. I am running Windows 2000

 Martin.

 I have run into a problem when I started to learn / use Xfree on my
 XP laptop.
 
 When I launch via /usr/X11R6/bin/startxwin.bat at the Cygwin prompt,
 I get the background window, but the terminal window, which on my
 Win98 machine is my shell running bash, appears to be iconized in
 the upper left corner, and when I click on it, it disappears.
 
 I apologize for the awkward and no doubt technically incorrect way I
 have explained this, but I was hoping someone would say, oh, I know
 what that idiot is babbling about.
 
 Wayne Keen
 


 Martin Bosticky
 Software Engineer
 Opcom
 Office +61 7 3371 1311
 Fax +61 7 3371 1257
 Email [EMAIL PROTECTED]
 Web www.opcom.com.au http://www.opcom.com.au/






RE: Mouse dragging slow in XWin-Test56 with -emulate3buttons

2002-06-26 Thread Harold Hunt

Bradey,

Thanks for notifying other users of this.

I appreciate it when people send these sorts of things directly to the list,
like you've just done.  (No, he didn't send it to me privately first, I just
wanted to reward good behavior instead of waiting to complain about
someone's bad behavior.)

Hmm... I'm sure Alexander Gottwald and I didn't have a 0.5 second timeout in
mind when we wrote the emulate 3 buttons option.  There may or may not be
something that can be done to accomodate for this.  At the very least, we
could set some sort of upper-bound on the emulation timeout and we could
warn the user when they try to exceed this value.  That would at least
prevent people from doing silly things that weren't planned for.  I'll take
a look at this when I get a chance.

Thanks again,

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Bradey Honsinger
 Sent: Wednesday, June 26, 2002 11:30 PM
 To: '[EMAIL PROTECTED]'
 Subject: Mouse dragging slow in XWin-Test56 with -emulate3buttons


 I upgraded to Test60 and noticed that dragging the mouse to select text or
 move a window had gotten very slow--I had to hold down the mouse
 button and
 count one thousand one before moving it. After a bit of investigation, I
 found that removing the '-emulate3buttons 500' argument from my
 XWin command
 line made dragging work fine again. The problem was probably more
 pronounced
 for me than for most others because my timeout was so high--the default is
 50ms, and I was using 500ms.

 I back-tracked through the test series and found that the
 behaviour started
 with Test56--Test55 was fine. I'm guessing it had something to do
 with this
 changelog entry for Test56:

   - InitOutput.c - Fix a typo that set iE3BTimeout to TRUE instead
 of the specified timeout parameter when using the 3 button
 mouse emulation timeout parameter with a single X screen.
 (Stuart Adamson)

 I didn't diff the sources, but it sounds like XWin was never using the
 timeout parameter to -emulate3buttons until this typo was fixed. If that's
 the case, then this problem was just a latent bug in my XWin
 startup script,
 not a problem with XWin.

 In any case, even if it is a bug, I don't need a fix--I just wanted to let
 anyone else who encountered the problem know what the workaround was.

 - Bradey




[ANNOUNCEMENT] Server Test 61

2002-06-26 Thread Harold Hunt

Links:

I just posted Test 61 to the server development page:
http://xfree86.cygwin.com/devel/shadow/

You can install the Test 61 package via setup.exe by selecting the
'test' package: XFree86-xserv-4.2.0-8

Server Test Series binary and source code releases are now
available via the sources.redhat.com ftp mirror network
(http://cygwin.com/mirrors.html) in the
pub/cygwin/xfree/devel/shadow/ directory.  You may wish to note the
desired filename in the links below, then download from your
closest mirror (http://cygwin.com/mirrors.html).

Server binary, direct link:
http://www.msu.edu/~huntharo/xwin/shadow/XWin-Test61.exe.bz2 (1070 KiB)

Server source, direct link:
http://www.msu.edu/~huntharo/xwin/shadow/xwin-20020627-0020.tar.bz2 (72 KiB)


Changes:

1) General - Fix the KDE 3.0 alpha-channel icon bug that appeared
only when running Windows at 32 bits per pixel.  Many more details
below.  (Alan Hourihane)

2) General - pScreenInfo-dwDepth used to refer to the depth that the
user specified with the -depth parameter or the depth returned by
GetDeviceCaps (BITSPIXEL) and pScreenInfo-dwBPP used to refer to the
bits of color per pixel.  For example, running Windows at 32 bit color
would mean dwDepth == 32 and dwBPP == 24.  It turns out that this was
exactly backwards from what it should be.

The dwDepth variable new refers to the color ``depth'' of a pixel,
that is, the number of bits that make up the color specification for a
pixel.  For example, a 32 bit pixel uses 24 bits to represent color
plus an 8 bit pad for alignment purposes and a 16 bit pixel can use 15
or 16 bits to represent color.  The dwBPP variable now refers to the
bits used to store each pixel, that is, the number of bits that each
pixel occupies in the framebuffer memory.  For example, a 32 bit pixel
occupies 32 bits in the framebuffer memory while a 24 bit pixel
occupies 24 bits in the framebuffer memory (the former pixels are 32
bit aligned, while the latter pixels are called ``packed'' because the
pixels are not aligned and any given pixel may actually be stored in
two separate 32 bit units).

The meaning of dwDepth and dwBPP was corrected throughout the
source code, touching files such as wincmap.c, winscrinit.c,
InitOutput.c, winshadddnl.c, winshaddd.c, winshadgdi.c,
winnativegdi.c, winpfbdd.c, and win.h.  Also, we modify the depth 24
pixmap format at runtime to use 24 bits per pixel, instead of 32, when
Windows is running in 24 bit color; this matches the Windows pixel
format when running in 24 bit color.

The end result of all of this is that we now no longer report that
we have a depth 32 visual, as depth 32 visuals do not exist.  What we
were previously calling a depth 32 visual is actually a depth 24
visual with a different bits per pixel.  Advertising a proper visual
when running Windows at 32 bit color corrects the problem of KDE 3.0
not displaying icons or text with alpha channels.  Alan did the
magical part of discovering the underlying problem, I did the grunt
work of cleaning the code and making sure that all of the corner cases
were still handled.  (Alan Hourihane, Harold Hunt)

3) winshaddd.c, winshadddnl.c, winshadgdi.c, win.h, winscrinit.c -
Remove the essentially unused dwStride and dwStrideBytes variables
from the ScreenInfoRec.  (Harold Hunt)

4) winshaddd.c, winshadddnl.c - In winBltExposedRegionsShadowDD* ()
we try to restore the primary DirectDraw surface up to
WIN_REGAIN_SURFACE_RETRIES (currently 1) times when a bit block
transfer of the exposed regions fails.  This corrects the case where
switching a notebook from its internal display to an external display
(or vice versa) would cause the Cygwin/XFree86 window to blank and
fail to redraw itself until the Cygwin/XFree86 window was minimized
and then restored.  (Harold Hunt)


Enjoy,

Harold




RE: [ANNOUNCEMENT] Server Test 61

2002-06-26 Thread Harold Hunt

I've posted the patch against the current CVS tree for changes up through
Test 61 (and a few minutes afterwards), for those of you following the
development of Cygwin/XFree86:
http://www.msu.edu/~huntharo/xwin/shadow/xwin-Test61.diff.bz2 (21 KiB)

Here's a couple questions:

1) Should I start posting CVS diff files with each test release?  If there
are developers out there interested in this I can do it; if there aren't, I
might as well not bother.

2) Are the change logs too wordy?  I've been told that when speaking I tend
to offer a flood of information.  Should I post shorter change logs, or
should I post a summary at the top of the change log?  I have been trying to
make short descriptions of bug fixes appear at the top of the change logs so
that people can see that a bug has been fixed without reading the in-depth
description of what had to be changed to fix the bug.  Is it useful to put
those short descriptions at the top?

3) How do you like the first six hours I've had to work on Cygwin/XFree86
without any homework to slow me down, for the first time in 18 months?  :)


Oh yeah, Test61 will need some series testing by users with hardware that
does ``packed'' 24 bit color pixels (Windows will let you select 24 bit
color rather than 32 bit color when such hardware is present).  I haven't
got a single machine that can do packed 24 bit pixels so I haven't been able
to test at 24 bit color.

Once these graphics changes have stabilized I'll start looking at Jehan's
systray icon patch.

Thanks for testing,

Harold




RE: [PATCH] systray icon

2002-06-23 Thread Harold Hunt

Jehan,

Interesting.

I've received this and filed it.  I'll have to wait until after my final on
Wednesday to look at this and start merging it.

On the bright side, after Wednesday I'll be working 40 hours a week until
the end of August but I won't be taking a class so I won't have homework for
the first time in 18 months.  Yippee...  :)  Hopefully I'll be able to spend
a little more time on Cygwin/XFree86.

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Jehan Bing
 Sent: Sunday, June 23, 2002 8:18 PM
 To: Cygwin XFree
 Subject: [PATCH] systray icon


 Hello everybody,

 Here is another patch which adds the -systray option. With this option
 on, instead of adding buttons to the taskbar, it adds icons to the
 notification area (a.k.a. systray).
 To work, there must be a X.ico (see attachment) in the same directory
 than XWin.exe

 Left click on the icon shows the window if it was hidden, hide it
 otherwise.
 Right click displays the system menu (there isn't one in fullscreen)

 Notes:
 - I added a file (winsystray.c) so make depend is in order.
 - The patch also changes the title to include the screen number. To
 get the screen number, I'm searching the g_ScreenInfo array. I'm sure
 there must be a better way to get this number (search for HACK, there
 are 3 places).
 - The option doesn't work well in fullscreen mode. For some reason,
 when one click on the systray icon, the application isn't activated
 (doesn't switch to fullscreen, no WM_ACTIVATEAPP received) but the
 application still captures the mouse event, it's as if the desktop
 doesn't respond anymore. For those who try and/or want to fix it (I
 don't have the beginning of an idea for that so help is welcome), to
 recover from the freeze, open the start menu with the Windows key,
 then click outside the menu.
 - I fixed a couple typos (CYGDEGUG and missing '\n' for
 -lesspointer usage)
 - X.ico would be better off added as a resource to the application
 instead of an external file (or both if we want to allow customization).
 Can we do that with cygwin?
 - An improvment would be to add the screen number to the icon
 itself. It would be better than waiting for the tooltip.
 - I would like to change the left click behavior. I want it to put
 the window to the foreground if it was not (hidden behind another
 window), hide it otherwise. However, when one click on the systray, the
 systray become the foreground window. Does someone know how to get the
 handle of the previous foreground window?

 Jehan





[ANNOUNCEMENT] xwinclip Test 06 (Cygwin/XFree86 and Windows clipboard integration)

2002-06-21 Thread Harold Hunt

Links:

I just posted Test 06 to the xwinclip development page:
http://xfree86.cygwin.com/devel/xwinclip/

xwinclip binary and source code releases are available via the
sources.redhat.com ftp mirror network
(http://cygwin.com/mirrors.html) in the
pub/cygwin/xfree/devel/xwinclip/ directory.  You may wish to note the
desired filename in the links below, then download from your
closest mirror (http://cygwin.com/mirrors.html).

xwinclip binary, direct link:
http://www.msu.edu/~huntharo/xwin/xwinclip/xwinclip-Test06.exe.bz2 (6 KB)

Server source, direct link:
http://www.msu.edu/~huntharo/xwin/xwinclip/xwinclip-20020622-0007.tar.bz2
(10
KB)


Changes:

1) xevents.c, xevents.h, xwinclip.c - Add real support for
COMPOUND_TEXT, TARGETS, and UTF8_STRING selection types.  Grab
clipboard contents in Unicode, if supported, convert to multi-byte
character set, then stick the result into the appropriate target.
This allows Japanese text to be transferred via xwinclip.  Other
eastern languages (Korean, Chinese, etc.) may also work.  (Matsuzaki
Kensuke)

2) xwinclip.c - Add a UnicodeSupport function to check if we have
Unicode support or not.  Currently this is done by just checking if we
are on an NT-based platform or not.  (Harold Hunt)


Enjoy,

Harold




RE: broken lndir so cant build tree

2002-06-18 Thread Harold Hunt

Gotta reply to the list, not me.

Harold

 -Original Message-
 From: ...2«... [mailto:[EMAIL PROTECTED]]
 Sent: Monday, June 17, 2002 10:02 PM
 To: Harold L Hunt
 Subject: Re: broken lndir so cant build tree


 lndir still, and always had, made a bunch of links regardless of the arg.
 but either ive failed to d/ from cvs properly or lndir is traversing and
 stopping somewhere it shouldnt. is there anyway to double check i
 have the correct source tree to begin with? i try cvs update -d
 all the time.

 dan

 snip
 swan@BRONCO ~/x-devel/build
 $ rm std/ -rf

 swan@BRONCO ~/x-devel/build
 $ mkdir std

 swan@BRONCO ~/x-devel/build
 $ cd std/

 swan@BRONCO ~/x-devel/build/std
 $ lndir.exe /home/swan/x-devel/xc
 ..: File exists

 swan@BRONCO ~/x-devel/build/std
 $ ls
 CVSMakefileconfig  fontsprograms
 INSTALL-X.org  RELNOTEScvs-update.log  include  registry
 Imakefile  RELNOTES-X.org  doc lib  util
 LABEL  bug-report  extras  nls  workInProgress

 swan@BRONCO ~/x-devel/build/std
 $ make World  World.log 21

 swan@BRONCO ~/x-devel/build/std
 $ tail World.log
 make[2]: Entering directory `/home/swan/x-devel/xc/fonts'
 make[2]: *** No rule to make target `clean'.  Stop.
 make[2]: Leaving directory `/home/swan/x-devel/xc/fonts'
 cleaning in ./doc...
 make[2]: Entering directory `/home/swan/x-devel/xc/doc'
 make[2]: *** No rule to make target `clean'.  Stop.
 make[2]: Leaving directory `/home/swan/x-devel/xc/doc'
 make[1]: *** [clean] Error 2
 make[1]: Leaving directory `/home/swan/x-devel/build/std'
 make: *** [World] Error 2

 swan@BRONCO ~/x-devel/build/std
 $ which lndir
 /usr/bin/lndir

 /snip

 - Original Message -
 From: Harold L Hunt [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Monday, June 17, 2002 11:29 PM
 Subject: Re: broken lndir so cant build tree


  Dan,
 
   thanks for the idea, but im getting the same behaviour with that also.
 
  You did remember to copy lndir.exe to /usr/bin or wherever you
 copied the
 last
  lndir.exe to, right?
 
  If so, then just go ahead and specify a full path, such as
  lndir /home/dan/x-devel/xc
 
  Hope that helps,
 
  Harold
 
 





FW: xwinclip i18n patch

2002-06-18 Thread Harold Hunt

This is Kensuke Matsuzaki's initial I18N patch for xwinclip.

He sent a follow-up that I will forward shortly.

Harold

-Original Message-
From: MATSUZAKI Kensuke [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 17, 2002 4:25 AM
To: Harold Hunt
Subject: xwinclip i18n patch


This is a patch that add COMPOUND_TEXT and TARGETS support
and little fix for UTF8_STRING to xwinclip.

/**
* MATSUZAKI Kensuke
* mail: [EMAIL PROTECTED]
**/




xwinclip-i18n.patch
Description: Binary data


FW: xwinclip i18n patch

2002-06-18 Thread Harold Hunt

This is Kensuke Matsuzaki's second I18N patch for xwinclip.

Let me know what you guys think of it.

I'm going to apply it within a few days, with the change that it will
determine if you are running Windows 95/98/Me or Windows NT/2000/XP before
it tries calling GetClipboardData with CF_UNICODETEXT, which only works on
NT/2000/XP.

Harold

-Original Message-
From: MATSUZAKI Kensuke [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 17, 2002 1:50 PM
To: Harold Hunt
Cc: MATSUZAKI Kensuke
Subject: Re: xwinclip i18n patch


Hi.

I send new patch that use Xutf8* and CF_UNICODETEXT.

Previous patch use Xmb*, but XLocase doesn't well on
ja_JP.SJIS(Japanese encoding), so it is necessary for Japanese
to apply Mr Fujieda's I18n extension for Cygwin DLL.
#http://www.jaist.ac.jp/~fujieda/cygwin/i18n.shtml

New patch workes without Fujieda's path.

GetClipboardData(CF_UNICODETEXT) is supported only NT/2000/XP.
And CP_UTF8 for WideCharToMultiByte is not supported in 95.

I used it for dozens minutes on Windows 2000/XP.
I can cutpaste Japanesse text between Internet Explorer/Notepad
on Windows and Emacs/Mozilla/KWord on X.
It seems this patch works well.
But I have not tested other locale something like Chinese, Korean, Thai.

/**
 * MATSUZAKI Kensuke
 * mail: [EMAIL PROTECTED]
 **/



xwinclip-i18n-utf.patch
Description: Binary data


RE: Problem starting X

2002-06-18 Thread Harold Hunt

Chris,

 You do have to specify both test and curr if you want both a test and a
 curr version.  As soon as you specify any one of curr, test, or prev,
 you have to explicitly specify everything.

Done.  Thanks.

Harold



RE: Cygwin/XFree86 - patches up to Test59

2002-06-18 Thread Harold Hunt

Ian,

The xoncygwin tree on sourceforge is for the Native GDI development only.
We're trying to keep the tree on sourceforge up to date, but that is not our
primary concern.

So, you kinda had it backwards :)

Harold

 -Original Message-
 From: Ian Burrell [mailto:[EMAIL PROTECTED]]
 Sent: Tuesday, June 18, 2002 6:41 PM
 To: Harold Hunt
 Cc: [EMAIL PROTECTED]
 Subject: Re: Cygwin/XFree86 - patches up to Test59


 Harold Hunt wrote:
  All changes from Server Test Series releases Test 56, Test 57,
 Test 58, and
  Test 59.
 

 Are these patches in the CVS tree for the sourceforge.net xoncygwin
 project? I am assuming that is where Cygwin/XFree86 development happens
 and when things are stable they get fed to the XFree86 developers and
 added to their CVS tree.

   - Ian

 --
 Ian Burrell
 [EMAIL PROTECTED]
 http://www.znark.com/





[ANNOUNCEMENT] Server Test 59

2002-06-14 Thread Harold Hunt

Links:

I just posted Test 59 to the server development page:
http://xfree86.cygwin.com/devel/shadow/

You can install the Test 59 package via setup.exe by selecting the
'test' package: XFree86-xserv-4.2.0-6

Server Test Series binary and source code releases are now
available via the sources.redhat.com ftp mirror network
(http://cygwin.com/mirrors.html) in the
pub/cygwin/xfree/devel/shadow/ directory.  You may wish to note the
desired filename in the links below, then download from your
closest mirror (http://cygwin.com/mirrors.html).

Server binary, direct link:
http://www.msu.edu/~huntharo/xwin/shadow/XWin-Test59.exe.bz2 (1051 KiB)

Server source, direct link:
http://www.msu.edu/~huntharo/xwin/shadow/xwin-20020614-0826.tar.bz2 (72 KiB)
(next link is multiple lines, concatenate them manually)
http://www.msu.edu/~huntharo/xwin/shadow/
xc-programs-Xserver-os-osinit-20020614-0826.c.diff (1 KiB)
(next link is multiple lines, concatenate them manually)
http://www.msu.edu/~huntharo/xwin/shadow/
xc-config-cf-cygwin-20020614-0826.cf.diff (1 KiB)



Changes:

1) win.h, xc/config/cf/cygwin.cf - Stop building RANDR and disable
Cygwin/XFree86's LAYER support.  These two extensions were causing KDE
3.0 icons with alpha channels to not display.  RENDER is still
enabled.  (Harold Hunt)

2) xc/programs/Xserver/os/osinit.c - Don't close the stdin, stdout,
stderr file handles on Cygwin.  We are no longer a command-line
application so stdin, stdout, and stderr point to our first three file
handles, rather than to their usual locations.  This keeps the log
file from being closed when you run XWin.exe with 'start XWin.exe'.
(Stuart Adamson)

3) winwndproc.c - Call TrackMouseEvent to setup tracking for the
WM_MOUSELEAVE message.  When we see a WM_MOUSELEAVE message we show
the cursor if we are hiding it.  This will prevent cursors from
disappearing when using the -lesspointer parameter.  (Harold Hunt)


Enjoy,

Harold




Workaround, for now

2002-06-14 Thread Harold Hunt

I've found a workaround, for now.

It turns out that the RENDER extension is working find on Cygwin/XFree86,
but the LAYER and/or RANDR extensions are causing problems when displaying
icons with alpha channels.  For now the solution is to just disable LAYER
and RANDR, since we don't even know what they do (lack of documentation from
the creator).

I may look into the particular problem with LAYER and/or RANDR later, but
for now consider this BUG CLOSED.

Thanks for your help, especially Waldo, who pointed me to the alpha channel.

Harold Hunt




RE: [PATCH] RE: Ghost cursors (was: RE: alt-tab: client window receives tab / pressing both...)

2002-06-13 Thread Harold Hunt

Nevermind, I just implemented the patch that I was talking about below.

However, I'm getting a strange problem where if I pass any 0 argument
parameters (e.g. -lesspointer) to XWin.exe and I start with 'start XWin' on
Windows 2000 then my log file only contains two lines:

ddxProcessArgument () - Initializing default screens
winInitializeDefaultScreens () - w 1024 h 768


If I start with 'start /B XWin' then the log is normal.  I don't understand
what is going on here.

Maybe I've just done too many compiles and I need to restart my computer.
Or maybe I need to go to bed...

Harold


 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Harold Hunt
 Sent: Thursday, June 13, 2002 2:15 AM
 To: cygx
 Subject: RE: [PATCH] RE: Ghost cursors (was: RE: alt-tab: client window
 receives tab / pressing both...)


 Stuart,

 Naturally, now that I have applied the -lesspointer patch I have
 remembered
 why we switched away from hiding the Windows mouse cursor when we were
 inactive.  The reason goes like this:

 1) User has a Cygwin/XFree86 window that is away from the task bar.

 2) User activates the Cygwin/XFree86 window to bring it to the top, though
 the window is small (say 640x480 on a 1024x768 screen) so it doesn't cover
 all other windows.

 3) Now the user activates another application via the taskbar,
 say a Cygwin
 bash shell.  This other application does not completely cover the
 Cygwin/XFree86 window.

 4) The user moves the mouse into the Cygwin/XFree86 window, without
 clicking, thus hiding the mouse cursor but not activating the
 Cygwin/XFree86
 window.

 5) A popup window from another application grabs the focus and either the
 popup window covers the area underneath the mouse or the user moves the
 mouse into the popup window in such a way as to not cross the non-client
 area of the Cygwin/XFree86 window.

 6) At this point Cygwin/XFree86 should no longer be hiding the
 mouse cursor
 because a) we aren't active and b) the mouse cursor is not over
 our window.
 However, our only way of detecting that the mouse pointer has left our
 window when we are inactive is to watch for the non-client area mouse
 messages.  In this test case we never see a non-client area mouse
 message so
 we never show the cursor.


 I can't remember if this actually causes the Windows cursor to
 not be shown
 for the popup window or not.  It may depend entirely on the version of
 Windows, or it may depend on the popup window, etc.

 All I can say is that the -lesspointer parameter is your guy's
 baby and I'll
 send people to you if they complain about -lesspointer causing
 their cursor
 to disappear over other Windows windows.  :)

 I think the very simple method to make -lesspointer more robust is to call
 TrackMouseEvent with the TME_LEAVE flag when we get our first client area
 mouse message.  Then when the mouse leaves our client area (and
 I'm assuming
 that a popup covering the area underneath the mouse qualifies as
 leaving the
 client area) we will get a WM_MOUSELEAVE message.  We can simply show the
 Windows mouse cursor if it is being hidden at that time.  Simple, eh?


 Harold





RE: Status of multi-windowed server

2002-06-13 Thread Harold Hunt

http://cygwin.com/ml/cygwin-xfree/2002-06/msg00086.html

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of E
 Sent: Thursday, June 13, 2002 3:50 AM
 To: [EMAIL PROTECTED]
 Subject: Status of multi-windowed server


 Hi,

 I was wondering what the status was of using the cygwin xfree server in a
 multi-windowed mode (ie Opening a MS-Windows window for each X client
 window instead of a single window for the X desktop).

 I've browsed the FAQ, website, and did a few searches of the archives for
 this list, but couldn't find anything recent or definitive on the
 status of
 this feature.

 Thanks.

 E.





RE: How to start messing around with creating a rootless mode...

2002-06-13 Thread Harold Hunt

Stuart,

  But on the overall, I don't think it's really the way to go. Again, I
  don't known much about X so it may not be reasonable but what about
  creating a Windows window for each X window? This would allow
 each X App
   to appear in the taskbar like any Windows application.

 This is how eXceed works and it makes more sense to me.  When I'm working
 in rootless mode - typically I won't be running a window manager.


Right.  That is exactly why I described the method of getting started as I
did: because everything you do for drawing in rootless mode will still be
needed when you are drawing to individual windows.

Say what?  That's right, you're still going to have to have a method of
drawing the root window as transparent and setting the clipping region of
the root window to nothing when the server looses the focus.

Once you've got it so that twm can draw windows that float above the
Windows desktop, then you can start worrying about holding hwnd's to
individual windows, etc.

Harold




RE: How to start messing around with creating a rootless mode...

2002-06-13 Thread Harold Hunt

Robert,

I totally forgot that you had worked on a rootless mode.  I'd definitely be
interested in seeing the patches.

Thanks,

Harold




RE: [ANNOUNCEMENT] Server Test 58

2002-06-13 Thread Harold Hunt

Alexander,

  Then you can download them just by running setup.exe and point to any
  mirror.  Then you wouldn't need a separate setup.ini file.

 But the mirrors are not updated instantly. The test release would need
 about one day to spread to the mirrors.

Chris was referring to the fact that, in addition to placing the test
release stand-alone files (e.g., XWin-Test58.exe.bz2) on my msu.edu site and
distributing them via the sources.redhat.com network, I have also been
placing a modified XFree86-xserv-4.2.0-?.tar.bz2 for Cygwin's setup.exe in
cygwin/xfree/release/XFree86/XFree86-xserv/.  Chris was saying that instead
of telling users to point setup.exe to that other directory I could just put
the test package in the normal directory and mark it as 'test' in
setup.hint.

Hope that clears things up,

Harold




Updated on sourceware: XFree86-xserv-4.2.0-5

2002-06-12 Thread Harold Hunt

The XFree86-xserv-4.2.0-5 package has been updated in the Cygwin
distribution.

This is a synchronization with all the fixes that have been applied
Server Test Series - Test 57.  These fixes are listed below:


1) winwndproc.c - Call DefWindowProc after processing WM_NCMOUSEMOVE
messages.  This should fix the highlighting of the minimize and exit
buttons in Windows XP.  (Jehan Bing)

2) winwndproc.c, win.h, winallpriv.c - Make the cursor state
variable, fCursor, a static local variable in
winwndproc.c/winWindowProc (), rather than a member variable in the
winPrivScreenRec structure.  This makes sense because the Windows
cursor is either hidden or shown, as Windows does not hide or show the
mouse cursor on a per-window basis.  This also greatly simplifies the
handling of hiding and showing the Windows mouse cursor.  (Jehan
Bing)

3) InitOutput.c, win.h, wincreatewnd.c - Add a -nodecoration
parameter that creates the Cygwin/XFree86 window that is the same size
as the desktop, without a border.  The end effect is that you can
still get to the taskbar (even with Auto Hide enabled) and easily
switch to other application while not giving up any screen space to
the title bar, borders, etc.  (Jehan Bing)

4) winkeybd.c - Disregard the bogus key releases that we see when
losing the focus via Alt+Tab.  (Stuart Adamson)

5) win.h, winkeybd.h, winkeybd.c, winwndproc.c - Release all pressed
keys when the X server loses the keyboard focus.  (Stuart
Adamson)

6) InitOutput.c - Fix a typo that set iE3BTimeout to TRUE instead of
the specified timeout parameter when using the 3 button mouse
emulation timeout parameter with a single X screen.  (Stuart
Adamson)

7) wincursor.c - See if we are the foreground window before warping
the Windows cursor position.  This fixes the new bug that occurs if
you launch Cygwin/XFree86 and give another application the focus.  In
that case the Windows mouse cursor would still jump to the center of
the screen, even though the Cygwin/XFree86 window was not active.
(Harold Hunt)

8) winkeybd.h - Fix the bug where pressing both shift keys then
releasing them both would still cause all keyboard input to be
shift-modified.  The fix was to set the fixup for the non-extended
VK_SHIFT key to KEY_ShiftL.  (Harold Hunt)

9) wincreatewnd.c - Pass SW_SHOWNORMAL instead of SW_HIDE to
ShowWindow when running a DirectDraw engine in fullscreen mode.  This
fixes the bug where launching Cygwin/XFree86 then giving another
application the focus before the Cygwin/XFree86 window was displayed
would cause Cygwin/XFree86 to never display a window or register a
window handle on the Windows taskbar.  (Harold Hunt)


--
Harold Hunt

To update your installation, click on the Install Cygwin now link
on the http://cygwin.com/ web page.  This downloads setup.exe to
your system.  Save it and run setup, answer the questions and pick
up 'XFree86-xserv' from the 'XFree86' category.  You may need to
click the Full button if it doesn't show up.

Note that downloads from sources.redhat.com (aka cygwin.com) aren't
allowed due to bandwidth limitations.  This means that you will need
to find a mirror which has this update.

In the US, ftp://archive.progeny.com/cygwin/
is a reliable high bandwidth connection.

In Japan, ftp://ftp.u-aizu.ac.jp/pub/gnu/gnu-win32/ is usually
up-to-date.

In DK, http://mirrors.sunsite.dk/cygwin/ is usually up-to-date.

If one of the above doesn't have the latest version of this package
you can either wait for the site to be updated or find another
mirror.

Please  send questions or comments to the Cygwin/XFree86 mailing list at:
[EMAIL PROTECTED] .  If you want to subscribe go to:
http://cygwin.com/lists.html I would appreciate if you would use
this mailing list rather than emailing me directly.  This includes
ideas and comments about the setup utility or Cygwin/XFree86 in general.

If you want to make a point or ask a question the Cygwin/XFree86 mailing
list is the appropriate place.



RE: xwinclip-test04

2002-06-12 Thread Harold Hunt

Gerard,

How long is awhile?  20 seconds or 30 minutes?

If it dumps core after 20 seconds then it is because XWin.exe is taking too
long to launch so OpenDisplay fails.  Test05 fixes that problem.

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Pille Geert (bkarnd)
 Sent: Wednesday, June 12, 2002 10:11 AM
 To: '[EMAIL PROTECTED]'
 Subject: xwinclip-test04


 cuts and pastes both ways when not running fullscreen.

 performance problem remains solved.

 xwinclip-test04 dumpes core when XWin runs fullscreen, but only after a
 while.

 Here ends our transmission.

 Gerard.


 ===
 This email is confidential and intended solely for the use of the
 individual to whom it is addressed.
 If you are not the intended recipient, be advised that you have
 received this email in error and that any use, dissemination,
 forwarding, printing, or copying of this email is strictly prohibited.
 You are explicitly requested to notify the sender of this email
 that the intended recipient was not reached.





[ANNOUNCEMENT] Server Test 58

2002-06-12 Thread Harold Hunt

Links:

I just posted Test 58 to the server development page:
http://xfree86.cygwin.com/devel/shadow/

You can install the Test 58 package via setup.exe by pointing setup.exe
to the cygwin/xfree/testing/ directory on your favorite mirror.
For example, you could point setup.exe at:
http://archive.progeny.com/cygwin/xfree/testing/

Server Test Series binary and source code releases are now
available via the sources.redhat.com ftp mirror network
(http://cygwin.com/mirrors.html) in the
pub/cygwin/xfree/devel/shadow/ directory.  You may wish to note the
desired filename in the links below, then download from your
closest mirror (http://cygwin.com/mirrors.html).

Server binary, direct link:
http://www.msu.edu/~huntharo/xwin/shadow/XWin-Test58.exe.bz2 (1078 KiB)

Server source, direct link:
http://www.msu.edu/~huntharo/xwin/shadow/xwin-20020613-0102.tar.bz2 (72 KiB)


Changes:

1) InitOutput.c, XWin.man, win.h, winwndproc.c - Add the -lesspointer
command line parameter which causes Cygwin/XFree86 to hide the Windows
mouse cursor when the mouse is over any Cygwin/XFree86 window (whether
activated or not).  (Stuart Adamson)


Enjoy,

Harold




RE: [ANNOUNCEMENT] Server Test 58

2002-06-12 Thread Harold Hunt

Chris,

 Why not just install the latest server test packages in the normal
 cygwin place but mark it as test in setup.hint?

 I don't recall this being suggested before.  Apologies if this has already
 been discussed.

Oh, I'm aware that that functionality is there... but I have been trying to
avoid looking for the docs on it or an example setup.hint for it.  You know,
the old beer or coding conflict...

Harold




RE: [PATCH] RE: Ghost cursors (was: RE: alt-tab: client window receives tab / pressing both...)

2002-06-12 Thread Harold Hunt

Stuart,

Naturally, now that I have applied the -lesspointer patch I have remembered
why we switched away from hiding the Windows mouse cursor when we were
inactive.  The reason goes like this:

1) User has a Cygwin/XFree86 window that is away from the task bar.

2) User activates the Cygwin/XFree86 window to bring it to the top, though
the window is small (say 640x480 on a 1024x768 screen) so it doesn't cover
all other windows.

3) Now the user activates another application via the taskbar, say a Cygwin
bash shell.  This other application does not completely cover the
Cygwin/XFree86 window.

4) The user moves the mouse into the Cygwin/XFree86 window, without
clicking, thus hiding the mouse cursor but not activating the Cygwin/XFree86
window.

5) A popup window from another application grabs the focus and either the
popup window covers the area underneath the mouse or the user moves the
mouse into the popup window in such a way as to not cross the non-client
area of the Cygwin/XFree86 window.

6) At this point Cygwin/XFree86 should no longer be hiding the mouse cursor
because a) we aren't active and b) the mouse cursor is not over our window.
However, our only way of detecting that the mouse pointer has left our
window when we are inactive is to watch for the non-client area mouse
messages.  In this test case we never see a non-client area mouse message so
we never show the cursor.


I can't remember if this actually causes the Windows cursor to not be shown
for the popup window or not.  It may depend entirely on the version of
Windows, or it may depend on the popup window, etc.

All I can say is that the -lesspointer parameter is your guy's baby and I'll
send people to you if they complain about -lesspointer causing their cursor
to disappear over other Windows windows.  :)

I think the very simple method to make -lesspointer more robust is to call
TrackMouseEvent with the TME_LEAVE flag when we get our first client area
mouse message.  Then when the mouse leaves our client area (and I'm assuming
that a popup covering the area underneath the mouse qualifies as leaving the
client area) we will get a WM_MOUSELEAVE message.  We can simply show the
Windows mouse cursor if it is being hidden at that time.  Simple, eh?


Harold




RE: Slow application launch in Outlook with xwinclip.exe running

2002-06-10 Thread Harold Hunt

Eric,

Interesting.  I've heard reports of this before.

However, I'm unable to duplicate this problem.

I suspect that the problem has something to do with the fact that X events
don't come in that often, so we may not process our Windows events in a
timely manner.  I have been searching forever for a non-blocking equivalent
to XNextEvent... and I finally found one!  Here is Owen Taylor's response to
someone looking for the same thing:
http://www.xfree86.org/pipermail/xpert/2001-December/013978.html

===
 For reasons to do with a user interface element I'm working on,
 I need something like select.  Do the XCheck*Event() functions
 block?  I'm really reluctant to use pthreads, as this isn't portable
 enough for what I'm trying to do.

 Specifically, if the app is in a certain state, I want to update the
 window every 1/32 of a second, but I need to keep processing events too.
 If XCheckWindowEvent() doesn't block, and is reasonably quick, it will
 do perfectly.  Does it?

The standard way of doing a non-blocking check is

 if (XPending (display))
   {
 XNextEvent (display, event);
   }

Using any of the XCheck*Event functions can be relatively slow, since
they need to search the entire queue. (If you had to use one, I'd
suggest using XCheckIfEvent with an appropriate predicate. But XPending()
should be as good or better.)

Of course, what real toolkits do is select() on ConnectionNumber(display)
to know when they need to call XPending() without having to poll
continuously.
===


I was very intrigued to see this.  This not only means that I can make
xwinclip better, but it means that I can finally integrate clipboard support
into XWin.exe, since we'll actually be able to see some sort of shutdown
message, rather than having XNextEvent fail and call exit ().  (Obviously
you can't integrate a clipboard client in the server if every time you reset
you call exit ()... cause you would exit instead of resetting.)

I've done a small rewrite of xwinclip to use select () on both the X event
handle and /dev/windows (which is a socket that watches the Windows message
queue).  This should solve the problem that you are seeing with Outlook
because we will process our Windows messages in a timely manner.

I'll post the new xwinclip in just a few minutes.

It won't be long now until we can get rid of xwinclip and have clipboard
integration directly in XWin.exe.

Harold




[ANNOUNCEMENT] xwinclip Test 04 (Cygwin/XFree86 and Windows clipboard integration)

2002-06-10 Thread Harold Hunt

Links:

I just posted Test 04 to the xwinclip development page:
http://xfree86.cygwin.com/devel/xwinclip/

xwinclip binary and source code releases are available via the
sources.redhat.com ftp mirror network
(http://cygwin.com/mirrors.html) in the
pub/cygwin/xfree/devel/xwinclip/ directory.  You may wish to note the
desired filename in the links below, then download from your
closest mirror (http://cygwin.com/mirrors.html).

xwinclip binary, direct link:
http://www.msu.edu/~huntharo/xwin/xwinclip/xwinclip-Test04.exe.bz2 (4 KB)

Server source, direct link:
http://www.msu.edu/~huntharo/xwin/xwinclip/xwinclip-20020610-2055.tar.bz2 (6
KB)


Changes:

1) xwinclip.c - Use select () in ConnectionNumber(pDisplay) and
/dev/windows instead of calling XNextEvent, which blocks until the
next event.  This has many benefits: Windows messages are now
processed almost immediately after they come in (the old approach
could take minutes), we can catch the X shutdown and restart messages
rather than having XNextEvent call exit () when it sees that the
connection has closed (we don't currently catch these events), and the
clipboard integration code can now be rewritten with the assumption
that we can and will see the Windows events when they arrive without
an X event immediately preceeding them (which may allow us to stop
stealing ownership of the X selection).  (Harold Hunt)

Here is a description of using select instead of XNextEvent:
http://www.xfree86.org/pipermail/xpert/2001-December/013978.html

Here are two examples of how to use select instead of XNextEvent:
http://www.neosoft.com/tcl/tclhtml/tclFAQ/part2/faq-doc-54.html
http://www-h.eng.cam.ac.uk/help/tpl/graphics/X/signals.html
(That second one is towards the bottom, just find `ConnectionNumber')

2) xwinclip.c - Move the X event loop into new function
FlushXEventQueue.  (Harold Hunt)


Enjoy,

Harold




RE: KDE (or gnome)

2002-06-10 Thread Harold Hunt

You have to keep replies to the mailing list.

Someone on the list probably can explain this better than I.  (And how would
my time better be spent, developing features or answering simple questions
that take a lot of writing?  :)

Harold

 -Original Message-
 From: Splatter van Upchuck [mailto:[EMAIL PROTECTED]]
 Sent: Monday, June 10, 2002 7:09 PM
 To: Harold L Hunt
 Subject: Re: KDE (or gnome)


 What else runs under XFree then? I can't figure that looking at a
 couple of
 terminal sessions and XClock constitutes the entire XFree86
 experience under
 cygwin surely? Or does it???


  Neither Gnome nor KDE on Cygwin are ready for newbies yet.
 They are very
  preliminary packages.  You have to really know what you are doing to get
  either of them working.

 laughter Well, I had a hankering to actually wind up with a 'desktop'
 believe it or not :-) Although I have one technically speaking, there's
 absolutely nothing on it as I said above...so what am I missing Harold???
  I recommend that you just be happy with looking at KDE and Gnome on your
  friend's linux boxes.

 I could use just a *little* help here..y'know..pointers in the right
 direction? Else what is the point of cygwin to begin with...aside from the
 avowed intent of allowing programmers to port stuff over from one
 environment to anothersurely that's not the only reason for cygwins'
 existence

 Thanks for the response Haroldbut please suggest ideas, I don't mind
 doing a ton of reading and trying to make something work.

 -Splat






How to start messing around with creating a rootless mode...

2002-06-09 Thread Harold Hunt

Now that we have the -nodecoration parameter we can start messing around
with making the some initial moves towards a rootless mode, just like
XDarwin.  Here are some initial steps to take that would help you learn a
little about creating a rootless mode:

1) Start off by simply overriding PaintWindowBackground to paint a
transparent background to cause the X Windows (still managed by a window
manager such as twm) to 'float' above the Windows desktop when
Cygwin/XFree86 has the focus.

2) You'll need to look at
xc/programs/Xserver/hw/darwin/quartz/rootlessScreen.c/RootlessPaintWindowBac
kground ().  There is a check in this function that paints the root window
background using the 'magic' transparent color.  You'll need to do something
like this for Cygwin/XFree86, so you'll need to start by finding the Windows
'magic' transparent color.  You'll also need to put a function that is
almost equivalent to this function into some file in hw/xwin/.

3) You now need to wrap the paint background function so that our paint
background function gets called first.  XDarwin does this in
xc/programs/Xserver/hw/darwin/quartz/rootlessScreen.c/RootlessWrap ().  To
start you'll need to make a similar function to this in hw/xwin/, or you
could just copy the WRAP macro and the call to it for PaintWindowBackground
into hw/xwin/winscrinit.c/winFinishScreenInitFB ().  Darwin calls
RootlessWrap through a convoluted sequence something like:
DarwinAddScreen-QuartzSetupScreen-AquaSetupScreen-RootlessInit-RootlessW
rap.


If you do all that you'd have put Cygwin/XFree86 on the road to having a
rootless mode.


Good luck,

Harold




RE: [ANNOUNCEMENT] Server Test 57

2002-06-09 Thread Harold Hunt

Jehan,

That last message fired off before I was done... my Ctrl key is sticking so
when I hit Enter it sent a Ctrl+Enter, which sends the message.

 I don't think you need to manage the cursor in WM_ACTIVATEAPP, managing
 it in WM_ACTIVATE should be enough because, if I'm not wrong, XWin will
 always receive a WM_ACTIVATE with a WM_ACTIVATEAPP.

Then again, your version gets trapped in a state where the cursor is shown,
whereas I haven't seen that problem with Test57 yet :)

I remember spending a *lot* of time reading the docs about WM_ACTIVATE and
WM_ACTIVATEAPP to figure out where to show and hide the cursor.  There were
constant bug repots until I got it right, so I'm going to tend to believe
that the show/hide in WM_ACTIVATEAPP is required, until someone presents me
with some sample code and documentation exerpts that shows me that 1)
they've spent more time on the problem than I have and 2) that the show/hide
code in WM_ACTIVATEAPP is indeed not needed.

Until then, I'm inclined to leave the processing as it is.

Harold




RE: [patch] cursor

2002-06-08 Thread Harold Hunt

Jehan,

 - Last, WM_NCMOUSEMOVE calls the default winproc. This should fix
 the min/max/close button highlight problem on WinXP (Although I don't
 have XP so I can't test)

That's an excellent catch.  I went back and read the Platform SDK docs about
WM_NCMOUSEMOVE:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winui/winui
/windowsuserinterface/userinput/mouseinput/mouseinputreference/mouseinputmes
sages/wm_ncmousemove.asp

As I thought, the documentation for WM_NCMOUSEMOVE does say that you are
supposed to return 0 if you process that message.  However, they fail to
mention that things such as button highlighting are handled by
DefWindowProc, which you still need to call if you want to preserve that
default behavior.  This document gave me some indications that this was the
case:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winui/winui
/windowsuserinterface/userinput/mouseinput/aboutmouseinput.asp

One thing that is not entirely clear is whether we should call
DefWindowProc, then return 0, or if we should just 'break' after our
processing of the message and return whatever DefWindowProc returns.  I've
opted for the latter, for now.


 - Moreover, the cursor state is global to the application, not to
 each window. So I made fCursor a global variable, which simplifies the
 code more (doesn't care about ScreenPrivLast anymore). Potentially, we
 could get rid of fCursor  altogether by using GetCursorInfo instead
 (don't know about performance issues though).

Making the cursor state a global variable is probably a good idea; or, we
could at least make it a static inside winWindowProc if it is not accessed
elsewhere.  This would take care of the cursor hiding/showing problems that
happen when we have multiple screens.  (e.g. XWin -screen 0 640 480 -screen
1 1024 768)

I'll go ahead and switch the cursor state variable to a global.


 - It maybe just a matter of preferences but for me, I prefer if the
 windows cursor is hidden in the client area of X if it isn't active. I
 personnally find it ugly to have two mouse cursors on top of each other
 :p. It's then not necessary to show/hide the mouse upon (de)activation.
 This simplifies the code a bit.

This is really a matter of preference.  I originally coded it this way, but
I got enough complaints that I switched to the current system of not hiding
the cursor when we don't have the focus.  Maybe we can make this a
configuration option?  As it is it just reverts to previous functionality,
so I'll skip it for now.

Thanks,

Harold




[ANNOUNCEMENT] Server Test 57

2002-06-08 Thread Harold Hunt

Links:

I just posted Test 57 to the server development page:
http://xfree86.cygwin.com/devel/shadow/

You can install the Test 57 package via setup.exe by pointing setup.exe
to the cygwin/xfree/testing/ directory on your favorite mirror.
For example, you could point setup.exe at:
http://mirrors.rcn.net/pub/sourceware/cygwin/xfree/testing/

Server Test Series binary and source code releases are now
available via the sources.redhat.com ftp mirror network
(http://cygwin.com/mirrors.html) in the
pub/cygwin/xfree/devel/shadow/ directory.  You may wish to note the
desired filename in the links below, then download from your
closest mirror (http://cygwin.com/mirrors.html).

Server binary, direct link:
http://www.msu.edu/~huntharo/xwin/shadow/XWin-Test57.exe.bz2 (1078 KiB)

Server source, direct link:
http://www.msu.edu/~huntharo/xwin/shadow/xwin-20020608-2149.tar.bz2 (72 KiB)


Changes:

1) winwndproc.c - Call DefWindowProc after processing WM_NCMOUSEMOVE
messages.  This should fix the highlighting of the minimize and exit
buttons in Windows XP.  (Jehan Bing)

2) winwndproc.c, win.h, winallpriv.c - Make the cursor state
variable, fCursor, a static local variable in
winwndproc.c/winWindowProc (), rather than a member variable in the
winPrivScreenRec structure.  This makes sense because the Windows
cursor is either hidden or shown, as Windows does not hide or show the
mouse cursor on a per-window basis.  This also greatly simplifies the
handling of hiding and showing the Windows mouse cursor.  (Jehan
Bing)


Enjoy,

Harold




RE: [patch] cursor

2002-06-08 Thread Harold Hunt

Jehan,

 A static would do the job but, by personnally, I don't like static in a
 function. It's easy to miss the static keyword when reading the code
 which then make it hard to understand (or at least, I missed it. Several
 times already I spent a few hours to try to understand why the code was
 working just because I missed it :p).

Okay, I have implemented a new convention: static variable names are now
prefixed with 's_', just like globals are prefixed with 'g_'.

I've updated all files in the hw/xwin directory and I'll submit that patch
to XFree86.

Harold




RE: A couple of patches

2002-06-07 Thread Harold Hunt

Now that is what I like to see: on a guy's first post to the list he sends
two bug reports and two patches.  Outstanding!

I've applied both patches (with formatting fixes) and I'll release a new
server binary shortly.

I also added a patch for the, press both shifts, release both shifts, input
remains shifted bug.

 Side note - I had to comment out the Beep() call in winkeydb.c as this was
 causing X to hang.

You must be looking at some old source... the function has been changed to
MessageBeep.  The comments have also been updated to indicate that Beep is a
really bad idea.

Thanks for the patches,

Harold

P.S. Regarding the three button emulation patch, I can only say, how
embarrassing.  I can't believe I have not caught that one on my own.

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Stuart Adamson
 Sent: Friday, June 07, 2002 5:33 AM
 To: '[EMAIL PROTECTED]'
 Subject: A couple of patches


 Attached are a couple of patches.  These fix a few bugs that were annoying
 me in XFree86 4.2.0.
 I can't get access to CVS at the moment so this might be fixed in
 there - if
 so then feel
 free to ignore them ;)

 1) Key strokes when X loses / gains focus.  winkeydb.c now tracks
 which keys
 are up and down
and releases all down keys when focus is lost.  Also, it kills phantom
 key up messages
being received (typcially when ALT-TAB'ing to the X server).  This was
 causing (a) ICE to
switch between windows and (b) bash to see a tab and try to
 auto-complete
 causing cygwin to
thrash my hard disk looking for all executables in my path ;(


 2) emulate3buttons didn't work correctly in single screen mode as
 InitOutput
 set the timeout to
TRUE (1) rather than the default (50) or user supplied value.
 This made
 getting the middle
button a matter of good timing ;)

 Side note - I had to comment out the Beep() call in winkeydb.c as this was
 causing X to hang.  The comments just above the call about the arguments
 being ignored are not true - under
 Win NT / 2000 the arguments are used (according to MSDN at least ;)).


 Regards


 Stuart






Updated on sourceware: XFree86-xserv-4.2.0-4

2002-06-07 Thread Harold Hunt

The XFree86-xserv-4.2.0-4 package has been updated in the Cygwin
distribution.

Stuart Adamson's patches have been applied:
http://cygwin.com/ml/cygwin-xfree/2002-06/msg00056.html

Stuart's patches cover:
1) Releasing all pressed keys when XWin.exe loses focus

2) Discarding some bogus Alt key releases (I think) when we Alt+Tab out of
XWin.exe

3) Fixing a typo in InitOutput.c set an infinite timeout for three button
emulation when the user specified a timeout value for a single screen.

In addition, I have fixed:
1) Pressing both shifts then releasing both shifts leaves all input shifted.

--
Harold Hunt

To update your installation, click on the Install Cygwin now link
on the http://cygwin.com/ web page.  This downloads setup.exe to
your system.  Save it and run setup, answer the questions and pick
up 'XFree86-xserv' from the 'XFree86' category.  You may need to
click the Full button if it doesn't show up.

Note that downloads from sources.redhat.com (aka cygwin.com) aren't
allowed due to bandwidth limitations.  This means that you will need
to find a mirror which has this update.

In the US, ftp://mirrors.rcn.net/mirrors/sources.redhat.com/cygwin/
is a reliable high bandwidth connection.

In Japan, ftp://ftp.u-aizu.ac.jp/pub/gnu/gnu-win32/ is usually
up-to-date.

In DK, http://mirrors.sunsite.dk/cygwin/ is usually up-to-date.

If one of the above doesn't have the latest version of this package
you can either wait for the site to be updated or find another
mirror.

Please  send questions or comments to the Cygwin/XFree86 mailing list at:
[EMAIL PROTECTED] .  If you want to subscribe go to:
http://cygwin.com/lists.html I would appreciate if you would use
this mailing list rather than emailing me directly.  This includes
ideas and comments about the setup utility or Cygwin/XFree86 in general.

If you want to make a point or ask a question the Cygwin/XFree86 mailing
list is the appropriate place.




RE: [PATCH] -nodecoration parameter

2002-06-07 Thread Harold Hunt

Jehan,

Excellent!  I've applied this patch as well.  I'm going to release this as a
test release in a few moments so that I don't overwhelm users with new
Cygwin setup.exe packages.

Keep feeding me patches guys!!  :)

Harold

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Jehan
 Sent: Friday, June 07, 2002 9:22 PM
 To: [EMAIL PROTECTED]
 Subject: [PATCH] -nodecoration parameter


 Hi,

 Here is a little patch that adds a -nodecoration parameter to XWin.
 With this parameter on (and no -fullscreen), the XWin window won't have
 titlebar nor border. It cumulates the advantage of both fullscreen
 (doesn't waste estate, especially if your taskbar in set to auto-hide)
 and non-fullscreen mode (Windows window on top of XWin, taskbar and
 other desktop toolbar still visible, always-on-top (winamp) window are
 still accessible).

 Jehan





  1   2   3   >