According to Unwired pg119:
QUOTE
Patching requires a regular programming Extended Test for that software type using Software + Logic and an interval of 1 week. In place of rating, however, use the difference between the degraded rating and the regular rating of the program.
So to keep a program current takes 1 week and 1 hit on a Logic+Software test. Assuming a Programming Suite 5 is available to a hacker with 4 Software skill and 7 Logic thats 16 dice. To keep from making the Commando witnessing the rolls from clawing his own eyes out he buys hits at the standard 4:1 so his 16 dice buy 4 hits... but he only needs 1 hit.
Q: Is his 4 hits able to patch 4 rating points spread 1 rating point per program across each of 4 programs?
Q:If so, is the same dice-rolling method permissible with other tests like forging licenses and programming program options?
DISCLAIMER: I know that extended tests for forging lifestyle are handled differently, I'm asking about other software tests.
====
I'm posting this in the missions forums since the book is not explicit and there are serious time constraints for maintenance functions. Every four games patching has to be restarted! My weekly SR GM will certainly do it one way and there are several ways folks can simplify it... my question is how it is to be handled for SR missions.