Simplified ROM folder structure

modules/build/lib/build.js

@@ -227,7 +227,7 @@ var machineElements = {
                 'id': "romBIOS",
                 'addr': "0xfe000",
                 'size': "0x2000",
-                'file': "/devices/pc/rom/5150/bios/1981-04-24/PCBIOS-REV1.json"
+                'file': "/devices/pc/rom/5150/1981-04-24/PCBIOS-REV1.json"
             }
         ],
         'addr': {

modules/pcjs/bin/ibm5150.json

@@ -28,7 +28,7 @@
       "name": "",
       "addr": 0xfe000,
       "size": 0x02000,
-      "file": "/devices/pc/rom/5150/bios/1981-04-24/PCBIOS-REV1.json",
+      "file": "/devices/pc/rom/5150/1981-04-24/PCBIOS-REV1.json",
       "notify": ""
     }
   ],

modules/shared/lib/dumpapi.js

@@ -43,11 +43,11 @@
  *
  * Similarly, our "FileDump API" used to look like:
  *
- *      http://jsmachines.net/bin/convrom.php?rom=/devices/pc/bios/5150/1981-04-24.rom&format=json
+ *      http://jsmachines.net/bin/convrom.php?rom=/devices/pc/rom/5150/1981-04-24/PCBIOS-REV1.rom&format=json
  *
  * and that request now looks like:
  *
- *      http://www.pcjs.org/api/v1/dump?file=/devices/pc/bios/5150/1981-04-24.rom&format=json
+ *      http://www.pcjs.org/api/v1/dump?file=/devices/pc/rom/5150/1981-04-24/PCBIOS-REV1.rom&format=json
  *
  * I don't think it makes sense to avoid "query" parameters, because blending the path of a disk image with the
  * the rest of the URL would be (a) confusing, and (b) more work to parse.

modules/textout/lib/textout.js

@@ -88,7 +88,7 @@ TextOut.asTargetRefs = ["call", "jmp", "jz", "jnz", "jc", "jnc", "ja", "jna", "j
  *
  * Examples
  * ---
- *      node modules/textout/bin/textout --file=devices/pc/bios/compaq/deskpro386/1988-01-28.nasm --nasm
+ *      node modules/textout/bin/textout --file=devices/pc/rom/compaq/deskpro386/1988-01-28/1988-01-28.asm --nasm
  */
 TextOut.CLI = function()
 {