Running WG as NT Service

[hiwayman]

I am trying to re-install a wg system that has been off line for many years. I set up the WG to run an an NT service, and have set the service to allow it to interact with the desktop, but it does not. Have I forgotten something.

Thanks

[Toyduck]

I am trying to re-install a wg system that has been off line for many years. I set up the WG to run an an NT service, and have set the service to allow it to interact with the desktop, but it does not. Have I forgotten something.

Thanks

No, I do not believe it was ever programed with an interface to use when it was run as a service. When I first used it I used to have it in my user's start menu option, then modified the NT 4 registry to have the user auto logon when ever the system went through a re-boot.

Now I just run it as a service under Win Server 2003.

Now I could be wrong if any out there cares to correct me!

TD

[hiwayman]

I remember in the past having the status console show up when worldgroup was run as a service. The more that I think about it, I think that there was a change in the registry that had to be done manually in addition to setting the service to interact with the desktop. I remember talking to someone at galacticomm and getting the procedure. I will continue looking through my notes to see if I can find it.

[Toyduck]

I remember in the past having the status console show up when worldgroup was run as a service. The more that I think about it, I think that there was a change in the registry that had to be done manually in addition to setting the service to interact with the desktop. I remember talking to someone at galacticomm and getting the procedure. I will continue looking through my notes to see if I can find it.

That would be nice, I modified the registry to get the old style status window, which I like to use and do use on my test system. Being able to access it on the main server would also be useful.

[frcorey]

no console as a service. in application mode you can run it with the new console or the old dos style console with registry change.

[hiwayman]

I only found part of the notes on the procedure. It was to edit the registry and change the path to the executable from wgsserv.exe to wgsappgo.exe.
there was some other changes to prevent an error message on startup. I could only find reference to the first part, and not the other registry changes. I downloaded a program "alwaysup' and created a service using wgsappgo.exe as the executable and it works fine.

[dspain]

I am trying to re-install a wg system that has been off line for many years. I set up the WG to run an an NT service, and have set the service to allow it to interact with the desktop, but it does not. Have I forgotten something.

Thanks

No, I do not believe it was ever programed with an interface to use when it was run as a service. When I first used it I used to have it in my user's start menu option, then modified the NT 4 registry to have the user auto logon when ever the system went through a re-boot.

Now I just run it as a service under Win Server 2003.

Now I could be wrong if any out there cares to correct me!

TD

yeah the NT service is invisible, no interaction interface, to interact with it use the active-html pages to navigate.

[hiwayman]

I apologize for being a little vague.
When WorldGroup is installed and run as a service using the default WGSSRV.EXE executable to start the service there is no interface. There was a work around given to me allow WorldGroup to be run as a service and have the interface for people who wanted it. The solution that was given to me was as follows,


If you want to run Worldgroup as a service under Windows NT and want the default interface that is present when running Worldgroup from the startup menu the following changes need to be made. If you want to use the DOS console interface, make the following changes to the registry:
HKEY_LOCAL-MACHINE
GALACTICOMM
WORLDGROUP SERVER
CURRENT VERSION
Use Console Window 0x00000000(0)
change this to 0x00000000(1)

To make the interface available when being run as a service make the following changes to the registry


HKEY_LOCAL-MACHINE
SYSTEM
CURRENT CONTROL SET
SERVICES
WGSCONTROL
IMAGE PATH "PATH TO /wgssrv.exe
change to Path to /wgsappgo.exe



In order to prevent the error service not responding to control function, make the following changes to the registry.

This was continued on a second page that I cannot find. We ran Worldgroup with this configuration for several years and had the interface available to us, I just cannot remember what other changes to the registry were made to prevent the startup error.

In order to bypass this problem I downloaded the program alwaysup and used this program to create the service using WGSAPPGO.EXE as the executable. I now have Worldgroup running as a service using Windows 2003 server, and have the interface. If I want to run it as a service without the interface I can always revert back to the original configuration.

Hal

[dspain]

I apologize for being a little vague.
When WorldGroup is installed and run as a service using the default WGSSRV.EXE executable to start the service there is no interface. There was a work around given to me allow WorldGroup to be run as a service and have the interface for people who wanted it. The solution that was given to me was as follows,


If you want to run Worldgroup as a service under Windows NT and want the default interface that is present when running Worldgroup from the startup menu the following changes need to be made. If you want to use the DOS console interface, make the following changes to the registry:
HKEY_LOCAL-MACHINE
GALACTICOMM
WORLDGROUP SERVER
CURRENT VERSION
Use Console Window 0x00000000(0)
change this to 0x00000000(1)

To make the interface available when being run as a service make the following changes to the registry


HKEY_LOCAL-MACHINE
SYSTEM
CURRENT CONTROL SET
SERVICES
WGSCONTROL
IMAGE PATH "PATH TO /wgssrv.exe
change to Path to /wgsappgo.exe



In order to prevent the error service not responding to control function, make the following changes to the registry.

This was continued on a second page that I cannot find. We ran Worldgroup with this configuration for several years and had the interface available to us, I just cannot remember what other changes to the registry were made to prevent the startup error.

In order to bypass this problem I downloaded the program alwaysup and used this program to create the service using WGSAPPGO.EXE as the executable. I now have Worldgroup running as a service using Windows 2003 server, and have the interface. If I want to run it as a service without the interface I can always revert back to the original configuration.

Hal

in version 3.30+ for some god unknown reason running the original control panel like majorbbs/worldgroup dos had it causes lock ups on the console, using another cw3220mt.dll was supposed to be the fix but it didnt (although gcomm said it did) so if you found a working workaround, awesome ill have to look into it although i prefer the server to remain hidden personally, its gonna go good in my new DOCS for wg im gonna release, just some text to help sysops with all the new workarounds,tweaks we been utilizing.

[banjaxster]

I posted a fix for the dos console in the mud sysop forums and now it seems they are gone since i just tried to logon there.Here is the fix:

Use Windows explorer to browse all files in your \winnt folder. Right
click on the file "_default.pif" (it may appear as just "_default"). Under the
"Memory" tab, set the "Initial environment" to 4096. If memory serves, that
should do it for ya.
It has fixed it for me,you may need to reboot the machine.