https://bugs.winehq.org/show_bug.cgi?id=56512
Bug ID: 56512 Summary: Chessbase 17 does not recognise valid key on install Product: Wine Version: 9.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: dav75uk@yahoo.co.uk Distribution: ---
On running the setup program for the installer you are prompted (after agreeing to the terms) to enter the installation key which is 5 blocks of 5 alphanumeric characters followed by a block indicating the product (here CB17). On wine 9.5 this complains the key is invalid and there is no output in the console. The key is valid as it can be installed on a Windows machine so something in the validation must be broken.
Note the original workaround for Chessbase 11 which allowed things to work without the key able to be activated is not applicable here since the key is on the installer, thus you'll need the key validated to even install the program.
There is a potentially a workaround (see Chessbase 15 appdb entry - effectively copy it installed from a Windows machine) which I'll try out.
https://bugs.winehq.org/show_bug.cgi?id=56512
--- Comment #1 from David dav75uk@yahoo.co.uk --- Added to Chessbase 15 appdb entry as likely the same issue.
https://bugs.winehq.org/show_bug.cgi?id=56512
--- Comment #2 from David dav75uk@yahoo.co.uk --- Had to install winetricks vcrun2017 similar to the workaround. Also found mfplat.dll in system32 was not being found despite existing. Copied from a windows 10 machine and now it's happy.
https://bugs.winehq.org/show_bug.cgi?id=56512
Bartosz gang65@poczta.onet.pl changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |gang65@poczta.onet.pl
--- Comment #3 from Bartosz gang65@poczta.onet.pl --- What kind of library solve the problem? What kind of issue is resolved by winetricks vcrun2017?
https://bugs.winehq.org/show_bug.cgi?id=56512
--- Comment #4 from David dav75uk@yahoo.co.uk --- This was because on running the installed application couldn't find mfc140.dll which vcrun2017 solved, although as mentioned there were issues with mfplat.dll (version in system32 didn't work [wouldn't load] had to use native windows version).
This was more a comment on the workaround for the install as described on the Chessbase 15 appdb page when tried with Chessbase 17. The reason for raising this bug was the installer doesn't accept a valid key so you wouldn't even get to the point of running the application.
https://bugs.winehq.org/show_bug.cgi?id=56512
--- Comment #5 from David dav75uk@yahoo.co.uk --- You can't activate in-program after the workaround as it doesn't have a valid serial number.
You can see this if you run ChessBaseAdminTool.exe which is distributed free with CBReader2017 (also free to download)
On running the tool I see the following for the serial number (including that for the CBReaders): 345#$a which I'm guessing is some 'null' valid.
For ChessBase 11 I see a valid number.
This might be because how it was installed, or a wine bug - hard to say.
Would it be possible to compare the installation of CBReader2017 on Windows and Linux+wine and see if there is a valid serial on the windows version vs the wine version. If so that should point at where to look and whether there is a fix.
The danger of fixing this of course is it still may fail to activate but patch the security which allows CBase17 to continue to run despite failing activation meaning the program is either hobbled or it fails / quits early.
https://bugs.winehq.org/show_bug.cgi?id=56512
--- Comment #6 from David dav75uk@yahoo.co.uk --- I've just retried install from scratch and it's working!
Couple of things that I did:
I had to use winecfg to set the wine version, I had to set it to windows 10. It was currently not popping up this was a problem (I saw it on reboot) and was just exiting silently.
The issue on this ticket might have been fixed by appending an extra character to the end of the key. The key for these products is a fixed string depending on which product it is. In this case CB17. First time it didn't work, second time I added a space at the end and it did. I don't remember having to do this on the windows install, so might be a bug somewhere. I may try unregister, delete and try again to see if this is indeed needed.
I also noticed the serial number was now there on the admin tool and it said registered. The in-app key check (first time you run it - probably to try to stop install and copy) worked as well now the serial number was valid.
This can be closed though. I'll try again soon to see if the key entry is a difference wine vs windows, and I'll mention it on the application page. I'll also update the review as soon as we get to the stable version - it might be deserving of silver now.
https://bugs.winehq.org/show_bug.cgi?id=56512
David dav75uk@yahoo.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME
--- Comment #7 from David dav75uk@yahoo.co.uk --- Install from scratch was successful.
https://bugs.winehq.org/show_bug.cgi?id=56512
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #8 from Austin English austinenglish@gmail.com --- Closing.
-
WineHQ Bugzilla