Shredder Classic 4

[IWB]

In general I agree with the sandardisation of pathes but sometimes you just want to remotly try a computer from a friend ...
How practical are your proposals of adapters calling other adapters ...
Worst case: Engine -> Inbetween -> Polyglott -> WB2UCI -> GUI and back

Sorry but that is too much hassle for a CB related problem

Thanks anyhow
Ingo

Indeed, if the GUI has common settings for all engines (e.g. tablebase paths) it would be problematic if these had to be different on the remote machine. (OTOH, standardization is a good thing, so why would you want pathnames to be different on another machine?) For options that would just pertain to a single engine the only problem would be that you cannot use the GUI's browse buttons to set them. (But typing them in the GUI dialogs still seems much preferable over meddling with ini files...)

OTOH, the InBetween adapter already can do arbitrary substitutions in commands, configured by an ini file. So people that really want to have non-standard organization of their files can use InBetween to translate the pathnames on one machine to the pathnames on the remote machine. Doing that in a separate program keeps the communication function pure.

If the engine is UCI you could also use Polyglot on the remote machine (which would have its own ini file on the remote machine). And then install it as a WB engine, so that the network communication is through the compact WB protocol rather than ultra-verbose UCI. When you use a 64-bit WB2UCI.exe, would CB not automatically recognize the engine as 64 bit?

[hgm]

Well, you know the first law of computer Chess: "When you use a crappy GUI you have to deal with crap!".

But fortunately it is not quite as bad as the chain you propose above, as Polyglot and WB2UCI already support their own config files. So I mentioned them as an alternative to InBetween, not to be used together with it. So you could have

engine - Polyglot - connect (server) <----> connect (client) - WB2UCI - GUI

or

engine - InBetween - connect (server) <----> connect (client) - GUI

The latter is slightly simpler, but not necessarily faster, as you have to send much more over the network connection, which is probably a lot slower than pipes between programs on the same machine. The Connect server would just have to specify inbetween.exe instead of the engine.exe, and InBetween would find the engine commands and all settings specific to the remote machine in its ini file. (But you wanted that info to be in an ini file somewhere anyway, and it doesn't matter much if connect.exe would be using that ini file, or InBetween would do that.)

The first solution has the advantage that the GUI cannot look beyond WB2UCI, hiding the 32-bit stuff from view. WB2UCI can be configured not to transfer the value of settings that are not common to both machines (e.g. the egtpath command), so that Polyglot would use the 'default' for it that was specified in its ini file.

[IWB]

The easiest one would be a 64 bit "connect2" software as i am having identical pathes!
My proposal was just for the occasional user (as this thread started) and as a substitution for the once easy to use RS232 Autoplayer. I doubt that the occasional user wants to do what you propose. (Maybe I'll try it sometimes but I need to have a lot of time left then )

Ingo

Well, you know the first law of computer Chess: "When you use a crappy GUI you have to deal with crap!".

But fortunately it is not quite as bad as the chain you propose above, as Polyglot and WB2UCI already support their own config files. So I mentioned them as an alternative to InBetween, not to be used together with it. So you could have

engine - Polyglot - connect (server) <----> connect (client) - WB2UCI - GUI

or

engine - InBetween - connect (server) <----> connect (client) - GUI

The latter is slightly simpler, but not necessarily faster, as you have to send much more over the network connection, which is probably a lot slower than pipes between programs on the same machine. The Connect server would just have to specify inbetween.exe instead of the engine.exe, and InBetween would find the engine commands and all settings specific to the remote machine in its ini file. (But you wanted that info to be in an ini file somewhere anyway, and it doesn't matter much if connect.exe would be using that ini file, or InBetween would do that.)

The first solution has the advantage that the GUI cannot look beyond WB2UCI, hiding the 32-bit stuff from view. WB2UCI can be configured not to transfer the value of settings that are not common to both machines (e.g. the egtpath command), so that Polyglot would use the 'default' for it that was specified in its ini file.

[hgm]

The easiest one would be a 64 bit "connect2" software as i am having identical pathes!

Yes, I understand that, but I would first have to install a 64-bit compiler on a computer where this does not interfere with my usual stuff, or it would already have been on my website. You know how it is: "The impossible we do right away, but miracles take somewhat longer".

People that, for whatever reason, cannot use the same paths on both machines cannot avoid to do some extra work to solve the problems this raises. And we already agreed that a config file would be a possible solution for that. There doesn't seem to be much backlash from making that an inbetween.ini file.

[hgm]

OK, I think I managed to create a 64-bit version:

http://hgm.nubati.net/connect64.exe

It does allow the rename trick for hiding the arguments as part of the filename.

[Nordlandia]

I can't try that .exe file because my internet connection is wired by cable /=

???

What's that got to do with it?

What i mean is how can i communicate between two computers, in case internet connection is wired and only connected to one computer (RJ45 Ethernet Cable)

[hgm]

You mean that one of the computers is not connected to the internet in any way? Then it can of course not communicate over it...

[Nordlandia]

You mean that one of the computers is not connected to the internet in any way? Then it can of course not communicate over it...

Yes, i currently have wired connection.

How about two laptops in LAN mode or is internet connection required for both

[IWB]

That works perfectly! Thanks a lot!!!


So at least the Fritz 14 GUI has a limit of 3072MB if it detects a 32 bit "engine".

Now I run into the "problem" that the DF14 GUI has a limit at 11156MB of Hash for 64 bit Enignes (as my computer "only" has 16 GB of memory, the remote computer has 32GB) - but that has nothing to do with you

(But a wrapper with fixed settings for an engine could overcome that obstacle )

Thanks again, that is helping a lot!
Ingo

OK, I think I managed to create a 64-bit version:

http://hgm.nubati.net/connect64.exe

It does allow the rename trick for hiding the arguments as part of the filename.

[hgm]

Yes, i currently have wired connection.

How about two laptops in LAN mode or is internet connection required for both

You lost me completely. Are both computers connected, (whether wired or wireless), yes or no? It cannot be both connected and not connected to the internet, as you claim.