all the right friends in all the right places

Wulf's cases

runsinpacks — Sun, 10 Jul 2011 15:26:00 GMT

>NPC Casefile:
Patch code for program with puncture wound through hand. Needed patch to stop injury from spreading before resync.
Cosmetic repairs for a program who landed on her nose. Also advised to decrease neat energy intake.
Legless program in a building Rinzler blew up.

Minor lacerations, bruising, and armor damage due to a building collapse (Rinzler)
Wide-frame scan for code extrapolation, fed code into an open file, incorporated necessary patches/rewrites, tested the fix for compatibility. Incorporated changes into disc(s). Had to collapse memories and dump backup templates just to have processing room for the entirety of the information needed to insert the changes into the complex code. Resynced.
Complications: even a surface scan showed evidence of the large-scale tampering that Rinzler's code had endured. Also, incorporating the fixes took longer because of the complex way the two discs interacted. Procedure was exhausting.
Case notes: workspace snapshot, file of notes and exceptions pertaining to Rinzler's configuration, peripheral information ("took longer to resync but stayed partially aware", "could read his own code").
Follow-up: none.

Glass lacerations with debris in the wound (Aadi)
Medium scan for code extrapolation & to locate debris. Placed code in a flat pane/file next to workspace. Immobilized injured area with a code needle that stopped its energy flow. Extracted glass (no details mentioned) & dropped it in receptacle for derezzing later. Removed needle; rescanned for comparison. Rewrote damaged code in pane/file. Decompressed (Stream code. Scan for errata. Save. Reduce to template. Save. File secure. Memory cleared. Ready.); most information now ONLY in pane/file. Incorporated changes into disc. Cleared cache. Resynced.
Complications: none.
Case notes: notes on glass injuries. Also, various ISO exceptions, for reference when working with other ISOs. Luckily ISO surface format & circuit energy flow is similar to that of Basic programs; if it'd been a more complicated injury he might have only been able to stabilize it. (Used to have a large library of such exceptions; Clu erased it.)
Follow-up: Patient advised to rest more, as chronic lack of downtime had been impeding her healing.

Disc slice to left shoulder; program's healing protocols inoperative (Anon)
Light scan for code extrapolation. Placed code in a read/write file. Isolated damaged code strings. Repaired, with aid of code copied from either side of the gash. Resynced.
Medium scan for issues with healing subroutines, accessing permissions and directory trees. Discovered truncated subroutines stemming from an upgrade that was reverted when Anon was rerezzed.
Complications: Wulf doesn't have the permissions to rewrite and redirect the truncated subroutines; a User would have to do it.
Case notes:
Follow-up: Patient advised to request help from a User in re truncated subroutines, and to get injuries dealt with promptly until that happens.

Energy depletion due to rerezz (Echo)
Fed her an energy packet ~~and fortunately got away without being derezzed for insolence~~.
Complications: one of these days his protocols, which don't let him take time to summon backup if a program seems injured, are going to force him to tend to a sentry who, once recovered, will go haywire and disc him. He can just see it. :/
Case notes: nothing but the incident log.
Follow-up: none ~~unless Echo follows him home~~.

Severe energy depletion and surface damage after rerezzing (Radia)
(Still working on thread.)
Complications: ISO codes.
Case notes: a ton of data on ISO codes.
Follow-up:

Injury ()
Complications:
Retained:
Follow-up:

Stuff Wulf is involved in

runsinpacks — Fri, 01 Jul 2011 19:50:49 GMT

Fluff meme (threading with Ram)

Snow Day meme (threading with Eric and Sash)
Snow Day meme (threading with Loki)

Wulf and Eric || Walkthrough

runsinpacks — Thu, 26 May 2011 18:33:11 GMT

Who: Wulf (runsinpacks) and his User, Eric Kleinberg (lil_bro_lost)
Where: an Encom I/O tower and The Real World.
When: late 1988.
What: Wulf's User takes him through one last demo run before sending him off.

Wulf:
Wulf just, um. Will be looking skeptically up at the IO beam, not sure what he's doing here. His User wrote him to repair and interact with other programs, so being called from the other side isn't something that often happens to him.

Eric:
Eric, meanwhile, is looking over his shoulder at his mun like she's a crazy person. Because, really, wouldn't one of the other programs be better for this? Tron or Clu? He can ask for a status update, maybe.

C:/> display scan results: drive C:

Wulf:
It was a little confusing, to be honest. Wulf wasn't even supposed to keep most of the processed data, just cycle it over to the system monitors for storage.

"Well, I've got the end results, anyway," he called uncertainly, squinting up into the light. "You'll have to ask someone else for the breakdown, but the results, yeah, there's no shortage of those. It should be enough to tell you what ran successfully and still needs work."

There was a silence -- the User typically responded in his own time. Wulf waited, trying not to close his eyes against the powerful light, and considered the question again as a second interpretation of its intent occurred to him.

Remote as the possibility was, he answered it, in the interests of completeness.

"..I'm all right too."

Eric:
C:/> run demo: display
C:/> print demo: results
If he was going to be sending this little program over to someone else, he was damn well going to show off what itw as capable of. he was proud of it!

Wulf:
"I did save that demo... um... here it is." A quick rummage in his kit produced his packet of tools and the hypotheticals designed to test and maintain his skill. This was a dance he'd done many times during and after compilation. To repeat it now, carefully completing each step of the demo as a completed program with no slips or recodings to fear, was both nostalgic and satisfying. Almost half a microcycle went by as he lost himself in the motions and instructions, feeling a strange peace settle around him as he completed the run. It was... good, to know what he was made for and to do it well.

At his User's next instruction, a tentative, reluctant smile crept onto his narrow face.

"You really think so?" He'd done what he could according to the functions he'd been given, but for his results to be important enough for Print... he'd never expected that.

Eric:
There we go. "See, that's what happens when you do good work," which felt a little absurd, but Eric had discovered programming almost required talking to yourself. The programs, which was really talking to yourself. "Now... let's get you packed up and off to this Flynn guy."

C:/> pkzip
C:/> move B:/

Wulf:
The praise left Wulf with an almost giddy feeling of warmth and belonging. He closed his eyes, holding still for a moment as he tucked it away deep in his memory. Given his purpose, it was always important to do that; who knew, after this, whether he'd ever hear that voice again?

"Who's Flynn?" he asked, but all his User would tell him was that Flynn was someone who needed a program like him, and he must do his best and everything would be okay. Users were sometimes cryptic.

"As if I'd ever do less," he answered, but the smile still lingering on his face robbed the words of irony.

The light didn't really feel bad anymore as he plucked his descending disc out of the beam. Returning it to its rightful place, he shrugged his kit back onto his shoulder and, with a last confident look upward at the gateway to the other world, he left the platform and walked toward the waiting transport. At least he wouldn't have to be active for the trip. B:/ wasn't a bad way to travel, but he'd heard it could be really tedious in there.
_____

runsinpacks — Fri, 20 May 2011 09:00:33 GMT

...all right, so it's better than being a sentry. I just wish I knew what happens next.

Wulf's mun:
--Slowtags
--Prefers gen-only threading
--Is really friendly actually :D