From: Eric McDonald <mcdonald@phy.cmich.edu>
To: xconq7@sources.redhat.com
Subject: Re: New Xconq Windows Executable
Date: Wed, 27 Aug 2003 16:17:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0308270026080.11752-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <Pine.LNX.4.44.0308262312070.11427-100000@leon.phy.cmich.edu>
On Tue, 26 Aug 2003, Eric McDonald wrote:
>Then find tcl84.dll and tk84.dll and copy them into the
> _same_ directory where xconq.exe is located.
Actually, you can disregard this step unless you are having
problems getting Xconq to run.
I was thinking about something else when I wrote that.
next prev parent reply other threads:[~2003-08-27 4:29 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-27 4:29 Eric McDonald
2003-08-27 16:17 ` Eric McDonald [this message]
2003-08-27 16:37 ` Jim Kingdon
2003-08-27 17:20 ` Eric McDonald
2003-08-27 18:40 ` Hans Ronne
2003-08-27 19:53 ` Eric McDonald
2003-08-28 3:26 ` Hans Ronne
2003-08-28 13:38 ` Juergen Ruehle
2003-08-29 0:44 ` Eric McDonald
2003-08-29 8:35 ` Eric McDonald
2003-08-29 15:22 ` Juergen Ruehle
2003-08-30 5:47 ` Eric McDonald
2003-08-29 9:06 ` Hans Ronne
2003-08-29 15:57 ` Eric McDonald
2003-09-05 4:54 ` Tcl/Tk Interface Unification (was Re: New Xconq Windows Executable) Eric McDonald
2003-09-05 15:06 ` Hans Ronne
2003-09-05 15:51 ` Eric McDonald
2003-09-06 6:05 ` Hans Ronne
2003-09-15 3:43 ` Tcl/Tk Interface Unification Eric McDonald
2003-09-15 3:50 ` Hans Ronne
2003-09-15 14:32 ` Eric McDonald
2003-09-15 18:39 ` Hans Ronne
2003-09-15 19:38 ` Eric McDonald
2003-09-15 23:31 ` Hans Ronne
2003-09-16 13:53 ` Build system overhaul (Was: Tcl/Tk Interface Unification) Juergen Ruehle
2003-09-16 18:15 ` Eric McDonald
2003-09-16 20:23 ` Eric McDonald
2003-09-17 10:32 ` Hans Ronne
2003-09-17 15:54 ` Juergen Ruehle
2003-09-18 2:37 ` Build system overhaul Eric McDonald
2003-09-08 17:46 ` Tcl/Tk Interface Unification (was Re: New Xconq Windows Executable) Eric McDonald
2003-08-27 18:04 New Xconq Windows Executable Bill Macon
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=Pine.LNX.4.44.0308270026080.11752-100000@leon.phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=xconq7@sources.redhat.com \
/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).