From fgo-confirm@lists.yourfunmail.com Sun Jan 2 22:09:00 2000 From: fgo-confirm@lists.yourfunmail.com (fgo-confirm@lists.yourfunmail.com) Date: Sun, 02 Jan 2000 22:09:00 -0000 Subject: Your Confirmation is Required! -- Request Number 229253 Message-ID: <20000103070911.DC13E92C@poppyjill.connectcorp.net> One more step -- Confirmation Required -- Just click on Reply, then click on Send. Margarita Maria here (the real live teenage girl that puts this whole thing together) to say that there is just one more easy step and you will be successfully subscribed to For Girls Only!!! the official e-zine for girls of the new millennium. You are getting this letter because I have received a subscription request either from you personally or from someone who thought you would enjoy this FREE online service. Being the anti-spam person that I am, I need to make sure that you really want to receive this all-new Internet newsletter. First, let me tell you my Privacy Policy: I do not tolerate Spam or junk e-mail. I personally guarantee that I will never sell or give your e-mail address to anyone. For Girls Only!!! is the greatest new e-zine on the 'Net - chock-full of girly stuff; you know - Makeup tips, Hairdo Hints, and Free Kotex Samples! *** JUST KIDDING!!! *** Actually, I COULD have done it that way, but I'd rather think you're much smarter than to fall for that kind of lame poppycock. So, it's really about growth and becoming happy with Who You Are instead of trying to make yourself into someone else's idea of "Miss Perfect." We'll talk about school, and boys, and family life, and lots of stuff girls need to know. Because, Let's face it: GIRLS ROCK!!! If you are not a girl, and have received this letter in error, I am very sorry, but, do not despair, I have a few constructive suggestions for you as alternatives to bashing your monitor in???? 1) Delete this message and forget about it, and have a fabulous day! 2) Tell all the girls you know to subscribe to For Girls Only!!! because they will love you for it! 3) Have a good laugh, because someone figured it would be a funny joke to subscribe you to an e-zine designed for girls only. 4) Go ahead and subscribe, and spy on the girls. (Be advised: girls spy on guys, too!) *** To join our FGO family, simply reply to this message without changing anything. Just click on Reply, then click on Send. If For Girls Only!!! is not for you then simply delete this message without replying. (Caution! Replying to this message for ANY reason will automatically subscribe you.) Love, Margarita Maria Editor and Host: o) Questions? Visit our web site at http://www.YourFunMail.com/fgo From ssiddiqi@inspirepharm.com Mon Jan 3 06:32:00 2000 From: ssiddiqi@inspirepharm.com (Suhaib Siddiqi) Date: Mon, 03 Jan 2000 06:32:00 -0000 Subject: FW: [Fwd: YAHOO, I got xclock to work under XGGI!!!] Message-ID: The following message is from John Fortin. Suhaib > -----Original Message----- > From: John Fortin [ mailto:fortinj@ibm.net ] > Sent: Sunday, January 02, 2000 10:35 PM > To: Mike MacDonald; Suhaib M. Siddiqi > Subject: [Fwd: YAHOO, I got xclock to work under XGGI!!!] > > > Suhaib, > > Could you post to the maillist. I'm blocked for the moment... > > John > > John Fortin wrote: > > > > All, > > Just for your info, I have finally gotten > xclock ( my initial test > > case) to work under mingw32/Directx/GGI/XGGI!!! > > > > Now for Keyboard and Mouse debugging!! > > > > John > From ssiddiqi@inspirepharm.com Mon Jan 3 11:59:00 2000 From: ssiddiqi@inspirepharm.com (Suhaib Siddiqi) Date: Mon, 03 Jan 2000 11:59:00 -0000 Subject: DX server.. References: Message-ID: in xc/config/cf/cygwin.cf from #define StandardDefines delete -DX_NOT_POSIX I accidently left it. Cygwin is POSIX. I added it when I was patching the code for MingW32. After you edit cygwin.cf, run a make clean first then make World and you should be fine. Regardiung patches failing for xterm, that is because my patches are already part of xterm in 3.9.16... ignore all the failed patches for xterm. Suhaib > -----Original Message----- > From: Mike MacDonald [ mailto:mmacdonald@tsi.gte.com ] > Sent: Monday, January 03, 2000 2:36 PM > To: 'Dakshinamurthy Karra'; 'ssiddiqi@inspirepharm.com' > Subject: RE: DX server.. > > > This is what I get when I patch 3.9.16: > > gcc -O2 -pedantic -fno-strength-reduce -fnative-struct > -m486 -g -Wall > -I../../include -I../../exports/include/X11 -I../.. > -I../../exports/include > -D__i386__ -DWIN32_LEAN_AND_MEAN -DX_LOCALE -D_MT -D_X86_ > -D__STDC__ > -DNO_TCP_H -D__CYGWIN__ -DX_NOT_POSIX -D_REENTRANT -D_GNU_SOURCE > -DFUNCPROTO=15 -DNARROWPROTO -DCPP_PROGRAM="\"cpp\"" > -c imake.c -o > imake.o > imake.c: In function `main': > imake.c:407: warning: implicit declaration of function `mktemp' > imake.c: In function `wrapup': > imake.c:452: warning: implicit declaration of function `unlink' > imake.c: In function `FindImakefile': > imake.c:639: warning: implicit declaration of function `access' > imake.c: In function `doit': > imake.c:756: warning: implicit declaration of function `fork' > imake.c:760: warning: passing arg 1 of `wait' from > incompatible pointer type > imake.c:762: invalid operands to binary & > imake.c:762: invalid operands to binary & > imake.c:763: union has no member named `w_T' > imake.c:764: invalid operands to binary & > imake.c:764: union has no member named `w_T' > imake.c:765: union has no member named `w_T' > imake.c:772: warning: implicit declaration of function `dup2' > imake.c:773: warning: implicit declaration of function `execvp' > imake.c: In function `ReadLine': > imake.c:1513: warning: implicit declaration of function > `ftruncate' > imake.c: At top level: > imake.c:782: warning: `parse_utsname' defined but not used > imake.c:852: warning: `trim_version' defined but not used > make[2]: *** [imake.o] Error 1 > make[1]: *** [imake.bootstrap] Error 2 > make: *** [World] Error 2 > > Maybe I'm missing a header file? Is this what you get Karra? > From fortinj@ibm.net Mon Jan 3 19:45:00 2000 From: fortinj@ibm.net (John Fortin) Date: Mon, 03 Jan 2000 19:45:00 -0000 Subject: XGGI Update Message-ID: <38716DB3.E5D6F07D@ibm.net> More good news... I have gotten xterm to (mostly) work. Some keys are not mapped properly ( backspace for one) but I can type Upper/Lower case, commands work, and lots of control-keys work (ex. ctrl-m as alternate enter). Suhaib, Have you ever tried compiling XGGI using straight mingw32?? I would like to get away from the cygwin1.dll, if possible. How about the other X11 binaries ( xterm, twm, etc ?) Thanks John From khan@NanoTech.Wisc.EDU Mon Jan 3 19:59:00 2000 From: khan@NanoTech.Wisc.EDU (Mumit Khan) Date: Mon, 03 Jan 2000 19:59:00 -0000 Subject: XGGI Update References: <38716DB3.E5D6F07D@ibm.net> Message-ID: <200001040359.VAA17226@hp2.xraylith.wisc.edu> John Fortin writes: > Have you ever tried compiling XGGI using straight mingw32?? I would > like to get away from the cygwin1.dll, if possible. How about the other > X11 binaries ( xterm, twm, etc ?) Chances of xterm building under Mingw is pretty small, given that it needs pseudo ttys. XGGI should build under Mingw however, and if not, I can provide a hand there. Most of the clients should build easily under Mingw, except for the likes of xterm. Rxvt should build under Mingw, unless it's gone through major code changes in the last few years. Got any perf numbers yet? Just being greedy, sorry ;-) Regards, Mumit From fortinj@ibm.net Mon Jan 3 20:08:00 2000 From: fortinj@ibm.net (John Fortin) Date: Mon, 03 Jan 2000 20:08:00 -0000 Subject: XGGI Update References: <200001040359.VAA17226@hp2.xraylith.wisc.edu> Message-ID: <38717300.74C609C3@ibm.net> > Chances of xterm building under Mingw is pretty small, given that it needs > pseudo ttys. I think I had heard that before... > > XGGI should build under Mingw however, and if not, I can provide a hand > there. > > Most of the clients should build easily under Mingw, except for the likes > of xterm. Rxvt should build under Mingw, unless it's gone through major > code changes in the last few years. > > Got any perf numbers yet? Just being greedy, sorry ;-) Still have to do the mouse interface. Should be pretty easy though, compared to the keyboard interface. John From Ssiddiqi@inspirepharm.com Mon Jan 3 20:28:00 2000 From: Ssiddiqi@inspirepharm.com (Suhaib M. Siddiqi) Date: Mon, 03 Jan 2000 20:28:00 -0000 Subject: XGGI Update References: <38717300.74C609C3@ibm.net> Message-ID: On 04-Jan-00 John Fortin wrote: >> Chances of xterm building under Mingw is pretty small, given that it needs >> pseudo ttys. > > I think I had heard that before... True, xterm compiles best with Cygwin. It had been discussed before on several mailing list. MingW32 cannot build xterm because Win32 (native) has no tty support > >> >> XGGI should build under Mingw however, and if not, I can provide a hand >> there. >> >> Most of the clients should build easily under Mingw, except for the likes >> of xterm. Rxvt should build under Mingw, unless it's gone through major >> code changes in the last few years. xdm, and a few others cannot be build using MingW32... including xedit and glx from xfree86 4.0. Cygwin is best suited for that. >> >> Got any perf numbers yet? Just being greedy, sorry ;-) > > Still have to do the mouse interface. Should be pretty easy though, > compared to the keyboard interface. I am looking forward to John's great work Suhaib > > John ---------------------------------- E-Mail: Suhaib M. Siddiqi Date: 03-Jan-00 Time: 23:21:55 ---------------------------------- From Ssiddiqi@inspirepharm.com Mon Jan 3 20:35:00 2000 From: Ssiddiqi@inspirepharm.com (Suhaib M. Siddiqi) Date: Mon, 03 Jan 2000 20:35:00 -0000 Subject: XGGI Update References: <200001040359.VAA17226@hp2.xraylith.wisc.edu> Message-ID: Hi Mumit, On 04-Jan-00 Mumit Khan wrote: > John Fortin writes: >> Have you ever tried compiling XGGI using straight mingw32?? I would >> like to get away from the cygwin1.dll, if possible. How about the other >> X11 binaries ( xterm, twm, etc ?) > > Chances of xterm building under Mingw is pretty small, given that it needs > pseudo ttys. That is true. xterm, xedit and xdm cannot be compiled using MingW32. > > XGGI should build under Mingw however, and if not, I can provide a hand > there. Yes you can do that. I am working on it already. You can get the precompiled libs from my URL at siddiqi.webjump.com. The set contains precompiled cfb, cfb16, cfb32 and all other needed libs to compile an Xserver. You can get only XGGI code from GGI-project URL compile using my precompiled libs... it is just an imagination, I have not tried. I had been patching X11R6.4 code for MingW32 and it is a lot more work then patching Xfree for Cygwin. and all other needed > > Most of the clients should build easily under Mingw, except for the likes > of xterm. Rxvt should build under Mingw, unless it's gone through major > code changes in the last few years. Actually some important clients needed by X-server do not build using MSVC, unless you get my MSVC patches. > > Got any perf numbers yet? Just being greedy, sorry ;-) perf for XGGI should not be good. Even on Linux it has a bad perf... XGGI is a low level Xserver which run on top of GGI libs which affects perf Suhaib > > Regards, > Mumit ---------------------------------- E-Mail: Suhaib M. Siddiqi Date: 03-Jan-00 Time: 23:28:03 ---------------------------------- From Ssiddiqi@inspirepharm.com Mon Jan 3 20:40:00 2000 From: Ssiddiqi@inspirepharm.com (Suhaib M. Siddiqi) Date: Mon, 03 Jan 2000 20:40:00 -0000 Subject: XGGI Update References: <38716DB3.E5D6F07D@ibm.net> Message-ID: On 04-Jan-00 John Fortin wrote: > More good news... I have gotten xterm to (mostly) work. Some keys are > not mapped properly ( backspace for one) > but I can type Upper/Lower case, commands work, and lots of control-keys > work (ex. ctrl-m as alternate enter). John That could be termcap file in your /etc. > > Suhaib, > Have you ever tried compiling XGGI using straight mingw32?? I would > like to get away from the cygwin1.dll, if possible. How about the other > X11 binaries ( xterm, twm, etc ?) > John xterm cannot be compiled using MingW32 or MSVC because it requires ttys. I am patching X11 code for MingW32. It is a lot more work to patch X11 code for MingW32 then for Cygwin. I would in the near future provide XGGI binaries compiled with MSVC and also Cygwin. Suhaib > Thanks > John ---------------------------------- E-Mail: Suhaib M. Siddiqi Date: 03-Jan-00 Time: 23:35:03 ---------------------------------- From kdmurthy@vsnl.com Mon Jan 3 20:48:00 2000 From: kdmurthy@vsnl.com (kdmurthy@vsnl.com) Date: Mon, 03 Jan 2000 20:48:00 -0000 Subject: XGGI Update Message-ID: <200001040446.KAA03766@mypage.vsnl.com> Mumit Khan wrote: > XGGI should build under Mingw however, and if not, I can provide a hand > there. > This will be great for the DirectX based server also. Currently the server is functional with VC-6 and should be portable to Mingw32. When we are at it, is there any how-to about compiling a VC program under Mingw or cygwin? (Trying to find a easy way out). -- KD From kdmurthy@vsnl.com Mon Jan 3 20:53:00 2000 From: kdmurthy@vsnl.com (kdmurthy@vsnl.com) Date: Mon, 03 Jan 2000 20:53:00 -0000 Subject: XGGI Update Message-ID: <200001040450.KAA17857@mypage.vsnl.com> "Suhaib M. Siddiqi" wrote: > xdm, and a few others cannot be build using MingW32... including xedit and > glx from xfree86 4.0. Cygwin is best suited for that. I do not think so. Since xdm (client portion which was required by the X Servers) works with VC6, it should work with mingw32 also. Or am I missing something here? > >> Got any perf numbers yet? Just being greedy, sorry ;-) How do we get perf numbers for a X-Server? -- KD From khan@NanoTech.Wisc.EDU Mon Jan 3 22:43:00 2000 From: khan@NanoTech.Wisc.EDU (Mumit Khan) Date: Mon, 03 Jan 2000 22:43:00 -0000 Subject: XGGI Update References: <200001040446.KAA03766@mypage.vsnl.com> Message-ID: <200001040642.AAA17448@hp2.xraylith.wisc.edu> kdmurthy@vsnl.com writes: > > This will be great for the DirectX based server also. Currently the > server is functional with VC-6 and should be portable to Mingw32. > > When we are at it, is there any how-to about compiling a VC program > under Mingw or cygwin? (Trying to find a easy way out). VC <-> Mingw is typically easy to trivial; the only gotchas are that VC code tends to expect MSVCRT runtime, which has slight differences from the CRTDLL runtime (and is an issue only if you're using the CRTDLL based Mingw GCC). VC <-> Cygwin is a completely different story of course. The runtimes are radically different, and potentially need large effort to do the port. For those who don't use VC specific constructs, and avoid the nonportable VC runtime-specific features, it should be reasonable. Regards, Mumit From bobak@ekf.deltav.hu Tue Jan 4 00:23:00 2000 From: bobak@ekf.deltav.hu (Bobák Csaba) Date: Tue, 04 Jan 2000 00:23:00 -0000 Subject: Newbie Question Message-ID: <3871AD5E.181F619E@ekf.deltav.hu> Hi all, I have to tell I'm new to xfree development (and not so experienced in Unix development), and I'll have to port a Linux graphics processing software (Cantata) to Win9x. So I started to read the CygWin and CygWin-XFree mail archives. I found that there are no working XServers yet, and I was sad about my lost-before-started project. Later I read that John Fortin has made a working xclock - that's what I wanted to do next. Now, I'm so confused about these two thingies: - no XServer, and - working xclock Anyone (preferably John), please write me about how to run that xclock (and any x clients) without an xserver. Thatks for your *quick* answer. B.Csaba From ssiddiqi@inspirepharm.com Tue Jan 4 03:55:00 2000 From: ssiddiqi@inspirepharm.com (Suhaib Siddiqi) Date: Tue, 04 Jan 2000 03:55:00 -0000 Subject: XGGI Update References: <200001040446.KAA03766@mypage.vsnl.com> Message-ID: > Mumit Khan wrote: > > XGGI should build under Mingw however, and if not, I > can provide a hand > > there. > > > > This will be great for the DirectX based server also. > Currently the > server is functional with VC-6 and should be portable to Mingw32. > > When we are at it, is there any how-to about compiling a > VC program > under Mingw or cygwin? (Trying to find a easy way out). I offered you a few times to e-mail me patches which I would NO doubt release ackowledging your authorship. The e-mals went answered. In my opinion, it would not be good to split the cygwin-xfree project to several sites and some cygwin-xfree mailing list start their own sites... of course it is users choice. It is a GPLed project and our aim is to provide Win32 users a free first-class X-server. Since I have X code setup for Cygwin, MSVC and working on MingW32 I could look at your code and help you port to other compilers. Regards Suhaib > > -- KD > From ssiddiqi@inspirepharm.com Tue Jan 4 03:57:00 2000 From: ssiddiqi@inspirepharm.com (Suhaib Siddiqi) Date: Tue, 04 Jan 2000 03:57:00 -0000 Subject: XGGI Update References: <200001040450.KAA17857@mypage.vsnl.com> Message-ID: > > "Suhaib M. Siddiqi" wrote: > > xdm, and a few others cannot be build using MingW32... > including xedit and > > glx from xfree86 4.0. Cygwin is best suited for that. > > I do not think so. Since xdm (client portion which was > required by the X > Servers) works with VC6, Sorry for not adding xdm security.... >it should work with mingw32 also. Or am I > missing something here? first thing is to get *.cf files right for MingW32. xdm or other clients (except xterm) can be compiled with MingW32 after libs and others code is patched properly. > > >> Got any perf numbers yet? Just being greedy, sorry ;-) > > How do we get perf numbers for a X-Server? use xperf.exe. Suhaib > > -- KD > From ssiddiqi@inspirepharm.com Tue Jan 4 04:01:00 2000 From: ssiddiqi@inspirepharm.com (Suhaib Siddiqi) Date: Tue, 04 Jan 2000 04:01:00 -0000 Subject: XGGI Update References: <200001040642.AAA17448@hp2.xraylith.wisc.edu> Message-ID: > > kdmurthy@vsnl.com writes: > > > > This will be great for the DirectX based server also. > Currently the > > server is functional with VC-6 and should be portable > to Mingw32. > > > > When we are at it, is there any how-to about compiling > a VC program > > under Mingw or cygwin? (Trying to find a easy way out). > > VC <-> Mingw is typically easy to trivial; the only > gotchas are that > VC code tends to expect MSVCRT runtime, which has slight > differences > from the CRTDLL runtime (and is an issue only if you're using the > CRTDLL based Mingw GCC). > > VC <-> Cygwin is a completely different story of course. > The runtimes > are radically different, and potentially need large > effort to do the > port. That is why I mentioned in my previous e-mails, that patching X code for MingW32 is a lot more work then patching it for Cygwin. Regardless I am working on it and would release it whenever completed. Regards Suhaib >For those who don't use VC specific constructs, and > avoid the > nonportable VC runtime-specific features, it should be > reasonable. > > Regards, > Mumit > From ssiddiqi@inspirepharm.com Tue Jan 4 04:05:00 2000 From: ssiddiqi@inspirepharm.com (Suhaib Siddiqi) Date: Tue, 04 Jan 2000 04:05:00 -0000 Subject: Newbie Question References: <3871AD5E.181F619E@ekf.deltav.hu> Message-ID: *> Hi all, > I have to tell I'm new to xfree development (and not > so experienced > in Unix development), > and I'll have to port a Linux graphics processing > software (Cantata) to > Win9x. So I started to read the CygWin and CygWin-XFree > mail archives. I > found that there are no working XServers yet, and I was > sad about my > lost-before-started project. Later I read that John > Fortin has made a > working xclock - that's what I wanted to do next. Now, > I'm so confused > about these two thingies: > - no XServer, and cygwin-xfree is a development project. The X-server are being developed. You can still use X11R6.x libs/development tools from cygwin-xfree with Cygwin and port your "Cantata" to Windows. You would need a commercial Xserver to display your ported application till our X-servers are functional. > - working xclock Yes, that is right. John had been working on XGGI since almost a year. He now has an x-server which is not yet ready to be released for public. Regards Suhaib > Anyone (preferably John), please write me about how to > run that xclock > (and any x clients) without an xserver. > Thatks for your *quick* answer. > > B.Csaba > From fortinj@ibm.net Tue Jan 4 06:55:00 2000 From: fortinj@ibm.net (John Fortin) Date: Tue, 04 Jan 2000 06:55:00 -0000 Subject: XGGI Update References: Message-ID: <387209E0.6CA5BF1D@ibm.net> Mike MacDonald wrote: > >More good news... I have gotten xterm to (mostly) work. Some keys are > >not mapped properly ( backspace for one) > > Under most unices (including cygwin) I have to put an stty erase command in > my .profile to remap backspace anyway.. Works now... had a bug in the keyboard handler. Even ctrl-alt-backspace works to kill the server. I'm going to start the mouse handling tonight. Back to the books :) John From fortinj@ibm.net Tue Jan 4 07:46:00 2000 From: fortinj@ibm.net (John Fortin) Date: Tue, 04 Jan 2000 07:46:00 -0000 Subject: XGGI Update References: Message-ID: <387215F4.FA52FCE9@ibm.net> Mike MacDonald wrote: > Sorry.. I was on the lines of termcap.. I can't wait to get your server up > and running.. I'm kinda obsolete now, but thats a good thing :) > No, your not!! This is a seperate server from the xfree86 server you have been working on. I still have to go through another subsystem (libggi) in order to run. This has overhead attached and probably not much hope of acceleration any time soon. I believe a direct port without libggi would be faster and more efficient (and a GOOD idea to boot). So please, keep on trucking on your port. John From kdmurthy@vsnl.com Tue Jan 4 08:28:00 2000 From: kdmurthy@vsnl.com (kdmurthy@vsnl.com) Date: Tue, 04 Jan 2000 08:28:00 -0000 Subject: XGGI Update Message-ID: <200001041626.VAA09359@mypage.vsnl.com> Suhaib Siddiqi wrote: > I offered you a few times to e-mail me patches which I would NO > doubt release ackowledging your authorship. The e-mals went > answered. Unfortunately I have a very demanding day job, which allows me to work only during the weekends :-(. The code is not yet in a state where I can *display* to others. Once I clean it up, I will send the patches. Please note that having a working software doesn't mean that it is still releasable. > In my opinion, it would not be good to split the cygwin-xfree > project to several sites and some cygwin-xfree mailing list start > their own sites... of course it is users choice. It is a GPLed > project and > our aim is to provide Win32 users a free first-class X-server. > At no point in time I mentioned about splitting cygwin-xfree. I realize the fantastic work done by you, mike and fortin till now and sorry if you felt like that. However, I am not sure the methodology cygwin-xfree is using is the right approach (basing on xfree86, using GGI layer over and above directx and not concentrating on GDI based X-Server). That does not prevent me from contributing to the project. > Since I have X code setup for Cygwin, MSVC and working on MingW32 > I could look at your code and help you port to other compilers. > Please give me some time. How can I learn about cygwin/mingw if I take your help for porting without atleast giving it a try myself ;-) Regards KD From fortinj@ibm.net Tue Jan 4 08:51:00 2000 From: fortinj@ibm.net (John Fortin) Date: Tue, 04 Jan 2000 08:51:00 -0000 Subject: XGGI Update References: <200001041626.VAA09359@mypage.vsnl.com> Message-ID: <38722513.D1B9B9BA@ibm.net> > > At no point in time I mentioned about splitting cygwin-xfree. I realize the fantastic work done by you, mike and fortin till now and sorry if you felt like that. However, I am not sure the methodology cygwin-xfree is using is the right approach (basing on xfree86, using GGI layer over and above directx and not concentrating on GDI based X-Server). That does not prevent me from contributing to the project. > PLEASE, PLEASE, PLEASE, not another flame war on the various merits, right or wrongness, GDI vs DirectX, approaches. EVERY approach has pros and cons associated with it. The GOAL is to have a free X-Server available. The more types, the better.... But lets get at least one working first... > > > Since I have X code setup for Cygwin, MSVC and working on MingW32 > > I could look at your code and help you port to other compilers. > > > Please give me some time. How can I learn about cygwin/mingw if I take your help for porting without atleast giving it a try myself ;-) > But again, why reinvent the wheel if it is not needed. Suhaib has a great deal of experience with the various compilers and the source. So to me, if I wanted to get something done efficiently, I would use the available resources (namely Suhaib). From kd@blr.vsnl.net.in Tue Jan 4 09:33:00 2000 From: kd@blr.vsnl.net.in (Dakshinamurthy Karra) Date: Tue, 04 Jan 2000 09:33:00 -0000 Subject: Fwd: RE: XGGI Update Message-ID: <00010423044300.00430@indica> ---------- Forwarded Message ---------- Subject: RE: XGGI Update Date: Tue, 4 Jan 2000 11:36:09 -0500 From: "Suhaib Siddiqi" Hi KD, Can you please also forward a copy of this message to cygwin-xfree list? I am putting a new Firewall and took down some SMTP security features. Unfortunately during that time span ORBS got my SMTP server in their database... horrible, now I cannot post to cygwin-xfree list. > > Suhaib Siddiqi wrote: > > I offered you a few times to e-mail me patches which I would NO > > doubt release ackowledging your authorship. The e-mals went > > answered. > Unfortunately I have a very demanding day job, which > allows me to work only during the weekends :-(. I understand. I do not mean to be critical. Your code would not be released to public till you would give OK. It would only help us to look at your inventions and add improvements. >The code > is not yet in a state where I can *display* to others. > Once I clean it up, I will send the patches. Please note > that having a working software doesn't mean that it is > still releasable. That is understood. Cygwin-xfree is a development project and we expect users to help fix bugs and contribute improvemnets. > > > In my opinion, it would not be good to split the cygwin-xfree > > project to several sites and some cygwin-xfree mailing > list start > > their own sites... of course it is users choice. It is a GPLed > > project and > > our aim is to provide Win32 users a free first-class X-server. > > > At no point in time I mentioned about splitting > cygwin-xfree. I realize the fantastic work done by you, > mike and fortin till now and sorry if you felt like that. Wrong wordings, bad language, I take it back. sorry. > However, I am not sure the methodology cygwin-xfree is > using is the right approach (basing on xfree86, using GGI > layer over and above directx and not concentrating on GDI > based X-Server). That does not prevent me from > contributing to the project. Everyone is welcome to contribute his/her ideas. It was initial idea to base project on xfree86 code or at least most of the code on xfree86. This got at least project started, and I am sure with the help of other developers, like you, we would have a good X-server, either xfree86 based or not. > > > Since I have X code setup for Cygwin, MSVC and working > on MingW32 > > I could look at your code and help you port to other compilers. > > > Please give me some time. How can I learn about > cygwin/mingw if I take your help for porting without > atleast giving it a try myself ;-) > I understand Regards Suhaib > > Regards > KD > ------------------------------------------------------- From mmacdonald@tsi.gte.com Tue Jan 4 09:38:00 2000 From: mmacdonald@tsi.gte.com (Mike MacDonald) Date: Tue, 04 Jan 2000 09:38:00 -0000 Subject: FW: libz.dll Message-ID: -----Original Message----- From: Mike MacDonald Sent: Tuesday, January 04, 2000 12:37 PM To: 'Suhaib Siddiqi' Subject: RE: libz.dll Its used when you type make World when it gets to the fonts.. The error it gives is tremendously irritating because it creates a windows modal box and won't continue until you click ok.. Thing is that there are alot of statements that generate the error all in a row, so you can be stuck clicking ok for hours.. -----Original Message----- From: Suhaib Siddiqi [ mailto:ssiddiqi@inspirepharm.com ] Sent: Tuesday, January 04, 2000 12:18 PM To: Mike MacDonald Subject: RE: libz.dll libz.dll is used by almost nothing. It will get installed when you type make install. Suhaib > -----Original Message----- > From: Mike MacDonald [ mailto:mmacdonald@tsi.gte.com ] > Sent: Tuesday, January 04, 2000 12:19 PM > To: 'Suhaib Siddiqi' > Subject: RE: libz.dll > > > I found it.. Its compiling the libz.dll, but not copying > it to someplace in > the path. I just need to figure out how to get it in the path.. > > -----Original Message----- > From: Suhaib Siddiqi [ mailto:ssiddiqi@inspirepharm.com ] > Sent: Tuesday, January 04, 2000 12:00 PM > To: Mike MacDonald > Subject: RE: libz.dll > > > > > libx.dll code in in libs directory and should compile. > Can you cut and paste the error messages you receive. I remember > fixing the libz.dll problems a long time ago. I may have > missed it. > > Suhaib > > > -----Original Message----- > > From: Mike MacDonald [ mailto:mmacdonald@tsi.gte.com ] > > Sent: Tuesday, January 04, 2000 12:03 PM > > To: 'Suhaib Siddiqi' > > Subject: libz.dll > > > > > > When I make world, it gets pissy looking for a libz.dll.. > > I figured I'd > > run it by you before I started trying to fix it.. > > > From mmacdonald@tsi.gte.com Tue Jan 4 09:50:00 2000 From: mmacdonald@tsi.gte.com (Mike MacDonald) Date: Tue, 04 Jan 2000 09:50:00 -0000 Subject: FW: libz.dll Message-ID: -----Original Message----- From: Mike MacDonald Sent: Tuesday, January 04, 2000 12:49 PM To: 'Suhaib Siddiqi' Subject: RE: libz.dll Yeah, 3.9.16 with the 3.9.15 patch.. The new *.cf files would be killer! -----Original Message----- From: Suhaib Siddiqi [ mailto:ssiddiqi@inspirepharm.com ] Sent: Tuesday, January 04, 2000 12:35 PM To: Mike MacDonald Subject: RE: libz.dll Which version are you compiling? 3.9.16? I can send you new *.cf files which would copy all the *.dll to export/bin Suhaib > -----Original Message----- > From: Mike MacDonald [ mailto:mmacdonald@tsi.gte.com ] > Sent: Tuesday, January 04, 2000 12:24 PM > To: 'Suhaib Siddiqi' > Subject: RE: libz.dll > > > It really should copy to ../../exports/bin though, and have the > xc/exports/bin directory added to the path when making the fonts.. > > -----Original Message----- > From: Suhaib Siddiqi [ mailto:ssiddiqi@inspirepharm.com ] > Sent: Tuesday, January 04, 2000 12:00 PM > To: Mike MacDonald > Subject: RE: libz.dll > > > > > libx.dll code in in libs directory and should compile. > Can you cut and paste the error messages you receive. I remember > fixing the libz.dll problems a long time ago. I may have > missed it. > > Suhaib > > > -----Original Message----- > > From: Mike MacDonald [ mailto:mmacdonald@tsi.gte.com ] > > Sent: Tuesday, January 04, 2000 12:03 PM > > To: 'Suhaib Siddiqi' > > Subject: libz.dll > > > > > > When I make world, it gets pissy looking for a libz.dll.. > > I figured I'd > > run it by you before I started trying to fix it.. > > > From fortinj@ibm.net Tue Jan 4 10:00:00 2000 From: fortinj@ibm.net (John Fortin) Date: Tue, 04 Jan 2000 10:00:00 -0000 Subject: [Fwd: XGGI Update] Message-ID: <38723564.AA29560D@ibm.net> From kd@blr.vsnl.net.in Tue Jan 4 10:31:00 2000 From: kd@blr.vsnl.net.in (Dakshinamurthy Karra) Date: Tue, 04 Jan 2000 10:31:00 -0000 Subject: XGGI Update References: <200001041626.VAA09359@mypage.vsnl.com> <38722513.D1B9B9BA@ibm.net> Message-ID: <00010500022401.00430@indica> On Tue, 04 Jan 2000, John Fortin wrote: > PLEASE, PLEASE, PLEASE, not another flame war on the various merits, right or wrongness, GDI vs DirectX, approaches. EVERY approach has pros and cons associated with it. The GOAL is to have a free X-Server available. The more types, the better.... But lets get at least one working first... Got the message. Desisting from making anymore comments ;-) > But again, why reinvent the wheel if it is not needed. Suhaib has a great deal of experience with the various compilers and the source. So to me, if I wanted to get something done efficiently, I would use the available resources (namely Suhaib). Here I differ. More the merrier applies to software development. We need more people who understand the system and work on it. Taking help from Suhaib without even attempting is bad. Let us kill this thread here and get back to our semi working X Servers ;-) -- KD From ssiddiqi@inspire.InspirePharm.Com Tue Jan 4 18:13:00 2000 From: ssiddiqi@inspire.InspirePharm.Com (Suhaib M. Siddiqi) Date: Tue, 04 Jan 2000 18:13:00 -0000 Subject: test Message-ID: <200001050213.VAA24167@inspire.InspirePharm.Com> orbs test From ssiddiqi@inspirepharm.com Wed Jan 5 04:31:00 2000 From: ssiddiqi@inspirepharm.com (Suhaib Siddiqi) Date: Wed, 05 Jan 2000 04:31:00 -0000 Subject: FW: [Fwd: xperf on XGGI (in case you are interested ...)] Message-ID: John, It looks not bad for an non-xaa server. Did you run all the x11perf (x11perf -display 127.0.0.1:0.0 -all)? On my 550 MHz PIII machine it takes almost an hour to complete all the test. I will put the bench-mark x11perf tests file at cygwin-xfree Home Page. The file is almost 250 KB big. I do not want to dump all the list users with it. XGGI gives same x11perf tests at Linux, which is almost 1/10 th of an xaa multihead optimized x-server. The low perf is because Xggi does not utilize xaa. Suhaib Here are just a few x11perf test values to give you an idea. Sync time adjustment is 0.6801 msecs. 10000000 reps @ 0.0005 msec (1980000.0/sec): Dot 10000000 reps @ 0.0007 msec (1430000.0/sec): Dot 10000000 reps @ 0.0007 msec (1340000.0/sec): Dot 10000000 reps @ 0.0006 msec (1580000.0/sec): Dot 10000000 reps @ 0.0014 msec (719000.0/sec): Dot 50000000 trep @ 0.0008 msec (1260000.0/sec): Dot 1000000 reps @ 0.0050 msec (198000.0/sec): 1x1 rectangle 1000000 reps @ 0.0051 msec (194000.0/sec): 1x1 rectangle 1000000 reps @ 0.0034 msec (294000.0/sec): 1x1 rectangle 1000000 reps @ 0.0033 msec (307000.0/sec): 1x1 rectangle 1000000 reps @ 0.0031 msec (321000.0/sec): 1x1 rectangle 5000000 trep @ 0.0040 msec (250000.0/sec): 1x1 rectangle 2000000 reps @ 0.0040 msec (251000.0/sec): 10x10 rectangle 2000000 reps @ 0.0040 msec (251000.0/sec): 10x10 rectangle 2000000 reps @ 0.0041 msec (245000.0/sec): 10x10 rectangle 2000000 reps @ 0.0040 msec (252000.0/sec): 10x10 rectangle 2000000 reps @ 0.0041 msec (241000.0/sec): 10x10 rectangle 10000000 trep @ 0.0040 msec (248000.0/sec): 10x10 rectangle 324000 reps @ 0.0163 msec ( 61400.0/sec): 100x100 rectangle 324000 reps @ 0.0167 msec ( 59800.0/sec): 100x100 rectangle 324000 reps @ 0.0163 msec ( 61400.0/sec): 100x100 rectangle 324000 reps @ 0.0163 msec ( 61400.0/sec): 100x100 rectangle 324000 reps @ 0.0182 msec ( 55000.0/sec): 100x100 rectangle 1620000 trep @ 0.0168 msec ( 59700.0/sec): 100x100 rectangle 20000 reps @ 0.4461 msec ( 2240.0/sec): 500x500 rectangle 20000 reps @ 0.4436 msec ( 2250.0/sec): 500x500 rectangle 20000 reps @ 0.4441 msec ( 2250.0/sec): 500x500 rectangle 20000 reps @ 0.4451 msec ( 2250.0/sec): 500x500 rectangle 20000 reps @ 0.4461 msec ( 2240.0/sec): 500x500 rectangle 100000 trep @ 0.4450 msec ( 2250.0/sec): 500x500 rectangle 1000000 reps @ 0.0051 msec (195000.0/sec): 1x1 stippled rectangle (8x8 stipple ) 1000000 reps @ 0.0050 msec (198000.0/sec): 1x1 stippled rectangle (8x8 stipple ) 1000000 reps @ 0.0050 msec (200000.0/sec): 1x1 stippled rectangle (8x8 stipple ) 1000000 reps @ 0.0030 msec (331000.0/sec): 1x1 stippled rectangle (8x8 stipple ) 1000000 reps @ 0.0029 msec (341000.0/sec): 1x1 stippled rectangle (8x8 stipple ) 5000000 trep @ 0.0042 msec (237000.0/sec): 1x1 stippled rectangle (8x8 stipple ) > Sigh, blocked again :( > > John Fortin wrote: > > > > Not quite sure how to interpret this... > > > > John > > > > x11perf - X11 performance program, version 1.5 > > The GGI Project server version 3330 on localhost:0.0 > > from home > > Tue Jan 04 23:35:32 2000 > > > > Sync time adjustment is 36.6857 msecs. > > > > 50000 reps @ 0.1157 msec ( 8650.0/sec): 10-pixel ellipse > > 50000 reps @ 0.1453 msec ( 6880.0/sec): 10-pixel ellipse > > 50000 reps @ 0.1333 msec ( 7500.0/sec): 10-pixel ellipse > > 50000 reps @ 0.1761 msec ( 5680.0/sec): 10-pixel ellipse > > 50000 reps @ 0.1201 msec ( 8330.0/sec): 10-pixel ellipse > > 250000 trep @ 0.1381 msec ( 7240.0/sec): 10-pixel ellipse > > > > 21000 reps @ 0.2549 msec ( 3920.0/sec): 100-pixel ellipse > > 21000 reps @ 0.2935 msec ( 3410.0/sec): 100-pixel ellipse > > 21000 reps @ 0.3516 msec ( 2840.0/sec): 100-pixel ellipse > > 21000 reps @ 0.3749 msec ( 2670.0/sec): 100-pixel ellipse > > 21000 reps @ 0.2963 msec ( 3370.0/sec): 100-pixel ellipse > > 105000 trep @ 0.3143 msec ( 3180.0/sec): 100-pixel ellipse > > > > 20000 reps @ 0.5637 msec ( 1770.0/sec): 500-pixel ellipse > > 20000 reps @ 0.6412 msec ( 1560.0/sec): 500-pixel ellipse > > 20000 reps @ 0.5557 msec ( 1800.0/sec): 500-pixel ellipse > > 20000 reps @ 0.5722 msec ( 1750.0/sec): 500-pixel ellipse > > 20000 reps @ 0.6272 msec ( 1590.0/sec): 500-pixel ellipse > > 100000 trep @ 0.5920 msec ( 1690.0/sec): 500-pixel ellipse > > > > 15000 reps @ 0.4222 msec ( 2370.0/sec): 100-pixel > dashed ellipse > > 15000 reps @ 0.3929 msec ( 2550.0/sec): 100-pixel > dashed ellipse > > 15000 reps @ 0.4149 msec ( 2410.0/sec): 100-pixel > dashed ellipse > > 15000 reps @ 0.4262 msec ( 2350.0/sec): 100-pixel > dashed ellipse > > 15000 reps @ 0.3856 msec ( 2590.0/sec): 100-pixel > dashed ellipse > > 75000 trep @ 0.4084 msec ( 2450.0/sec): 100-pixel > dashed ellipse > > > > 10000 reps @ 0.5013 msec ( 1990.0/sec): 100-pixel > double-dashed > > ellipse > > 10000 reps @ 0.4463 msec ( 2240.0/sec): 100-pixel > double-dashed > > ellipse > > 10000 reps @ 0.5013 msec ( 1990.0/sec): 100-pixel > double-dashed > > ellipse > > 10000 reps @ 0.4243 msec ( 2360.0/sec): 100-pixel > double-dashed > > ellipse > > 10000 reps @ 0.4903 msec ( 2040.0/sec): 100-pixel > double-dashed > > ellipse > > 50000 trep @ 0.4727 msec ( 2120.0/sec): 100-pixel > double-dashed > > ellipse > > > > 40000 reps @ 0.1503 msec ( 6650.0/sec): 10-pixel > wide ellipse > > 40000 reps @ 0.1748 msec ( 5720.0/sec): 10-pixel > wide ellipse > > 40000 reps @ 0.2078 msec ( 4810.0/sec): 10-pixel > wide ellipse > > 40000 reps @ 0.1886 msec ( 5300.0/sec): 10-pixel > wide ellipse > > 40000 reps @ 0.2118 msec ( 4720.0/sec): 10-pixel > wide ellipse > > 200000 trep @ 0.1867 msec ( 5360.0/sec): 10-pixel > wide ellipse > > > > 12500 reps @ 0.4139 msec ( 2420.0/sec): 100-pixel > wide ellipse > > 12500 reps @ 0.4635 msec ( 2160.0/sec): 100-pixel > wide ellipse > > 12500 reps @ 0.4491 msec ( 2230.0/sec): 100-pixel > wide ellipse > > 12500 reps @ 0.4499 msec ( 2220.0/sec): 100-pixel > wide ellipse > > 12500 reps @ 0.4499 msec ( 2220.0/sec): 100-pixel > wide ellipse > > 62500 trep @ 0.4452 msec ( 2250.0/sec): 100-pixel > wide ellipse > > > > 4000 reps @ 1.6258 msec ( 615.0/sec): 500-pixel > wide ellipse > > 4000 reps @ 1.6108 msec ( 621.0/sec): 500-pixel > wide ellipse > > 4000 reps @ 1.5833 msec ( 632.0/sec): 500-pixel > wide ellipse > > 4000 reps @ 1.4608 msec ( 685.0/sec): 500-pixel > wide ellipse > > 4000 reps @ 1.4483 msec ( 690.0/sec): 500-pixel > wide ellipse > > 20000 trep @ 1.5458 msec ( 647.0/sec): 500-pixel > wide ellipse > > > > 1750 reps @ 2.9619 msec ( 338.0/sec): 100-pixel > wide dashed > > ellipse > > 1750 reps @ 2.8648 msec ( 349.0/sec): 100-pixel > wide dashed > > ellipse > > 1750 reps @ 2.8076 msec ( 356.0/sec): 100-pixel > wide dashed > > ellipse > > 1750 reps @ 2.9276 msec ( 342.0/sec): 100-pixel > wide dashed > > ellipse > > 1750 reps @ 2.7105 msec ( 369.0/sec): 100-pixel > wide dashed > > ellipse > > 8750 trep @ 2.8545 msec ( 350.0/sec): 100-pixel > wide dashed > > ellipse > > > > 1750 reps @ 2.8362 msec ( 353.0/sec): 100-pixel wide > > double-dashed ellipse > > 1750 reps @ 3.2419 msec ( 308.0/sec): 100-pixel wide > > double-dashed ellipse > > 1750 reps @ 3.2076 msec ( 312.0/sec): 100-pixel wide > > double-dashed ellipse > > 1750 reps @ 3.0248 msec ( 331.0/sec): 100-pixel wide > > double-dashed ellipse > > 1750 reps @ 3.0819 msec ( 324.0/sec): 100-pixel wide > > double-dashed ellipse > > 8750 trep @ 3.0785 msec ( 325.0/sec): 100-pixel wide > > double-dashed ellipse > > > > 27000 reps @ 0.2042 msec ( 4900.0/sec): 10-pixel > partial ellipse > > 27000 reps @ 0.1631 msec ( 6130.0/sec): 10-pixel > partial ellipse > > 27000 reps @ 0.1190 msec ( 8400.0/sec): 10-pixel > partial ellipse > > 27000 reps @ 0.1349 msec ( 7410.0/sec): 10-pixel > partial ellipse > > 27000 reps @ 0.1490 msec ( 6710.0/sec): 10-pixel > partial ellipse > > 135000 trep @ 0.1540 msec ( 6490.0/sec): 10-pixel > partial ellipse > > > > 21600 reps @ 0.2654 msec ( 3770.0/sec): 100-pixel > partial ellipse > > 21600 reps @ 0.2802 msec ( 3570.0/sec): 100-pixel > partial ellipse > > 21600 reps @ 0.2904 msec ( 3440.0/sec): 100-pixel > partial ellipse > > 21600 reps @ 0.2705 msec ( 3700.0/sec): 100-pixel > partial ellipse > > 21600 reps @ 0.1812 msec ( 5520.0/sec): 100-pixel > partial ellipse > > 108000 trep @ 0.2576 msec ( 3880.0/sec): 100-pixel > partial ellipse > > > > 10800 reps @ 0.6429 msec ( 1560.0/sec): 10-pixel > wide partial > > ellipse > > 10800 reps @ 0.6216 msec ( 1610.0/sec): 10-pixel > wide partial > > ellipse > > 10800 reps @ 0.6420 msec ( 1560.0/sec): 10-pixel > wide partial > > ellipse > > 10800 reps @ 0.6068 msec ( 1650.0/sec): 10-pixel > wide partial > > ellipse > > 10800 reps @ 0.6327 msec ( 1580.0/sec): 10-pixel > wide partial > > ellipse > > 54000 trep @ 0.6292 msec ( 1590.0/sec): 10-pixel > wide partial > > ellipse > > > > 3600 reps @ 1.5176 msec ( 659.0/sec): 100-pixel > wide partial > > ellipse > > 3600 reps @ 1.5898 msec ( 629.0/sec): 100-pixel > wide partial > > ellipse > > 3600 reps @ 1.6231 msec ( 616.0/sec): 100-pixel > wide partial > > ellipse > > 3600 reps @ 1.4398 msec ( 695.0/sec): 100-pixel > wide partial > > ellipse > > 3600 reps @ 1.4704 msec ( 680.0/sec): 100-pixel > wide partial > > ellipse > > 18000 trep @ 1.5281 msec ( 654.0/sec): 100-pixel > wide partial > > ellipse > > > > 40000 reps @ 0.2066 msec ( 4840.0/sec): 10-pixel > filled ellipse > > 40000 reps @ 0.2078 msec ( 4810.0/sec): 10-pixel > filled ellipse > > 40000 reps @ 0.1651 msec ( 6060.0/sec): 10-pixel > filled ellipse > > 40000 reps @ 0.1173 msec ( 8520.0/sec): 10-pixel > filled ellipse > > 40000 reps @ 0.1556 msec ( 6430.0/sec): 10-pixel > filled ellipse > > 200000 trep @ 0.1705 msec ( 5870.0/sec): 10-pixel > filled ellipse > > > > 15000 reps @ 0.3962 msec ( 2520.0/sec): 100-pixel > filled ellipse > > 15000 reps @ 0.3676 msec ( 2720.0/sec): 100-pixel > filled ellipse > > 15000 reps @ 0.4042 msec ( 2470.0/sec): 100-pixel > filled ellipse > > 15000 reps @ 0.3749 msec ( 2670.0/sec): 100-pixel > filled ellipse > > 15000 reps @ 0.3529 msec ( 2830.0/sec): 100-pixel > filled ellipse > > 75000 trep @ 0.3792 msec ( 2640.0/sec): 100-pixel > filled ellipse > > > > 3000 reps @ 1.9444 msec ( 514.0/sec): 500-pixel > filled ellipse > > 3000 reps @ 2.0378 msec ( 491.0/sec): 500-pixel > filled ellipse > > 3000 reps @ 1.8911 msec ( 529.0/sec): 500-pixel > filled ellipse > > 3000 reps @ 1.9111 msec ( 523.0/sec): 500-pixel > filled ellipse > > 3000 reps @ 1.9478 msec ( 513.0/sec): 500-pixel > filled ellipse > > 15000 trep @ 1.9464 msec ( 514.0/sec): 500-pixel > filled ellipse > > > > 13500 reps @ 0.2410 msec ( 4150.0/sec): 10-pixel > fill chord partial > > ellipse > > 13500 reps @ 0.2491 msec ( 4010.0/sec): 10-pixel > fill chord partial > > ellipse > > 13500 reps @ 0.3269 msec ( 3060.0/sec): 10-pixel > fill chord partial > > ellipse > > 13500 reps @ 0.2899 msec ( 3450.0/sec): 10-pixel > fill chord partial > > ellipse > > 13500 reps @ 0.3388 msec ( 2950.0/sec): 10-pixel > fill chord partial > > ellipse > > 67500 trep @ 0.2891 msec ( 3460.0/sec): 10-pixel > fill chord partial > > ellipse > > > > 18000 reps @ 0.3302 msec ( 3030.0/sec): 100-pixel > fill chord > > partial ellipse > > 18000 reps @ 0.3335 msec ( 3000.0/sec): 100-pixel > fill chord > > partial ellipse > > 18000 reps @ 0.3219 msec ( 3110.0/sec): 100-pixel > fill chord > > partial ellipse > > 18000 reps @ 0.3119 msec ( 3210.0/sec): 100-pixel > fill chord > > partial ellipse > > 18000 reps @ 0.2880 msec ( 3470.0/sec): 100-pixel > fill chord > > partial ellipse > > 90000 trep @ 0.3171 msec ( 3150.0/sec): 100-pixel > fill chord > > partial ellipse > > > > 21600 reps @ 0.3566 msec ( 2800.0/sec): 10-pixel > fill slice partial > > ellipse > > 21600 reps @ 0.4002 msec ( 2500.0/sec): 10-pixel > fill slice partial > > ellipse > > 21600 reps @ 0.2071 msec ( 4830.0/sec): 10-pixel > fill slice partial > > ellipse > > 21600 reps @ 0.2423 msec ( 4130.0/sec): 10-pixel > fill slice partial > > ellipse > > 21600 reps @ 0.2627 msec ( 3810.0/sec): 10-pixel > fill slice partial > > ellipse > > 108000 trep @ 0.2938 msec ( 3400.0/sec): 10-pixel > fill slice partial > > ellipse > > > > 14400 reps @ 0.2988 msec ( 3350.0/sec): 100-pixel > fill slice > > partial ellipse > > 14400 reps @ 0.3447 msec ( 2900.0/sec): 100-pixel > fill slice > > partial ellipse > > 14400 reps @ 0.3481 msec ( 2870.0/sec): 100-pixel > fill slice > > partial ellipse > > 14400 reps @ 0.3252 msec ( 3070.0/sec): 100-pixel > fill slice > > partial ellipse > > 14400 reps @ 0.3336 msec ( 3000.0/sec): 100-pixel > fill slice > > partial ellipse > > 72000 trep @ 0.3301 msec ( 3030.0/sec): 100-pixel > fill slice > > partial ellipse > > > > 20000 reps @ 0.3687 msec ( 2710.0/sec): Scroll 10x10 pixels > > 20000 reps @ 0.3247 msec ( 3080.0/sec): Scroll 10x10 pixels > > 20000 reps @ 0.3002 msec ( 3330.0/sec): Scroll 10x10 pixels > > 20000 reps @ 0.3717 msec ( 2690.0/sec): Scroll 10x10 pixels > > 20000 reps @ 0.4242 msec ( 2360.0/sec): Scroll 10x10 pixels > > 100000 trep @ 0.3579 msec ( 2790.0/sec): Scroll 10x10 pixels > > > > 5000 reps @ 1.3007 msec ( 769.0/sec): Scroll > 100x100 pixels > > 5000 reps @ 1.1667 msec ( 857.0/sec): Scroll > 100x100 pixels > > 5000 reps @ 1.2567 msec ( 796.0/sec): Scroll > 100x100 pixels > > 5000 reps @ 1.1587 msec ( 863.0/sec): Scroll > 100x100 pixels > > 5000 reps @ 1.2007 msec ( 833.0/sec): Scroll > 100x100 pixels > > 25000 trep @ 1.2167 msec ( 822.0/sec): Scroll > 100x100 pixels > > > > 600 reps @ 8.5555 msec ( 117.0/sec): Scroll > 500x500 pixels > > 600 reps @ 8.7222 msec ( 115.0/sec): Scroll > 500x500 pixels > > 600 reps @ 9.5555 msec ( 105.0/sec): Scroll > 500x500 pixels > > 600 reps @ 8.1722 msec ( 122.0/sec): Scroll > 500x500 pixels > > 600 reps @ 8.4555 msec ( 118.0/sec): Scroll > 500x500 pixels > > 3000 trep @ 8.6922 msec ( 115.0/sec): Scroll > 500x500 pixels > From fortinj@ibm.net Wed Jan 5 05:33:00 2000 From: fortinj@ibm.net (John Fortin) Date: Wed, 05 Jan 2000 05:33:00 -0000 Subject: [Fwd: xperf on Exceed (in case you are interested ...)] References: Message-ID: <387348EE.22675FA5@ibm.net> > > We can also check these against Exceed and other commercial servers. I did it against Exceed also if you want to see them too. John. x11perf - X11 performance program, version 1.5 Hummingbird Communications Ltd. server version 6020 on localhost:0.0 from home Tue Jan 04 19:18:03 2000 Sync time adjustment is 4.4910 msecs. 300000 reps @ 0.0218 msec ( 45900.0/sec): 10-pixel ellipse 300000 reps @ 0.0211 msec ( 47500.0/sec): 10-pixel ellipse 300000 reps @ 0.0207 msec ( 48400.0/sec): 10-pixel ellipse 300000 reps @ 0.0207 msec ( 48300.0/sec): 10-pixel ellipse 300000 reps @ 0.0196 msec ( 51100.0/sec): 10-pixel ellipse 1500000 trep @ 0.0208 msec ( 48200.0/sec): 10-pixel ellipse 240000 reps @ 0.0226 msec ( 44200.0/sec): 100-pixel ellipse 240000 reps @ 0.0249 msec ( 40200.0/sec): 100-pixel ellipse 240000 reps @ 0.0247 msec ( 40500.0/sec): 100-pixel ellipse 240000 reps @ 0.0226 msec ( 44200.0/sec): 100-pixel ellipse 240000 reps @ 0.0176 msec ( 56800.0/sec): 100-pixel ellipse 1200000 trep @ 0.0225 msec ( 44400.0/sec): 100-pixel ellipse 60000 reps @ 0.0814 msec ( 12300.0/sec): 500-pixel ellipse 60000 reps @ 0.0823 msec ( 12200.0/sec): 500-pixel ellipse 60000 reps @ 0.0824 msec ( 12100.0/sec): 500-pixel ellipse 60000 reps @ 0.0814 msec ( 12300.0/sec): 500-pixel ellipse 60000 reps @ 0.0813 msec ( 12300.0/sec): 500-pixel ellipse 300000 trep @ 0.0818 msec ( 12200.0/sec): 500-pixel ellipse 175000 reps @ 0.0304 msec ( 32900.0/sec): 100-pixel dashed ellipse 175000 reps @ 0.0304 msec ( 32900.0/sec): 100-pixel dashed ellipse 175000 reps @ 0.0301 msec ( 33200.0/sec): 100-pixel dashed ellipse 175000 reps @ 0.0304 msec ( 32900.0/sec): 100-pixel dashed ellipse 175000 reps @ 0.0298 msec ( 33600.0/sec): 100-pixel dashed ellipse 875000 trep @ 0.0302 msec ( 33100.0/sec): 100-pixel dashed ellipse 175000 reps @ 0.0326 msec ( 30700.0/sec): 100-pixel double-dashed ellipse 175000 reps @ 0.0311 msec ( 32200.0/sec): 100-pixel double-dashed ellipse 175000 reps @ 0.0298 msec ( 33600.0/sec): 100-pixel double-dashed ellipse 175000 reps @ 0.0304 msec ( 32900.0/sec): 100-pixel double-dashed ellipse 175000 reps @ 0.0320 msec ( 31300.0/sec): 100-pixel double-dashed ellipse 875000 trep @ 0.0312 msec ( 32100.0/sec): 100-pixel double-dashed ellipse 400000 reps @ 0.0173 msec ( 57800.0/sec): 10-pixel wide ellipse 400000 reps @ 0.0148 msec ( 67500.0/sec): 10-pixel wide ellipse 400000 reps @ 0.0211 msec ( 47300.0/sec): 10-pixel wide ellipse 400000 reps @ 0.0266 msec ( 37600.0/sec): 10-pixel wide ellipse 400000 reps @ 0.0266 msec ( 37500.0/sec): 10-pixel wide ellipse 2000000 trep @ 0.0213 msec ( 47000.0/sec): 10-pixel wide ellipse 100000 reps @ 0.0511 msec ( 19600.0/sec): 100-pixel wide ellipse 100000 reps @ 0.0472 msec ( 21200.0/sec): 100-pixel wide ellipse 100000 reps @ 0.0473 msec ( 21200.0/sec): 100-pixel wide ellipse 100000 reps @ 0.0472 msec ( 21200.0/sec): 100-pixel wide ellipse 100000 reps @ 0.0494 msec ( 20300.0/sec): 100-pixel wide ellipse 500000 trep @ 0.0484 msec ( 20700.0/sec): 100-pixel wide ellipse 40000 reps @ 0.2306 msec ( 4340.0/sec): 500-pixel wide ellipse 40000 reps @ 0.2306 msec ( 4340.0/sec): 500-pixel wide ellipse 40000 reps @ 0.2321 msec ( 4310.0/sec): 500-pixel wide ellipse 40000 reps @ 0.2304 msec ( 4340.0/sec): 500-pixel wide ellipse 40000 reps @ 0.2306 msec ( 4340.0/sec): 500-pixel wide ellipse 200000 trep @ 0.2309 msec ( 4330.0/sec): 500-pixel wide ellipse 5000 reps @ 0.9991 msec ( 1000.0/sec): 100-pixel wide dashed ellipse 5000 reps @ 0.9651 msec ( 1040.0/sec): 100-pixel wide dashed ellipse 5000 reps @ 0.9771 msec ( 1020.0/sec): 100-pixel wide dashed ellipse 5000 reps @ 0.9771 msec ( 1020.0/sec): 100-pixel wide dashed ellipse 5000 reps @ 0.9651 msec ( 1040.0/sec): 100-pixel wide dashed ellipse 25000 trep @ 0.9767 msec ( 1020.0/sec): 100-pixel wide dashed ellipse 12500 reps @ 0.4260 msec ( 2350.0/sec): 100-pixel wide double-dashed ellipse 12500 reps @ 0.4388 msec ( 2280.0/sec): 100-pixel wide double-dashed ellipse 12500 reps @ 0.4212 msec ( 2370.0/sec): 100-pixel wide double-dashed ellipse 12500 reps @ 0.4300 msec ( 2330.0/sec): 100-pixel wide double-dashed ellipse 12500 reps @ 0.4388 msec ( 2280.0/sec): 100-pixel wide double-dashed ellipse 62500 trep @ 0.4310 msec ( 2320.0/sec): 100-pixel wide double-dashed ellipse 270000 reps @ 0.0203 msec ( 49200.0/sec): 10-pixel partial ellipse 270000 reps @ 0.0211 msec ( 47300.0/sec): 10-pixel partial ellipse 270000 reps @ 0.0230 msec ( 43500.0/sec): 10-pixel partial ellipse 270000 reps @ 0.0258 msec ( 38700.0/sec): 10-pixel partial ellipse 270000 reps @ 0.0602 msec ( 16600.0/sec): 10-pixel partial ellipse 1350000 trep @ 0.0301 msec ( 33200.0/sec): 10-pixel partial ellipse 324000 reps @ 0.0159 msec ( 62800.0/sec): 100-pixel partial ellipse 324000 reps @ 0.0156 msec ( 64100.0/sec): 100-pixel partial ellipse 324000 reps @ 0.0196 msec ( 50900.0/sec): 100-pixel partial ellipse 324000 reps @ 0.0141 msec ( 71100.0/sec): 100-pixel partial ellipse 324000 reps @ 0.0146 msec ( 68700.0/sec): 100-pixel partial ellipse 1620000 trep @ 0.0160 msec ( 62700.0/sec): 100-pixel partial ellipse 108000 reps @ 0.0310 msec ( 32300.0/sec): 10-pixel wide partial ellipse 108000 reps @ 0.0508 msec ( 19700.0/sec): 10-pixel wide partial ellipse 108000 reps @ 0.0326 msec ( 30700.0/sec): 10-pixel wide partial ellipse 108000 reps @ 0.0208 msec ( 48100.0/sec): 10-pixel wide partial ellipse 108000 reps @ 0.0203 msec ( 49200.0/sec): 10-pixel wide partial ellipse 540000 trep @ 0.0311 msec ( 32200.0/sec): 10-pixel wide partial ellipse 25200 reps @ 0.2070 msec ( 4830.0/sec): 100-pixel wide partial ellipse 25200 reps @ 0.2046 msec ( 4890.0/sec): 100-pixel wide partial ellipse 25200 reps @ 0.2046 msec ( 4890.0/sec): 100-pixel wide partial ellipse 25200 reps @ 0.2046 msec ( 4890.0/sec): 100-pixel wide partial ellipse 25200 reps @ 0.2026 msec ( 4940.0/sec): 100-pixel wide partial ellipse 126000 trep @ 0.2047 msec ( 4890.0/sec): 100-pixel wide partial ellipse 600000 reps @ 0.0101 msec ( 98600.0/sec): 10-pixel filled ellipse 600000 reps @ 0.0144 msec ( 69600.0/sec): 10-pixel filled ellipse 600000 reps @ 0.0168 msec ( 59400.0/sec): 10-pixel filled ellipse 600000 reps @ 0.0166 msec ( 60100.0/sec): 10-pixel filled ellipse 600000 reps @ 0.0166 msec ( 60400.0/sec): 10-pixel filled ellipse 3000000 trep @ 0.0149 msec ( 67100.0/sec): 10-pixel filled ellipse 200000 reps @ 0.0266 msec ( 37600.0/sec): 100-pixel filled ellipse 200000 reps @ 0.0274 msec ( 36500.0/sec): 100-pixel filled ellipse 200000 reps @ 0.0272 msec ( 36800.0/sec): 100-pixel filled ellipse 200000 reps @ 0.0272 msec ( 36800.0/sec): 100-pixel filled ellipse 200000 reps @ 0.0266 msec ( 37600.0/sec): 100-pixel filled ellipse 1000000 trep @ 0.0270 msec ( 37000.0/sec): 100-pixel filled ellipse 40000 reps @ 0.1441 msec ( 6940.0/sec): 500-pixel filled ellipse 40000 reps @ 0.1454 msec ( 6880.0/sec): 500-pixel filled ellipse 40000 reps @ 0.1456 msec ( 6870.0/sec): 500-pixel filled ellipse 40000 reps @ 0.1426 msec ( 7010.0/sec): 500-pixel filled ellipse 40000 reps @ 0.1399 msec ( 7150.0/sec): 500-pixel filled ellipse 200000 trep @ 0.1435 msec ( 6970.0/sec): 500-pixel filled ellipse 540000 reps @ 0.0221 msec ( 45300.0/sec): 10-pixel fill chord partial ellipse 540000 reps @ 0.0353 msec ( 28300.0/sec): 10-pixel fill chord partial ellipse 540000 reps @ 0.0262 msec ( 38100.0/sec): 10-pixel fill chord partial ellipse 540000 reps @ 0.0196 msec ( 51000.0/sec): 10-pixel fill chord partial ellipse 540000 reps @ 0.0168 msec ( 59600.0/sec): 10-pixel fill chord partial ellipse 2700000 trep @ 0.0240 msec ( 41700.0/sec): 10-pixel fill chord partial ellipse 288000 reps @ 0.0187 msec ( 53500.0/sec): 100-pixel fill chord partial ellipse 288000 reps @ 0.0187 msec ( 53600.0/sec): 100-pixel fill chord partial ellipse 288000 reps @ 0.0185 msec ( 54100.0/sec): 100-pixel fill chord partial ellipse 288000 reps @ 0.0187 msec ( 53600.0/sec): 100-pixel fill chord partial ellipse 288000 reps @ 0.0231 msec ( 43300.0/sec): 100-pixel fill chord partial ellipse 1440000 trep @ 0.0195 msec ( 51200.0/sec): 100-pixel fill chord partial ellipse 243000 reps @ 0.0192 msec ( 52200.0/sec): 10-pixel fill slice partial ellipse 243000 reps @ 0.0204 msec ( 49100.0/sec): 10-pixel fill slice partial ellipse 243000 reps @ 0.0190 msec ( 52800.0/sec): 10-pixel fill slice partial ellipse 243000 reps @ 0.0199 msec ( 50300.0/sec): 10-pixel fill slice partial ellipse 243000 reps @ 0.0190 msec ( 52800.0/sec): 10-pixel fill slice partial ellipse 1215000 trep @ 0.0195 msec ( 51400.0/sec): 10-pixel fill slice partial ellipse 144000 reps @ 0.0347 msec ( 28800.0/sec): 100-pixel fill slice partial ellipse 144000 reps @ 0.0343 msec ( 29100.0/sec): 100-pixel fill slice partial ellipse 144000 reps @ 0.0361 msec ( 27700.0/sec): 100-pixel fill slice partial ellipse 144000 reps @ 0.0351 msec ( 28500.0/sec): 100-pixel fill slice partial ellipse 144000 reps @ 0.0336 msec ( 29800.0/sec): 100-pixel fill slice partial ellipse 720000 trep @ 0.0348 msec ( 28800.0/sec): 100-pixel fill slice partial ellipse 600000 reps @ 0.0088 msec (114000.0/sec): Scroll 10x10 pixels 600000 reps @ 0.0089 msec (113000.0/sec): Scroll 10x10 pixels 600000 reps @ 0.0089 msec (113000.0/sec): Scroll 10x10 pixels 600000 reps @ 0.0088 msec (114000.0/sec): Scroll 10x10 pixels 600000 reps @ 0.0088 msec (114000.0/sec): Scroll 10x10 pixels 3000000 trep @ 0.0088 msec (113000.0/sec): Scroll 10x10 pixels 50000 reps @ 0.1119 msec ( 8940.0/sec): Scroll 100x100 pixels 50000 reps @ 0.1109 msec ( 9020.0/sec): Scroll 100x100 pixels 50000 reps @ 0.1141 msec ( 8760.0/sec): Scroll 100x100 pixels 50000 reps @ 0.1097 msec ( 9110.0/sec): Scroll 100x100 pixels 50000 reps @ 0.1097 msec ( 9110.0/sec): Scroll 100x100 pixels 250000 trep @ 0.1113 msec ( 8990.0/sec): Scroll 100x100 pixels 20000 reps @ 0.3813 msec ( 2620.0/sec): Scroll 500x500 pixels 20000 reps @ 0.3868 msec ( 2590.0/sec): Scroll 500x500 pixels 20000 reps @ 0.3873 msec ( 2580.0/sec): Scroll 500x500 pixels 20000 reps @ 0.3843 msec ( 2600.0/sec): Scroll 500x500 pixels 20000 reps @ 0.3818 msec ( 2620.0/sec): Scroll 500x500 pixels 100000 trep @ 0.3843 msec ( 2600.0/sec): Scroll 500x500 pixels From ssiddiqi@inspirepharm.com Wed Jan 5 09:18:00 2000 From: ssiddiqi@inspirepharm.com (Suhaib Siddiqi) Date: Wed, 05 Jan 2000 09:18:00 -0000 Subject: [Fwd: xperf on Exceed (in case you are interested ...)] References: <387348EE.22675FA5@ibm.net> Message-ID: John, What is your hardware spec? e.g video card, video ram, cpu speed, RAM. With Exceed 6.2 I get 20 times better xperf on my machine with Dell XPS 550 PIII, 128 MB, NIVIDA TNT 32 MB, Dell Trinitron 17", with 1280 x 1024 pixels Display at 16.7 Mil colors, 75 Hz Refresh Frequency. Of course the xperf results of two different x-servers should compared on same hardware and OS. Comparing your Exceed and Xggi results, it in fact looks pretty good. Suhaib > -----Original Message----- > From: cygwin-xfree-owner@sourceware.cygnus.com > [ mailto:cygwin-xfree-owner@sourceware.cygnus.com]On Behalf Of John > Fortin > Sent: Wednesday, January 05, 2000 8:37 AM > To: cygwin-xfree@sourceware.cygnus.com > Subject: Re: [Fwd: xperf on Exceed (in case you are > interested ...)] > > > > > > We can also check these against Exceed and other > commercial servers. > > I did it against Exceed also if you want to see them too. > > John. > > x11perf - X11 performance program, version 1.5 > Hummingbird Communications Ltd. server version 6020 on > localhost:0.0 > from home > Tue Jan 04 19:18:03 2000 > > Sync time adjustment is 4.4910 msecs. > > 300000 reps @ 0.0218 msec ( 45900.0/sec): 10-pixel ellipse > 300000 reps @ 0.0211 msec ( 47500.0/sec): 10-pixel ellipse > 300000 reps @ 0.0207 msec ( 48400.0/sec): 10-pixel ellipse > 300000 reps @ 0.0207 msec ( 48300.0/sec): 10-pixel ellipse > 300000 reps @ 0.0196 msec ( 51100.0/sec): 10-pixel ellipse > 1500000 trep @ 0.0208 msec ( 48200.0/sec): 10-pixel ellipse > > 240000 reps @ 0.0226 msec ( 44200.0/sec): 100-pixel ellipse > 240000 reps @ 0.0249 msec ( 40200.0/sec): 100-pixel ellipse > 240000 reps @ 0.0247 msec ( 40500.0/sec): 100-pixel ellipse > 240000 reps @ 0.0226 msec ( 44200.0/sec): 100-pixel ellipse > 240000 reps @ 0.0176 msec ( 56800.0/sec): 100-pixel ellipse > 1200000 trep @ 0.0225 msec ( 44400.0/sec): 100-pixel ellipse > > 60000 reps @ 0.0814 msec ( 12300.0/sec): 500-pixel ellipse > 60000 reps @ 0.0823 msec ( 12200.0/sec): 500-pixel ellipse > 60000 reps @ 0.0824 msec ( 12100.0/sec): 500-pixel ellipse > 60000 reps @ 0.0814 msec ( 12300.0/sec): 500-pixel ellipse > 60000 reps @ 0.0813 msec ( 12300.0/sec): 500-pixel ellipse > 300000 trep @ 0.0818 msec ( 12200.0/sec): 500-pixel ellipse > > 175000 reps @ 0.0304 msec ( 32900.0/sec): 100-pixel > dashed ellipse > 175000 reps @ 0.0304 msec ( 32900.0/sec): 100-pixel > dashed ellipse > 175000 reps @ 0.0301 msec ( 33200.0/sec): 100-pixel > dashed ellipse > 175000 reps @ 0.0304 msec ( 32900.0/sec): 100-pixel > dashed ellipse > 175000 reps @ 0.0298 msec ( 33600.0/sec): 100-pixel > dashed ellipse > 875000 trep @ 0.0302 msec ( 33100.0/sec): 100-pixel > dashed ellipse > > 175000 reps @ 0.0326 msec ( 30700.0/sec): 100-pixel > double-dashed > ellipse > 175000 reps @ 0.0311 msec ( 32200.0/sec): 100-pixel > double-dashed > ellipse > 175000 reps @ 0.0298 msec ( 33600.0/sec): 100-pixel > double-dashed > ellipse > 175000 reps @ 0.0304 msec ( 32900.0/sec): 100-pixel > double-dashed > ellipse > 175000 reps @ 0.0320 msec ( 31300.0/sec): 100-pixel > double-dashed > ellipse > 875000 trep @ 0.0312 msec ( 32100.0/sec): 100-pixel > double-dashed > ellipse > > 400000 reps @ 0.0173 msec ( 57800.0/sec): 10-pixel wide ellipse > 400000 reps @ 0.0148 msec ( 67500.0/sec): 10-pixel wide ellipse > 400000 reps @ 0.0211 msec ( 47300.0/sec): 10-pixel wide ellipse > 400000 reps @ 0.0266 msec ( 37600.0/sec): 10-pixel wide ellipse > 400000 reps @ 0.0266 msec ( 37500.0/sec): 10-pixel wide ellipse > 2000000 trep @ 0.0213 msec ( 47000.0/sec): 10-pixel wide ellipse > > 100000 reps @ 0.0511 msec ( 19600.0/sec): 100-pixel > wide ellipse > 100000 reps @ 0.0472 msec ( 21200.0/sec): 100-pixel > wide ellipse > 100000 reps @ 0.0473 msec ( 21200.0/sec): 100-pixel > wide ellipse > 100000 reps @ 0.0472 msec ( 21200.0/sec): 100-pixel > wide ellipse > 100000 reps @ 0.0494 msec ( 20300.0/sec): 100-pixel > wide ellipse > 500000 trep @ 0.0484 msec ( 20700.0/sec): 100-pixel > wide ellipse > > 40000 reps @ 0.2306 msec ( 4340.0/sec): 500-pixel > wide ellipse > 40000 reps @ 0.2306 msec ( 4340.0/sec): 500-pixel > wide ellipse > 40000 reps @ 0.2321 msec ( 4310.0/sec): 500-pixel > wide ellipse > 40000 reps @ 0.2304 msec ( 4340.0/sec): 500-pixel > wide ellipse > 40000 reps @ 0.2306 msec ( 4340.0/sec): 500-pixel > wide ellipse > 200000 trep @ 0.2309 msec ( 4330.0/sec): 500-pixel > wide ellipse > > 5000 reps @ 0.9991 msec ( 1000.0/sec): 100-pixel wide dashed > ellipse > 5000 reps @ 0.9651 msec ( 1040.0/sec): 100-pixel wide dashed > ellipse > 5000 reps @ 0.9771 msec ( 1020.0/sec): 100-pixel wide dashed > ellipse > 5000 reps @ 0.9771 msec ( 1020.0/sec): 100-pixel wide dashed > ellipse > 5000 reps @ 0.9651 msec ( 1040.0/sec): 100-pixel wide dashed > ellipse > 25000 trep @ 0.9767 msec ( 1020.0/sec): 100-pixel wide dashed > ellipse > > 12500 reps @ 0.4260 msec ( 2350.0/sec): 100-pixel wide > double-dashed ellipse > 12500 reps @ 0.4388 msec ( 2280.0/sec): 100-pixel wide > double-dashed ellipse > 12500 reps @ 0.4212 msec ( 2370.0/sec): 100-pixel wide > double-dashed ellipse > 12500 reps @ 0.4300 msec ( 2330.0/sec): 100-pixel wide > double-dashed ellipse > 12500 reps @ 0.4388 msec ( 2280.0/sec): 100-pixel wide > double-dashed ellipse > 62500 trep @ 0.4310 msec ( 2320.0/sec): 100-pixel wide > double-dashed ellipse > > 270000 reps @ 0.0203 msec ( 49200.0/sec): 10-pixel > partial ellipse > 270000 reps @ 0.0211 msec ( 47300.0/sec): 10-pixel > partial ellipse > 270000 reps @ 0.0230 msec ( 43500.0/sec): 10-pixel > partial ellipse > 270000 reps @ 0.0258 msec ( 38700.0/sec): 10-pixel > partial ellipse > 270000 reps @ 0.0602 msec ( 16600.0/sec): 10-pixel > partial ellipse > 1350000 trep @ 0.0301 msec ( 33200.0/sec): 10-pixel > partial ellipse > > 324000 reps @ 0.0159 msec ( 62800.0/sec): 100-pixel > partial ellipse > 324000 reps @ 0.0156 msec ( 64100.0/sec): 100-pixel > partial ellipse > 324000 reps @ 0.0196 msec ( 50900.0/sec): 100-pixel > partial ellipse > 324000 reps @ 0.0141 msec ( 71100.0/sec): 100-pixel > partial ellipse > 324000 reps @ 0.0146 msec ( 68700.0/sec): 100-pixel > partial ellipse > 1620000 trep @ 0.0160 msec ( 62700.0/sec): 100-pixel > partial ellipse > > 108000 reps @ 0.0310 msec ( 32300.0/sec): 10-pixel wide partial > ellipse > 108000 reps @ 0.0508 msec ( 19700.0/sec): 10-pixel wide partial > ellipse > 108000 reps @ 0.0326 msec ( 30700.0/sec): 10-pixel wide partial > ellipse > 108000 reps @ 0.0208 msec ( 48100.0/sec): 10-pixel wide partial > ellipse > 108000 reps @ 0.0203 msec ( 49200.0/sec): 10-pixel wide partial > ellipse > 540000 trep @ 0.0311 msec ( 32200.0/sec): 10-pixel wide partial > ellipse > > 25200 reps @ 0.2070 msec ( 4830.0/sec): 100-pixel > wide partial > ellipse > 25200 reps @ 0.2046 msec ( 4890.0/sec): 100-pixel > wide partial > ellipse > 25200 reps @ 0.2046 msec ( 4890.0/sec): 100-pixel > wide partial > ellipse > 25200 reps @ 0.2046 msec ( 4890.0/sec): 100-pixel > wide partial > ellipse > 25200 reps @ 0.2026 msec ( 4940.0/sec): 100-pixel > wide partial > ellipse > 126000 trep @ 0.2047 msec ( 4890.0/sec): 100-pixel > wide partial > ellipse > > 600000 reps @ 0.0101 msec ( 98600.0/sec): 10-pixel > filled ellipse > 600000 reps @ 0.0144 msec ( 69600.0/sec): 10-pixel > filled ellipse > 600000 reps @ 0.0168 msec ( 59400.0/sec): 10-pixel > filled ellipse > 600000 reps @ 0.0166 msec ( 60100.0/sec): 10-pixel > filled ellipse > 600000 reps @ 0.0166 msec ( 60400.0/sec): 10-pixel > filled ellipse > 3000000 trep @ 0.0149 msec ( 67100.0/sec): 10-pixel > filled ellipse > > 200000 reps @ 0.0266 msec ( 37600.0/sec): 100-pixel > filled ellipse > 200000 reps @ 0.0274 msec ( 36500.0/sec): 100-pixel > filled ellipse > 200000 reps @ 0.0272 msec ( 36800.0/sec): 100-pixel > filled ellipse > 200000 reps @ 0.0272 msec ( 36800.0/sec): 100-pixel > filled ellipse > 200000 reps @ 0.0266 msec ( 37600.0/sec): 100-pixel > filled ellipse > 1000000 trep @ 0.0270 msec ( 37000.0/sec): 100-pixel > filled ellipse > > 40000 reps @ 0.1441 msec ( 6940.0/sec): 500-pixel > filled ellipse > 40000 reps @ 0.1454 msec ( 6880.0/sec): 500-pixel > filled ellipse > 40000 reps @ 0.1456 msec ( 6870.0/sec): 500-pixel > filled ellipse > 40000 reps @ 0.1426 msec ( 7010.0/sec): 500-pixel > filled ellipse > 40000 reps @ 0.1399 msec ( 7150.0/sec): 500-pixel > filled ellipse > 200000 trep @ 0.1435 msec ( 6970.0/sec): 500-pixel > filled ellipse > > 540000 reps @ 0.0221 msec ( 45300.0/sec): 10-pixel > fill chord partial > ellipse > 540000 reps @ 0.0353 msec ( 28300.0/sec): 10-pixel > fill chord partial > ellipse > 540000 reps @ 0.0262 msec ( 38100.0/sec): 10-pixel > fill chord partial > ellipse > 540000 reps @ 0.0196 msec ( 51000.0/sec): 10-pixel > fill chord partial > ellipse > 540000 reps @ 0.0168 msec ( 59600.0/sec): 10-pixel > fill chord partial > ellipse > 2700000 trep @ 0.0240 msec ( 41700.0/sec): 10-pixel > fill chord partial > ellipse > > 288000 reps @ 0.0187 msec ( 53500.0/sec): 100-pixel fill chord > partial ellipse > 288000 reps @ 0.0187 msec ( 53600.0/sec): 100-pixel fill chord > partial ellipse > 288000 reps @ 0.0185 msec ( 54100.0/sec): 100-pixel fill chord > partial ellipse > 288000 reps @ 0.0187 msec ( 53600.0/sec): 100-pixel fill chord > partial ellipse > 288000 reps @ 0.0231 msec ( 43300.0/sec): 100-pixel fill chord > partial ellipse > 1440000 trep @ 0.0195 msec ( 51200.0/sec): 100-pixel fill chord > partial ellipse > > 243000 reps @ 0.0192 msec ( 52200.0/sec): 10-pixel > fill slice partial > ellipse > 243000 reps @ 0.0204 msec ( 49100.0/sec): 10-pixel > fill slice partial > ellipse > 243000 reps @ 0.0190 msec ( 52800.0/sec): 10-pixel > fill slice partial > ellipse > 243000 reps @ 0.0199 msec ( 50300.0/sec): 10-pixel > fill slice partial > ellipse > 243000 reps @ 0.0190 msec ( 52800.0/sec): 10-pixel > fill slice partial > ellipse > 1215000 trep @ 0.0195 msec ( 51400.0/sec): 10-pixel > fill slice partial > ellipse > > 144000 reps @ 0.0347 msec ( 28800.0/sec): 100-pixel fill slice > partial ellipse > 144000 reps @ 0.0343 msec ( 29100.0/sec): 100-pixel fill slice > partial ellipse > 144000 reps @ 0.0361 msec ( 27700.0/sec): 100-pixel fill slice > partial ellipse > 144000 reps @ 0.0351 msec ( 28500.0/sec): 100-pixel fill slice > partial ellipse > 144000 reps @ 0.0336 msec ( 29800.0/sec): 100-pixel fill slice > partial ellipse > 720000 trep @ 0.0348 msec ( 28800.0/sec): 100-pixel fill slice > partial ellipse > > 600000 reps @ 0.0088 msec (114000.0/sec): Scroll 10x10 pixels > 600000 reps @ 0.0089 msec (113000.0/sec): Scroll 10x10 pixels > 600000 reps @ 0.0089 msec (113000.0/sec): Scroll 10x10 pixels > 600000 reps @ 0.0088 msec (114000.0/sec): Scroll 10x10 pixels > 600000 reps @ 0.0088 msec (114000.0/sec): Scroll 10x10 pixels > 3000000 trep @ 0.0088 msec (113000.0/sec): Scroll 10x10 pixels > > 50000 reps @ 0.1119 msec ( 8940.0/sec): Scroll 100x100 pixels > 50000 reps @ 0.1109 msec ( 9020.0/sec): Scroll 100x100 pixels > 50000 reps @ 0.1141 msec ( 8760.0/sec): Scroll 100x100 pixels > 50000 reps @ 0.1097 msec ( 9110.0/sec): Scroll 100x100 pixels > 50000 reps @ 0.1097 msec ( 9110.0/sec): Scroll 100x100 pixels > 250000 trep @ 0.1113 msec ( 8990.0/sec): Scroll 100x100 pixels > > 20000 reps @ 0.3813 msec ( 2620.0/sec): Scroll 500x500 pixels > 20000 reps @ 0.3868 msec ( 2590.0/sec): Scroll 500x500 pixels > 20000 reps @ 0.3873 msec ( 2580.0/sec): Scroll 500x500 pixels > 20000 reps @ 0.3843 msec ( 2600.0/sec): Scroll 500x500 pixels > 20000 reps @ 0.3818 msec ( 2620.0/sec): Scroll 500x500 pixels > 100000 trep @ 0.3843 msec ( 2600.0/sec): Scroll 500x500 pixels > From fortinj@ibm.net Wed Jan 5 10:05:00 2000 From: fortinj@ibm.net (John Fortin) Date: Wed, 05 Jan 2000 10:05:00 -0000 Subject: [Fwd: xperf on Exceed (in case you are interested ...)] References: Message-ID: <387387F6.D001C725@ibm.net> > John, > > What is your hardware spec? e.g video card, video ram, cpu speed, > RAM. > With Exceed 6.2 I get 20 times better xperf on my machine > with Dell XPS 550 PIII, 128 MB, NIVIDA TNT 32 MB, Dell Trinitron > 17", with 1280 x 1024 pixels Display at 16.7 Mil colors, 75 Hz > Refresh Frequency. I'm at work, so I don't remember everything but I believe this is about right... Gateway PII 350, 8 mg AGP, 64 meg ram, Win98, 1024x768x65k at 75 Hz, 17" Monitor (Whatever gateway used) John John From ssiddiqi@inspirepharm.com Thu Jan 6 09:35:00 2000 From: ssiddiqi@inspirepharm.com (Suhaib Siddiqi) Date: Thu, 06 Jan 2000 09:35:00 -0000 Subject: Cygwin xfree URL Message-ID: I have updated Cygwin-Xfree Home Page and FAQ to reflect John Fortin's recent achievements with X-server. Suhaib From fortinj@ibm.net Thu Jan 6 18:41:00 2000 From: fortinj@ibm.net (John Fortin) Date: Thu, 06 Jan 2000 18:41:00 -0000 Subject: XGGI Success!! Message-ID: <387551D1.9006BC06@ibm.net> All, I am happy to announce that I have a working X-Server using XGGI running under Win98. * Mouse Tracking, LButton, RButton work * KB works I have Successfully run xterm, twm, xclock, oclock, xmag, x11perf, aixterm, xterm (from aix), ddd (from aix) Now it is a matter of fine tuning. The current version runs in a window, not full screen. I did this for debugging purposes, but I think I like it. Things to do: - make version for NT - clean up mouse support, add 3-button support - more fonts needed - make window moveable - optimize the code better Thanks John From fortinj@ibm.net Thu Jan 6 19:00:00 2000 From: fortinj@ibm.net (John Fortin) Date: Thu, 06 Jan 2000 19:00:00 -0000 Subject: XGGI Success!! References: <387551D1.9006BC06@ibm.net> <387553F4.430D830C@wgn.net> Message-ID: <3875564D.A0C729E1@ibm.net> "$Bill Luebkert" wrote: > > John Fortin wrote: > > > > All, > > I am happy to announce that I have a working X-Server using XGGI > > running under Win98. > > > > * Mouse Tracking, LButton, RButton work > > * KB works > > > > I have Successfully run xterm, twm, xclock, oclock, xmag, x11perf, > > aixterm, xterm (from aix), ddd (from aix) > > > > > > Now it is a matter of fine tuning. > > > > The current version runs in a window, not full screen. I did this for > > debugging purposes, but I think I like it. > > > > Things to do: > > > > - make version for NT > > NT can wait. :) > > > - clean up mouse support, add 3-button support > > That would be a nice. > > > - more fonts needed > > That can wait. :) > > > - make window moveable > > That would be nice too. > > > - optimize the code better > > That can wait too. :) > > When do you plan on making it available for download? Probably next week. I need to package it. Just understand that this is an alpha version, and bugs are going to be there. > > Since I'm not familiar with XGGI, are we talking about a Cygwin compiled version here? > or MingW? or native? or ?? The win32 version of XGGI is a cygwin executable for now. Suhaib is working on a mingw version of the X11 libs. When that happens, we should be able to create a native ( non-cygwin ) XGGI Server. The libGGI library will also be made available... John Checkout the XGGI Homepage. It will explain it better than I can http://www.stacken.kth.se/~mackan/ggi/xggi/ From khan@NanoTech.Wisc.EDU Thu Jan 6 20:09:00 2000 From: khan@NanoTech.Wisc.EDU (Mumit Khan) Date: Thu, 06 Jan 2000 20:09:00 -0000 Subject: XGGI Success!! References: <387551D1.9006BC06@ibm.net> Message-ID: On Thu, 6 Jan 2000, John Fortin wrote: > All, > I am happy to announce that I have a working X-Server using XGGI > running under Win98. Congratulations, John! And kudos to the rest of xfree86-win32 team for great work. Regards, Mumit From kdmurthy@vsnl.com Thu Jan 6 20:35:00 2000 From: kdmurthy@vsnl.com (kdmurthy@vsnl.com) Date: Thu, 06 Jan 2000 20:35:00 -0000 Subject: XGGI Success!! Message-ID: <200001070432.KAA19484@mypage.vsnl.com> Congratulations every one involved in the project. This is a great achievement for xfree project. Regards KD John Fortin wrote: > > All, > I am happy to announce that I have a working X-Server using XGGI > running under Win98. From cgf@cygnus.com Thu Jan 6 22:49:00 2000 From: cgf@cygnus.com (Chris Faylor) Date: Thu, 06 Jan 2000 22:49:00 -0000 Subject: XGGI Success!! References: <387551D1.9006BC06@ibm.net> Message-ID: <20000107014826.A22273@cygnus.com> On Thu, Jan 06, 2000 at 09:39:13PM -0500, John Fortin wrote: > I am happy to announce that I have a working X-Server using XGGI >running under Win98. This is incredible. Congratulations, John! cgf From ssiddiqi@inspirepharm.com Fri Jan 7 04:06:00 2000 From: ssiddiqi@inspirepharm.com (Suhaib Siddiqi) Date: Fri, 07 Jan 2000 04:06:00 -0000 Subject: XGGI Success!! References: <3875564D.A0C729E1@ibm.net> Message-ID: Congratulations, John. Marvelous work. Suhaib > -----Original Message----- > From: cygwin-xfree-owner@sourceware.cygnus.com > [ mailto:cygwin-xfree-owner@sourceware.cygnus.com]On Behalf Of John > Fortin > Sent: Thursday, January 06, 2000 9:58 PM > To: $Bill Luebkert; cygwin-xfree@sourceware.cygnus.com > Subject: Re: XGGI Success!! > > > > > "$Bill Luebkert" wrote: > > > > John Fortin wrote: > > > > > > All, > > > I am happy to announce that I have a working > X-Server using XGGI > > > running under Win98. > > > > > > * Mouse Tracking, LButton, RButton work > > > * KB works > > > > > > I have Successfully run xterm, twm, xclock, > oclock, xmag, x11perf, > > > aixterm, xterm (from aix), ddd (from aix) > > > > > > > > > Now it is a matter of fine tuning. > > > > > > The current version runs in a window, not > full screen. I did this for > > > debugging purposes, but I think I like it. > > > > > > Things to do: > > > > > > - make version for NT > > > > NT can wait. :) > > > > > - clean up mouse support, add 3-button support > > > > That would be a nice. > > > > > - more fonts needed > > > > That can wait. :) > > > > > - make window moveable > > > > That would be nice too. > > > > > - optimize the code better > > > > That can wait too. :) > > > > When do you plan on making it available for download? > > Probably next week. I need to package it. Just > understand that this > is an alpha version, and bugs are going to be there. > > > > > Since I'm not familiar with XGGI, are we talking about > a Cygwin compiled version here? > > or MingW? or native? or ?? > > The win32 version of XGGI is a cygwin executable for now. > Suhaib is > working on a mingw version of the X11 libs. When that happens, we > should be able to create a native ( non-cygwin ) XGGI Server. > > The libGGI library will also be made available... > > John > > > > Checkout the XGGI Homepage. It will explain it better than I can > > http://www.stacken.kth.se/~mackan/ggi/xggi/ > From ssiddiqi@inspirepharm.com Fri Jan 7 04:10:00 2000 From: ssiddiqi@inspirepharm.com (Suhaib Siddiqi) Date: Fri, 07 Jan 2000 04:10:00 -0000 Subject: XGGI Success!! References: <3875564D.A0C729E1@ibm.net> Message-ID: > > When do you plan on making it available for download? > > Probably next week. I need to package it. Just > understand that this > is an alpha version, and bugs are going to be there. > > > > > Since I'm not familiar with XGGI, are we talking about > a Cygwin compiled version here? > > or MingW? or native? or ?? > > The win32 version of XGGI is a cygwin executable for now. > Suhaib is > working on a mingw version of the X11 libs. When that happens, we > should be able to create a native ( non-cygwin ) XGGI Server. The XGGI executable which uses Cygwin is already available at ftp://sourceware.cygnus.com/pub/cygwin/xfree/pre-alpha-xfree-cygwin- b20.1.tar.bz2 But you will need libGGI/DirectX libraries to use it... which will be coming soon. Suhaib > > The libGGI library will also be made available... > > John > > > > Checkout the XGGI Homepage. It will explain it better than I can > > http://www.stacken.kth.se/~mackan/ggi/xggi/ > From ssiddiqi@inspirepharm.com Fri Jan 7 10:30:00 2000 From: ssiddiqi@inspirepharm.com (Suhaib Siddiqi) Date: Fri, 07 Jan 2000 10:30:00 -0000 Subject: xfree86/cpp References: <4.2.2.20000107111010.00aa8d30@nis-pop.lanl.gov> Message-ID: *> > Dear Suhaib, > thanks for taking the task to make xfree86 run on cygwin. > I do have a > question for you: What are the exact commands to compile > the original > sources from xfree86? When I apply the cygwin-xfree.diff > file usinf patch > -p0 get very far > complaining that /lib/cpp wasn't found. Make a symlink to cpp.exe for example ln -s /cygnus/cygwin-b20/H-i586-cygwin32/lib/gcc-lib/i586-cygwin32/2.95.2/ cpp.exe /cygnus/cygwin-b20/H-i586-cygwin32/bin/cpp.exe or you could add cygwin.cf in /xc/config/cf Replace the line: #define Cppcmd cpp by #define CppCmd /cygnus/cygwin-b20/H-i586-cygwin32/lib/gcc-lib/i586-cygwin32/2.95.2/ cpp.exe (or whatever you gcc-lib install path is ) >Do I need to use > -p1? I have tried > ten times now to compile but always something is wrong! > If you could help I > would be happy!!! > > Thanks, > Haje > > ---------------------------------------------------------- > ------------------ > Haje Korth > Space and Atmospheric Sciences (NIS-1) > MS D466 > Los Alamos National Laboratory > Los Alamos, NM 87545 > Phone: (505) 667-0788 > FAX: (505) 665-7395 > e-mail: hkorth@lanl.gov > http://nis-www.lanl.gov/~hkorth > ---------------------------------------------------------- > ------------------ > From mattl@d2k.com Fri Jan 7 11:20:00 2000 From: mattl@d2k.com (Matt Lewandowsky) Date: Fri, 07 Jan 2000 11:20:00 -0000 Subject: XGGI Success!! Message-ID: <9569BB51CAE7D211AB9C0090273CB759387873@D2K_BDC> But has it been tested in NT? I'd rather not grab it until I know that it's not supposed to kill my box. ;) Thanks, Matt -----Original Message----- From: John Fortin [ mailto:fortinj@ibm.net ] Sent: Thursday, January 06, 2000 6:39 PM To: cygwin-xfree@sourceware.cygnus.com Subject: XGGI Success!! All, I am happy to announce that I have a working X-Server using XGGI running under Win98. ---Rest Of Message Snipped--- From ssiddiqi@inspirepharm.com Fri Jan 7 11:25:00 2000 From: ssiddiqi@inspirepharm.com (Suhaib Siddiqi) Date: Fri, 07 Jan 2000 11:25:00 -0000 Subject: XGGI Success!! References: <9569BB51CAE7D211AB9C0090273CB759387873@D2K_BDC> Message-ID: John wrote in his announcement: Things to do: - make version for NT - clean up mouse support, add 3-button support - more fonts needed - make window moveable - optimize the code better So, it might you if hrew him on your NT box. > -----Original Message----- > From: cygwin-xfree-owner@sourceware.cygnus.com > [ mailto:cygwin-xfree-owner@sourceware.cygnus.com]On Behalf Of Matt > Lewandowsky > Sent: Friday, January 07, 2000 2:18 PM > To: John Fortin; cygwin-xfree@sourceware.cygnus.com > Subject: RE: XGGI Success!! > > > But has it been tested in NT? I'd rather not grab it > until I know that > it's not supposed to kill my box. ;) > > Thanks, > > Matt > > -----Original Message----- > From: John Fortin [ mailto:fortinj@ibm.net ] > Sent: Thursday, January 06, 2000 6:39 PM > To: cygwin-xfree@sourceware.cygnus.com > Subject: XGGI Success!! > > > All, > I am happy to announce that I have a working > X-Server using XGGI > running under Win98. > > ---Rest Of Message Snipped--- > From ssiddiqi@inspirepharm.com Fri Jan 7 11:31:00 2000 From: ssiddiqi@inspirepharm.com (Suhaib Siddiqi) Date: Fri, 07 Jan 2000 11:31:00 -0000 Subject: XGGI Success!! References: <9569BB51CAE7D211AB9C0090273CB759387874@D2K_BDC> Message-ID: No idea. It depends upon DirectX version John used. Suhaib > -----Original Message----- > From: Matt Lewandowsky [ mailto:mattl@d2k.com ] > Sent: Friday, January 07, 2000 2:27 PM > To: Suhaib Siddiqi > Subject: RE: XGGI Success!! > > > I was just wondering if it was at all usable in NT yet. > I'm willing to > test as soon as something that isn't guaranteed to kill > my machine is > out. > > Thanks, > > Matt > > -----Original Message----- > From: Suhaib Siddiqi [ mailto:ssiddiqi@inspirepharm.com ] > Sent: Friday, January 07, 2000 11:19 AM > To: Matt Lewandowsky; John Fortin; > cygwin-xfree@sourceware.cygnus.com > Subject: RE: XGGI Success!! > > > > > John wrote in his announcement: > > > Things to do: > > - make version for NT > - clean up mouse support, add 3-button support > - more fonts needed > - make window moveable > - optimize the code better > > > So, it might you if hrew him on your NT box. > > > > > -----Original Message----- > > From: cygwin-xfree-owner@sourceware.cygnus.com > > [ mailto:cygwin-xfree-owner@sourceware.cygnus.com]On > Behalf Of Matt > > Lewandowsky > > Sent: Friday, January 07, 2000 2:18 PM > > To: John Fortin; cygwin-xfree@sourceware.cygnus.com > > Subject: RE: XGGI Success!! > > > > > > But has it been tested in NT? I'd rather not grab it > > until I know that > > it's not supposed to kill my box. ;) > > > > Thanks, > > > > Matt > > > > -----Original Message----- > > From: John Fortin [ mailto:fortinj@ibm.net ] > > Sent: Thursday, January 06, 2000 6:39 PM > > To: cygwin-xfree@sourceware.cygnus.com > > Subject: XGGI Success!! > > > > > > All, > > I am happy to announce that I have a working > > X-Server using XGGI > > running under Win98. > > > > ---Rest Of Message Snipped--- > > > From kd@blr.vsnl.net.in Sat Jan 8 08:36:00 2000 From: kd@blr.vsnl.net.in (Dakshinamurthy Karra) Date: Sat, 08 Jan 2000 08:36:00 -0000 Subject: DX Server gets compiled on Cygwin now... Message-ID: <00010822073900.00421@indica> Greetings, I got the DX server working on cygwin - it gets compiled, linked and when executed gives the famous bw screen of X. However, None of the clients are able to display on the screen. If I run xterm (or any other client) on a different box, netstat shows the connection is established but no window appears on the screen. It might be a problem which I had when I applied patches to the X 3.3.5 source code, I got errors in the following files: xc/include/extensions/Imakefile.rej xc/include/extensions/xf86rush.h.rej xc/include/extensions/xf86rushstr.h.rej xc/lib/ICE/ICE-def.cpp.rej xc/lib/Xext/Xext-def.cpp.rej xc/lib/Xxf86rush/Imakefile.rej xc/programs/Xserver/Xext/Imakefile.rej xc/programs/Xserver/Xext/xf86Rush.c.rej and forced to make a modification in os/xf86misc.c (undeclared xf86OsMouseProc error) before I could get the Xvfb server compiled. xterm linking says "ncurses" not found - but I think it is OK. Any help will be appreciated. Thanks and Regards KD From ssiddiqi@inspirepharm.com Sat Jan 8 08:42:00 2000 From: ssiddiqi@inspirepharm.com (Suhaib Siddiqi) Date: Sat, 08 Jan 2000 08:42:00 -0000 Subject: DX Server gets compiled on Cygwin now... References: <00010822073900.00421@indica> Message-ID: > > Greetings, > > I got the DX server working on cygwin - it gets compiled, > linked and when > executed gives the famous bw screen of X. Cool... > > However, None of the clients are able to display on the > screen. If I run xterm > (or any other client) on a different box, netstat shows > the connection is > established but no window appears on the screen. Too bad ;-) > > It might be a problem which I had when I applied patches > to the X 3.3.5 source > code, I got errors in the following files: > > xc/include/extensions/Imakefile.rej > xc/include/extensions/xf86rush.h.rej > xc/include/extensions/xf86rushstr.h.rej > xc/lib/ICE/ICE-def.cpp.rej > xc/lib/Xext/Xext-def.cpp.rej > xc/lib/Xxf86rush/Imakefile.rej > xc/programs/Xserver/Xext/Imakefile.rej > xc/programs/Xserver/Xext/xf86Rush.c.rej You can compare *.rej files with originals and make changes manually. There are very few changes in these files. > > and forced to make a modification in os/xf86misc.c > (undeclared xf86OsMouseProc > error) before I could get the Xvfb server compiled. > > xterm linking says "ncurses" not found - but I think it is OK. Yes it does matter... if you do not have ncurses installed go to /xc/config/cf/cygwin.cf file and chnage the -lncurses to -ltermcap If we had your sources we could straighten these bugs. Regards Suhaib > > Any help will be appreciated. > > Thanks and Regards > KD > From kd@blr.vsnl.net.in Sat Jan 8 09:04:00 2000 From: kd@blr.vsnl.net.in (Dakshinamurthy Karra) Date: Sat, 08 Jan 2000 09:04:00 -0000 Subject: DX Server gets compiled on Cygwin now... References: Message-ID: <00010822353601.00421@indica> On Sat, 08 Jan 2000, Suhaib Siddiqi wrote: > You can compare *.rej files with originals and make changes > manually. There are very few changes in these files. They failed because all of them are *already* applied. Except in one header file. > If we had your sources we could straighten these bugs. I Know. And I am fast reaching the point where I will giveup. I am trying to download the latest snapshot of cygwin. Let me check it out with it. Regards KD From corinna@vinschen.de Sat Jan 8 09:10:00 2000 From: corinna@vinschen.de (Corinna Vinschen) Date: Sat, 08 Jan 2000 09:10:00 -0000 Subject: DX Server gets compiled on Cygwin now... References: <00010822353601.00421@indica> Message-ID: <38776F44.BB5CEB2B@vinschen.de> Dakshinamurthy Karra wrote: > [...] > I am trying to download the latest snapshot of cygwin. Let me check it out with > it. Don't do this. The latest snapshot (20000106) is in an early state of rearrangement. Take the 20000105 snapshot instead. Regards, Corinna From ssiddiqi@inspirepharm.com Sat Jan 8 09:11:00 2000 From: ssiddiqi@inspirepharm.com (Suhaib Siddiqi) Date: Sat, 08 Jan 2000 09:11:00 -0000 Subject: DX Server gets compiled on Cygwin now... References: <00010822353601.00421@indica> Message-ID: > > On Sat, 08 Jan 2000, Suhaib Siddiqi wrote: > > You can compare *.rej files with originals and make changes > > manually. There are very few changes in these files. > > They failed because all of them are *already* applied. > Except in one header > file. I know that could be a problem. XFree86 organization took a lot of my work and merged it into their official sources tree. But, they did apply all the patches, therefore I had been noticing these problems. At some point in near future I hope I would be ale to convience XFree86 organization to apply all the patches not only part of it, because it creates more work for me to help other users fix the problems created by applying part of the patches. > > > If we had your sources we could straighten these bugs. > > I Know. And I am fast reaching the point where I will giveup. Do not give up please. What I mean more members of cygwin-xfree developers team has access to your code better are the chances we can fix problems. > > I am trying to download the latest snapshot of cygwin. > Let me check it out with > it. It will not make much difference except AF_UNIX socket... Regards Suhaib > > Regards > KD > From kd@blr.vsnl.net.in Sat Jan 8 10:37:00 2000 From: kd@blr.vsnl.net.in (Dakshinamurthy Karra) Date: Sat, 08 Jan 2000 10:37:00 -0000 Subject: DX Server gets compiled on Cygwin now... References: Message-ID: <00010900083001.00479@indica> Now it works. I just need to copy the SecurityPolicy file across in the appropriate directory. The server was dumping the error and I was blind!!! On Sat, 08 Jan 2000, Suhaib Siddiqi wrote: > At some point in near future I hope I would be ale to convience > XFree86 organization to apply all the patches not only part of it, > because it creates more work for me to help other users fix the > problems created by applying part of the patches. I think we should do that. We are fast approaching *real* working X-Servers and lets us strive for getting the source trees merged. > Do not give up please. What I mean more members of cygwin-xfree > developers team has access to your code better are the chances we > can fix problems. I do not mean giving up in that sense ;-). > It will not make much difference except AF_UNIX socket... I realized it. From ssiddiqi@inspirepharm.com Sat Jan 8 10:43:00 2000 From: ssiddiqi@inspirepharm.com (Suhaib Siddiqi) Date: Sat, 08 Jan 2000 10:43:00 -0000 Subject: DX Server gets compiled on Cygwin now... References: <00010900083001.00479@indica> Message-ID: > Now it works. I just need to copy the SecurityPolicy file > across in the > appropriate directory. The server was dumping the error > and I was blind!!! Are you using the xdm or linked against the libcrypt as I explained on cygwin-xfree URL? The xfree86 3.3.5 with my security patches for xdm forces to have a SecurityPolicy, unless you turn it off in *.cf files during compilation. Well, at least it is good that SecurityPolicy enforcement worked under Cygwin. > On Sat, 08 Jan 2000, Suhaib Siddiqi wrote: > > At some point in near future I hope I would be ale to convience > > XFree86 organization to apply all the patches not only > part of it, > > because it creates more work for me to help other users fix the > > problems created by applying part of the patches. > > I think we should do that. We are fast approaching *real* > working X-Servers and > lets us strive for getting the source trees merged. That I would do once I have sources from everyone, binries and sources get tested by 100s of users at cygwin-xfree. After that I will try to get them merged in xfree86 source tree so users can compile the code on their own... and we do not branch of xfree86 projects. > > Do not give up please. What I mean more members of cygwin-xfree > > developers team has access to your code better are the > chances we > > can fix problems. > > I do not mean giving up in that sense ;-). > > > It will not make much difference except AF_UNIX socket... > I realized it. > Suhaib From cgf@cygnus.com Sat Jan 8 18:12:00 2000 From: cgf@cygnus.com (Chris Faylor) Date: Sat, 08 Jan 2000 18:12:00 -0000 Subject: DX Server gets compiled on Cygwin now... References: <00010822353601.00421@indica> <38776F44.BB5CEB2B@vinschen.de> Message-ID: <20000108211121.A703@cygnus.com> On Sat, Jan 08, 2000 at 06:09:24PM +0100, Corinna Vinschen wrote: >Dakshinamurthy Karra wrote: >> [...] >> I am trying to download the latest snapshot of cygwin. Let me check it out with >> it. > >Don't do this. The latest snapshot (20000106) is in an early state >of rearrangement. > >Take the 20000105 snapshot instead. Either snapshot should work. I doubt that he wants to rebuild the DLL from scratch. There's no need to do this. Just take the DLL itself. The latest snapshot works fine, AFAIK. cgf From corinna@vinschen.de Sun Jan 9 01:14:00 2000 From: corinna@vinschen.de (Corinna Vinschen) Date: Sun, 09 Jan 2000 01:14:00 -0000 Subject: DX Server gets compiled on Cygwin now... References: <00010822353601.00421@indica> <38776F44.BB5CEB2B@vinschen.de> <20000108211121.A703@cygnus.com> Message-ID: <38785158.8D240941@vinschen.de> Chris Faylor wrote: > > On Sat, Jan 08, 2000 at 06:09:24PM +0100, Corinna Vinschen wrote: > >Dakshinamurthy Karra wrote: > >> [...] > >> I am trying to download the latest snapshot of cygwin. Let me check it out with > >> it. > > > >Don't do this. The latest snapshot (20000106) is in an early state > >of rearrangement. > > > >Take the 20000105 snapshot instead. > > Either snapshot should work. I doubt that he wants to rebuild the DLL > from scratch. There's no need to do this. > > Just take the DLL itself. The latest snapshot works fine, AFAIK. Ah, you're right. I'm too fixed on the sources. Corinna From ssiddiqi@inspirepharm.com Mon Jan 10 12:50:00 2000 From: ssiddiqi@inspirepharm.com (Suhaib Siddiqi) Date: Mon, 10 Jan 2000 12:50:00 -0000 Subject: MSVC vs Cygwin X11 progs References: <387A4358.AD1BA2E5@ibm.net> Message-ID: John, Great... I was actually expecting the code compiled with MSVC and Cygwin/GCC to have same speed. Using MSVC you have to omit a lot of optimozation which xfree86.org introduced in X11R6.x, while with Cygwin/GCC I was able to port almost all what is compiled on Linux. Cygwin UNIX emulation does make code slower, in this case in comparision to MSVC it is not bad. I am ccing this cygwin-xfree list for other users info. Suhaib > -----Original Message----- > From: John Fortin [ mailto:fortinj@ibm.net ] > Sent: Monday, January 10, 2000 3:39 PM > To: Suhaib Siddiqi > Subject: MSVC vs Cygwin X11 progs > > > Suhaib, > Just for the heck of it, I ran the MCVC version of > x11perf against > the cygwin version. I expected the MSVC version to be > faster and I > wanted to see by how much. > > Well, I was suprised by the results. They were very > even. Some > tests cygwin x11perf was faster, some msvc x11perf was > faster. Overall, > they seemed very close. > > Attached are the results.... Run under P180, 128 MG > Ram, 16bit color > under Hummingbird. > > John > > From cgf@cygnus.com Fri Jan 14 17:35:00 2000 From: cgf@cygnus.com (Chris Faylor) Date: Fri, 14 Jan 2000 17:35:00 -0000 Subject: VNC Message-ID: <20000114212607.A3929@cygnus.com> I don't remember if this has come up before but I was wondering if anyone has looked at the Windows version of vnc to see if any of the code in it would be usable by this project. The URL for the project is: http://www.uk.research.att.com/vnc -- cgf@cygnus.com http://www.cygnus.com/ From Ssiddiqi@inspirepharm.com Sat Jan 15 10:29:00 2000 From: Ssiddiqi@inspirepharm.com (Suhaib M. Siddiqi) Date: Sat, 15 Jan 2000 10:29:00 -0000 Subject: VNC References: <20000114212607.A3929@cygnus.com> Message-ID: I would check soon. ATT does provide a Win32 native version but sort of limited in capabilities. Suhaib On 15-Jan-00 Chris Faylor wrote: > I don't remember if this has come up before but I was wondering if > anyone has looked at the Windows version of vnc to see if any of the > code in it would be usable by this project. > > The URL for the project is: > > http://www.uk.research.att.com/vnc > > -- > cgf@cygnus.com > http://www.cygnus.com/ ---------------------------------- E-Mail: Suhaib M. Siddiqi Date: 15-Jan-00 Time: 13:26:19 ---------------------------------- From hans.de.bok@philips.com Mon Jan 17 01:20:00 2000 From: hans.de.bok@philips.com (hans.de.bok@philips.com) Date: Mon, 17 Jan 2000 01:20:00 -0000 Subject: VNC Message-ID: <0056890007967017000002L972*@MHS> cfg@cygnus.com wrote: >I don't remember if this has come up before but I was wondering if >anyone has looked at the Windows version of vnc to see if any of the >code in it would be usable by this project. >The URL for the project is: > http://www.uk.research.att.com/vnc The VNC code is very usable in this project. A few weeks ago I ported Xvnc to Windows and now I am working on the integration of this ported Xvnc and the (Windows) VncViewer. This is not as easy as I first hoped it would be but currently display and pointer device are functional. I am now working on keyboard support, support of options (hardcoded at this moment) and improvement of the code. Hans hans.de.bok@philips.com From ssiddiqi@inspirepharm.com Mon Jan 17 09:26:00 2000 From: ssiddiqi@inspirepharm.com (Suhaib Siddiqi) Date: Mon, 17 Jan 2000 09:26:00 -0000 Subject: First Alpha X-server for Win32 is out: Message-ID: To all: John Fortin's GGI based first X-server is available for testing. Please note this is ALPHA RELEASE and has some known and unkown problems. Thanks John for marvelous work. What to do to get a copy of Alpha X-server: 1) Dowload from ftp://sourceware.cygnus.com/pub/cygwin/xfree/pre-alpha-xfree-cygwin- b20.1.tar.bz2 2) Unbzip2 and untar pre-alpha-xfree-cygwin-b20.1.tar.bz2 to /usr/X11R6 on your C:\ drive. 3) Download ggi.tar.gz for MingW32/Cygwin from http://pws.prserv.net/thefortins/ggi.tar.gz Note: At the moment John Fortin may not have a link to ggi.tar.gz at his home page, therefore you need to type: http://pws.prserv.net/thefortins/ggi.tar.gz to get the ggi.tar.gz. 3) ungzip and untar the ggi.tar.gz to /usr/local.It untars into usr/local/ from whatever directory you untar from ( not /usr/local) 4) You need to set the following: GGI_DEBUG=0 # or whatever debug level you want GGI_DEFMODE=800x600[GT_16BIT] # or 800x600[GT_32BIT] if using 32bit color 640x480 1024x768 should work also. Your current resolution needs to be larger then the mode you are asking for. if you are currently at 800x600, only 640x480 and smaller will work. GGI_CONFDIR=path to config files (ex. export GGI_CONFDIR=c:/usr/local/etc/ggi) 5) Go into the /usr/local/etc/ggi directory and changed the .root parameter, in libggi.conf file, to the proper path (ex. c:/usr/local/lib) 6) Go into Go into the /usr/local/etc/ggi directory and edit libggi.conf file. In #Display abbrevations column add the following: directx display/directx.dll 7) Go into /usr/local/lib directory and issue the following commands from Cygwin bash shell cp libgg-0-0-7.dll libgg-0-0-6.dll cp libgii-0-0-7.dll libgii-0-0-6.dll NOW YOU SHOULD BE ABLE TO RUN XGGI X-server using the following command from /usr/X11R6/bin directory (or from anywhere if X11R6/bin is in your PATH) ./XGGI -targets directx & KNOWN PROBLEMS: There are still a couple of bugs. The cursor doesn't always match where the windows cursor is. The work around is to bring both to the bottom right of the screen. This resyncs them. The mouse doesn't show up over the X console if the X console is parially behind a Win32 window and does not have the focus. PLEASE DIRECT ALL QUESTIONS AND SUGGESTIONS TO CYGWIN-XFREE@SOURCEWARE.CYGNUS.COM MAILING LIST. ---------------------------------------- I will update Cygwin-xfree URL later today. Karra's DirectX based framebuffer X-server for Win32 is comming soon (Hopefully within next 2 weeks) Suhaib From burgers@ecn.nl Tue Jan 18 13:12:00 2000 From: burgers@ecn.nl (Teun Burgers) Date: Tue, 18 Jan 2000 13:12:00 -0000 Subject: VNC Message-ID: <388448A3.72F33351@ecn.nl> Chris Faylor wrote: > I don't remember if this has come up before but I was wondering if > anyone has looked at the Windows version of vnc to see if any of the > code in it would be usable by this project. > The URL for the project is: > http://www.uk.research.att.com/vnc This is very useful and a very good alternative to the previously free and now almost-free microimages MiX server, that is mentioned on the cygwin links page! Using VNC I could very easily display X-applications from my Digital Unix station on my PC over a network, all with pre-compiled VNC binaries. thanks for the hint Teun Burgers From hans.de.bok@philips.com Wed Jan 19 08:20:00 2000 From: hans.de.bok@philips.com (hans.de.bok@philips.com) Date: Wed, 19 Jan 2000 08:20:00 -0000 Subject: GDI based X-server available Message-ID: <0056890008033532000002L922*@MHS> A first version of my GDI based X server is available for those who are interested. It is basically a merge of a Windows port of Xvnc and Vncviewer for Windows with the rfb layer removed. It works fine with Imagemagick and many other programs but it will crash on a few tests of x11perf . Options are currently ignored: it is "hardcoded" for 800x600x16. You only need the executable and the default set of fonts. I have no website (yet) but I will email the executable on request. Hans hans.de.bok@philips.com From KendallB@scitechsoft.com Wed Jan 19 19:45:00 2000 From: KendallB@scitechsoft.com (Kendall Bennett) Date: Wed, 19 Jan 2000 19:45:00 -0000 Subject: GDI based X-server available References: <0056890008033532000002L922*@MHS> Message-ID: <200001191947884.SM00169@KENDALLB> Hi Hans, > A first version of my GDI based X server is available for those > who are interested. It is basically a merge of a Windows port of > Xvnc and Vncviewer for Windows with the rfb layer removed. It works > fine with Imagemagick and many other programs but it will crash on > a few tests of x11perf . Options are currently ignored: it is > "hardcoded" for 800x600x16. You only need the executable and the > default set of fonts. I have no website (yet) but I will email the > executable on request. Sounds cool. Perhaps the server can be put up next to the Cygwin ones? Is this compiled with Cygwin, or some other compiler? Also are you planning on putting the source code patches up for others to use and help development with? Regards, +---------------------------------------------------------------+ | SciTech Software - Building Truly Plug'n'Play Software! | +---------------------------------------------------------------+ | Kendall Bennett | Email: KendallB@scitechsoft.com | | Director of Engineering | Phone: (530) 894 8400 | | SciTech Software, Inc. | Fax : (530) 894 9069 | | 505 Wall Street | ftp : ftp.scitechsoft.com | | Chico, CA 95928, USA | www : http://www.scitechsoft.com | +---------------------------------------------------------------+ From hans.de.bok@philips.com Thu Jan 20 02:34:00 2000 From: hans.de.bok@philips.com (hans.de.bok@philips.com) Date: Thu, 20 Jan 2000 02:34:00 -0000 Subject: GDI based X-server available Message-ID: <0056890008045814000002L942*@MHS> >> A first version of my GDI based X server is available for those >> who are interested. It is basically a merge of a Windows port of >> Xvnc and Vncviewer for Windows with the rfb layer removed. It works >> fine with Imagemagick and many other programs but it will crash on >> a few tests of x11perf . Options are currently ignored: it is >> "hardcoded" for 800x600x16. You only need the executable and the >> default set of fonts. I have no website (yet) but I will email the >> executable on request. >Sounds cool. Perhaps the server can be put up next to the Cygwin >ones? Is this compiled with Cygwin, or some other compiler? Also are >you planning on putting the source code patches up for others to use >and help development with? The server is compiled, as a project, with Visual C++ because I don't know how to compile programs that use the WIN32 API with Cygwin. I planned to make the source code available, but first I want to remove lots of unused code and rearrange some other parts. Hans From ssiddiqi@inspirepharm.com Thu Jan 20 04:45:00 2000 From: ssiddiqi@inspirepharm.com (Suhaib Siddiqi) Date: Thu, 20 Jan 2000 04:45:00 -0000 Subject: GDI based X-server available References: <0056890008045814000002L942*@MHS> Message-ID: > >> A first version of my GDI based X server is available for those > >> who are interested. It is basically a merge of a > Windows port of > >> Xvnc and Vncviewer for Windows with the rfb layer > removed. It works > >> fine with Imagemagick and many other programs but it > will crash on > >> a few tests of x11perf . Options are currently ignored: it is > >> "hardcoded" for 800x600x16. You only need the > executable and the > >> default set of fonts. I have no website (yet) but I > will email the > >> executable on request. > > >Sounds cool. Perhaps the server can be put up next to the Cygwin > >ones? Is this compiled with Cygwin, or some other > compiler? Also are > >you planning on putting the source code patches up for > others to use > >and help development with? > > The server is compiled, as a project, with Visual C++ > because I don't > know how to compile programs that use the WIN32 API with Cygwin. > I planned to make the source code available, but first I want to > remove lots of unused code and rearrange some other parts. > Unfortunately, I think VNC canot be put on the same server as as Cygwin. The VNC code is owned by AT&T, though available free of cost but it does puts a lot of restrictions. Therefore you do not see VNC code being redistributed by Linux vendors and at other public domain archives. Beside the lasted version of VNC binaries available from AT&T are native WIN32 port of VNC and XVNC, so what is advantage of having yours MSVC and Cygwin compiled binaries? Suhaib > Hans > From hans.de.bok@philips.com Thu Jan 20 06:11:00 2000 From: hans.de.bok@philips.com (hans.de.bok@philips.com) Date: Thu, 20 Jan 2000 06:11:00 -0000 Subject: GDI based X-server available Message-ID: <0056890008053532000002L922*@MHS> >Unfortunately, I think VNC canot be put on the same server as as >Cygwin. >The VNC code is owned by AT&T, though available free of cost but it >does puts a lot of restrictions. Therefore you do not see VNC code >being redistributed by Linux vendors and at other public domain >archives. According to the VNC homepage the VNC code is available under the terms of the GNU Public Licence.... >Beside the lasted version of VNC binaries available from AT&T are >native WIN32 port of VNC and XVNC, so what is advantage of having >yours MSVC and Cygwin compiled binaries? The native WIN32 port consists of VncViewer and WinVnc. WinVnc is a native server for the rfb protocol and is NOT a Windows port of Xvnc ! Xvnc is a native unix server for the rfb protocol. It is in fact an X server using the rfb protocol instead of keyboard/pointer-device/display for input/output. I first ported Xvnc to Windows. Running this ported Xvnc and VncViewer on the same machine gives the same functionality as an X server, only server and viewer still need a TCP/IP connection to communicate using the rfb protocol. The next step was to merge the source code of the ported Xvnc and the source code of the native Windows VncViewer. The result is a X server for Windows ! The viewer and server are now one, no more need for a TCP/IP connection and the rfb protocol. This program has nothing to do with VNC other then sharing a part of the source code. Hans hans.de.bok@philips.com From cgf@cygnus.com Thu Jan 20 08:49:00 2000 From: cgf@cygnus.com (Chris Faylor) Date: Thu, 20 Jan 2000 08:49:00 -0000 Subject: GDI based X-server available References: <0056890008045814000002L942*@MHS> Message-ID: <20000120114927.A7819@cygnus.com> On Thu, Jan 20, 2000 at 11:34:02AM +0100, hans.de.bok@philips.com wrote: >The server is compiled, as a project, with Visual C++ because I don't >know how to compile programs that use the WIN32 API with Cygwin. I am not sure what you mean by this. In general, you just use "gcc" to compile a program. There is nothing special required. cgf From ssiddiqi@inspirepharm.com Thu Jan 20 11:18:00 2000 From: ssiddiqi@inspirepharm.com (Suhaib Siddiqi) Date: Thu, 20 Jan 2000 11:18:00 -0000 Subject: GDI based X-server available References: <200001191947884.SM00169@KENDALLB> Message-ID: I checked the VNC license. The new license is GNU GPL. I have asked him to e-mail me binaries and his ported code. I will make it available to public. cygwin-xfree project requirement is that the same code which was used to compile bianries be available to users from the same site... of am I not correct Chris? Suhaib > -----Original Message----- > From: cygwin-xfree-owner@sourceware.cygnus.com > [ mailto:cygwin-xfree-owner@sourceware.cygnus.com]On > Behalf Of Kendall > Bennett > Sent: Wednesday, January 19, 2000 10:47 PM > To: cygwin-xfree@sourceware.cygnus.com > Subject: Re: GDI based X-server available > > > Hi Hans, > > > A first version of my GDI based X server is available for those > > who are interested. It is basically a merge of a Windows port of > > Xvnc and Vncviewer for Windows with the rfb layer > removed. It works > > fine with Imagemagick and many other programs but it > will crash on > > a few tests of x11perf . Options are currently ignored: it is > > "hardcoded" for 800x600x16. You only need the executable and the > > default set of fonts. I have no website (yet) but I > will email the > > executable on request. > > Sounds cool. Perhaps the server can be put up next to the Cygwin > ones? Is this compiled with Cygwin, or some other > compiler? Also are > you planning on putting the source code patches up for > others to use > and help development with? > > Regards, > > +---------------------------------------------------------------+ > | SciTech Software - Building Truly Plug'n'Play Software! | > +---------------------------------------------------------------+ > | Kendall Bennett | Email: KendallB@scitechsoft.com | > | Director of Engineering | Phone: (530) 894 8400 | > | SciTech Software, Inc. | Fax : (530) 894 9069 | > | 505 Wall Street | ftp : ftp.scitechsoft.com | > | Chico, CA 95928, USA | www : http://www.scitechsoft.com | > +---------------------------------------------------------------+ > From ssiddiqi@inspirepharm.com Thu Jan 20 11:20:00 2000 From: ssiddiqi@inspirepharm.com (Suhaib Siddiqi) Date: Thu, 20 Jan 2000 11:20:00 -0000 Subject: GDI based X-server available References: <20000120114927.A7819@cygnus.com> Message-ID: Once I get his code I will take a look at it. Suhaib > > On Thu, Jan 20, 2000 at 11:34:02AM +0100, > hans.de.bok@philips.com wrote: > >The server is compiled, as a project, with Visual C++ > because I don't > >know how to compile programs that use the WIN32 API with Cygwin. > > I am not sure what you mean by this. In general, you > just use "gcc" > to compile a program. There is nothing special required. > > cgf > From cgf@cygnus.com Thu Jan 20 15:15:00 2000 From: cgf@cygnus.com (Chris Faylor) Date: Thu, 20 Jan 2000 15:15:00 -0000 Subject: GDI based X-server available References: <200001191947884.SM00169@KENDALLB> Message-ID: <20000120170020.A9443@cygnus.com> On Thu, Jan 20, 2000 at 02:12:49PM -0500, Suhaib Siddiqi wrote: >I checked the VNC license. The new license is GNU GPL. I have asked >him to e-mail me binaries and his ported code. I will make it >available to public. cygwin-xfree project requirement is that the same >code which was used to compile bianries be available to users from the >same site... of am I not correct Chris? Yep. It's not just a Red Hat requirement... it's the law! cgf From ssiddiqi@inspirepharm.com Fri Jan 21 03:59:00 2000 From: ssiddiqi@inspirepharm.com (Suhaib Siddiqi) Date: Fri, 21 Jan 2000 03:59:00 -0000 Subject: GDI based X-server available References: <0056890008065490000002L902*@MHS> Message-ID: Hi Hans, Thanks for binaries. I will have look at it. However, I could not put your work on cygwin-xfree server unless I have access to the same source code you used to make the binaries. If you are on a direct Internet conect (i.e. not a modem) size of the attachment is not issue. I got a plenty of space on my mail server for me and can accept up to 1GB attachments. The fonts problem is xfree on Sourceware is because certain OS do not like the gzipped fonts. This is not the cygwin-xfree pre-alpha releases issue. It is a well known out-standing bug in Xfree86 source code. All you need to do cd to every fonts directory and run the gunzip *.gz command to decompress them, then run mkfontdir.exe in each fonts directory. Suhaib > -----Original Message----- > From: hans.de.bok@philips.com > [ mailto:hans.de.bok@philips.com ] > Sent: Friday, January 21, 2000 4:02 AM > To: ssiddiqi@inspirepharm.com > Subject: RE: GDI based X-server available > > << File: MEMO 01_21_00 09_59_47.txt >> << File: xvnc-0.1.zip >> > << File: main.zip >> -------------- next part -------------- A non-text attachment was scrubbed... Name: winmail.dat Type: application/vnd.ms-tnef Size: 2376 bytes Desc: not available URL: From ssiddiqi@inspirepharm.com Mon Jan 24 05:26:00 2000 From: ssiddiqi@inspirepharm.com (Suhaib Siddiqi) Date: Mon, 24 Jan 2000 05:26:00 -0000 Subject: GDI based X-server available References: <0056890008088403000002L932*@MHS> Message-ID: <200001241325.IAA12756@inspire.inspirepharm.com> Hans, Thanks. It works now. I noticed you hard coded the path /usr/lib for searching fonts and RGB file. Normally X11R6 stuff is installed in /usr/X11R6. It would be nice if you can modify the code so it works in fullscreen mode? I will put the binary plus source code of you GDI/XVNC based server on cygwin-xfree Home page for end-users. Suhaib -----Original Message----- From: hans.de.bok@philips.com To: Date: Mon, 24 Jan 2000 08:38:29 +0100 Subject: RE: GDI based X-server available >>I cannot get your xvnc binary to work on my NT 4.0 SP 6a work. I >>tried it with your fonts and mines too, but in both cases it flashes >>on the screen with "initallizing screen..." and disappers. > >>I will have a look at source code over the weekend. It seems to me >>a DLL initializatuion which causes xvnc to fail to initialize >>properly. > >I attached a new executable, now error messages are shown in a >messagebox, >this might give you a clue about what the problem can be. Please >remember >that the server is looking for fonts on the same drive as where you >put >the executable. So if Xvnc is in d:/xvnc the fonts should be in >d:/usr/lib/X11/fonts/misc. > >Hope this helps ! > >Hans > > From ssiddiqi@inspirepharm.com Mon Jan 24 13:23:00 2000 From: ssiddiqi@inspirepharm.com (Suhaib Siddiqi) Date: Mon, 24 Jan 2000 13:23:00 -0000 Subject: GDI based X-server available References: <0056890008075901000002L912*@MHS> Message-ID: I have uploaded to ftp://sourceware.cygnus.com/pub/cygwin/xfree Hans GDI X-server. The precompiled binary is: xvnc-win32.tar.bz2 and the sources for his server is in archive: xvnc-win-src.tar.bz2 Install the binaries in /usr/bin. Any questions and comments should be addressed to Hans de Bok at hans.de.bok@philips.com and cc to the cugwin-xfree@souirceware.cygnus.com. I am still waiting to hear from Karra about his DirectX based fullscreen server. No new news about it at the moment. Suhaib -------------- next part -------------- A non-text attachment was scrubbed... Name: winmail.dat Type: application/vnd.ms-tnef Size: 1868 bytes Desc: not available URL: From mattl@d2k.com Tue Jan 25 20:41:00 2000 From: mattl@d2k.com (Matt Lewandowsky) Date: Tue, 25 Jan 2000 20:41:00 -0000 Subject: XServer Woes Message-ID: <9569BB51CAE7D211AB9C0090273CB759387FA6@unknown.d2k.com> OK. I've taken the plunge and tried to run John Fortin's GGI/DX server under NT. However, I get the following when I try to run it: bash-2.02$ PEXExtensionInit: Couldn't open default PEX font file Roman_Merror opening security policy file /usr/X11R6/lib/X11/xserver/SecurityPolicy Fatal server error: could not open default font 'fixed' [1]+ Exit 1 ggiserver What am I doing wrong, since I'm fairly convinced that it is (yet again) my fault? I didn't see anything when I tried to RTFM. I even searched the digests that I keep archived in Outlook. I'm trying to remember the default locations for XF86, but it's been too long since I've had font issues like this... I think I'm looking in the right places... :( Thanks, --Matt P.S. In /usr/X11R6/lib/fonts/PEX, I have Roman.phont and Roman_M.phont, as well as a fonts.dir. But I cannot find the fixed font. :( I've already run mkfontdir in the /usr/X11R6/lib/fonts/* directories. P.P.S. I'm fairly impressed with the VNC-based X server. I mainly tried it out to see if it would run on NT without crashing my VNC server that I use to connect from home with. It's much faster (for my Eterms exported on the LAN) than Exceed, and it gives about the same number of errors, but the trade-off is the resolution: I can live with the 16 colors it gives (after all, I usually restrict my VNC sessions to 8-bit anyway, so no real color loss...), but I wish there were a way to specify a higher resolution... Running at 800x600 leaves a lot of wasted space on my 1280x1024 screen when I have a lot of serious X'ing to do. Just a wish that I'm sure has already been added to a TODO list... :) -- Matt Lewandowsky Jr. UNIX Systems Administrator, D2K Inc. mattl@d2k.com < mailto:mattl@d2k.com > 408-487-8897 The man with a new idea is a crank until the idea succeeds. - Mark Twain From ssiddiqi@inspirepharm.com Thu Jan 27 06:58:00 2000 From: ssiddiqi@inspirepharm.com (Suhaib Siddiqi) Date: Thu, 27 Jan 2000 06:58:00 -0000 Subject: XServer Woes References: <9569BB51CAE7D211AB9C0090273CB759387FA6@unknown.d2k.com> Message-ID: Have fonts in /usr/X11R6/lib/X11/fonts/misc gunziped them mkfontdri should fix it. Suhaib > -----Original Message----- > From: cygwin-xfree-owner@sourceware.cygnus.com > [ mailto:cygwin-xfree-owner@sourceware.cygnus.com]On Behalf Of Matt > Lewandowsky > Sent: Tuesday, January 25, 2000 11:41 PM > To: Cygwin-XFree Mailing List (E-mail) > Subject: XServer Woes > > > OK. I've taken the plunge and tried to run John Fortin's > GGI/DX server > under NT. However, I get the following when I try to run it: > > bash-2.02$ PEXExtensionInit: Couldn't open default PEX font file > Roman_Merror opening security policy file > /usr/X11R6/lib/X11/xserver/SecurityPolicy > > Fatal server error: > could not open default font 'fixed' > > [1]+ Exit 1 ggiserver > > What am I doing wrong, since I'm fairly convinced that it > is (yet again) > my fault? I didn't see anything when I tried to RTFM. I > even searched > the digests that I keep archived in Outlook. I'm trying > to remember the > default locations for XF86, but it's been too long since > I've had font > issues like this... I think I'm looking in the right places... :( > > Thanks, > > --Matt > > P.S. In /usr/X11R6/lib/fonts/PEX, I have Roman.phont and > Roman_M.phont, > as well as a fonts.dir. But I cannot find the fixed font. :( I've > already run mkfontdir in the /usr/X11R6/lib/fonts/* directories. > > P.P.S. I'm fairly impressed with the VNC-based X server. > I mainly tried > it out to see if it would run on NT without crashing my > VNC server that > I use to connect from home with. It's much faster (for my Eterms > exported on the LAN) than Exceed, and it gives about the > same number of > errors, but the trade-off is the resolution: I can live > with the 16 > colors it gives (after all, I usually restrict my VNC > sessions to 8-bit > anyway, so no real color loss...), but I wish there were a way to > specify a higher resolution... Running at 800x600 leaves > a lot of wasted > space on my 1280x1024 screen when I have a lot of serious > X'ing to do. > Just a wish that I'm sure has already been added to a > TODO list... :) > > -- > Matt Lewandowsky > Jr. UNIX Systems Administrator, D2K Inc. > mattl@d2k.com < mailto:mattl@d2k.com > 408-487-8897 > The man with a new idea is a crank > until the idea succeeds. - Mark Twain From mattl@d2k.com Thu Jan 27 08:33:00 2000 From: mattl@d2k.com (Matt Lewandowsky) Date: Thu, 27 Jan 2000 08:33:00 -0000 Subject: XServer Woes Message-ID: <9569BB51CAE7D211AB9C0090273CB75938802F@unknown.d2k.com> Same problem. :( Also, the first time I try to run it after logging into the window station gives an error stating that a memory location could not be "read". (Quotes from NT.) Has anyone gotten it working in NT? --Matt -----Original Message----- From: Suhaib Siddiqi [ mailto:ssiddiqi@inspirepharm.com ] Sent: Thursday, January 27, 2000 6:51 AM To: Matt Lewandowsky; Cygwin-XFree Mailing List (E-mail) Subject: RE: XServer Woes Have fonts in /usr/X11R6/lib/X11/fonts/misc gunziped them mkfontdri should fix it. Suhaib > -----Original Message----- > From: cygwin-xfree-owner@sourceware.cygnus.com > [ mailto:cygwin-xfree-owner@sourceware.cygnus.com]On Behalf Of Matt > Lewandowsky > Sent: Tuesday, January 25, 2000 11:41 PM > To: Cygwin-XFree Mailing List (E-mail) > Subject: XServer Woes > > > OK. I've taken the plunge and tried to run John Fortin's > GGI/DX server > under NT. However, I get the following when I try to run it: > > bash-2.02$ PEXExtensionInit: Couldn't open default PEX font file > Roman_Merror opening security policy file > /usr/X11R6/lib/X11/xserver/SecurityPolicy > > Fatal server error: > could not open default font 'fixed' > > [1]+ Exit 1 ggiserver > > What am I doing wrong, since I'm fairly convinced that it > is (yet again) > my fault? I didn't see anything when I tried to RTFM. I > even searched > the digests that I keep archived in Outlook. I'm trying > to remember the > default locations for XF86, but it's been too long since > I've had font > issues like this... I think I'm looking in the right places... :( > > Thanks, > > --Matt > > P.S. In /usr/X11R6/lib/fonts/PEX, I have Roman.phont and > Roman_M.phont, > as well as a fonts.dir. But I cannot find the fixed font. :( I've > already run mkfontdir in the /usr/X11R6/lib/fonts/* directories. > > P.P.S. I'm fairly impressed with the VNC-based X server. > I mainly tried > it out to see if it would run on NT without crashing my > VNC server that > I use to connect from home with. It's much faster (for my Eterms > exported on the LAN) than Exceed, and it gives about the > same number of > errors, but the trade-off is the resolution: I can live > with the 16 > colors it gives (after all, I usually restrict my VNC > sessions to 8-bit > anyway, so no real color loss...), but I wish there were a way to > specify a higher resolution... Running at 800x600 leaves > a lot of wasted > space on my 1280x1024 screen when I have a lot of serious > X'ing to do. > Just a wish that I'm sure has already been added to a > TODO list... :) > > -- > Matt Lewandowsky > Jr. UNIX Systems Administrator, D2K Inc. > mattl@d2k.com < mailto:mattl@d2k.com > 408-487-8897 > The man with a new idea is a crank > until the idea succeeds. - Mark Twain From fortinj@attglobal.net Thu Jan 27 09:02:00 2000 From: fortinj@attglobal.net (John Fortin) Date: Thu, 27 Jan 2000 09:02:00 -0000 Subject: XServer Woes References: <9569BB51CAE7D211AB9C0090273CB759388033@unknown.d2k.com> Message-ID: <38907A26.8857D6B2@attglobal.net> Matt Lewandowsky wrote: > Do you have any tips on the font issues? I'm hoping to only have to use > Exceed for XDMCP broadcasts and queries. I've been using the VNC-based > server lately because all the commercial servers seem to have problems > with IE5 on Solaris. All the buttons are pink and they don't recognise > when it refreshes its windows. > You did run mkfontdir in each font directory?? > > P.S. I was wondering if you plan on making a statically linked version > for those without Cygwin. Or even if it's possible... I know that our > DBA (who sits next to me), for one, doesn't need all of its > functionality. (Such as everything else in the program folder.) It will not happen until we get mingw versions of XGGI and X11 libs. John From siddiqis@ipass.net Thu Jan 27 09:19:00 2000 From: siddiqis@ipass.net (Suhaib M. Siddiqi) Date: Thu, 27 Jan 2000 09:19:00 -0000 Subject: XServer Woes References: <9569BB51CAE7D211AB9C0090273CB75938802F@unknown.d2k.com> Message-ID: > Same problem. :( Also, the first time I try to run it after logging into > the window station gives an error stating that a memory location could > not be "read". (Quotes from NT.) Has anyone gotten it working in NT? > Yes, I had it working on NT. So did John Fortin. Try unzipping all the fonts in all the fonts directories in /usr/X11R6/lib/X11/fonts and then run mkfontdir in each subdirectory. Is your /usr/X11R6 installation on a C:\drive? If not then /usr directory can be mounted to /usr. Suhaib > --Matt > > > > -----Original Message----- > From: Suhaib Siddiqi [ mailto:ssiddiqi@inspirepharm.com ] > Sent: Thursday, January 27, 2000 6:51 AM > To: Matt Lewandowsky; Cygwin-XFree Mailing List (E-mail) > Subject: RE: XServer Woes > > > > > Have fonts in /usr/X11R6/lib/X11/fonts/misc gunziped them mkfontdri > should fix it. > > Suhaib > > -----Original Message----- > > From: cygwin-xfree-owner@sourceware.cygnus.com > > [ mailto:cygwin-xfree-owner@sourceware.cygnus.com]On Behalf Of Matt > > Lewandowsky > > Sent: Tuesday, January 25, 2000 11:41 PM > > To: Cygwin-XFree Mailing List (E-mail) > > Subject: XServer Woes > > > > > > OK. I've taken the plunge and tried to run John Fortin's > > GGI/DX server > > under NT. However, I get the following when I try to run it: > > > > bash-2.02$ PEXExtensionInit: Couldn't open default PEX font file > > Roman_Merror opening security policy file > > /usr/X11R6/lib/X11/xserver/SecurityPolicy > > > > Fatal server error: > > could not open default font 'fixed' > > > > [1]+ Exit 1 ggiserver > > > > What am I doing wrong, since I'm fairly convinced that it > > is (yet again) > > my fault? I didn't see anything when I tried to RTFM. I > > even searched > > the digests that I keep archived in Outlook. I'm trying > > to remember the > > default locations for XF86, but it's been too long since > > I've had font > > issues like this... I think I'm looking in the right places... :( > > > > Thanks, > > > > --Matt > > > > P.S. In /usr/X11R6/lib/fonts/PEX, I have Roman.phont and > > Roman_M.phont, > > as well as a fonts.dir. But I cannot find the fixed font. :( I've > > already run mkfontdir in the /usr/X11R6/lib/fonts/* directories. > > > > P.P.S. I'm fairly impressed with the VNC-based X server. > > I mainly tried > > it out to see if it would run on NT without crashing my > > VNC server that > > I use to connect from home with. It's much faster (for my Eterms > > exported on the LAN) than Exceed, and it gives about the > > same number of > > errors, but the trade-off is the resolution: I can live > > with the 16 > > colors it gives (after all, I usually restrict my VNC > > sessions to 8-bit > > anyway, so no real color loss...), but I wish there were a way to > > specify a higher resolution... Running at 800x600 leaves > > a lot of wasted > > space on my 1280x1024 screen when I have a lot of serious > > X'ing to do. > > Just a wish that I'm sure has already been added to a > > TODO list... :) > > > > -- > > Matt Lewandowsky > > Jr. UNIX Systems Administrator, D2K Inc. > > mattl@d2k.com < mailto:mattl@d2k.com > 408-487-8897 > > The man with a new idea is a crank > > until the idea succeeds. - Mark Twain From siddiqis@ipass.net Thu Jan 27 09:22:00 2000 From: siddiqis@ipass.net (Suhaib M. Siddiqi) Date: Thu, 27 Jan 2000 09:22:00 -0000 Subject: XServer Woes References: <38907A26.8857D6B2@attglobal.net> Message-ID: > > > Matt Lewandowsky wrote: > > > Do you have any tips on the font issues? I'm hoping to only have to use > > Exceed for XDMCP broadcasts and queries. I've been using the VNC-based > > server lately because all the commercial servers seem to have problems > > with IE5 on Solaris. All the buttons are pink and they don't recognise > > when it refreshes its windows. > > > > You did run mkfontdir in each font directory?? > > > > > > P.S. I was wondering if you plan on making a statically linked version > > for those without Cygwin. Or even if it's possible... I know that our > > DBA (who sits next to me), for one, doesn't need all of its > > functionality. (Such as everything else in the program folder.) > > It will not happen until we get mingw versions of XGGI and X11 libs. Use Hans XGDI server based upon XVNC. I got his fullscreen version. In North Carolina life is dead after getting hit by 3 feets of snow in one nite. After testing I will upload Hans fulsscreen XGDI server next week. XGDI at the moment does not use Cygwin1.dll. But NOTE that XGDI has borrowed code from XVNC therefore XVNC GPL license applies to it. The binaries and soruces are at ftp://sourceware.cygnus.com/cygwin/xfree Suhaib > > John From ssiddiqi@inspirepharm.com Mon Jan 31 09:16:00 2000 From: ssiddiqi@inspirepharm.com (Suhaib Siddiqi) Date: Mon, 31 Jan 2000 09:16:00 -0000 Subject: XGDI/XVNC server new version now available!!! Message-ID: The new version of Hans de Bok's XGDI server based upon XVNC is available now for download from: ftp://sourceware.cygnus.com/cygwin/xfree You will need: 1) xvnc-win32.tar.bz2 (binaries only) 2) xvnc-win-src.tar.bz2 (source code only) This server has AT&T VNC code borrowed therefore GPL for AT&T VNC license applies on all the code under programs/Xserver/hw/vnc subdirectory. The binaries are not linked to cygwin1.dll. This version does not use any code from xfree86 (programs/Xserver/hw/xfree86) therefore does not classify as a port of xfree86 to Win32. This newest version offers fullscreen capabilities. Please read the README file in xvnc-win32.tar.bz2. Anyone willing to take up the task of adding multi-windowing capbilities? Thanks to Hans de Bok for great work. Also thanks to other developers who are contributing to Cygwin Win32 X-server development. Still to come Karra's DirectX server for xfree86!!! Lately he hadd been very busy with work therefore his DirectX server had been delayed. Suhaib From siddiqis@ipass.net Mon Jan 31 18:01:00 2000 From: siddiqis@ipass.net (Suhaib M. Siddiqi) Date: Mon, 31 Jan 2000 18:01:00 -0000 Subject: XGDI/XVNC server is broken on Win2k References: Message-ID: Andrew, Sorry about the bounced message. Could you forward the header of the bounced message to me at siddiqis@ipass.net so I can fix the problem at the SMTP server? Our server rejects almost all the free web-based mail services. This is to reduce spam. XGDI has nothing to do with DirectX. It uses old M$ GDI (gdi32.lib and kernel32.lib). However, I had not tested it on Win2K therefore I could not say it would/wount not work. It does work on Win95/98 and NT 4.0 with SP6a. Could you send exact error message you get when XGDI server crashes? On The Red Hat (Cygnus) Sourceware server you would find the sources for XGDI. They include MSVC 6.0 project files. If you have MSVC 6.0 compiler, you might consider recompiling it on Win2K. Perhaps that help. I apologize for the incomplete ftp address. The corect URLs are, as you posted: Source ftp://sourceware.cygnus.com/pub/cygwin/xfree/xvnc-win-src.tar.bz2 Binary ftp://sourceware.cygnus.com/pub/cygwin/xfree/xnvc-win32.tar.bz2 I am cc'ing to cygwin list. Hans could answer your questions. It is his code. Regards Suhaib > -----Original Message----- > From: owner-devel@XFree86.Org [ mailto:owner-devel@XFree86.Org]On Behalf > Of Andrew van der Stock > Sent: Monday, January 31, 2000 8:06 PM > To: Xfree86-Devel > Subject: RE: XGDI/XVNC server is broken on Win2k > > > FYI, the binary package does not run on Windows 2000 (which uses DirectX > 7.0). I tried sending mail to Suhaib, but his mailer is broken > and rejected > my message. > > Andrew