![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
A Busy Weekend
Mar. 19th, 2007 11:51 amWell, I had another busy weekend.
Saturday was, as usual, gaming. Week #17 of our AD&D game. If you're wondering why I'm no longer writing about the game sessions here, it's because I've instead been logging the games at an AP thread at RPGnet:
http://forum.rpg.net/showthread.php?t=285217
We're still heading into a troubling transition when Donald has to move in a couple of months, but we'll see what happens.
There was, of course, also writing. The history of Hero Games, plus another 5k words on RQ elfs--which brings me to about 50k on the latter project, and in sight of the end.
I'm taking the latter half of this week off, from Wednesday to Friday. I'm planning to relax, get a new computer game (probably Icewind Dale 2), and otherwise have fun, but I'm also planning to get the RQ project done so I can stop doing this ridiculous double-duty that's been eating up every spare moment since the start of January. At a minimum I'll get a full draft done over that time. Optimally I'll also do a full edit.
However, the weekend was made all the more busy due to massive problems at Skotos. (Sigh.) There was a scheduled maintenance window on Sunday for electrical work at our ISP, which is always an ISP's way of saying, "We don't expect any downtime, but if there is some, don't say we didn't warn you." Unfortunately there was some foul-up in their electrical work and they temporarily short-circuited the whole facility, rebooting every machine there, which of course included every Skotos machine and RPGnet. This type of mistake happens sometimes, and I'm not upset about it, but it sure fouled up my weekend plans.
Tons of software didn't come up right, and when we got that straightened out, we found three machines not responding at all. I had to go down to the facility and ended up spending 4+ hours of my Sunday solving problems, with the helpful remote aid of our lead engineer. One machine had been cabled wrong, and the problem didn't show up until a reboot. Another had generated some CPU errors, and the problem didn't show up until a reboot. The last either got its boot sector corrupted, or maybe just didn't have its boot sector set up right, and the problem didn't show up until a reboot. Anyway, I got two out of three machines fixed yesterday, and the last should be coming over to my house today, for what I hope is an easy fix once I actually have it hooked up to a CD-ROM.
That made it all the more challenging to get my planend writing done this weekend. Fortunately I was on a Hero Games roll Saturday night, and I wrote up until 1.30am, finishing a first draft of that article, and on Sunday I pushed through on elfs, and finished my 5k words at midnight. Whew.
It's going to be really nice when I'm not juggling two projects. That, of course, means that the history book deadline is drawing nearer, but with FASA and Hero Games drafted this month, and Flying Buffalo and Games Workshop being my next two, with pages of notes already in place, I'm feeling pretty good about the overall status of the project.
Saturday was, as usual, gaming. Week #17 of our AD&D game. If you're wondering why I'm no longer writing about the game sessions here, it's because I've instead been logging the games at an AP thread at RPGnet:
http://forum.rpg.net/showthread.php?t=285217
We're still heading into a troubling transition when Donald has to move in a couple of months, but we'll see what happens.
There was, of course, also writing. The history of Hero Games, plus another 5k words on RQ elfs--which brings me to about 50k on the latter project, and in sight of the end.
I'm taking the latter half of this week off, from Wednesday to Friday. I'm planning to relax, get a new computer game (probably Icewind Dale 2), and otherwise have fun, but I'm also planning to get the RQ project done so I can stop doing this ridiculous double-duty that's been eating up every spare moment since the start of January. At a minimum I'll get a full draft done over that time. Optimally I'll also do a full edit.
However, the weekend was made all the more busy due to massive problems at Skotos. (Sigh.) There was a scheduled maintenance window on Sunday for electrical work at our ISP, which is always an ISP's way of saying, "We don't expect any downtime, but if there is some, don't say we didn't warn you." Unfortunately there was some foul-up in their electrical work and they temporarily short-circuited the whole facility, rebooting every machine there, which of course included every Skotos machine and RPGnet. This type of mistake happens sometimes, and I'm not upset about it, but it sure fouled up my weekend plans.
Tons of software didn't come up right, and when we got that straightened out, we found three machines not responding at all. I had to go down to the facility and ended up spending 4+ hours of my Sunday solving problems, with the helpful remote aid of our lead engineer. One machine had been cabled wrong, and the problem didn't show up until a reboot. Another had generated some CPU errors, and the problem didn't show up until a reboot. The last either got its boot sector corrupted, or maybe just didn't have its boot sector set up right, and the problem didn't show up until a reboot. Anyway, I got two out of three machines fixed yesterday, and the last should be coming over to my house today, for what I hope is an easy fix once I actually have it hooked up to a CD-ROM.
That made it all the more challenging to get my planend writing done this weekend. Fortunately I was on a Hero Games roll Saturday night, and I wrote up until 1.30am, finishing a first draft of that article, and on Sunday I pushed through on elfs, and finished my 5k words at midnight. Whew.
It's going to be really nice when I'm not juggling two projects. That, of course, means that the history book deadline is drawing nearer, but with FASA and Hero Games drafted this month, and Flying Buffalo and Games Workshop being my next two, with pages of notes already in place, I'm feeling pretty good about the overall status of the project.