Extract.exe source code
Can someone assure me that the source for extract.exe is included in the cygwin-xfree source code before I pull it down? I have the archived binary distribution of cygwin-xfree 4.1.0, but I didn't hold on to the extract.exe when I archived these. Now, unfortunately, the extract.exe available appears to have been built to a new version of the cygwin.dll (as appears to have the entire distribution. The way this is done doesn't seem to be tracked very well), and as you can tell, I do not have broadband access to upgrade my Cygwin distribution. If someone has an extract.exe that will work with the a Cygwin distribution for the following system, could they point me to where I could get it? snip $ uname -a CYGWIN_NT-5.0 TOKYO 1.1.8(0.34/3/2) 2001-01-31 10:08 i686 unknown /snip Thanks in advance, Shaddy
RE: How do I run it?
Finally getting back to this after a very busy week. http://xfree86.cygwin.com/docs/ug/ The User's Guide tells you how to install Cygwin/XFree86, including the startup batch files and shell scripts. I can guarantee that you will not be successful in installing Cygwin/XFree86 until you follow those instructions. Got it. It turns out I had muddled through steps 1-5, but not 6-8. I have now extracted the startup scripts, and subsequently tried all 3 startup methods from Chapter 4, without success. There seems to be some kind of problem in getting the X server to start. startxwin.bat in a command window says startxwin.bat - Starting on Windows 95/98/Me then a window titled xterm appears. After a few seconds a window titled twm appears, then both close. After a few more seconds this appears in the command window, followed by the command prompt: /USR/X11R6/BIN/XSETROOT: unable to open display '127.0.0.1:0.0' startxwin.sh in a bash window says X connection to 127.0.0.1:0.0 broken (explicit kill or server shutdown). and the prompt appears, followed a few seconds later by this message: xterm Xt error: Can't open display: 127.0.0.1:0.0 startx in a bash window says xinit: not found
RE: How do I run it?
Perry, Take a look at /tmp/XWin.log... my suspicion is that you goofed on installing the fonts. Harold -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Perry Hutchison Sent: Saturday, April 20, 2002 5:51 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: How do I run it? Finally getting back to this after a very busy week. http://xfree86.cygwin.com/docs/ug/ The User's Guide tells you how to install Cygwin/XFree86, including the startup batch files and shell scripts. I can guarantee that you will not be successful in installing Cygwin/XFree86 until you follow those instructions. Got it. It turns out I had muddled through steps 1-5, but not 6-8. I have now extracted the startup scripts, and subsequently tried all 3 startup methods from Chapter 4, without success. There seems to be some kind of problem in getting the X server to start. startxwin.bat in a command window says startxwin.bat - Starting on Windows 95/98/Me then a window titled xterm appears. After a few seconds a window titled twm appears, then both close. After a few more seconds this appears in the command window, followed by the command prompt: /USR/X11R6/BIN/XSETROOT: unable to open display '127.0.0.1:0.0' startxwin.sh in a bash window says X connection to 127.0.0.1:0.0 broken (explicit kill or server shutdown). and the prompt appears, followed a few seconds later by this message: xterm Xt error: Can't open display: 127.0.0.1:0.0 startx in a bash window says xinit: not found
Re: [ANNOUNCEMENT] cygwin/xfree86 setup.exe packages available for comments and testing
Robert Collins wrote: -Original Message- From: Charles Wilson [mailto:[EMAIL PROTECTED]] Sent: Saturday, April 20, 2002 12:59 PM Also, setup must do the following (even without new 'views' and whatnot) Setup should already do that, why not make a test setup.ini and see what happens :]. It's all data driven and there is no requirement for -src packages to follow the same name as the base. Whaddaya know. It works. point setup.exe here: http://www.neuro.gatech.edu/users/cwilson/cygutils/testing/ There are 3 packages, bob, bobx, and boby. only bob has a -src package, the other two have source: lines that explicitly specify bob's source package. It seems to work perfectly -- with only a single niggle: if you select the source for more than one of [bob|bobx|boby], then it is downloaded only once (good) but is unpacked three times. This isn't a terrible thing, but it is a waste of effort If you play around with this, you can clean up by uninstalling the binary packages, and deleting the file /usr/src/bob.file.src. (Or, you can delete /bob.file, /bobx.file, /boby.file, and /usr/src/bob.file.src, and remove the bob, bobx, and boby entries from /etc/setup/installed.db) So, except for the niggle above, if upset were modified to allow the external-src: keyword, then multiple-binary-packages from one -src package would work! (and the niggle isn't a show stopper). --Chuck
Re: info: single install xfree86 + minimal cygwin?
On Tue, Apr 09, 2002 at 09:53:34PM -0400, Christopher Faylor wrote: On Tue, Apr 09, 2002 at 06:34:29PM -0700, Ian Burrell wrote: Is the script for building setup.ini files from a directory hierarchy available anywhere? I want to setup a test install directory with the full hierarchy and setup.hint files. Also, I ran into a problem with the xfree-fonts-100dpi and xfree-fonts-75dpi packages. With a hand-generated setup.ini, they weren't being displayed. This might be because the last component starts with a number and something is confused about where the version starts. Yes, a -75dpi part of a tar file will look like a version number. Can you use an underscore instead? Btw, the new version of 'upset' does the right thing with things like this. If you have a directory called 'XFree86-fonts-100dpi' it will no longer assume that 100dpi is part of the version string. It just uses the directory name as a prefix for the .tar.bz2 files. cgf
RE: How do I run it?
Take a look at /tmp/XWin.log... my suspicion is that you goofed on installing the fonts. No font complaints, but it evidently won't run with the standard VGA display driver. /tmp/XWin.log says: winInitializeDefaultScreens () - w 640 h 480 _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root winDetectSupportedEngines () - Windows 95/98/Me winDetectSupportedEngines () - DirectDraw not installed winSetEngine () - Using Shadow GDI DIB winAdjustVideoModeShadowGDI () - Using Windows display depth of 1 bits per pixel winScreenInit () - Unsupported display depth: 1 Change your Windows display depth to 15, 16, 24, or 32 bits per pixel. winScreenInit () - Supported depths: 8080c080 Fatal server error: Couldn't add screen 0 but the only choices available in display properties are 16-color (selected) and monochrome. Time to drag out the Win 95 CD and see what might work with a Trident TGUI9440-3
RE: info: single install xfree86 + minimal cygwin?
Chris, Btw, the new version of 'upset' does the right thing with things like this. If you have a directory called 'XFree86-fonts-100dpi' it will no longer assume that 100dpi is part of the version string. It just uses the directory name as a prefix for the .tar.bz2 files. That's good for completeness. But I am a stickler for tradition, so I stuck with the old -f100 package name in that case. :) Harold
RE: xfree86 install makes wininit not working
Robert, Hmm. What happens if you supply a (say) 16Kb subset of the wininit.ini file to windows ME - does it process it correctly? Rob Hi Rob, Renaming is done - but now renamed file haved 8.3 names with ~ and are unusable, I think, by X, since names are incorrect - too bad. What's your prognosis on this? Is this a problem that is specific to Sylvain's machine or is this going to be a problem because Cygwin/XFree86 has over 4000 files in the font directories? Is there some limit to the allowed size of wininit.ini, or did you suggest testing a subset simply to see if one of the commands in the latter part of the file was invalid? Basically: do we need to pull the Cygwin/XFree86 setup.exe release for now, or can I go on with making changes to the web page, etc to announce the release? Harold
Re: info: single install xfree86 + minimal cygwin?
On Sat, Apr 20, 2002 at 08:01:12PM -0400, Harold Hunt wrote: Btw, the new version of 'upset' does the right thing with things like this. If you have a directory called 'XFree86-fonts-100dpi' it will no longer assume that 100dpi is part of the version string. It just uses the directory name as a prefix for the .tar.bz2 files. That's good for completeness. But I am a stickler for tradition, so I stuck with the old -f100 package name in that case. :) That's fine. I was just mentioning this for the archives. I think that the new 'upset' behavior allows a lot more flexibility in naming. cgf
Re: xfree86 install makes wininit not working
On Sun, Apr 21, 2002 at 12:59:26PM +1000, Robert Collins wrote: What's your prognosis on this? Is this a problem that is specific to Sylvain's machine or is this going to be a problem because Cygwin/XFree86 has over 4000 files in the font directories? I haven't come to a root cause yet. Have you actually duplicated the problem, Robert? Maybe I've missed something but I don't think I've seen an indication that this isn't just a Wine problem. cgf
RE: xfree86 install makes wininit not working
-Original Message- From: Christopher Faylor [mailto:[EMAIL PROTECTED]] Sent: Sunday, April 21, 2002 1:15 PM To: [EMAIL PROTECTED] Subject: Re: xfree86 install makes wininit not working On Sun, Apr 21, 2002 at 12:59:26PM +1000, Robert Collins wrote: What's your prognosis on this? Is this a problem that is specific to Sylvain's machine or is this going to be a problem because Cygwin/XFree86 has over 4000 files in the font directories? I haven't come to a root cause yet. Have you actually duplicated the problem, Robert? Maybe I've missed something but I don't think I've seen an indication that this isn't just a Wine problem. The user reported the problem as being under Windows ME. Rob
RE: How do I run it?
I don't know that the Windows 95 CD will be of help, but I found Trident's page for the card: http://www.tridentmicro.com/drivers/download/tgui9440.html The Windows 95 driver is here: http://www.tridentmicro.com/drivers/download/tgui_tvga/w95-9440.exe Hope that helps. Let me know if this fixes the problem. Yes, that fixes it. The Trident SVGA driver on the original Windows 95 (OSR2) CD works after a fashion, but the version 4.something from this download is considerably better. I was amazed to discover that the ancient unknown-origin monitor I've been using handles 1024x768 with no trouble :) I've still got some xauth issues to work through when connecting from other hosts, but that's generic X rather than CygWin/XFree. Now to track down a CygWin port of fvwm2 ...
open-file replacements with win9x
We've got a problem folks: From MSDN === To rename or delete a file on Windows 95/98/Me Check for the existence of the WININIT.INI file in the Windows directory. If WININIT.INI exists, open it and add new entries to the existing [rename] section. If the file does not exist, create the file and create a [rename] section. Add lines of the following format to the [rename] section: DestinationFileName=SourceFileName Both DestinationFileName and SourceFileName must be short file names. To delete a file, use NUL as the value for DestinationFileName. === Note that both files must be shortnames. I had _assumed_ that the OS would preserve the attached long file name. But (as the list records show)... I had not been able to test it to see that this was indeed the behaviour we would get. If anyone with a 16 bit windows box out there has the time to do some test cases and see if my assumption was wrong, or if the current reported case was a fluke that went wrong, that would be great. As to _why_ 600 odd files needed replacing, I've yet to look closely at that aspect. Rob
