Client-side support for the original DiskDump API is finally limping along

devices/pc/video/ati/vga/README.md

@@ -19,11 +19,11 @@ Each ROM chip apparently contains 32Kb of data, but only the upper 16Kb of each
 
 and merge them into a single 64Kb file, using the PCjs [FileDump](/modules/filedump/lib/) utility:
 
-	filedump --file=VGA_Wonder_V3-1.02_EVEN.BIN --merge=VGA_Wonder_V3-1.02_ODD.BIN --format=rom --output=VGA_Wonder_V3-1.02.rom
+	filedump --file=1988-11-11/archive/VGA_Wonder_V3-1.02_EVEN.BIN --merge=1988-11-11/archive/VGA_Wonder_V3-1.02_ODD.BIN --format=rom --output=1988-11-11/archive/VGA_Wonder_V3-1.02.rom
 
 Then, within the resulting 64Kb file, we extract the ROM code+data from the upper 32Kb:
 
-	filedump --file=VGA_Wonder_V3-1.02.rom --offset=32768 --format=json --output=VGA_Wonder_V3-1.02.json
+	filedump --file=1988-11-11/archive/VGA_Wonder_V3-1.02.rom --offset=32768 --format=json --output=1988-11-11/VGA_Wonder_V3-1.02.json
 
 And now we have a JSON-encoded ROM image that PCjs machines can load.
 
@@ -31,7 +31,7 @@ And now we have a JSON-encoded ROM image that PCjs machines can load.
 
 To create a human-readable dump, you can use the following command:
 
-	filedump --file=VGA_Wonder_V3-1.02.json --format=bytes --comments
+	filedump --file=1988-11-11/VGA_Wonder_V3-1.02.json --format=bytes --comments
 
 Here are the first 12 lines from that dump:
 
@@ -47,4 +47,3 @@ Here are the first 12 lines from that dump:
 	0x72,0x20,0x42,0x69,0x6F,0x73,0x2C,0x20,0x56,0x65,0x72,0x73,0x69,0x6F,0x6E,0x20, // 0x00000090 r Bios, Version 
 	0x56,0x33,0x2D,0x31,0x2E,0x30,0x32,0x20,0x0D,0x0A,0x00,0x1E,0x06,0x57,0x56,0x55, // 0x000000A0 V3-1.02 .....WVU
 	0x52,0x51,0x53,0x50,0xBA,0xE8,0x46,0xB0,0x16,0xEE,0xBA,0x02,0x01,0xB0,0x01,0xEE, // 0x000000B0 RQSP..F.........
-

devices/pc/video/ibm/vga/1986-10-27/ibm-vga.nasm

@@ -1,4 +1,4 @@
-;
+Aa;
 ;   ROM BIOS for IBM VGA Adapter (aka IBM PS/2 Display Adapter)
 ;   (C)COPYRIGHT IBM Corp. 1984, 1986 10/27/86
 ;