YUKI.N Drive Re-Ignition

[THUNDERBOLT][UNCLASSIFIED] Tachyon transmission. To: Grand Admiral Stripey, Hontou ni Taihen desu (NEMU-class space station, coords 1-17N 103-51E). From: CPL (NS) Zyl, hontou ni sou omou (LUNA-class light cruiser, current coords 51-30N 0-7W). Re: REDCON ICHI achieved. Advice implemented. Main local drive system [YUKI.N] for fully operational once again. Maintenance logs and diagnostics are attached for reference.

Local support and supply depots were unable to reinitialize drive due to incompatibility between this region’s XPHome install and our originating region, OEM-issued key. Initial initialization based on XPPro system failed due to friendly key (starts with FCKGW and ends with 2B7Q8) being no longer operational and complicated by disk surface irregularities that corrupted networking drivers. Original XPHome package with original key was received two days ago from the third node of the net, bringing the situation up to REDCON SAN.

REDCON NI was achieved after successful linguistics augmentation. Basic visual and aural functionalities were enhanced with the relevant Compaq website drivers. OEM advised that hardware model was actually X1031AP rather than X1000 as originally believed. Receiving field data was re-established with internet connnection backoline (specifying main and alt DNS servers under networking tab of connection properties), utorrent and adding the relevant firewall rules to achieve a green light on the DHT. Data observation came back onstream with updating DirectX to version 9 or above (MS authentication required), followed up comrade CCCP codecs, tested on data held on external drive [REI.A].

REDCON ICHI finally reached with bsplayer for image capture, APS6 for imaging editing (recorded macro 4tw), WinSCP for uploading to server and voice comms restored for Hontou ni Skype conference. Looking forward to return to home base and fleet concentration exercise in XX-07-2007. [UNCLASSIFIED]


3 Responses to “YUKI.N Drive Re-Ignition”


  1. 1 starcaptor

    The famous FCKGW key >D
    Glad ure back in the green to reign in the new year =)

  2. 2 quigonkenny

    “OEM advised that hardware model was actually X1031AP rather than X1000 as originally believed.”

    Gotta love the HP/Compaq naming convention. I can see that first meeting with the department that handles the labelling…

    Boss: Okay, the guys in corporate have decided that we’re going to name all of our Compaq models a certain way.
    Labeller#1: All right.
    Boss: Okay, first, every series is going to have a master series number. The one that uses this case design, for instance, will be the X1000 series.
    Labeller#2: Okay, makes sense.
    Boss: All right, now inside of each series, we’ll break down each hardware configuration into different model numbers that are based off of the master series number, like, say…X1031.
    Labeller#3: Good, good…
    Boss: And we’ll add a suffix to the model name to let everyone know what region the unit is for. For instance, US for the United States, or EA for Eurasia, or AP for Asia/Pacific. All this is because it will be very important for the customers to know exactly which model they have, so if they have to download drivers they’ll get the right ones.
    Labeller#4: That makes a lot of sense, boss; they’ve put a lot of thought into this.
    Boss: You betcha. They sure have. Now, the most important thing–and here is where you guys come in–the absolute most important thing, and I can’t stress this enough, is that the only model number to appear on the unit be the master series number.
    Labellers: Huh?

  3. 3 Zyl

    Thanks, starcaptor. It’s good to be in the green.

    quigonkenny, well at least they stuck the model number on the bottom and I could translate that into X1031AP in the end. Given how screwed up a lot of these things are, thanking goodness for small mercies.

Leave a Reply

Quicktags: