This is just a little diagnostic to help me if there are any issues with the auto-restart. I’ll probably remove it at the next release.

?

It’s of no concern, and is expected when not in an auto-restart situation. There is no way to suppress the messages.

?

I have absolutely no idea why it should appear on the console when nothing else does. It might be worth giving me the full logfile so I can get a fuller picture.

?

And as I keep saying over and over again (if anyone else is reading this), please send the whole log file with your queries – don’t extract bits of it because experience shows that extracts nearly always don’t contain the information I need.

?

Richard

?

?

Well, that didn’t throw any light on it. I really can’t see why just those three lines should appear on the console.

?

I presume by ‘console’ you mean the banner window? And when you say ‘no others show’, ?presumably you mean the usual stuff shows, like this:

?

+==============================================================================

+

+ IBC version 3.16.0-beta.1

+

+ Running TWS 1020 at 21/12/2022 18:20:00.76

+

+ Diagnostic information is logged in:

+

+ C:\IBC-Paper\.\Logs\IBC-3.16.0-beta.1_TWS-1020_WEDNESDAY.txt

+

+

+ ** Caution: closing this window will close TWS 1020 **

+

?

But you get these three extra lines at the end?

?

If you mean something else, please send a screenshot if you can capture one.

?

The only other thing that might be of interest is the value of the LOG_PATH setting in StartTWS.bat.

?

Ah, this is becoming clearer now. I misunderstood what you wrote initially: I took it to mean that all these lines are appearing on the console:

?

Finding autorestart file

INFO: Could not find files for the given pattern(s).

autorestart file not found

?

but actually you just mean the middle line – re-reading it now I see you stated quite clearly what you meant, so apologies that I misunderstood.

?

The reason for the difference is that the first and last of these lines are simply the result of echo statements, whereas the middle one is an error message produced by the ‘where’ command when trying to locate the autorestart file: presumably it’s written to the STDERR stream.

?

Now my DisplayBannerAndLaunch.bat script redirects STDERR to STDOUT, and STDOUT is redirected to the logfile. But if ib_insync doesn’t use DisplayBannerAndLaunch.bat, and just calls the low-level StartIBC.bat directly, then perhaps STDERR is not being redirected in this way, so it ends up elsewhere.

?

So I guess this is not really a question for me: you’ll need to check what ib_insync does.

?

On the other hand, I may be able to discard this error message altogether since it doesn’t really add anything of value, but initial attempts at this have failed (normally one would redirect STDERR for the command to NUL with 2>NUL, but this doesn’t work because the ‘where’ command is within nested FOR ?statements, and it gives a syntax error. But I’ll fiddle a bit more to see if I can bend it to my will. At the end of the day, though, does this actually really matter at all?

?

Richard

?

?