Well, it won't be WinHelp...
Submitted by Noltar on Sun, 2004-03-14 21:31.
...so it might actually be useful.
I'm curious about the amount of demand among PennMUSH users for updated, and possibly improved, documentation for running the server on Windows. As always, questions about it come up from time to time, but overall it seems that people figure it out on their own.
Are there things that those of you out there running Penn on Windows would like to see better documented? I know people still use Nick Gammon's site as a reference, though it is somewhat dated, and the READMEs cover the essentials... so what is missing? What is lacking? And, what needs to be replaced? Feel free to comment with your ideas and requests, and we'll see just what kind of solutions I can put together.
Click 
Something I'd like to see is
Something I'd like to see is a step-by-step process of how to apply patches in a Window environment. There's -some- information, but it still involves having somewhat of a *nix-based background.
A short answer...
Well, those using MSys+MinGW to compile already have patch within MSys, and can use the steps listed below without any extra work.
For those using MSVC++, the easiest way is to download a Win32 version of patch, such as the one available from http://unxutils.sourceforge.net. Install them into C:\Windows or another part of your PATH, or add their location to your PATH. The zip file puts them into /bin and /usr/local/wbin directories by default. Copying them to C:\Windows or C:\Windows\system is probably the easiest if you don't know how to edit your PATH.
Then do the following after placing the patchfile in your pennmush directory:
1) Open a command prompt.
2) cd to your pennmush directory
3) patch -p1 < patchfile
4) Recompile
5) Run your shiny newly patched mush
SSL as default config in MSVC
The readme in /win32 was pretty self-explanatory. The only other thing I'd add is to tell people to change the project configuration on MSVC to a non-SSL build. Otherwise, you'll get that missing library linking error for slesy32.lib, or something similar. Chee in PennMUSH helped me out, but otherwise I would've spent my time tracking, then adding that library to my compiler.
Compile the already compiled?
Is it possible to take a pre-compiled Win32 binary, load up MinGW+MSys, apply the latest patches, and then compile into a useful Windows game?
I tried compiling the original source, and was successful, but it left me without an executeable file.
Apparently not, as I just tri
Apparently not, as I just tried it.
What I'm trying to do is take the source code for PennMUSH and then compile it into a working Windows executeable, an executeable that can be patched.
Executables themselves are ne
Executables themselves are never patched in PennMUSH. You patch source and rebuild executables.
What I would like to see.
I would like to see more help for the MSVC++ Users. The entire documentation is surrounding MinGW+MSys (*nix enviroment).
Also... I would like see better ddocumention for adding powers (with powers) and flags (With Privelages).
~ Paige