There seems to no incoming or outgoing mail.
There seems to no incoming or outgoing mail.
Well, I guess there is after all....
There seems to no incoming or outgoing mail.
Well, I guess there is after all....
Indeed there is <G>
Yeah, but I still got that cycle and the message... It may be working, but what's causing the cycle and the message?
Re: REX is waiting for config files to be unlocked
By: Bill Gordon to Joe Delahaye on Thu Dec 20 2012 14:05:16
Yeah, but I still got that cycle and the message... It may be working,
but what's causing the cycle and the message?
If you exit from the rex config utility the wrong way, it will leave
a busy semaphore, thus preventing Rex from starting up, or
continuing. Remove that semaphone, and all will work once more. I
have my Rex startup batch file check for that and if it exists, it
will remove it.
If you exit from the rex config utility the wrong way, it will leave a busy semaphore, thus preventing Rex from starting up, or continuing. Remove that semaphone, and all will work once more. I have my Rex startup batch file che for that and if it exists, it will remove it.
Nope, nothing there that is not supposed to be. Not a ".0" file anywhere. And still I have the thing saying "REX is waiting for config files to be unlocked", but it IS working.
Any more ideas?
If you exit from the rex config utility the wrong way, it will leave a
busy semaphore, thus preventing Rex from starting up, or continuing.
Remove that semaphone, and all will work once more. I have my Rex
startup batch file che for that and if it exists, it will remove it.
Nope, nothing there that is not supposed to be. Not a ".0" file
anywhere. And still I have the thing saying "REX is waiting for
config files to be unlocked", but it IS working.
Any more ideas?
Any more ideas?
You have checked all the subfolders/directories withing Irex? Have
the correct paths inserted, etc? As Roy showed you, here is MY batch
file that I start Rex with on windows startup even
cd \irex
if exist c:\irex\sema\rex*.* del c:\irex\sema\rex*.*
rexw -daemon
If you want to load REX as a service, rather than a program in a window,
you can use this line to load it.
rexw -daemon -tray
When you load it this way, it will reside as a small icon in the tray next
to your system clock. You can mouse click on the icon to bring it up in a window of its own and when you're done with it, a click on the Window X
will put it back in the tray. i.e. you haven't exited IREX, you've just closed the window. Only Alt-X will (should) close REX...
If you want to load REX as a service, rather than a program in a
window, you can use this line to load it.
rexw -daemon -tray
When you load it this way, it will reside as a small icon in the tray
next to your system clock. You can mouse click on the icon to bring it
up in a window of its own and when you're done with it, a click on the
Window X will put it back in the tray. i.e. you haven't exited IREX,
you've just closed the window. Only Alt-X will (should) close REX...
Hey, thanks, that's a great bit of information. Appreciate it.
will put it back in the tray. i.e. you haven't exited IREX,
you've just closed the window. Only Alt-X will (should) close
REX...
Hey, thanks, that's a great bit of information. Appreciate it.
For reasons unknown to us Bill Gordon said thus to Roy Witt:
will put it back in the tray. i.e. you haven't exited IREX,
you've just closed the window. Only Alt-X will (should) close
REX...
Hey, thanks, that's a great bit of information. Appreciate it.
Also, a good idea is, to create a backup of your irex directory when it is working. I do it here frequently to an external drive because sometimes wind will update and then reboot. If Irex happened to be running at that time.... get the same thing you're talking about. I just reboot, delete my existing I directory and copy over the backup and I'm back running again. :)
If Irex happened to be running at that time.... get the same
thing you're talking about. I just reboot, delete my existing I
directory and copy over the backup and I'm back running again.
:)
Hi Gaylen, long time no talk to <g> how you doing you old
codger? I have never had that problem with my irex, set it up
the first time i started using it and it's been running ever
since.
Yeah , some people have that luck but though it happens rarely, it does happen occasionally. Might just be cause I'm running two boards, Synchronet ( for DoveNet mail ) and of course I've switched all the way back to ProBoard for my regular board. Yeah, I like being retro I
guess. :) Like I said though, it only happens when I have an automatic performing some duty or other.
Yeah , some people have that luck but though it happens rarely, it
does happen occasionally. Might just be cause I'm running two
boards, Synchronet ( for DoveNet mail ) and of course I've
switched all the way back to ProBoard for my regular board. Yeah,
I like being retro I guess. :) Like I said though, it only
happens when I have an automatic performing some duty or other.
The only way you'll be able to fix that problem is to set Windows
to download the updates, but not apply them or reboot your machine
until you say so. That way you can safely download/install
updates, shut down Irex safely, and reboot.
The only way you'll be able to fix that problem is to set Windows
to download the updates, but not apply them or reboot your machine
until you say so. That way you can safely download/install
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...
The only way you'll be able to fix that problem is to set Windows
to download the updates, but not apply them or reboot your machine
until you say so. That way you can safely download/install
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...
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.
Doing fairly well but busy as heck. One more year till I can retire and believe me I'm looking forward to it. :)
the first time i started using it and it's been running ever
since.
Yeah , some people have that luck but though it happens rarely, it does happ occasionally. Might just be cause I'm running two boards, Synchronet ( for DoveNet mail ) and of course I've switched all the way back to ProBoard for m regular board. Yeah, I like being retro I guess. :) Like I said though, it only happens when I have an automatic Windows update and Irex is performing s duty or other. <sigh>
Take care and good hearing from you.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,042 |
Nodes: | 15 (0 / 15) |
Uptime: | 144:03:36 |
Calls: | 500,263 |
Calls today: | 1 |
Files: | 95,201 |
D/L today: |
104 files (65,589K bytes) |
Messages: | 464,618 |