mudinfo.net

Thank you for the wonderful guide.

I followed it for the most part with a Win 7 64-bit SP1 Home Premium OS VM in VirtualBox and I have just a few observations that might help some people..

Since this was my first time messing with setting up my own board, I didn't really know how to obtain the key for MMUD properly.

To clarify: When you get Worldgroup set up properly and connect to it, there will be the "WG Reg #" that I'd seen on that initial page. It has the format of "00XXXXXX". Enter this in to the keygen for MUD to get the proper keys to get your MUD working.

Haven't yet gotten to messing with DialSoft or FU Globals as I'm really just playing around at this point, I am able to log in from my host computer running MegaMUD to my board running as a guest VM on the machine and I'm pretty satisfied with that after about 8 hours of what I consider "playing around with shit" when I had zero clue what I was doing beforehand.

I do have a question/issue though that perhaps someone can help with:

I did the migration from Btrieve over to Pervasive pSQL v9, with the 9.52 hotfix. I found a license somewhere but in the License utility it displays as "Workgroup". I'm pretty sure this is different from the key I'll need since I installed the Windows server version of it. Anyone able to clarify and maybe point me in the right direction for that key? I saw it referenced above; didn't see the key.

Thanks again for the awesome guide, really helpful.

Since it's just stock 1.11p as far as I know atm, I will now look in to some fixes that apparently have to be made with a hex editor and/or mods, both of which I have no clue on.. more things to learn. Thanks again.

I can't remember, but I fired up my old box and this is what it has:
According to this, it may not matter: http://www.goldstarsoftware.com/PSQL-wo ... server.asp

Seems like the workgroup and server are both engines, workgroup just has less capabilities (5 users max, no 64-bit, etc). None of which I think will matter for mmud.

Awesome, thanks for the reply. Worst case scenario, after the 30 day trial for the server runs out I start getting errors and then work from there.

Well it's been 30 days and the Btrieve error 161 of doom showed up. Apparently the workgroup license isn't hacking whatever I'm doing. Permanent server key seems to be the key..

While attempting to setup WG on a new Windows 10 laptop, 64-bit, I was having some issues that I thought I would share the fix for. The setup file for WG (SETUP.EXE) would not launch however there was a hung 32-bit installer task in showing in Task Manager. I did not see the progress bar at all and setting the file to run in compatibility mode and/or as administrator did not get it to work. The install did complete successfully once I disabled "Check apps and files" in Windows Defender Security Center. The default setting is "Warn" but this would not allow the install to complete. Good luck!

MiOw wrote:While attempting to setup WG on a new Windows 10 laptop, 64-bit, I was having some issues that I thought I would share the fix for. The setup file for WG (SETUP.EXE) would not launch however there was a hung 32-bit installer task in showing in Task Manager. I did not see the progress bar at all and setting the file to run in compatibility mode and/or as administrator did not get it to work. The install did complete successfully once I disabled "Check apps and files" in Windows Defender Security Center. The default setting is "Warn" but this would not allow the install to complete. Good luck!

Yeah having the same problem. Just installed 10 a few days ago. I disabled the check apps and files, still a no go. Sits there and does nothing. Tried in compat mode too.


EDIT: Found fix on FB. " Task Manager, details tab, right click setup, choose "analyze wait chain". It shows a tree of process that are blocking it."

Necrosaro420 wrote:EDIT: Found fix on FB. " Task Manager, details tab, right click setup, choose "analyze wait chain". It shows a tree of process that are blocking it."

What's the actual fix? End task the things in waiting?

syntax wrote:

Necrosaro420 wrote:EDIT: Found fix on FB. " Task Manager, details tab, right click setup, choose "analyze wait chain". It shows a tree of process that are blocking it."

What's the actual fix? End task the things in waiting?

Was a suggestion on FB group. I tried it, and it worked for me! It shows you what the WG install is waiting on. His was something different, mine was my Logitech keyboard/mouse app was blocking it for some reason. I closed that part of the chain out, and installed just fine.

Necrosaro420 wrote:

syntax wrote:

Necrosaro420 wrote:EDIT: Found fix on FB. " Task Manager, details tab, right click setup, choose "analyze wait chain". It shows a tree of process that are blocking it."

What's the actual fix? End task the things in waiting?

Was a suggestion on FB group. I tried it, and it worked for me! It shows you what the WG install is waiting on. His was something different, mine was my Logitech keyboard/mouse app was blocking it for some reason. I closed that part of the chain out, and installed just fine.

No, I get it. I want to update the instructions to include this. And since I'm banned from the FB group I can't look.

syntax wrote:

Necrosaro420 wrote:

syntax wrote:

Necrosaro420 wrote:EDIT: Found fix on FB. " Task Manager, details tab, right click setup, choose "analyze wait chain". It shows a tree of process that are blocking it."

What's the actual fix? End task the things in waiting?

Was a suggestion on FB group. I tried it, and it worked for me! It shows you what the WG install is waiting on. His was something different, mine was my Logitech keyboard/mouse app was blocking it for some reason. I closed that part of the chain out, and installed just fine.

No, I get it. I want to update the instructions to include this. And since I'm banned from the FB group I can't look.

Say what? Why would they ban you? smh

This is the post I got it from:


Jason Schwartz Ok. I figured it out!

Overwolf was blocking the setup.exe for some reason. I discover this by going to the Task Manager, details tab, right click setup, choose "analyze wait chain". It shows a tree of process that are blocking it.