Computer Chess Club Archives


Search

Terms

Messages

Subject: Re: What about the GUI for XTiger?

Author: Christophe Theron

Date: 10:17:55 06/17/03

Go up one level in this thread


On June 17, 2003 at 03:02:47, Russell Reagan wrote:

>On June 17, 2003 at 02:09:14, Christophe Theron wrote:
>
>>>I wonder how hard it would be to make a "TUI to XBoard" adapter. Probably could
>>>do it in a shell script without too much trouble.
>>
>>
>>I don't know exactly. But it's not really a priority for me.
>
>I was thinking it might be a good project for one of us computer chess nerds.
>I've often thought it would be interesting to create of meta-protocol and a GUI
>that supported the meta-protocol. Let's say the meta-protocol's command for a
>new game was "newgame", and the xboard command is "new", and the Chess Tiger TUI
>command is "reset" (just an example). We could have a config file (configurable
>through a GUI or text editor) and do something like: newgame=reset, and then the
>meta-protocol GUI would support Chess Tiger. The GUI could support engines that
>don't support any protocol, as well as xboard and UCI, and whatever other text
>pipe protocols were created in the future.
>
>
>>I'm using a terrific product called Win4Lin.
>
>Ah yes, I know of the product. Didn't think of it.
>
>
>>99% of the Windows applications work without any problem. Virtually anything
>>works. The only exceptions are applications that access some specific hardware
>>and DOS applications trying to access to the VGA mode (so Rebel does not work).
>
>When you say "specific hardware", does that include things like MMX? For
>instance, could you run Fritz MMX, or only Fritz?



MMX is not a problem.

The problem would be for example a program that needs to access a specific
hardware extension like a video capture card. Win4Lin does not offer support for
drivers for specific hardware, and you cannot install the driver provided with
the specific hardware because the Windows you install under Linux cannot have
direct access to the hardware.

To avoid this problem Win4Lin provides Windows drivers for all the standard
hardware (video, keyboard, printer and so on). So the copy of Windows you are
running can coexist with Linux because all calls from Windows to the hardware
drivers are translated into Linux calls.

But the small weakness of this method is that you cannot install real Windows
drivers under Win4Lin.

So if you need support for a specific hardware extension you still have to dual
boot. Fortunately 99% of the Windows application do not need to have access to
any specific hardware.



    Christophe



This page took 0 seconds to execute

Last modified: Thu, 15 Apr 21 08:11:13 -0700

Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.