mudinfo.net

I don't run the patch but I believe it puts it in
General setup/TCP/IP settings.

Yeah I deleted all the files it overwrites and then copied over and works fine. Just went through the first cleanup and it crashed on one of those files...

An unrecoverable error has occured:
WGSFNDO: CAN'T READ "GALTNTD"


After I click ok, then it seems to load the board up just fine.

I don't know for sure the issue is but here is a couple of troubleshooting steps to try.

First look for GALTNTD in the settings and see if it has a bad setting.
Second look for a file named GALTNTD and see if you can replace it with a better copy.

It's an actual file in the telnet server. So looks like you need to work on the update so more. When you remove the files make sure you removed .MDF and .DMD files.



BOUT THIS MODULE

This module is a drop-in replacement for the standard GALTNTD Telnet Server
that ships with Worldgroup 3.x for NT. This version adds the ability for
the SysOp to configure the port that the server listens for telnet on. In
addition, the SysOp may define a configurable second port for the server
to listen for telnets on.

Don't have any dmd files in any of the wgserv installs I can find that I have installed. Tried deleting all the files manually and copy it over again, and same issue. Also, which one of these options should I select? #2 just crashes with a windows error (Windows don't crash, it just like times out? or something) I've been doing next to the bottom.

Looks like you have two version in there but most likely with different names.

I have zipped up my galtntd* from a working directory of wg 3.30.

Here is my suggestion remove all files with "del galtntd*.*", download galtntd.rar and unzip those into your wg directory. Then try to launch WG.

I have also zipped up my galtnt files. It the telnet client I believe, but thought I offer these up also if you wanted to remove all galtnt* files.

If you get that pop again, that means you have the telnet server files renamed to something else and wg is picking it up. And then it can get messy, you can disable the module in offline utils and see what DMD pops up, and go from there.

Seems like the first file took care of it. Ran a couple cleanups and went smooth. Appreciate it.