Subj : REX is waiting for config files to be unlocked
To : Nicholas Boel
From : mark lewis
Date : Sat Mar 30 2013 05:21 pm
GH> Yeah , some people have that luck but though it happens rarely, it
GH> does happen occasionally. Might just be cause I'm running two
GH> boards, Synchronet ( for DoveNet mail ) and of course I've
GH> switched all the way back to ProBoard for my regular board. Yeah,
GH> I like being retro I guess. :) Like I said though, it only
GH> happens when I have an automatic performing some duty or other.
NB> The only way you'll be able to fix that problem is to set Windows
NB> to download the updates, but not apply them or reboot your machine
NB> until you say so. That way you can safely download/install
NB> updates, shut down Irex safely, and reboot.
that may not always work the way you want it to... m$ can still override and
force the update in along with the reboot... this is exactly what happened to
bob juge's large and very popular system... it corrupted the VM that his
fidonet stuff was running in, the backups were bad, and the drives the original
image(s) were made from were no longer available... it was too much to loose
and too much to try to recover so he ended up leaving fidonet because of it...
it was a huge blow to the network and there was a lot of folks having to adjust
their systems to connect elsewhere for their traffic...
