| Sun, 30 Jun 2013 01:17:30 +0000 | 
  Michael Spacefalcon | 
  
   beginning of Mokopir-FFS verbal description
   
   | 
 
 
  | Sat, 18 May 2013 23:43:46 +0000 | 
  Michael Spacefalcon | 
  
   MysteryFFS: extract utility seems to work
   
   | 
 
 
  | Sat, 18 May 2013 23:08:13 +0000 | 
  Michael Spacefalcon | 
  
   MysteryFFS: beginning of the extract utility
   
   | 
 
 
  | Sat, 18 May 2013 21:09:33 +0000 | 
  Michael Spacefalcon | 
  
   MysteryFFS dump2: dumping all file fragments
   
   | 
 
 
  | Sat, 18 May 2013 19:48:07 +0000 | 
  Michael Spacefalcon | 
  
   MysteryFFS: dump2 started, dumping the initial frag of each file
   
   | 
 
 
  | Sat, 18 May 2013 19:21:09 +0000 | 
  Michael Spacefalcon | 
  
   MysteryFFS dump1 tool written
   
   | 
 
 
  | Sat, 18 May 2013 08:22:15 +0000 | 
  Michael Spacefalcon | 
  
   beginning to explore MysteryFFS
   
   | 
 
 
  | Thu, 25 Apr 2013 06:56:17 +0000 | 
  Michael Spacefalcon | 
  
   boot ROM re: some sensible documentation written up
   
   | 
 
 
  | Thu, 25 Apr 2013 06:03:27 +0000 | 
  Michael Spacefalcon | 
  
   boot ROM re: some better comments
   
   | 
 
 
  | Thu, 25 Apr 2013 05:47:59 +0000 | 
  Michael Spacefalcon | 
  
   boot ROM re: appears to be complete!
   
   | 
 
 
  | Thu, 25 Apr 2013 04:07:10 +0000 | 
  Michael Spacefalcon | 
  
   boot ROM re: got through the <w handler
   
   | 
 
 
  | Thu, 25 Apr 2013 03:16:17 +0000 | 
  Michael Spacefalcon | 
  
   boot ROM re: getting the download state machine, <p parsed
   
   | 
 
 
  | Thu, 25 Apr 2013 00:08:51 +0000 | 
  Michael Spacefalcon | 
  
   boot ROM re: unraveling the response message routine
   
   | 
 
 
  | Wed, 24 Apr 2013 23:49:39 +0000 | 
  Michael Spacefalcon | 
  
   boot ROM re: starting to unravel the serial command handling
   
   | 
 
 
  | Wed, 24 Apr 2013 22:48:12 +0000 | 
  Michael Spacefalcon | 
  
   boot ROM re: continuing plowing through the serial protocol code
   
   | 
 
 
  | Wed, 24 Apr 2013 19:32:45 +0000 | 
  Michael Spacefalcon | 
  
   boot ROM re: making inroads into the 0x2c8 routine
   
   |