Wulf's cases
>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:
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: