Hello St - Musaic.Net, 14-Aug-2004 17:35, you wrote:
> My point is this: For no reason, TB may at any time simply stop > looking for thebat.IPC - and thus TB won't know of the _future_ > commands you "send" it (by the way of the command line). Have you investigated why this is happening? SysInternals FileMon may be of help. Maybe your on-access virus scanner blocks the file, something like that? > (In fact, you don't even have to use _command_line_ method - you > may simply create the file (thebat.IPC) manually - just make sure > the syntax is correct and "here we go".) AFAIK you're running TB permanently (and at very short poll intervalls). An environment that, as you said some weeks ago, requires you to restart TB now and then. You could do that with a scheduled /EXIT when you're in doubt if the .IPC file is still interpreted, couldn't you? -- Best regards, Alexander There is no reason anyone would want a computer in their home. -- Ken Olson, president, chairman and founder of Digital Equipment Corp., 1977 ________________________________________________ Current version is 2.12.00 | 'Using TBUDL' information: http://www.silverstones.com/thebat/TBUDLInfo.html
