The Major BBS Forums (Archive)

Has anyone attempted to compile the WG server against WINE on a *NIX platform? I'm somewhat interested to see if it's possible. If so, porting over the server (and relatively recent updates to it) to the platform should be relatively simple. Once you can get it working against wine libs, making a native cross platform solution should be fairly trivial. This could open up a veritable cornucopia of new/returned developers, as quite a few have become sysadmins for *NIX servers and service providers.

A little update to all this...

I got WG 2.00 running in Dosbox, but without any telnet/dialup.
I wager that if I had a working standard modem, it would work quite well.
Some things that I did do:
Bumped the memory from 16 to 64
Increased cycles to 10000 (2ghz system)

Everything seemed to be functioning just fine.


Now...for WG 3.2...
I got it installed as DEMO, but...that's where the fun ended.
I can start any of the programs as well as the server. However, btrieve has a cow. If I could figure out the little (ginormous) issues with Btrieve under wine, I could probably get it going a little better.

I have yet to try WG Dos under VMware with packet drivers/etc...but I imagine it works fairly well.

Anyways, just thought I'd let you guys know how to testing was coming
Perhaps a newer Btrieve would have less issues? Also, whoever said they'd pulled Btrieve out of the systems...if you'd like I can test it under wine...I think it may actually prove to be a viable alternative for some people looking to provide "full featured" WG systems, based around the almost universally-accepted more secure OS of Linux/BSD.

I have been doing a fair bit with VMware, and just got my WG2 DOS running nicely in VM server. It's working very well, has all the IPX/SPX stuff running, hooks into my Novell server etc.

The 2 major issues I have, is 1) it uses 100 CPU time, even DOSidle doesn't help, probably polling for keystrokes or something like that, and 2) I am trying to find a way to elegantly shut WG down if the UPS gets low.

I had a bit of a play with QEMU, but the information on getting networking going is all conflicting and confusing to me at this point. The concept is good, and apparently most types of networking can be done.

For 2) I seem to recall that WG checked for the existance of certain files on the HD, and if they existed, it would eg shutdown.

Does anybody know anything about this or am I barking at the moon?

Cheers,

Peter

EArmbrust wrote:A little update to all this...

I got WG 2.00 running in Dosbox, but without any telnet/dialup.
I wager that if I had a working standard modem, it would work quite well.
Some things that I did do:
Bumped the memory from 16 to 64
Increased cycles to 10000 (2ghz system)

Everything seemed to be functioning just fine.


Now...for WG 3.2...
I got it installed as DEMO, but...that's where the fun ended.
I can start any of the programs as well as the server. However, btrieve has a cow. If I could figure out the little (ginormous) issues with Btrieve under wine, I could probably get it going a little better.

I have yet to try WG Dos under VMware with packet drivers/etc...but I imagine it works fairly well.

Anyways, just thought I'd let you guys know how to testing was coming
Perhaps a newer Btrieve would have less issues? Also, whoever said they'd pulled Btrieve out of the systems...if you'd like I can test it under wine...I think it may actually prove to be a viable alternative for some people looking to provide "full featured" WG systems, based around the almost universally-accepted more secure OS of Linux/BSD.

my native majorbbs for nt i tinkered with using powerlink as the primary db engine but ended up going BT instead using their sql version.
if i had the time i coulda prolly finished it up with powerlink but with everything going on i didnt have the time since wg was written around btrieve as the foundation for its data handling.
alot of people are down on bt but hell i look at it this way it works and has since the beginning so i will remain with it but a newer ver is whats needed over 6.15.