Needing a break from the typical grind of the day, since I have a renewed insterest in my old MBBS 6.x system; I decided to tinker during lunch today.
I snagged an embedded system board from the scrap pile. It has a 500Mhz embedded processor (I think it is a PII clone?), Via Tahoe Ethernet, ATI Rage video, 64MB Ram (8MB used for video), and a micro ATA interface, along with USB Ports (keyboard and mouse + peripherals). I did an image copy from my MBBS drive to a surplus 5GB Hitachi notebook drive. I then copied the via Rhine network drivers on to the drive. I plugged the drive in to the system and powered it up. MS-DOS came up, with network errors, but it was running. I ran the network setup utility and reconfigured it for the Via Rhine drivers, rebooted, and network was up and running.
I started MBBS... and BOOM... GP.
Scratched my head, disabled most of the modules, still GP faults.
Scratched my head again and paid close attention to it starting up. I noticed that it crashed right as it was displaying the audit trail. I copied the .VIR file for the audit trail over and restarted the system. It came right up. Shut down the BBS, enabled the modules, started the system, and voila it was up and running.
It occured to me that I took the BBS down in late 1999, and the 'new' audit trail entries were showing up with 07 instead for the year. I suspect there was a y2k glitch of sorts with the audit trail.
So far, 2 hours later, it is still running. I've bounced in to Crossroads, EOP, Infinity Complex, Kyrandia, QFM, the Forbidden Lands trilogy and Autowars so far. No crashes yet...
Not bad for software thats over a decade old.
Scary part is, it is running on a computer with a total power consumption of about 8 watts (hard drive runs about 2.5W and the system about 5W)... and way more computing power (not to mention memory) than my original 286 and subsequent 386 and 486 based systems had.
Of course I have no serial ports on this one, so I had to use IPX to log in for more than one user.
Geez... have I been re-addicted? (Or was it a dormant addiction lurking in the back of my mind?)
Rich
PS: Anyone had any luck with the universal ASPI driver for Dos? When I try to load it, the USB Keyboard and Mouse go dead and the system locks. I was hoping to be able to use USB peripherals too, if nothing else for ease of moving stuff around.
~8Watt MBBS 6.12 system... (AKA: What geeks do during lunch)
Moderator: Mod Squad
By all means, put the bbs up and try to keep it up, if you can get it working correctly on-line. It'd be nice to see some mbbs dos systems on-line. I had one running as an external game server to my main server, before it got taken out by power surges, but I don't know any one using mbbs at all any more. There are a few using worldgroup 2.0 dos.
If I recall correctly, y2k was only fixed on wg2 and higher.. don't quote me on that though. Joe or Dan would know the answer.
Crossroads of the elements was one of my favorite games, and many people like infinity complex. Quest for magic, you may have a few players too (i had a few players playing it, but the nt version crashed and couldn't be beat. so it was taken down.)
If I recall correctly, y2k was only fixed on wg2 and higher.. don't quote me on that though. Joe or Dan would know the answer.
Crossroads of the elements was one of my favorite games, and many people like infinity complex. Quest for magic, you may have a few players too (i had a few players playing it, but the nt version crashed and couldn't be beat. so it was taken down.)
To put it on the the net I'll need a working TCP module. Hrrm... or I suppose I could get creative and write a TCP-SPX gateway.
As I recall Crossroads was the most popular module even up through the late 90's. Followed by Forbidden Lands. After that I think it was Galtitrek, EOP and then G-Wars.
Rich
As I recall Crossroads was the most popular module even up through the late 90's. Followed by Forbidden Lands. After that I think it was Galtitrek, EOP and then G-Wars.
Rich
here ya go:Malakai wrote:By all means, put the bbs up and try to keep it up, if you can get it working correctly on-line. It'd be nice to see some mbbs dos systems on-line. I had one running as an external game server to my main server, before it got taken out by power surges, but I don't know any one using mbbs at all any more. There are a few using worldgroup 2.0 dos.
If I recall correctly, y2k was only fixed on wg2 and higher.. don't quote me on that though. Joe or Dan would know the answer.
Crossroads of the elements was one of my favorite games, and many people like infinity complex. Quest for magic, you may have a few players too (i had a few players playing it, but the nt version crashed and couldn't be beat. so it was taken down.)
Galacticomm Technologies, Inc Year 2000 Compliance Statement As of 9/30/98
Year 2000 Compliant Versions
Worldgroup for DOS 3.10 and higher
Worldgroup for NT/95 3.10 and higher
WebCast Personal - Dates not used in Product
ActiBase Add-on 2.0 and higher for Worldgroup
WebCast Add-on 2.1x and higher for Worldgroup
Not Year 2000 Compliant with No Plans to Update
The Major BBS - All Versions
Worldgroup 1.0x
Worldgroup 2.x
Worldgroup for DOS - 3.0x
Worldgroup for NT/95 3.0x
ActiBase Server - All Versions
WebCast ProServer - All Versions
Although these products will not likely crash, destroy data, or in other ways harm a system, they will perform inaccurate date calculations where post 1999 dates are involved.
Special Cases
Worldgroup Manager - Date handling in Worldgroup Manager is based on the Worldgroup Server the manager is connected to. If Worldgroup Manager connects to a version of the Worldgroup Server that is Year 2000 Compliant, dates will be handled properly. If Worldgroup Manager connects to a version of the Worldgroup Server that is not Year 2000 Compliant, dates will not be handled properly.
How you can update your software to be Year 2000 Compliant
To become year 2000 compliant you may purchase the necessary updated versions by calling Galacticomm Sales at 800/328-1128.
Thanks for the information. Being curoius I just pulled the source code for 6.12. The date calculations and comparisons appear to be 2 digit years. This breaks anything that performs a differential date calculation or a date comparision, which include years that cross the y2k boundry (pre 2000). I set all of my data files back to VIRgin and everything seems to work well thus far. The only things that I saw specifically that were broken:
1) The audit trail caused a GP when it had pre 2K dates in it.
2) The nightly stats did not update when the last updated occurred in a pre 2k date.
Rich
1) The audit trail caused a GP when it had pre 2K dates in it.
2) The nightly stats did not update when the last updated occurred in a pre 2k date.
Rich
thats a idea! first code mods for wg and mbbs.dspain wrote:here ya go:Malakai wrote:By all means, put the bbs up and try to keep it up, if you can get it working correctly on-line. It'd be nice to see some mbbs dos systems on-line. I had one running as an external game server to my main server, before it got taken out by power surges, but I don't know any one using mbbs at all any more. There are a few using worldgroup 2.0 dos.
If I recall correctly, y2k was only fixed on wg2 and higher.. don't quote me on that though. Joe or Dan would know the answer.
Crossroads of the elements was one of my favorite games, and many people like infinity complex. Quest for magic, you may have a few players too (i had a few players playing it, but the nt version crashed and couldn't be beat. so it was taken down.)
Galacticomm Technologies, Inc Year 2000 Compliance Statement As of 9/30/98
Year 2000 Compliant Versions
Worldgroup for DOS 3.10 and higher
Worldgroup for NT/95 3.10 and higher
WebCast Personal - Dates not used in Product
ActiBase Add-on 2.0 and higher for Worldgroup
WebCast Add-on 2.1x and higher for Worldgroup
Not Year 2000 Compliant with No Plans to Update
The Major BBS - All Versions
Worldgroup 1.0x
Worldgroup 2.x
Worldgroup for DOS - 3.0x
Worldgroup for NT/95 3.0x
ActiBase Server - All Versions
WebCast ProServer - All Versions
Although these products will not likely crash, destroy data, or in other ways harm a system, they will perform inaccurate date calculations where post 1999 dates are involved.
Special Cases
Worldgroup Manager - Date handling in Worldgroup Manager is based on the Worldgroup Server the manager is connected to. If Worldgroup Manager connects to a version of the Worldgroup Server that is Year 2000 Compliant, dates will be handled properly. If Worldgroup Manager connects to a version of the Worldgroup Server that is not Year 2000 Compliant, dates will not be handled properly.
How you can update your software to be Year 2000 Compliant
To become year 2000 compliant you may purchase the necessary updated versions by calling Galacticomm Sales at 800/328-1128.
date time update. unless the code in in the restricted librarys.
the wg 3.xx date API was very useful when i converted wg 2.00 to use y2k dates.RichInFL wrote:Thanks for the information. Being curoius I just pulled the source code for 6.12. The date calculations and comparisons appear to be 2 digit years. This breaks anything that performs a differential date calculation or a date comparision, which include years that cross the y2k boundry (pre 2000). I set all of my data files back to VIRgin and everything seems to work well thus far. The only things that I saw specifically that were broken:
1) The audit trail caused a GP when it had pre 2K dates in it.
2) The nightly stats did not update when the last updated occurred in a pre 2k date.
Rich
you can pull alot of referenced code from my site.
yeah, a new modernized breakthru library,RichInFL wrote:Or just write a replacement GSBL... and restricted library for MBBS. Then it could be Y2K compliant, and not have a license issue either...thats a idea! first code mods for wg and mbbs.
date time update. unless the code in in the restricted librarys.
Rich
don't hold your breath...
yeah i got the GSBL code but i cant send it out but from what i see in its source nothing y2k issued there.frcorey wrote:yeah, a new modernized breakthru library,RichInFL wrote:Or just write a replacement GSBL... and restricted library for MBBS. Then it could be Y2K compliant, and not have a license issue either...thats a idea! first code mods for wg and mbbs.
date time update. unless the code in in the restricted librarys.
Rich
don't hold your breath...
basically the date api is your only problem.
problem with that is they didnt start releasing alot of API code until wg 3.0/nt in their sdk's.
rick may have some of the api's sources.
I just wanted to let you know galico.zip was corrupt. it's now been replaced if you want to re-download it.. sorry about that..
you may not even need it, as you should be able to use galico2.zip, if 6.1x supports ico at all.
you may not even need it, as you should be able to use galico2.zip, if 6.1x supports ico at all.
RichInFL wrote:Got the files... don't recall if ICO requires 6.2x or if it would run with 6.12.. will have to rack my brain, or dig out documents... or just simply try it and see what happens... one of the above...
Rich
I haven't had a chance to try installing the ICO yet. I did however move the MBBS drive from the embedded system board to an HP T5700 that was no longer in use. The system boots up and runs fine. It is a 1Ghz Transmeta Pro CPU, with 256MB Ram and a 2GB Hard Drive. It has a Via Rhine II Network Interface, an ATI Rage II video chip and a single serial port. It can be upgraded to 1GB PC 2100 Ram, and can utilize larger hard drives as well.
The system boots up and everything works fine. I have downloaded the VIA Rhine II packet drivers and will install them next. After that I will see if I can get ICO to run with MBBS 6.25 and go from there.
For the curious, here is a picture of the system:
It is roughly 8" x 8" x 2". The only moving part is the Toshiba 2GB 2.5" hard drive. It is drawing about .8 amps at 12V, or just under 10 watts. I figure the extra memory and CPU power consume that extra couple of watts. Still a small, fast little MBBS system.
Rich
The system boots up and everything works fine. I have downloaded the VIA Rhine II packet drivers and will install them next. After that I will see if I can get ICO to run with MBBS 6.25 and go from there.
For the curious, here is a picture of the system:
It is roughly 8" x 8" x 2". The only moving part is the Toshiba 2GB 2.5" hard drive. It is drawing about .8 amps at 12V, or just under 10 watts. I figure the extra memory and CPU power consume that extra couple of watts. Still a small, fast little MBBS system.
Rich
Thats a darn good question. Since I've never installed or run WG in any form, I can't answer that. Can anyone else? How about the 6.25 modules?Malakai wrote:Will the modules from 6.1x work with wg1?
I seem to recall there being problems running some of the modules compiled for 6.03 with 6.1x... but that is a long distant memory.
Rich
some will, some won't.Malakai wrote:Will the modules from 6.1x work with wg1?
I have mbbs 6.25 and wg2 and some mbbs moduals work and some don't. the librarys they were compiled with are different, so it depends on what the modual is calling and how.
case in point. I have Xroads for mbbs 6.25, works fine. but on wg2 it causes a GP crash when entered.
One of the BBSes I use to logon had both crossroads of the elements and infinity complex, most likely a wg1 bbs. I've heard that wg1 is closer to v6.25 than it is to wg2 as well. So, it's possible wg1 will run more modules from 6.xx than wg2 would, unless there were versions of crossroads and infinity complex made specifically for wg later on.. it'd be worth a shot to try it out.
yeah theres a wg specific version released after the mbbs one. i have it, but no coads for it.Malakai wrote:One of the BBSes I use to logon had both crossroads of the elements and infinity complex, most likely a wg1 bbs. I've heard that wg1 is closer to v6.25 than it is to wg2 as well. So, it's possible wg1 will run more modules from 6.xx than wg2 would, unless there were versions of crossroads and infinity complex made specifically for wg later on.. it'd be worth a shot to try it out.
there is one for mbbs i just never got it so i have no binaries.RichInFL wrote:I have just confirmed that MBBS 6.25 will not work with the ICO that is publically available. ICO requires WG 1.01 or later...
Bummer...
Rich
i'd go wg 1.01 ober mbbs anyhow, theres no web client etc, and its damn near the same thing. check it out on my site i got the 1.01 installer and source.
mbbs / wg 1.0 / wg 1.01 / wg 2.0 all use same code stretch.RichInFL wrote:If I can ever log back in to your system I'll check out WG 1.01...
It occured to me though that my activation codes for the various modules may not work with WG 1.01.. particularly the Forbidden Lands trilogy. The rest I can work around...
Rich
you'll be ok.
hmm, I don't think so, the msg files have differences. and the dats too prolly.RichInFL wrote:World Group 1.01 is installed, as well as the ICO. I was able to telnet in! Woohoo!
Now to configure the system... argh... hrrm... is there an easy way to move the configuration from MBBS 6.12 to WG 1.01, or do I have to recreate all the menu trees, libraries and forums?
Rich
I tryed to move my mbbs 6.25 to my wg 2.0
and it was not a pretty sight.
Yep still tinkering with it... unfortunately the stuff that pays the bills went super nova and I've been working a gazillion (well okay more like 16+) hours a day 7 days a week. It should be calming down soon, as evidenced by my being here to write this...Malakai wrote:Are you still messing with this bbs? Let us know when/if you ever get a good permanent board on-line.
I am re-evaluating my position on Internet Connectivity. The price from Vircom is annoying, and having to deal with them is even more annoying.
The ICO seems rather slow with WG 1. It is almost like running with dial in speeds. And it tends to pause ocassionally for no apparent reason. It is running on Dos 6.22, with 1Ghz PIII CPU, 256MB Ram, 6GB 7200 RPM IDE drive... so I don't think it is a system issue. If I just install 6.25 and use the ipx to talk to it I don't see the slow downs. This makes me think it is most likely the ICO. I haven't had time to try various versions of it... any sage time saving advice here would be greatly appreciated.
Rich
Re: ~8Watt MBBS 6.12 system... (AKA: What geeks do during lu
any luck on finding me the IC code?RichInFL wrote:Needing a break from the typical grind of the day, since I have a renewed insterest in my old MBBS 6.x system; I decided to tinker during lunch today.
I snagged an embedded system board from the scrap pile. It has a 500Mhz embedded processor (I think it is a PII clone?), Via Tahoe Ethernet, ATI Rage video, 64MB Ram (8MB used for video), and a micro ATA interface, along with USB Ports (keyboard and mouse + peripherals). I did an image copy from my MBBS drive to a surplus 5GB Hitachi notebook drive. I then copied the via Rhine network drivers on to the drive. I plugged the drive in to the system and powered it up. MS-DOS came up, with network errors, but it was running. I ran the network setup utility and reconfigured it for the Via Rhine drivers, rebooted, and network was up and running.
I started MBBS... and BOOM... GP.
Scratched my head, disabled most of the modules, still GP faults.
Scratched my head again and paid close attention to it starting up. I noticed that it crashed right as it was displaying the audit trail. I copied the .VIR file for the audit trail over and restarted the system. It came right up. Shut down the BBS, enabled the modules, started the system, and voila it was up and running.
It occured to me that I took the BBS down in late 1999, and the 'new' audit trail entries were showing up with 07 instead for the year. I suspect there was a y2k glitch of sorts with the audit trail.
So far, 2 hours later, it is still running. I've bounced in to Crossroads, EOP, Infinity Complex, Kyrandia, QFM, the Forbidden Lands trilogy and Autowars so far. No crashes yet...
Not bad for software thats over a decade old.
Scary part is, it is running on a computer with a total power consumption of about 8 watts (hard drive runs about 2.5W and the system about 5W)... and way more computing power (not to mention memory) than my original 286 and subsequent 386 and 486 based systems had.
Of course I have no serial ports on this one, so I had to use IPX to log in for more than one user.
Geez... have I been re-addicted? (Or was it a dormant addiction lurking in the back of my mind?)
Rich
PS: Anyone had any luck with the universal ASPI driver for Dos? When I try to load it, the USB Keyboard and Mouse go dead and the system locks. I was hoping to be able to use USB peripherals too, if nothing else for ease of moving stuff around.
audit trails were one of the crashing errors that the y2k patches fixed, wg2 does though have some y2k issuesMalakai wrote:By all means, put the bbs up and try to keep it up, if you can get it working correctly on-line. It'd be nice to see some mbbs dos systems on-line. I had one running as an external game server to my main server, before it got taken out by power surges, but I don't know any one using mbbs at all any more. There are a few using worldgroup 2.0 dos.
If I recall correctly, y2k was only fixed on wg2 and higher.. don't quote me on that though. Joe or Dan would know the answer.
Crossroads of the elements was one of my favorite games, and many people like infinity complex. Quest for magic, you may have a few players too (i had a few players playing it, but the nt version crashed and couldn't be beat. so it was taken down.)
Galacticomm Technologies, Inc Year 2000 Compliance Statement As of 9/30/98
Year 2000 Compliant Versions
Worldgroup for DOS 3.10 and higher
Worldgroup for NT/95 3.10 and higher
WebCast Personal - Dates not used in Product
ActiBase Add-on 2.0 and higher for Worldgroup
WebCast Add-on 2.1x and higher for Worldgroup
Not Year 2000 Compliant with No Plans to Update
The Major BBS - All Versions
Worldgroup 1.0x
Worldgroup 2.x
Worldgroup for DOS - 3.0x
Worldgroup for NT/95 3.0x
ActiBase Server - All Versions
WebCast ProServer - All Versions
Although these products will not likely crash, destroy data, or in other ways harm a system, they will perform inaccurate date calculations where post 1999 dates are involved.
Special Cases
Worldgroup Manager - Date handling in Worldgroup Manager is based on the Worldgroup Server the manager is connected to. If Worldgroup Manager connects to a version of the Worldgroup Server that is Year 2000 Compliant, dates will be handled properly. If Worldgroup Manager connects to a version of the Worldgroup Server that is not Year 2000 Compliant, dates will not be handled properly.
How you can update your software to be Year 2000 Compliant
To become year 2000 compliant you may purchase the necessary updated versions by calling Galacticomm Sales at 800/328-1128.
however i did today compile a new wg2 majorbbs.exe which adds
--> ability to boot your ghosted account on login
--> new sysop / globals to perform simple accounting commands
--> optional logon/logoff message display
im currently working on looking over the wgnt gcommlib and compiling all the date stuff into a new gcommlib, im hoping theres nothing missing from the wg2 one if so it will too get the y2k upgrade.
ill know if it works when it asks for my birthdate on login and it asks me for the 4 digit year.
after that i'd say wg2 is complete unless joe wants to add somethings he feels is missing from the kernel.
i decided to reopen my wg2 project since alot of older stuff isnt being ported people are running it so what the hell why not make it smooth like the terminal wgnt telnet bbs's.
contact me for a major tcp/ip telnet/rlogin only module that works up to your current line count.RichInFL wrote:To put it on the the net I'll need a working TCP module. Hrrm... or I suppose I could get creative and write a TCP-SPX gateway.
As I recall Crossroads was the most popular module even up through the late 90's. Followed by Forbidden Lands. After that I think it was Galtitrek, EOP and then G-Wars.
Rich
have you tested that this works? people been saying something about the ico files out there are messed up. im curious to know if they left something out, i been meaning to get around to compiling an ico package using the wgnt icosrc and compiling it for wg2Malakai wrote:The ICO option for mbbs is now freeware. You can download them on my bbs, under the Sysopflz library. The names of the files are:
galico.zip and galico2.zip
You can use the account name/pw i gave you to ftp in to it and grab them if you want.
they did release an ico for mbbs but i dont think anyone has that package.RichInFL wrote:Got the files... don't recall if ICO requires 6.2x or if it would run with 6.12.. will have to rack my brain, or dig out documents... or just simply try it and see what happens... one of the above...
Rich
i used to and for the life of me cannot locate it.
yeah you should be ok if you have reset your audit trail to 2007 that way nothing is over 100 years old.RichInFL wrote:Thanks for the information. Being curoius I just pulled the source code for 6.12. The date calculations and comparisons appear to be 2 digit years. This breaks anything that performs a differential date calculation or a date comparision, which include years that cross the y2k boundry (pre 2000). I set all of my data files back to VIRgin and everything seems to work well thus far. The only things that I saw specifically that were broken:
1) The audit trail caused a GP when it had pre 2K dates in it.
2) The nightly stats did not update when the last updated occurred in a pre 2k date.
Rich
i have the gsbl source code it doesnt cover the date api, thats in the gcommlibRichInFL wrote:Or just write a replacement GSBL... and restricted library for MBBS. Then it could be Y2K compliant, and not have a license issue either...thats a idea! first code mods for wg and mbbs.
date time update. unless the code in in the restricted librarys.
Rich
thats what im doing, i took the gcomm lib code from the wg 3.2 archive and am down porting it to wg2, then eplacing wg2's lib wih the new one and then im sure ill have to tinker with a couple baselinesfrcorey wrote:thats a idea! first code mods for wg and mbbs.dspain wrote:here ya go:Malakai wrote:By all means, put the bbs up and try to keep it up, if you can get it working correctly on-line. It'd be nice to see some mbbs dos systems on-line. I had one running as an external game server to my main server, before it got taken out by power surges, but I don't know any one using mbbs at all any more. There are a few using worldgroup 2.0 dos.
If I recall correctly, y2k was only fixed on wg2 and higher.. don't quote me on that though. Joe or Dan would know the answer.
Crossroads of the elements was one of my favorite games, and many people like infinity complex. Quest for magic, you may have a few players too (i had a few players playing it, but the nt version crashed and couldn't be beat. so it was taken down.)
Galacticomm Technologies, Inc Year 2000 Compliance Statement As of 9/30/98
Year 2000 Compliant Versions
Worldgroup for DOS 3.10 and higher
Worldgroup for NT/95 3.10 and higher
WebCast Personal - Dates not used in Product
ActiBase Add-on 2.0 and higher for Worldgroup
WebCast Add-on 2.1x and higher for Worldgroup
Not Year 2000 Compliant with No Plans to Update
The Major BBS - All Versions
Worldgroup 1.0x
Worldgroup 2.x
Worldgroup for DOS - 3.0x
Worldgroup for NT/95 3.0x
ActiBase Server - All Versions
WebCast ProServer - All Versions
Although these products will not likely crash, destroy data, or in other ways harm a system, they will perform inaccurate date calculations where post 1999 dates are involved.
Special Cases
Worldgroup Manager - Date handling in Worldgroup Manager is based on the Worldgroup Server the manager is connected to. If Worldgroup Manager connects to a version of the Worldgroup Server that is Year 2000 Compliant, dates will be handled properly. If Worldgroup Manager connects to a version of the Worldgroup Server that is not Year 2000 Compliant, dates will not be handled properly.
How you can update your software to be Year 2000 Compliant
To become year 2000 compliant you may purchase the necessary updated versions by calling Galacticomm Sales at 800/328-1128.
date time update. unless the code in in the restricted librarys.
6.25+ will work on wg1RichInFL wrote:Thats a darn good question. Since I've never installed or run WG in any form, I can't answer that. Can anyone else? How about the 6.25 modules?Malakai wrote:Will the modules from 6.1x work with wg1?
I seem to recall there being problems running some of the modules compiled for 6.03 with 6.1x... but that is a long distant memory.
Rich
if richinfla sends me the code he has ill port it to wg3 and it will work greatMalakai wrote:One of the BBSes I use to logon had both crossroads of the elements and infinity complex, most likely a wg1 bbs. I've heard that wg1 is closer to v6.25 than it is to wg2 as well. So, it's possible wg1 will run more modules from 6.xx than wg2 would, unless there were versions of crossroads and infinity complex made specifically for wg later on.. it'd be worth a shot to try it out.
all i need is the code i can do the hard part.
dont deal with them, talk to meRichInFL wrote:Yep still tinkering with it... unfortunately the stuff that pays the bills went super nova and I've been working a gazillion (well okay more like 16+) hours a day 7 days a week. It should be calming down soon, as evidenced by my being here to write this...Malakai wrote:Are you still messing with this bbs? Let us know when/if you ever get a good permanent board on-line.
I am re-evaluating my position on Internet Connectivity. The price from Vircom is annoying, and having to deal with them is even more annoying.
The ICO seems rather slow with WG 1. It is almost like running with dial in speeds. And it tends to pause ocassionally for no apparent reason. It is running on Dos 6.22, with 1Ghz PIII CPU, 256MB Ram, 6GB 7200 RPM IDE drive... so I don't think it is a system issue. If I just install 6.25 and use the ipx to talk to it I don't see the slow downs. This makes me think it is most likely the ICO. I haven't had time to try various versions of it... any sage time saving advice here would be greatly appreciated.
Rich
make -ftcplib
You do not own the rights to either product. Crossroads is owned by High Velocity, and Infinity Complex is owned by me. So you can not port them, you can not distribute them, and you shouldn't even have them. Lord knows if he sent it suddenly ArcticZone would have a similar game "coming out".dspain wrote:if richinfla sends me the code he has ill port it to wg3 and it will work greatMalakai wrote:One of the BBSes I use to logon had both crossroads of the elements and infinity complex, most likely a wg1 bbs. I've heard that wg1 is closer to v6.25 than it is to wg2 as well. So, it's possible wg1 will run more modules from 6.xx than wg2 would, unless there were versions of crossroads and infinity complex made specifically for wg later on.. it'd be worth a shot to try it out.
all i need is the code i can do the hard part.
Also, the GSBL source code you're so proud of having been accidentally given by a careless pretender to the gcomm ownership is the C source to the NT version that was ported from the original assembler for the original UNIX product. It would NOT function on the DOS systems. The assembler version is required.
I have looked at it, but I don't know assembler well enough to know if it does anything date specific. My suspicion is that it does not.