11.06.05 - Downtime Looks like a problem on my ISP's end (well, Covad's end, to be specific) caused my DSL connection to fail, which brought the whole shebang down for a couple hours yesterday. But, since you're reading this, it's back up again. -Xaroth 09.20.05 - California IP address Boatanchor is back up and running, and all appears to be well. Give everything a good testing, and then let me know how it goes. If you hit any snags, let me know. And, of course, if I'm hosting a domain for you, please switch the IP address over to 66.92.186.248, and let me know if it's working correctly. Thanks! -Xaroth 09.15.05 - Welcome to sunny California! We're moved in, and now that we've got internet, it's starting to feel a bit like home. It's going to be a little while before I start transferring the domains - I need to get the data off of boatanchor before I can do that. However, since the board is independant of boatanchor, I've set it up for now. Simply telnet to 66.92.186.248 on port 8088 or click here (assuming your browser supports launching telnet from a link). I'll post here again once I have the real boatanchor set up again. -Xaroth 08.24.05 - Since the board is down right now... I saw this and wanted to pass it along, but there's no Other Sites) room for the moment. As such, here's something I'm sure you'll all enjoy. Woot! -Xaroth 08.21.05 - New IP address If I'm hosting one of your domains, you can temporarily change your IP address to 208.42.66.81. This will need to change once more in about a month once I've got my permanent setup, but this will be the server's home until then. -Xaroth 08.17.05 - Temporary Server... So as you're all probably aware, I'm moving to California. To minimize downtime, I've set up this temporary boatanchor. There will be intermittant downtime as domains switch IPs, hardware gets moved around, etc. Once we're 100% set up in CA, there'll be similar downtimes. I'll try to keep it to a minimum, but just be aware of it. Also, if the server seems like it's moving slowly, that's because it is. It's now on a Celeron 600 that was never designed to be a server, and will be as its temporary home until we're in CA on the new stuff. Let me know if anything doesn't work the way it should. -Xaroth 04.01.05 - Name change! So, I've decided to change the name of the board. 8088 Online! was just too... old fashioned. Just log in, and I'm sure you'll agree the new name is much better. -Xaroth 03.16.05 - Board is back up... The little tiny CPU fan and little tiny case fans died, leaving the little tiny VIA CPU to overheat. Funny how that works. The board has been moved to some other old hardware I had lying around, and is operational again. Yes, the date is still off, and no, that can't be helped until I get sufficient time to fix the underlying design problem I had with that. Here's hoping that the RTC support is there for this particular chipset so at least the time will be kept correctly. :) -Xaroth 03.16.05 - Board is down So, in keeping with this past week and half's theme of nothing going quite right, the hardware that BeBS lives on has decided to give up the ghost. It now will sit there in an infinite reboot cycle, leading me to believe that maybe the CPU fan has gone out. I'll look into that, but in the meantime, I guess the board gets to just be down for a while. *sigh* -Xaroth 10.23.04 - Hooray! So, the problem, at the end, ended up being that the modem that the city uses for our water meter was causing line noise on the DSL channels. Luckily, we were not awake when the technician came. I say this because he called my cell phone and didn't leave a message. This allowed me to call him back directly to ask why the note he left read "unable to access yard". While I had him on the line, I asked what he thought the problem might be, and he said he suspected the water meter. So, while I was on hold with Qworst to schedule a new outing, I looked in the basement and traced the line back from the water meter. Sure enough, there's a little box that reads "Property of the City of Minneapolis". I tried unplugging that and seeing if I got a connection, which I did. So, not wanting to piss off the city, I plugged it back in, and sure enough - the modem started disconnecting again. The support rep I talked to, after the long hold, said that the very same filter I use to keep my phone lines from sounding squeeky and scratchy from the DSL could be used to keep the noise that the water meter was generating on the DSL line. (That is, filters work both ways). Qwest assured me that the filter would not interfere with the normal operation of the water meter box, so one filter in and 5 minutes later, and we're online at full speed! And to think - if I'd simply listened to those fuckers that said there was nothing to be done, I'd be stuck at 640k, paying for 1.5m anyway (since they're both the same price, apparently). The lessons here - Qwest tech support largely doesn't know what they're talking about, a little knowledge goes a long way (about how the system's set up in the first place), and persistence pays off. Now, just so long as they don't charge for the technician, I'll be fine. :P -Xaroth