Re: losing BBS/source from the 90's -- I was fortunate enough to regularly back things up to QIC tape, and lo and behold, 22 years later a hacked up box restored the BBS perfectly and it ran in DosBox on my laptop. I was pleasantly surprised that it all worked immediately. Hardest part was finding parts for a floppy tape and installing the right Windows version. Seeing the ANSI art made it all worth it... https://twi…
Frankly I'm most impressed that you had a QIC drive available.
A look at my BBS Software from '93
31–40 of 215 posts
Re: A look at my BBS Software from '93
#32I ran a single line PCBoard BBS in the mid to late 90's. PCBoard had its own plugins called PPEs. A lot of them were distributed as shareware. After finding a decompiler I had a lot of fun reading source code, making personal keygens, and finding security issues.
Re: A look at my BBS Software from '93
#33Anyone play TradeWars 2002? That's what I was doing in '93 on my BBS.
Yes! I've tried over the years to create a TW2002 clone, but I always stall out at the economic system. I've also tried to recreate Barren Realms Elite / Solar Realms Elite, but Amit lost the source code to that, too. Reverse engineering BBS games is hard! Maybe Legend of the Red Dragon would be easier... [Edit: I'm aware that there are TW2002 games out there right now, but those tend to be web-based, and I wanna do…
Re: A look at my BBS Software from '93
#34Earlier quoted context omitted.
OS/2 and C compilers were readily available for downloaded on BBses. I'm pretty sure I downloaded Turbo C onto like 20 floppy disks over ZModem or something. Not only did it take forever to download, but installing it was a huge pain, with all the disk swapping. I guess the hard disk didn't have enough space for both the raw disks and the install? I don't remember exactly. I never ran OS/2 but a friend did, and I'm p…
Yeah Borland Turbo C in DOS was the way to go. My first board ran on multi-tasking DOS in DESQview before moving over to OS/2 -> Windows over the years.
Re: A look at my BBS Software from '93
#35How old were you when you wrote this? Looks like a big system - was this your first major project? I seem to recall OS/2 and a C compiler cost money back? How did you get to be using those, through work or did you buy them? Why did you choose OS/2 - did you consider any other alternatives?
OS/2 and C compilers were readily available for downloaded on BBses. I'm pretty sure I downloaded Turbo C onto like 20 floppy disks over ZModem or something. Not only did it take forever to download, but installing it was a huge pain, with all the disk swapping. I guess the hard disk didn't have enough space for both the raw disks and the install? I don't remember exactly. I never ran OS/2 but a friend did, and I'm p…
Floppy-disk-based installers were often hardcoded to use the A: drive so even if there was space for the install and the floppy installer on the HDD, you'd need to copy the installer to the floppies to use it, unless you had some workaround.
Re: A look at my BBS Software from '93
#36Re: A look at my BBS Software from '93
#37Anyone play TradeWars 2002? That's what I was doing in '93 on my BBS.
Re: A look at my BBS Software from '93
#38Nice! Way better than most BBS's that I used to frequent back in the 80's and 90's. Great to see an OS/2 based one too - I remember switching to OS/2 for a small time "play" BBS that I set up in the early 90s... I was astounded at the ease of running multiple modem lines on OS/2 as compared to DOS or CP/M...
Re: A look at my BBS Software from '93
#39Too bad you lost the source code.
I know. It was on a computer that burned down in a fire. So, it's very much gone. Both that and the message archives from the bbs itself would have been a treasure trove of nostalgia.
edit: Oh I guess it was Midnight Sun? I don't remember if we ever interacted, but the ANSIs look familiar!
Re: A look at my BBS Software from '93
#40The most amazing thing about it all was that it was the public internet before there was a public internet. E-mails sent over FidoNET had an amazing weight to them that's hard to describe. It took a ton of effort just to get your BBS to participate in the network and once you did, data moved so slowly that you became very observant of each step of the process of communicating. First, you wrote the email in your mail editor (I loved GoldED). Then, another program bundled it up with other emails into some kind of binary packaging and passed it along to the mailer. The mailer took this bundle of mail and dialed out on the modem to the local FidoNET hub. If you lived in a rural location, this meant that you had to make a long-distance call to deliver the mail. My local hub was in Seguin, TX (~30 miles away) and it felt like a very big deal when my computer dialed him up to do a delivery. From there, the hub delivered it to a "star", which was a regional hub that dealt in larger volumes of mail. This was usually run by someone with money because their modems were making long-distance calls (including overseas) on a regular basis. From the star, your mail was shipped across long distances and then the process repeated in reverse until the recipient's system picked up the mail from their local hub. Then, when they replied, the whole thing happened again in reverse. It regularly took days to get a reply from across the world but it was so fun! Every single mail that you received in your inbox felt as important as someone writing a letter by hand and sending it via the postal service. I cherished getting emails, even if they were stupid.
I still dream about reviving a modern FidoNET (yes, I know it still exists) for the HN crowd. I write a lot of Go and I even read some of the FidoNET technical standards with the thought of a Go implementation of the protocols but never got anywhere in it. It's an enormous amount of work and I haven't had a real phone line in over a decade. Doing Fido over TCP/IP just doesn't feel the same. It's way too easy.