A couple days ago, I started messing with GHOST again, trying to create a multi-node GHOST server. My first attempt was to use Ray Gwinn's SIO/Vmodem software on the OS/2 machine and Netserial on another, to create virtual com ports through telnet.
I managed to get the netserial package to connect and send the right commands to the GHOST server. The batch files would run, etc, but the doors never would connect to the door games. I thought that it was something incompatible with netserial and SIO.
Well, this morning, I took out the SIO drives and connected the worldgroup system with a null modem cable to the GHOST server, and it did something similar. The only difference is that when it ran the batch file on the null modem cable setup, the node/comport wouldn't release - it just kind of froze. I re-adjusted the com port settings on the os/2 system, to make sure they were using standard comport settings, resetup the doors, even tried LORD, which supports standard and non-standard com ports, irqs, etc... still the same thing happens...
This is the first time I've used OS/2 warp, but maybe some one else around here knows how to get GHOST to work correctly with OS/2.
The last problem (that I've found a solution for) is getting daily maint run. There are a few programs out there that are made just to do certain tasks at different times, but possibly the best way to go would be to use an actual BBS node just to stay idle in a window and then run cleanup every 24 hours..
It should be fairly straightforward to run, at minimum, a 2-node GHOST server on OS/2, if only we could figure out how to make the doors communicate with the WG system... I don't know if GHOST isn't passing on the comport to the doors or what. I do know the doors themselves are reading the dropfiles though.
GHOST and OS/2 Warp
Moderator: Mod Squad
Re: GHOST and OS/2 Warp
talk to the sysop of ozone ozone.eesc.comMalakai wrote:A couple days ago, I started messing with GHOST again, trying to create a multi-node GHOST server. My first attempt was to use Ray Gwinn's SIO/Vmodem software on the OS/2 machine and Netserial on another, to create virtual com ports through telnet.
I managed to get the netserial package to connect and send the right commands to the GHOST server. The batch files would run, etc, but the doors never would connect to the door games. I thought that it was something incompatible with netserial and SIO.
Well, this morning, I took out the SIO drives and connected the worldgroup system with a null modem cable to the GHOST server, and it did something similar. The only difference is that when it ran the batch file on the null modem cable setup, the node/comport wouldn't release - it just kind of froze. I re-adjusted the com port settings on the os/2 system, to make sure they were using standard comport settings, resetup the doors, even tried LORD, which supports standard and non-standard com ports, irqs, etc... still the same thing happens...
This is the first time I've used OS/2 warp, but maybe some one else around here knows how to get GHOST to work correctly with OS/2.
The last problem (that I've found a solution for) is getting daily maint run. There are a few programs out there that are made just to do certain tasks at different times, but possibly the best way to go would be to use an actual BBS node just to stay idle in a window and then run cleanup every 24 hours..
It should be fairly straightforward to run, at minimum, a 2-node GHOST server on OS/2, if only we could figure out how to make the doors communicate with the WG system... I don't know if GHOST isn't passing on the comport to the doors or what. I do know the doors themselves are reading the dropfiles though.
hes been running os/2 for synchronet since as far as i can remember.
alot of old schoolers that were deep into the bbs scene in the 90's would know him as Dink.
I actually just figured it out.. well, I didn't figure out how to make the virtual com ports thing work (yet) but I figured out how to make GHOST work on real com ports... you just have to lock the baud rate in at 38400 on individual doors. If the door doesn't have that option, you're probably SOL.
With a normal motherboard or i/o card, it looks like you're stuck with 2 nodes, but with a digicard, you could probably have as many as you want, as long as the doors support them.
I'll probably do a writeup on it when more testing is done
With a normal motherboard or i/o card, it looks like you're stuck with 2 nodes, but with a digicard, you could probably have as many as you want, as long as the doors support them.
I'll probably do a writeup on it when more testing is done