I found a repository of MBBS / WG modules, and I have made sure to choose the modules that are for (WG3/nt). It's been about 50/50 installing them. Some have installed, some have needed tppatch to get past error 200, and then there are those that throw: "INIT: unable to read value softwarekeyProd (Error -1). Unable to continue installation".
That seems like the error that MajorMUD had before I found the Windows 10 installer version. Is this something that can be end-user remedied via a program to extract the ".Z" files, or is it a show stopper for those modules?
Thanks in advance,
Steve
Error installing some modules
Re: Error installing some modules
If you can extract the files (.dll, .msg, etc) from the installer, you can just drop those files into your BBSV10 directory and you should be good. I think that error you're getting is due to it looking for stuff in \WGSERV and not finding the directory, but I'm not sure. If there's something specific you can't get to work, I can try to help with it.
BlaZ
BlaZ
-
daniel_spain
- Posts: 429
- Joined: Sun Aug 09, 2020 2:39 am
Re: Error installing some modules
Slinky wrote:
> I found a repository of MBBS / WG modules, and I have made sure to choose
> the modules that are for (WG3/nt). It's been about 50/50 installing them.
> Some have installed, some have needed tppatch to get past error 200, and
> then there are those that throw: "INIT: unable to read value
> softwarekeyProd (Error -1). Unable to continue installation".
>
> That seems like the error that MajorMUD had before I found the Windows 10
> installer version. Is this something that can be end-user remedied via a
> program to extract the ".Z" files, or is it a show stopper for
> those modules?
>
> Thanks in advance,
> Steve
that error is where the vendor was using the registry key data to pull the reg info.
one thing you can do is install a default copy of 3.2 in a vm somewhere, run setup.exe
install to c:\wgserv then zip up WCC*.* and you now have "raw" data.
i built a series of various majormud distro archives when i began writing my own
majorbbs engine and i wanted to have raw vanilla data of specific versions.
> I found a repository of MBBS / WG modules, and I have made sure to choose
> the modules that are for (WG3/nt). It's been about 50/50 installing them.
> Some have installed, some have needed tppatch to get past error 200, and
> then there are those that throw: "INIT: unable to read value
> softwarekeyProd (Error -1). Unable to continue installation".
>
> That seems like the error that MajorMUD had before I found the Windows 10
> installer version. Is this something that can be end-user remedied via a
> program to extract the ".Z" files, or is it a show stopper for
> those modules?
>
> Thanks in advance,
> Steve
that error is where the vendor was using the registry key data to pull the reg info.
one thing you can do is install a default copy of 3.2 in a vm somewhere, run setup.exe
install to c:\wgserv then zip up WCC*.* and you now have "raw" data.
i built a series of various majormud distro archives when i began writing my own
majorbbs engine and i wanted to have raw vanilla data of specific versions.