#Chess edit bin file install
#Chess edit bin file windows

Here we redirect the saving to another file (specific for the user) To make absolutely sure, you could look in the winboard.ini file in the WinBoard folder (where you can get through the 'WinBoard Files' menu entry of 4.5.2). You should look for a file, not a folder. But I will look into it.)Īre you sure you looked in the correct AppData folder? Each user has its own, and there also are AppData folders for 'Administrator' and 'Default User' (on my Win2k, at least).

#Chess edit bin file install

I don't install anything there directly it is just WinBoard that creates it there the first time you run it and save settings.

(Not sure how I could make it do that, however, because it has a different pathname for each user, and all users that will have used WinBoard will have their own winboard.ini there, which would all have to be deleted. Indeed, the un-install doesn't remove the winboard.ini file in the AppData folder. This won't help you to downgrade to an older version, though. just cause an error popup, warning the user, but further ignore it. Perhaps I should make the WinBoard beta less allergic to non-existing options. Then a virgin settings file with that new name will be created. If you cannot find it, an emergency recovery method woud be to edit the winboard.ini in your WinBoard folder, and replace the last two options /settingsFile and /saveSettingsFile to some other filename.

#Chess edit bin file windows

So be sure to let Windows also list hidden files/folders (Tools -> Folder-Options -> View -> Show Hidden Files and Folders in the Windows explorer). Problem, however, is that on some Windows versions this is a hidden folder. The winboard.ini file with the saved settings (containing the offending option) is in the AppData (sometimes called Application Data) folder in your private Documents and Settings (C:/Documents and Settings//Application Data in my Win2k system). The ini file is not overwritten during install (to prevent overwriting your saved settings from a previous version some people have longe engine lists in there, and don't want to lose them when they upgrade). You have to throw away the winboard.ini file made by the newer version, or remove the offending options from it (if you want to keep your other settings) with some text editor like NotePad. Indeed, WinBoard has this problem of not being easy to downgrade to a previous version that has fewer options. (Which can be run by multiple WinBoard instances in parallel, by just clicking the tourney file.) Note that it is not only the Load Engine dialog that is new it also has a Tournament Options dialog that you can use to run tournaments with more than two engines. Perhaps I will do the same in a future WinBoard beta. I agree that the need for this edit button is unclear In fact, in the corresponding XBoard beta, I already redesigned all these dialogs to be always editable, without Edit button, and gave them a 'Save Changes' button in stead, so you can save the changes without closing the dialog. Again, this is by design, and has nothing to do with it being a beta version. To save the edited results, you just have to press 'OK'. If you use the Edit Tags or Edit Comment menu item, it directly pops up the windows in editable mode, with the button grayed out.

If their display is read-only, (when they popped up spontaneously) the Edit button is active, and as soon as you press it, it gets grayed out, because you don't need to press it anymore. (Look, for instance, at the Comment or Tags dialogs the stable version has. I don't know why, but WinBoard has always done it that way. That the edit button is grayed out is because you are already in Edit mode. It will still be that way 10 years after we released it as stable version. This has nothing to do with it being a beta. The idea is that you tell WinBoard the name of the book you want to edit (in the Common Engine dialog), and then edit it. (And even if it did, there are two engines. With the 'Engine Menu' (I suppose you mean the 'Engine #1/2 Settings' dialogs), you communicate directly with the engine, WinBoard knows nothing about it. They might even have a format specific for the engine (e.g. What else did you expect? The Engine books are not accessible to it only the engine knows what they are and where to find them. Indeed, it edits the book in the Common Engine menus.