This sounds like it should be the name of a JRPG https://en.m.wikipedia.org/wiki/Trembling_hand_perfect_equilibrium
Not enough love and attention is given to most modern Linux distro installers. It is really nice how easy and fast you can get a system installed and running.
In other news, I have written a class for my 6502 emulator that lets me simulate memory mapped IO devices. I've got for piping bytes to and from stdin/stdout and one that will perform "syscalls" depending on the value written to it. There's only 2 syscalls atm, one that exits the emulator and one that's essentially a host level breakpoint. It is at this time that I realize that I have spent way more time on this emulator than I was originally intending.
I just wanna mention that I am, in fact, a dumb bitch. I ordered both SOIC8 and SOIC16 clips fully expecting my x200t to use one of those form factors. No. Instead, it uses WSON8 which does NOT have clips for it because it's so god damn thin. I'm gonna have to whip something up that I can clamp down onto the board and will allow me to make precise contact with each of the chip's pins because I am not about to solder or desolder anything lmao. Not catastrophic, but annoying nonetheless.
Ok so hear me out. What if you had a perfectly normal 6502 processor but one day you discovered that it had an illegal opcode that spawns a clone of the processor and its attached memory. The only difference in its memory being that it would set its UNIVERSE REGISTER with the immediate value from the opcode that spawned it.
The universe register is just an arbitrary place in memory with no other other special function other than being given a value upon birth by the parent 6502.
This is very surprising. No one could have ever guessed this would happen in a billion years.
> Alexa and Google Home abused to eavesdrop and phish passwords
In other news, I've added conditional breakpoints so that's cool. I opted to define conditions as a hash that specifies the register, operation, and value to check against instead of getting messy with lambdas.The reason being is that this way I can programmatically check the definition of a breakpoint whereas a lambda (in ruby at least) is essentially write only. I don't have a specific use case in mind for this but I'd just like to keep options open for the future.
Finally figured out in which specific instances the overflow flag will be set and cleared. There's one resource out there at https://www.csh.rit.edu/~moffitt/docs/6502.html that lays each instruction out in the most granular way possible and I am infinitely grateful to it for that.