I have a purchased copy of Crossover linux professional, and have been playing around with the opensolaris build on my desktop. So far it's working great and I am very pleased with it. When I try and register the software (which I have to launch from the terminal using 'pfexec /opt/cxoffice/bin/cxregister') the process looks like it's working- I'm able to get as far as validating my account but the registration stops at this point saying it's unable to validate my credentials.
I've checked and the user/pass I'm using is correct. Has anyone successfully registered this build? Is it possible?
I don't know for sure, but it wouldn't surprize me if an unsupported
build in also unregisterable...ie; if it could be registered, that it itself
would be offering support that unsupported builds don't qualify for...(?)..
something like that....if this post goes (officially) unanswered, you could
also ask this question via info@codeweavers.com and they'll let you
known for sure...
I also have a Solaris build that has expired. The cxregister program downloads the "unlockable bottle" and complains about my username and password before failing.
Can one of the CodeWeavers staffers enable my account for Solaris or otherwise provide a regular package? -- Based on some earlier forum postings, it looks like Andrew Bogget has this super power.
I'm running CrossOver 8.0 on OpenSolaris snv_134, which still works well enough for Internet Explorer 6 and WinRAR.
I just spent some time on this and it turns out that fixing demo registration in the 8.0 Solaris builds is pretty hard. Instead we've just replaced the time-limited builds with fully enabled builds -- a quick reinstall should get you there.
We hope to have 9.x builds for Solaris someday, but we still need to figure out what to do about the new Python and pygtk dependencies.
Ok.... using the 9.1 builds, it still fails in registration. I don't know if the 9.1 build is time limited or not, but it would be nice to get the Buy Now/Register/Register Later/Exit dialog to go away....
Thanks. The registration works and it doesn't come up with the nag screen. Though I wish one could at least log bugs against this (I know it's unsupported, but a problem is a problem). The most serious of which is file dialog seizes when you move up to the root directory.
hey look, I'm not really trying to "fix" something that isn't broken but what do you mean you can't support an "unsupported build"? You've been very responsive to my problems with an opensolaris build as well as, it appears, other peoples'. Crap, I wouldn't even bother to call Microsoft or, yikes, Oracle for my opensolaris problems and they offer "support."
How far can we push you guys? Your "unsupported" builds have better support than those other guys' "supported" stuff. My 10.0.0 build is working great now. What would we have to do to get support?
But unsupported means we feel no obligation to help in any way. We often go months without looking over here, and it may not have been visible here, but we messed up on 9.2 pretty badly.
As an example of what unsupported means - we didn't test this Solaris build at all. That is, we do Solaris for a large customer of ours, and we tested this stuff in that context and in their environment. But the 'consumer' version of CrossOver requires python and gtk, and our 'stock' Solaris test systems don't have working versions. So we shipped this without running it once. Apparently we got lucky, and it worked 😊.
To get real support, you'd either need to be a large customer of ours, or generate a huge groundswell of popular support. You can see in this thread:
CodeWeavers or its third-party tools process personal data (e.g. browsing data or IP addresses) and use cookies or other identifiers, which are necessary for its functioning and required to achieve the purposes illustrated in our Privacy Policy. You accept the use of cookies or other identifiers by clicking the Acknowledge button.
