On Tue 26 Mar, Richard Torrens (RiscOS) wrote: > > In article <[EMAIL PROTECTED]>, > James Taylor <[EMAIL PROTECTED]> wrote: > > > > Then where's the problem? If it single tasks, any program running > > in a taskwindow on the same machine will not get control back > > until Blackhole stops single tasking. At this point you know that > > it has finished and is ready. > > Agreed. > > But some operations are on one computer, others on another. Unless > these take place in the correct sequence - there is a problem.
Perhaps what you need is two Perl programs talking to each other over the network. It looks fairly easy to do with the standard IO::Socket modules although I've not tried it myself. > Roscli is the command for !OscliD and WO_ is in WindOpen I'm not familiar with OscliD but if you're running it, I hope there's no possibility of anyone on the network being able to abuse it. At least if you wrote two Perl programs talking to each other over IP, you could build in a little security. They wouldn't even need to pass real star commands between them, just messages to indicate to each other that the next stage of the backup procedure should be triggered. > There's a funny in ShareFS about closing a file on a remote > computer. This messes up Perl's open statement, so you cannot > check it for success. Interesting, can you give more details? > Keystroke can do rather too much. I find it impossible to > remember half of what it can do! You're not the only one! In the end I decided it would be easier just to write my own program than try to learn how to use Keystroke. Those that make the effort to learn it say it's revolutionised their lives. I suppose it's no different to learning Perl or Emacs. :-) -- James Taylor <[EMAIL PROTECTED]> Based in Southam, Cheltenham, UK. PGP key available ID: 3FBE1BF9 Fingerprint: F19D803624ED6FE8 370045159F66FD02
