Overall methodology: Following the Assignments page, read through corresponding documentation within the Companion user manual, the command reference, the Robot Hardware Handbook, and other support.ns and develop.ns pages if necessary. Press every button, run every command option, and make sure it all works. Report your findings and any anomalies via email.

Reminder: You are a volunteer. Do not agree to do work you cannot do. It is better to admit when you're procrastinating, avoidant, or overworked than to cause the whole project to stall. We can find someone else, but the work won't get done if stubbornness, pride, or exhaustion gets in the way. It's okay to throw in the towel.

Step 0: Make sure you are running the latest OS version. These are announced via Group Notices in the Nanite Systems User Group. Relevant documentation for how to update is at this link.

Step 1: Start a notecard and document what you're working on, the date, your current OS and ATOS/E version, your region, and whatever else seems relevant. Examine menus or command line to get an understanding of how the features in question seem to be organized. here) and any features within or connected to them will be affected. Equivalently you can also re-attach your controller or re-log, but these "cleaner" resets do not quite capture the joie de vive of how bad SL region changes are.

Step 5: Repeat Step 3. Note anything that changed unexpectedly as a result of the TP.

Step 6: If you do catch problems in step 3 or 5, it's time to turn on debug mode and repeat the things that went wrong. Debug mode is enabled with the commands @coil ddt (for system memory) and @disk ddt (for user memory) and will spam your debug window like crazy. Turn it off when you're done by repeating those commands, and then save all the evidence.

Step 7: Mail in your report as a notecard to rhet0rica.resident.

Step 8: Next!