public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Russell K. Thompson II" <rkthomps@students.uwf.edu>
To: tolj@uni-duesseldorf.de
Cc: Michael Hirmke <mh@mike.franken.de>, cygwin@sourceware.cygnus.com
Subject: Re: Freeciv Binaries
Date: Wed, 31 Mar 1999 19:45:00 -0000	[thread overview]
Message-ID: <36E870BD.4185C056@students.uwf.edu> (raw)
Message-ID: <19990331194500.U5u4jMaPsYb_H4KV4KNHAOYFCqQA2mhEtYxuq2f9w-0@z> (raw)
In-Reply-To: <36E859BA.402A@uni-duesseldorf.de>

Stipe Tolj wrote:
> 
> Michael Hirmke wrote:
> >
> > Hi Russell,
> >
> > >       I was wondering if anyone has been able to run the freeciv binaries
> > >available from
> > > ftp://ftp.franken.de/pub/win32/develop/gnuwin32/cygwin/porters/Weiser_Michael
> > >/B20/ on Windows 95.  My server will run fine but when I run the client I get
> >
> > As the README states:
> >
> >    - system
> >      - WinNT 4.0 SP3 with cygwin B20.1 and egcs-1.1.1
> >
> > it hasn't been tested on any Win9x system.
> >
> 
> I had ported FreeCIV some time ago under b19 and b20 on Win98 and both
> server and client were working quite fine, even for some 2 hour sessions
> (using X-Win32 from StarNet).
> 
> I may put my port as binary and source form to our project's web site if
> there is interest.

I am very interested.  I would greatly appreciate it if you would make
these
available.

> 
> Regards,
> Stipe
> 
> --
> Stipe Tolj <tolj@uni-duesseldorf.de>
> 
> Cygwin Porting Project -- "We build UNIX on top of Windows"
> http://www.student.uni-koeln.de/cygwin
> 
> Department of Economical Computer Science
> University of Cologne, Germany
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com


  reply	other threads:[~1999-03-31 19:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-11 12:03 Russell K. Thompson II
     [not found] ` < 36E82137.95FAF831@students.uwf.edu >
1999-03-11 14:48   ` Michael Hirmke
1999-03-11 16:02     ` Stipe Tolj
1999-03-11 17:42       ` Russell K. Thompson II [this message]
     [not found]         ` < 36E870BD.4185C056@students.uwf.edu >
1999-03-11 20:13           ` Todd Goodman
1999-03-31 19:45             ` Todd Goodman
1999-03-31 19:45         ` Russell K. Thompson II
1999-03-31 19:45       ` Stipe Tolj
     [not found]     ` < 7Ced7NPppfB@mike.franken.de >
1999-03-11 20:02       ` Todd Goodman
1999-03-31 19:45         ` Todd Goodman
1999-03-31 19:45     ` Michael Hirmke
1999-03-12  7:11   ` Michael Weiser
1999-03-31 19:45     ` Michael Weiser
1999-03-12  9:40   ` Michael Weiser
     [not found]     ` < 36ea4933.31841385@mail.weiser.saale-net.de >
1999-03-13 13:39       ` X11R6.4 Pierre A. Humblet
     [not found]         ` < 3.0.5.32.19990313164119.00845e50@pop.ne.mediaone.net >
1999-03-14  4:51           ` X11R6.4 Michael Weiser
1999-03-31 19:45             ` X11R6.4 Michael Weiser
1999-03-31 19:45         ` X11R6.4 Pierre A. Humblet
1999-03-31 19:45     ` Freeciv Binaries Michael Weiser
1999-03-31 19:45 ` Russell K. Thompson II

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=36E870BD.4185C056@students.uwf.edu \
    --to=rkthomps@students.uwf.edu \
    --cc=cygwin@sourceware.cygnus.com \
    --cc=mh@mike.franken.de \
    --cc=tolj@uni-duesseldorf.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).