Pages: 1
RSS
Christmas Edition and THEBAT.IPC, can you still use THEBAT.IPC ?
 
one of the new features in the Christmas Edition is that TB no longer uses THEBAT.IPC on NT-based OS's, it remains only for 9.x

I'm using THEBAT.IPC from .vbs files and my own apps to automate TB, so my question is is it possible to configure the new version to use THEBAT.IPC ?

I'm not sure how to create a "named pipe" nor I want to change anything.
This should be possible, as the feature still exists.

thanks  
 
Unfortunately, thebat.ipc will no longer be available; but you should be easily be able to program named pipes under Visual Basic; there are several article in the internet about it: http://www.google.com/search?hl=en&q=named+pipe+visual+basic
 
Thanks for the reply Maxim.
But I'm quite unhappy to know this. It's probably not too difficult to deal with named pipes, but I'll have to learn, code and test new things, which indeed takes time - I'd prefer just not to do this.

Another thing is, with THEBAT.IPC it was very easy to detect when a command has been executed (or an attempt to execute finished) - one just had to detect that THEBAT.IPC no longer exists - not sure how to do this with pipes, although it's probably not too hard either.

It's really not a good idea to remove a feature that exists for years and the users utilize. It's OK to make it disabled by default, but why are you making it it completely unavailable? Especially when the feature actually still exists in the program.

Isn't it possible just to trick TheBat to think it's running on a 9.x OS ?
Or do something else to keep the old behavior?



 
To keep the old behaviour, you can run a second instance of thebat.exe and pass the required command-line parameters. This second thebat.exe will pass these paramerters to the first running thebat.exe via the named pipes.
Pages: 1