{"id":122,"date":"2006-08-21T20:46:20","date_gmt":"2006-08-22T00:46:20","guid":{"rendered":"http:\/\/unitstep.net\/blog\/2006\/08\/21\/getting-matlab-to-run-on-a-newer-athlon-64-x2-cpu\/"},"modified":"2006-08-24T23:43:08","modified_gmt":"2006-08-25T03:43:08","slug":"getting-matlab-to-run-on-a-newer-athlon-64-x2-cpu","status":"publish","type":"post","link":"https:\/\/unitstep.net\/blog\/2006\/08\/21\/getting-matlab-to-run-on-a-newer-athlon-64-x2-cpu\/","title":{"rendered":"Getting Matlab to run on a newer Athlon 64 (X2) CPU"},"content":{"rendered":"

I recently installed Matlab v7.0 (R14) on my new computer<\/a> and ran into some troubles. After starting Matlab, the program window would open as normal, but then it would shutdown almost immediately, usually after about a second or so delay, allowing me to tantalizingly see that it almost working. I did a search and found this helpful article<\/a> on how to fix the problem.<\/p>\n

The issue (Matlab closing right after start-up) stems from Matlab (at least this version, the newer versions might not be affected) not “recognizing” the processor string for newer AMD Athlon 64-based processors; in my case, I had an Athlon 64 X2 3800+. Matlab relies on different Basic Linear Algebra Subprograms (or BLAS<\/abbr>) routines for different types of CPUs, and these are stored in different DLL<\/abbr> files.<\/p>\n

The BLAS<\/abbr> file responsible for telling Matlab which DLL<\/abbr> file to use for what type of CPU is located at: <\/p>\n

%MATLAB7%\\bin\\win32\\blas.spec<\/code>
\n(where %MATLAB7%<\/code> is the path to your Matlab installation)<\/span><\/p>\n

To fix the problem, open up the file in a text-editor, and add the following two lines to the bottom:<\/p>\n

\r\nAuthenticAMD Family 15 Model 12 atlas_Athlon.dll # Athlon 64 (Newcastle)\r\nAuthenticAMD Family 15 Model * atlas_Athlon.dll # AMD64<\/code><\/pre>\n
This will tell Matlab to use the proper<\/strong> DLL<\/abbr> file with your newer AMD-64-based CPU, instead of apparently defaulting to using a Pentium DLL<\/abbr> file when an unrecognized CPU is detected.
\n<\/p>\n
More on the problem<\/h3>\n
As mentioned, the problem stems from the CPU being unrecognized by Matlab’s configuration file.  All CPUs have some sort of identifier string, and Matlab uses this to determine what DLL<\/abbr> file to use.  When an unrecognized CPU string is detected, it apparently defaults to using a Pentium DLL<\/abbr> file; this results in Matlab crashing when it’s run on an AMD-64-based CPU, and results in the crash-on-start behaviour.<\/p>\n
Why the different DLL<\/abbr> files for different CPUs? My guess is that the BLAS<\/abbr>, upon which Matlab is based, are optimized or made to work better with select CPUs.  It should be noted that these problems may not be experienced if you’re running a more current version of Matlab.<\/p>\n
I did a little more searching and found this forum thread<\/a> over at the Matlab website, where a different fix for the same problem is presented.  It involves setting a Windows environment variable instead of editing the blas.spec<\/code> file, but should do the same thing; I haven’t tried it.  This other forum thread<\/a> also details a similar procedure. <\/p>\n
Hope this helps in fixing any Matlab ailments you might have had, because running into a problem like this can be frustrating as heck when you need to have an assignment done for tomorrow!<\/p>\n
Update<\/h3>\n
I’d just like to say that a dual-core setup totally rocks<\/em>.  It’s awesome to be able to still play CS:S<\/abbr> while running a Matlab simulation.<\/p>","protected":false},"excerpt":{"rendered":"
I recently installed Matlab v7.0 (R14) on my new computer and ran into some troubles. After starting Matlab, the program window would open as normal, but then it would shutdown almost immediately, usually after about a second or so delay, allowing me to tantalizingly see that it almost working. I did a search and found […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[79,86],"tags":[],"_links":{"self":[{"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/posts\/122"}],"collection":[{"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/comments?post=122"}],"version-history":[{"count":0,"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/posts\/122\/revisions"}],"wp:attachment":[{"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/media?parent=122"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/categories?post=122"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/tags?post=122"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}