Hi Tobias,

I was wondering why nobody ever replied to my message until I logged on to
Janis Kracht's web site (http://www.filegate.net:8080/) for the first time
ever and saw your reply there.  It never arrived here for some reason.  So
I'm quoting it from the web site:

 > We have Msged in the Husky CVS, and in principle, any Husky developer
 > can work on it. This echo here is surely the best place to report bugs
 > and submit patches.
 > Given that your own programming qualities are proven :-), we could also
 > offer to you a CVS account so that you can submit the patches on your
 > own. To do so, you'd have to get a login at sourceforge.net, and then
 > write to Dmitry Sergienko {at} 2:464/910, who will enable your account
 > for the Husky project.

I've got an account on SF.  My CVS skills are rusty, but I do have it installed.  ;-)

Also, I suspect I probably won't be contributing much to Msged. Although
last time I said that to Paul Edwards I ended up taking over maintaining
the project altogether a year or so later...

If I had lots of free time then I'd probably spend some of it working on a
Windows GUI version of Msged, in Borland C++ Builder (which could be ported
to Kylix), but I don't really see that happening at the moment.

 > I'm curious - which compiler do you use to compile your NT version? I
 > always had big trouble with that one, and the NT version is, from my
 > side, the least tested of all versions.

Borland C++ Builder 3.0 (1998) ideally, which uses basically the same
compiler as the free version that they made available.  I've also got
MSVC++ 6.0, OpenWatcom & Cygwin to test with.  Plus a few others
(lcc-win32, Digital Mars...) probably not worth considering as a target to
port to.

I also have FreeBSD 4.5 & Linux 2.2 (SuSE) machines.

I did eventually get Msged to compile under BCB++.  The main problem is the
SMAPI code - particularly all that _fast/pascal/near/far calling convention
stuff.  I ended up going crazy and removing all the references entirely,
and obviously the code looks a lot cleaner now.  I don't really know why
there's any of the calling convention stuff in there when everybody's using
statically-linked libraries, and nobody is running old 16-bit DOS binaries
any more.  It would make life a hell of a lot easier to maintain the ports
it if all of that junk was ripped out.  

Good to hear from you again,

Regards
Andrew

-- mail{at}ozzmosis.com

--- Msged/NT 6.1.1