Conversation
|
Can you order them chronologically and use |
|
Can do, thanks for the feedback! |
eschaton
force-pushed
the
eschaton/concept-17-rom
branch
from
572b21d to
81d9f8d
Compare
Set the Corvus Concept 1.7 (Version 1 Level 7) ROMs as the default.
eschaton
force-pushed
the
eschaton/concept-17-rom
branch
from
81d9f8d to
308ca4d
Compare
| // the 1.7 ROM (at least) works with Corvus OS 1.2 | ||
| ROM_SYSTEM_BIOS(3, "v17", "Version 1 Level 7" ) | ||
| ROMX_LOAD("ccb17h.bin", 0x010000, 0x1000, CRC(6dd9718f) SHA1(7427d218dc13b1b319866d5a1e59e152fab082b3), ROM_BIOS(3) | ROM_SKIP(1)) | ||
| ROMX_LOAD("ccb17l.bin", 0x010001, 0x1000, CRC(107a3830) SHA1(0ea12ef13b0d11fcd83b306b3a1bb8014ba910c0), ROM_BIOS(3) | ROM_SKIP(1)) |
There was a problem hiding this comment.
Why the change to the labels here? We usually use "." format for these.
There was a problem hiding this comment.
Sorry, I'm not up on the terminology—which strings are you referring to as labels? I'm happy to change it however you like.
The Corvus code sometimes says "Version 1 Level 7" and sometimes "V1.7" and sometimes "1.7" while the code in the file uses "lvl" for the other values. For the filenames, I just lowercased the names of the files on Bitsavers, I could use exactly the same name or use the names from the removed code, it's all fine by me.
There was a problem hiding this comment.
The quoted strings, e.g. "ccb17h.bin", are called “labels” – MAME does use as file names when searching for assets. We usually try to format these by putting the label/mask code/etc. from the chips (in lowercase with restricted character set) before the final dot, and the PCB location afterwards.
For example "mon_4-000-v_2.1.a1" was from a chip labeled “MON 4-000-v 2.1” at PCB location A1 in an Intel development system.
Do you know what the labels and PCB locations for these chips are?
There was a problem hiding this comment.
Thanks for the explanation! I can check my Concepts for the PCB locations. (I assume a socket number like U37 would be ideal while grid location would be acceptable?)
Unfortunately I don't have the 1.7 ROMs in my Concepts so I can't check them for label/mask code/etc., and I don't think anything like that was recorded for the dumps on Bitsavers. Al does that when he can, so I expect the ROMs may have been hand-labeled.
3 participants
Set the Corvus Concept 1.7 (Version 1 Level 7) ROMs as the default.
With this, I've been able to successfully boot, install, and use the Corvus Concept OS 1.2 from Bitsavers.