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
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
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
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
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
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
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
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.
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
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.
-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
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
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
13 matches
Mail list logo