At some point in REX I included a feature to maintain clock setting through ram image swaps.
On Wed, Nov 1, 2017 at 8:21 AM, Brian Brindle <[email protected]> wrote: > Peter, > > The current clock in the M100 does just fine usually. Unless it sits for a > long time. My request for another one is just me being lazy. (sort of). > > I use my m100 in strange ways and often I have issues where it crashes or > locks up and requires a total system reset. > Most of my activities with it require accurate time. I'm either logging > things, tracking things or just doing notes etc. > With REX it's like a dream to recover from these situations. Granted, more > times than not REX is also the cause.. > > But right now I reset, load REXMGR, reload the RAM image and it takes > seconds. > > Then I have to set the clock by either going into BASIC and setting the 3 > variables or attaching one of my external devices > and running a basic program to do it for me. > > Not hard mind you but when I do this same thing in VirtualT the time is > always right so maybe I'm spoiled. > > > Brian > > > > > On Oct 31, 2017 7:01 PM, "Peter Vollan" <[email protected]> wrote: > > Let me sure that I understand: however correctly you set the time on > your Model 100, it will "drift off", because it cannot keep correct > time? > > > On 26 October 2017 at 12:58, John R. Hogerhuis <[email protected]> wrote: > > > > > > On Thu, Oct 26, 2017 at 12:22 PM, Brian Brindle <[email protected]> > wrote: > >> > >> Hey John, > >> > >> To move RAM images around I"m using REX, creating a backup of the RAM > >> image and saving it to "disk" or in this case Mcomm or my NADS. I like > Mcomm > >> because the directory it saves everything in on the phone is > automatically > >> backed up (by another application) to dropbox right now. Then I load > that > >> image in VirtualT on the PC. > >> > > > > Ah. Well, I did write a program to sync time with NADSBox. > > > > http://bitchin100.com/wiki/index.php?title=Synchronize_Time_ > with_your_NADS > > > > -- John. > > >
