Not a bug, but the init pattern in vice does not resemble this at all.
Perhaps it would be nice to have a startup ram BIN file and an option to randomize it with parameters...
About the ram chips, here they are..
but the init pattern in vice does not resemble this at all.
The init pattern was tweaked to resemble a common init pattern - and then carefully tweaked further so certain software that relies on it works. So like SID filters, it can only ever resemble "a" C64 - but never match a particular one.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
this the full mem from $800 to $FFFF
obtained by filling the mem with 00 then shutting down for a few minutes then dump.
I will make a better cold dump tomorrow... the previous one was incomplete..
here we go.. after some trickery I found a way to dump the full 64K or ram before the system starts and after a very cold boot.
Last edit: Zibri 2023-04-09
Whats the bug here?
In any case, the type of RAM chips is the interesting bit
Not a bug, but the init pattern in vice does not resemble this at all.
Perhaps it would be nice to have a startup ram BIN file and an option to randomize it with parameters...
About the ram chips, here they are..
The init pattern was tweaked to resemble a common init pattern - and then carefully tweaked further so certain software that relies on it works. So like SID filters, it can only ever resemble "a" C64 - but never match a particular one.
Added the dump to the testrepo.
you can simulate this one reasonably well using something like this:
-raminitstartvalue 0 -raminitvalueinvert 16 -raminitpatterninvert 0 -raminitvalueoffset 0 -raminitpatterninvertvalue 0 -raminitstartrandom 0 -raminitrepeatrandom 0 -raminitrandomchance 500