Tord Hoppe Posted August 13, 2019 Share Posted August 13, 2019 SP Pro PE v 2.654 Win 10 CM version 6.90 CM Stick 2.04 CM Serial is 2-nnnnnnn At end of installation, popup "Codemeter runtime: Unsupported operating system, major=6, version=2.2, sp=0.0, type=1". When closing the popup the installation says it´s completed but no .exe to start SB. I´ve rebooted computer after updating the CM firmware to 2.04 0 Quote Link to comment Share on other sites More sharing options...
Administrators Sean Posted August 13, 2019 Administrators Share Posted August 13, 2019 Try installing the newest codemeter runtime from the codemeter website, sb should work after that is installed. 0 Quote Link to comment Share on other sites More sharing options...
Gibsonm Posted August 13, 2019 Share Posted August 13, 2019 (edited) My guess is that Codemeter 6.90 is not supported under Win 10 (i.e. a Codemeter issue, not a SB / eSim issue). It just happens that when 2.654 was published back in 2012, that 6.90 was current for Win 7 or whatever. Perhaps download the latest Codemeter version for Win 10 and see how you go. Edited August 13, 2019 by Gibsonm 0 Quote Link to comment Share on other sites More sharing options...
Rotareneg Posted August 13, 2019 Share Posted August 13, 2019 (edited) That is indeed the problem you're seeing. I put 2.654 on my Win10 laptop recently when 4.1 wouldn't run You just need to skip the built-in codemeter install and download the newest one from Wibu. SB 2.654 itself works just fine on Windows 10. Edited August 13, 2019 by Rotareneg 0 Quote Link to comment Share on other sites More sharing options...
Tord Hoppe Posted August 14, 2019 Author Share Posted August 14, 2019 (edited) 6.90 is a fresh install yesterday from the CM website. When you say to skip the built-in CM install, I don't see that option anywhere. Just to be clear, I also think this is only caused by the CM stuff, not SB itself. 😀 Edit: 6.90 is from 30 july 2019. Edited August 14, 2019 by Tord Hoppe 0 Quote Link to comment Share on other sites More sharing options...
Members Ssnake Posted August 14, 2019 Members Share Posted August 14, 2019 Could well be that we separated the CodeMeter runtime installation from the Steel Beasts installation only with version 3.0. It's been seven, eight years. Memory is becoming fuzzy. I mean, this is one of the reasons that we release new versions of SB Pro. Sure, new features, better looks. But arguably it's even more so about adapting to the ever changing Windows environment. In 2011 "Windows 7" was but a rumor, and now it's discontinued already. 0 Quote Link to comment Share on other sites More sharing options...
Tord Hoppe Posted August 14, 2019 Author Share Posted August 14, 2019 Most likely Tried again and indeed the CM install happens during the overall install process, and that is when the popup comes. No selection to skip that part when trying the custom installation. 0 Quote Link to comment Share on other sites More sharing options...
Tord Hoppe Posted August 14, 2019 Author Share Posted August 14, 2019 Well, I think I solved it. Bought the upgrade to v4 0 Quote Link to comment Share on other sites More sharing options...
Furia Posted August 14, 2019 Share Posted August 14, 2019 WIse move. 😎 0 Quote Link to comment Share on other sites More sharing options...
Rotareneg Posted August 14, 2019 Share Posted August 14, 2019 I was misremembering, you can't skip it, but you can just ignore the error and then install the new Codemeter. But yeah, getting a newer version of SB is probably a better choice than running 2.6. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.