• The Two Larger Towers

    Here’s the capsule review of the Two Towers “extended” showing today:

    Only two restored scenes were particularly useful. The most important is the Boromir/Faramir Flashback. Say what you will about its overall usefulness to the plot, it was very interesting backstory in its own right. The other scene is the Eowyn’s Stew bit, mostly useful for showing us what a good cook Eowyn is. No no, that’s not right. It’s useful because we find out Aragorn’s age (which isn’t interesting in and of itself, but learning his age tells us something about his lineage).

    Another restored sequence is a bit of characterization goofiness from Merry and Pippin, where they find Saruman’s stash of pipeweed. Oddly enough I was delighted to see that sequence, since it’s one of the few bits from the books that remains vivid in my mind years after the reading. Your enjoyment mileage may vary, of course. Of questionable value is another “let’s give Merry and Pippin more screen time” sequence involving some magic water…

    As with Fellowship, most of the restored footage took the form of “making existing scenes just a bit longer.” Well, I can’t forget the additional Gimli, Comic Relief Dwarf moments. Le sigh. I was sort of hoping that the trend begun with the Fellowship extended release would continue, but apparently the movies’ creators don’t share my despair at using the dwarf almost exclusively for very cheap laughs. Ah well.

    Is Two Towers better in its extended form? Absolutely. Nothing is changed about the overall tone or pacing, and while some of the originally-excised scenes weren’t necessary for the sake of audience comprehension (we don’t need to see Theodred’s funeral: we know he’s dead) they don’t detract from the film either. No, not even the Comic Relief Dwarf moments. (I admit to laughing at the last one of those.)

    Mind you, most of the people who might find this review useful have probably already purchased the appropriate DVD release. Ah well…

  • Past, Present, Future – Round Forty-three

    PAST: What would you consider your first real accomplishment in life? We’re talking about something you put real, conscious effort into, here.

    PRESENT: What are you working on now that you’re hoping to have accomplished soon?

    FUTURE: What accomplishment would you like to be remembered for? (Hint: This is where you could get away with making up something delightfully improbable.)

    And I feel better for having accomplished this round of the PPF while under considerable stress. Huzzah! Comment so we know you were here, please? And as always, link back using the handy-dandy always-updated permalink below. Thank you!
    http://greyduck.net/ppf/

  • Of Windows, Phone Equipment And Troubleshooting

    The fun and excitement of the Enco situation this week has obscured another interesting technical situation. We ordered some new studio telephone equipment that arrived late last week, and today (at long last) we tried to configure its hub.

    Telos’ 2101 “hub” is a computer designed to manage remote phone sets. (This is the machine we thought was blue-screening last week, for those of you who’ve been following along at home.) It’s running Windows NT “Embedded,” which I’ve never seen before.

    So we tried to configure it over the network, which is the only way provided to configure one of these machines. After sorting out some subnet issues we were able to ping the box, but not talk to it via the provided configuration utility.

    “Oh,” Telos’ tech support says, “You have to authenticate to the box first.” Turns out we have to search for the machine by IP address through Windows networking, connect with username and password, then the configuration utility is allowed to do its job. Hmm. We didn’t see that anywhere in the documentation.

    Then things took a turn for the weird. See, it turns out that the provided utility is known for doing weird, bad things to the device it configures. Well, we don’t want that, do we? So we attempt to download updated software via the utility. And we attempt, and we try, and we try, and we attempt, and we try some more. All is for naught, however, and we can’t figure out why. One clue is that the reported software version on the 2101 is more than two years old. It is, in fact, almost the first “released” version of the 2101’s software. This baffles Telos’ tech support guy.

    In an attempt to figure out what’s going on (here comes the cool part) I’m instructed to fire up Netmeeting and use it to connect to the 2101… and upon connection I’m given a desktop to control! That’s right, folks. I was looking at an NT desktop via a Netmeeting instance designed to allow last-ditch system administration on a box that lacks keyboard and video display (but does provide the hookups therefore, go figure).

    To wrap up, it turns out that the software we were trying to connect to and update wasn’t even running on the computer. Telos is going to prep a new CF card with the most-recent software revision and “all that,” which we should receive next week. Supposedly we can just drop that CF card into place and ship them back the one we have, and then we’ll be able to use the web-based administration and (gasp!) actually have working, running software when we boot the device.

    Wow. I’m really glad I didn’t go home immediately after we finished up the Enco project today…

  • How’s your hair? Fine!

    I was in the shower the other morning and for the first time in the years I’ve been using the stuff decided to actually read the instructions on my bottle of Senscience shampoo.

    Now, most of the instructions are fairly normal, but one of the things they want me to do seems… odd. Let me show you. (My commentary is parenthetical.)

    DIRECTIONS: Wet hair thoroughly. (Okay, I’m with you so far.) Apply shampoo. (To the hair, I assume?) Lather well and rinse. (Gotcha.) Repeat if necessary. (It never has been, but I’ll keep that in mind.) Available exclusively at fine salons. (You said WHAT? You want me to get out of the shower right now, head to my nearest “fine salon” and buy a bottle of something I already have? Dripping wet naked? Are you people insane?)

    See what I mean?

    For the record, that last instruction is clearly before the paragraph break, and it shows up at the end of each language’s set of instructions. “Exclusif aux meilleurs salons,” and also “De venta exclusivamente en finos salones de belleza.” I am not making this up, as Dave Barry is wont to say. Bizarre, I tell you.

  • Enco Wars

    First thing Tuesday morning, the main Enco digital audio storage server died. After hours of troubleshooting and tinkering, we brought it back online… minus all of its audio data that was lost when one of the drives in its array died. (We’re running RAID 0 because it’s the only way we can get enough capacity out of the array.)

    We switched everybody over to the standby server, and told that server to restore its audio data to the main. No problem, right?

    Wrong.

    Shortly before midnight last night, the standby server decided to hang. We lost ten hours out of our restoration process because the server didn’t crash enough to come to the attention of my server monitor. Argh. (It was reporting X amount of available drive space… on a drive that was no longer responding. *grumble*)

    The plot thickens: An attempt to restart the “rsync” file transfer process revealed another problem. Rsync was starting over from the very first file… even though no differences between the source and destination files could be determined! I’ve come to believe that using rsync across operating systems is a Very Bad Idea. (I’m having a similar problem backing up our main office server. Le sigh.)

    So now I get to manually copy batches of audio data from the standby to the main server. This should only take, oh, another dozen hours or so. Nevermind that the copy command does a slower job than rsync, and nevermind the headache of updating to catch deleted files. I’m probably going to have to perform evil involving something like DirComp from a Windows workstation mapping both servers.

    All of this adds up to no vacation day tomorrow, and I’ll probably be here Saturday and Sunday as well. I’m going to be gone Monday, no matter what: No way am I missing out on Two Towers!

    UPDATE: It’s just about 9pm, and I’m just about to head back to the office. Why? Because the file transfer has stopped again. This graph shows the traffic on the network port through which the file transfer is being done. See that sudden stop right around 5:30? Right about the time I was leaving the building? Yeah, that’s just peachy.

    Near as I can tell (from shelling in to the standby server from home), this time the stoppage isn’t because the RAID controller in the standby server is a piece of crap. (That was the cause of last night’s crash.) I don’t know why it’s stopped, really. I only know that I have to go back down there and start it up again. Le sigh.

    At this rate I really will still be working on this “project” come Saturday. Argh. I love my job, really I do… but sometimes there are parts of my job I could do without.

  • All Hail Sumomo

    Another care package from The Great Wet North arrived today. No brownies this time, but I did get some music CDs and…

    Hey look, it’s a mug, and cocoa to drink from that mug! But wait… whose image is that on the mug? Let’s take a closer look:

    It’s Sumomo! I have a Sumomo mug! Yay!

    Wow. Whoever sent me this must be one heck of a nice person, huh?