Today I learned of one additional bug with the Rejuvenator.
Most folks here will never, ever care about this. But I was working with a friend today *(Crispy) with a new program he'd written that allows A1K's and StarDrives to soft-reboot without the need of a floppy disk. Really, really cool.
And this is regarding the RAD:, the recoverable RAM disk, which should be persistent until you manually remove it with the RemRAD command. The RAD command should make the program in question resident, and allow it to survive reboots.
I went through a process tonight to see if the clone Rejuve would honor the RAD.
It did not.
On soft-reboot, it cleared it out.
That being said, there does not appear to be any mention online anywhere of the Rejuvenator not honoring the RAD:. However, I'm not currently in the mood to pull my clone board to put in the OG board to re-test this.
Either way, it is something the clone board (and possibly original) suffers from. Again - this is an edge case, but it is something that affected a project I've been working on for weeks and surprised me.
Crispy:
It should survive any number of reboots.
For some reason it's messing with the chip ram memory, and overwriting or corrupting code that was in there before the reboot.
There's no way to do [my program] autoboot, or any other resident program, on an A1000 with a Rejuvenator.
Or, at least a cloned Rejuvenator. But possibly all of them.