Snoopy, it seems you have a habit of checking "yes" when you don't even know what the question was. The installer had a checkbox to enable service support, you checked yes. Apparently, you have no idea what a service is. Doing such things is bad. If "service support" meant "delete everything on your harddrive" you'd have a serious problem right now. If you don't know what something is, don't do it!
When Unreal runs in service mode, then of course there is no interface, that's what a service is! It runs in the background. If you want to see the interface then open a command prompt, cd to the Unreal directory and type:
unreal stop
unreal uninstall
wircd
Just my 2 cents as a a non-coding Unreal +Windows user, after having finally figured out how to setup 3.2 along comes 3.2.1 with module support. "Hooray!!" and "now what ?" are my first two reactions. I can see from the docs that I need at least two, for the ircd to run, but what do all the others in the modules folder do, and whether I want/need them is still a little confusing for me, and how to restore all the commands that were in prior versions for Windows, has me a little confused too. Any other links to dox on this subject is appreciated. Thanks. Oh, and supposing I wanted to load every single module in the modules folder, is there a shortcut, rather than having a separate line in the config for each one?
Only loading commands.dll is enough to load all commands (actually not all, because some commands are still not modularized). The other modules (m_*.dll) are commands one by one, which you don't have to load if commands.dll is loaded. One of the advantages of having all commands in modules is, you can disable those ones you don't want anyone to allow to use. See codemastr's post in this topic for more information. That topic also describes how wilcards work in the loadmodule directive.
