Jump to content
  • Announcements

    • Battlefront.com

      Special Upgrade 4 Tech Tips   12/27/2016

      Hi all! Now that Upgrade 4 is out and about in large quantities we have now discovered a few SNAFUs that happen out in the scary, real world that is home computing.  Fortunately the rate of problems is extremely small and so far most are easily worked around.  We've identified a few issues that have similar causes which we have clear instructions for work arounds here they are: 1.  CMRT Windows customers need to re-license their original key.  This is a result of improvements to the licensing system which CMBN, CMBS, and CMFB are already using.  To do this launch CMRT with the Upgrade and the first time enter your Engine 4 key.  Exit and then use the "Activate New Products" shortcut in your CMRT folder, then enter your Engine 3 license key.  That should do the trick. 2.  CMRT and CMBN MacOS customers have a similar situation as #2, however the "Activate New Products" is inside the Documents folder in their respective CM folders.  For CMBN you have to go through the process described above for each of your license keys.  There is no special order to follow. 3.  For CMBS and CMFB customers, you need to use the Activate New Products shortcut and enter your Upgrade 4 key.  If you launch the game and see a screen that says "LICENSE FAILURE: Base Game 4.0 is required." that is an indication you haven't yet gone through that procedure.  Provided you had a properly functioning copy before installing the Upgrade, that should be all you need to do.  If in the future you have to install from scratch on a new system you'll need to do the same procedure for both your original license key and your Upgrade 4.0 key. 4.  There's always a weird one and here it is.  A few Windows users are not getting "Activate New Products" shortcuts created during installation.  Apparently anti-virus software is preventing the installer from doing its job.  This might not be a problem right now, but it will prove to be an issue at some point in the future.  The solution is to create your own shortcut using the following steps: Disable your anti-virus software before you do anything. Go to your Desktop, right click on the Desktop itself, select NEW->SHORTCUT, use BROWSE to locate the CM EXE that you are trying to fix. The location is then written out. After it type in a single space and then paste this:

      -showui

      Click NEXT and give your new Shortcut a name (doesn't matter what). Confirm that and you're done. Double click on the new Shortcut and you should be prompted to license whatever it is you need to license. At this time we have not identified any issues that have not been worked around.  Let's hope it stays that way Steve
    • Battlefront.com

      Forum Reorganization   10/12/2017

      We've reorganized our Combat Mission Forums to reflect the fact that most of you are now running Engine 4 and that means you're all using the same basic code.  Because of that, there's no good reason to have the discussion about Combat Mission spread out over 5 separate sets of Forums.  There is now one General Discussion area with Tech Support and Scenario/Mod Tips sub forums.  The Family specific Tech Support Forums have been moved to a new CM2 Archives area and frozen in place. You might also notice we dropped the "x" from distinguishing between the first generation of CM games and the second.  The "x" was reluctantly adopted back in 2005 or so because at the time we had the original three CM games on European store shelves entitled CM1, CM2, and CM3 (CMBO, CMBB, and CMAK).  We didn't want to cause confusion so we added the "x".  Time has moved on and we have to, so the "x" is now gone from our public vocabulary as it has been from our private vocabulary for quite a while already.  Side note, Charles *NEVER* used the "x" so now we're all speaking the same language as him.  Which is important since he is the one programming them
kevinkin

Chip Flaws: in case you missed this

Recommended Posts

Oh yeah loads of fun there. This article has a nice little tid bit: https://www.theregister.co.uk/2018/01/02/intel_cpu_design_flaw/

"The fix is to separate the kernel's memory completely from user processes using what's called Kernel Page Table Isolation, or KPTI. At one point, Forcefully Unmap Complete Kernel With Interrupt Trampolines, aka ****WIT, was mulled by the Linux kernel team, giving you an idea of how annoying this has been for the developers."

LOL

Share this post


Link to post
Share on other sites

Got the Window 10 update last night that I presume contains the "fix" for this. Then I got my first ever BSOD on this machine a few hours later. 

Share this post


Link to post
Share on other sites

Pre and post patched Win 10 CM benchmarks need to be completed. The gaming industry is posting results for their products. Albeit players mostly. 

Maybe this will go away for our narrow purposes and we will see no performance hits. This is a rather big event never-the-less. Heads up. 

Kevin

Share this post


Link to post
Share on other sites
5 hours ago, Vanir Ausf B said:

Got the Window 10 update last night that I presume contains the "fix" for this. Then I got my first ever BSOD on this machine a few hours later. 

hmm interesting as I am noticing some less than stellar behavior in certain instances as well.  So far none affecting CM though.

Share this post


Link to post
Share on other sites
Posted (edited)

Surprised the malicious code can be written in JS and it's short. Two articles for those interested in going under the hood: 

https://www.react-etc.net/entry/exploiting-speculative-execution-meltdown-spectre-via-javascript

https://react-etc.net/page/meltdown-spectre-javascript-exploit-example

I am a hobbyist programmer. I thought that since JS can only run in a browser environment, the browser would provide security against this type of malicious code  i.e. writing or reading directly from memory. I can see it with assembly or C. What makes JS so dangerous is the code can be pushed to the local computer by an unwitting web surfer. 

Kevin

Edited by kevinkin

Share this post


Link to post
Share on other sites
On ‎05‎/‎01‎/‎2018 at 8:16 PM, Vanir Ausf B said:

Got the Window 10 update last night that I presume contains the "fix" for this. Then I got my first ever BSOD on this machine a few hours later.

You clearly crashed the NSA's warez.....Watch your back dude!  :ph34r:

Share this post


Link to post
Share on other sites

Funny you mention the NSA. There was some speculation originally that the Meltdown and Spectre vulnerabilities were identified by the Agency and entered the public domain via the leaks last Spring. 

Kevin

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×