Re: REX is waiting for config files to be unlocked
  By: mark lewis to Nicholas Boel on Sat Mar 30 2013 05:21 pm

 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. 

 ML> that may not always work the way you want it to... m$ can still override
 ML> and force the update in along with the reboot... this is exactly what
 ML> happened to bob juge's large and very popular system... it corrupted the
 ML> VM that his fidonet stuff was running in, the backups were bad, and the
 ML> drives the original image(s) were made from were no longer available... it
 ML> was too much to loose and too much to try to recover so he ended up
 ML> leaving fidonet because of it... it was a huge blow to the network and
 ML> there was a lot of folks having to adjust their systems to connect
 ML> elsewhere for their traffic...

Eh.. I've always been able to set Windows to download updates, but never
install them until I tell it to. This problem may lie in the fact that noone
ever takes a LOOK at the updates before they install them. You DO have the
option to NOT install an update if you don't want to. Letting everything M$
puts through go by is a problem in itself. That's why I switched to Linux over
a decade ago, and only keep a small Windows partition for any gaming addiction
I may encounter. :)
 
As for the huge system you speak of, they basically lost interest, more or
less. If they were still interested, they would have come back up from scratch,
because that's what Sysops do. Simple rescans would have gotten them their
message bases back in order. I/You/We/All of us may back up our stuff daily,
but if the interest isn't there anymore, that's it.

Regards,
Nick

--- SBBSecho 2.20-Linux