Sure that should work provided same ram size.
On Wednesday, August 14, 2019, Josh Malone wrote:
> Aren't the RAM images from REX compatible with RAM images saved out of
> Virtual T? You could cold-start a VT instance and save its RAM, rename
> it to .BY and load that into the REX, right?
>
> On
Aren't the RAM images from REX compatible with RAM images saved out of
Virtual T? You could cold-start a VT instance and save its RAM, rename
it to .BY and load that into the REX, right?
On Wed, Aug 14, 2019 at 7:16 AM Stephen Adolph wrote:
>
> To make a new ram image I would cold restart the m10
To make a new ram image I would cold restart the m100, install rexmgr, and
save the ram right away.
On Wednesday, August 14, 2019, Eric LK wrote:
> Thanks for your advises!
>
> I think I'll start by backup everything on the PC, and "reformat" the
> REX (deleting all RAM images).
>
> It seems eas
Thanks for your advises!
I think I'll start by backup everything on the PC, and "reformat" the
REX (deleting all RAM images).
It seems easy enough to backup whole RAM images as "BY" files from the
REXMGR so I'll do this regularly in case anything goes wrong in the
REX's flash :o)
I'll also have
On Sun, Aug 11, 2019 at 7:06 PM Stephen Adolph wrote:
>
> Wilson van Alst produced a piece of software that recovers ram files after
> a cold restart. Worth understanding how to use that.
>
>>
>>
I think TS-DOS also has a feature for getting data in RAM after a cold
start.
Erik you could also
Wrt the program name behavior... I suggest a cold restart.
I think you should test your backups also.
You could also go in and extract files one by one from a stored image into
a new cold restart ram. Probably there will be name corruption so the
extraction gives you the chance to rename.
I wou
Since there is some talk about REX on the list, it may be a good time
to ask a few questions I have about it :o)
I've been using the version 4.9 of the firmware with a M100 for a few months.
First, there is this thing in the documentation that I'm not sure to understand:
> REXMGR has to be locate
