A question about ports

Posted by Sapphiremagus on Wed 07 Nov 2001 01:17 AM — 11 posts, 35,818 views.

#0
Real quick question:

Does MushClient support a unix port?
Australia Forum Administrator #1
I take it you mean, "is there a Unix version of MUSHclient"?

No, not at present. The major problem with making such a port is that MUSHclient is coded using the MFC (Microsoft Foundation Class) library, which is a set of proprietary routines (written in C++) for the Microsoft Visual C++ compiler.

Re-doing all of the code using a different set of libraries (string handling, sorting, window-handling, lists, etc.) would take quite a while. It would be possible, and is on my list of things to do "one day".
USA #2
I've tried running MUSHclient with WINE, and had some
small amount of success, except that I can't get it to
connect to anything. Minor problem.

WINE apparently has something to help with porting stuff
over... have you checked that out?

(The Wine webpage is http://www.winehq.com.)
Australia Forum Administrator #3
I had a look but couldn't see anything relevant. Can you give the exact error message?

I am using OpenBSD which doesn't appear to have a WINE port.

Can you access the Internet using other programs under WINE? (eg. Windows telnet).
USA #4
I'm not sure exactly where the Winelib stuff is, there, to
be honest; I'm not a developer, so I never really looked.
:)

Telnet /does/ work properly. MUSHclient resolves the
addresses but doesn't connect, in most cases... it just
keeps trying forever. The only difference comes if I try
to connect to something running on my own machine--it
connects then, but displays nothing, although I can see
the results of things I've done if I watch in another
window. The config window is also wonky, but that's not a
big deal; it's usable, at least.

I'm running Mandrake 8.1 right now, and as far as I know,
the most recent Wine build. There are Wine builds for
FreeBSD at http://panter.soci.aau.dk/~dailywine/.
Australia Forum Administrator #5
Sounds like a problem with the Winsock (Windows Sockets) implementation under Wine.

You could try using VMware, that might work better.

OpenBSD and FreeBSD are not the same, I doubt the port for FreeBSD will work.
USA #6
Wonderful idea, except that VMWare costs money. I don't have much in the way of money, at the moment. Since telnet works, I'm not sure why MUSHclient wouldn't...
Australia Forum Administrator #7
You could try MUSHclient 1.04 from the Downloads page. This is much smaller and simpler, maybe it will work. :)
USA #8
I hadn't even thought about that, figures.

Downloaded 1.04, and it runs like a dream... well, insofar
as 1.04 ever did. On the one hand, it's providing a nice
opportunity to reminisce over the Good Old Days of my
MUSHing career, on the other hand it's reminding me
constantly how far things have come since then.

I don't suppose you archive past versions? It'd be
interesting to see if any of the in-between ones work.

Thank you, by the way, for many years of happy MUSHing,
now that I think about it, Nick. :)
Australia Forum Administrator #9
Quite a few older versions are on the ftp server. I can see 1.04, 2.14, 2.15, 3.00 to 3.06, 3.10 to 3.17.

Just substitute the appropriate version number in the file name and you should be able to download them (eg. mushclient214.exe).
Australia Forum Administrator #10
MUSHclient 3.27 has now been tested successfully under Wine. Note that Wine is an alpha release and it may not work for you, but using the latest release of Wine it seems to work OK with a few quirks.

Currently tested under codeweavers-wine-20020904-7.i386.rpm running under Debian 3.0 "Woody" release, using 4.2.1 of the XFree86 XWindows release.

You need to use the /wine command-line switch to MUSHclient in order to disable certain things (like COM objects and scripting) that don't currently work properly.

eg.


wine mushclient.exe /wine